(10-28-2016, 05:11 PM)Jack_Henderson Wrote: I do NOT see why "/l1" , "/l2" for joining an ongoing engagement is a problem. That's where it is used for routinely, and where it causes zero harm.
Also, if you meet factions that you want to interact with "/l1, /l2, engage", these are situations in which you would very seldom get anything else. OC-IMG, Hessian-RM, Rogue-LN... run or fight. 90 % probability. Potential for "real" and meaningful roleplay: Minimal!
So, in reality the difference is, whether I get 2 readable, correct typing sentences pre-engagement... or 2 badly typed ones. Where das "engagibugn" come from? From bad typers hammering the phrase into local fast. I'd prefer a clean "/l1" "Powering up weapons, target lined up!" every single time.
Furthermore, you killed the "#t" and "#c" in /g1 like "Attack #t at #c", which was literally the only way to lead fights without TS. That's a massive (!) downside because these messages are paramount to direct those who do not have Teamspeak.
Anyway, a really unnecessary change that does not add anything (roleplay quality will not be influenced at all) and takes away the useful #t, #c.
Yeah! totally agree!! In my mining operation, i really need to use my "/setmsg 1 #t ship full" or "/setmsg 6 #t in queue for mining" due several ships around... and of course also the useful "/setmsg 9 Help! hostile #t engaging haulers at #c" because the mining operation may be in diferent sectors...
(in my personal situation, i also missing up so much "/setmsg 4 Helium miner #t is on duty! Contact #t for price! Sector #c") hehehehehehe. You know... for the new young miners.
I think the problem is not the command... it is just those players who dont leave enough time for response... (I dont understand why in rules removed "leave enough time for response")
Remember... there are too many tools for create hotkeys and drop messages... dont really need /setmsg for to use presets... only you will miss #t and #c variables... really helpful variables INTO roleplaying in several forms.