Admin Notice: Temporary removal of the Setmsg command

[Jack_Henderson]

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.

---

+ IMG| DISCORD: https://discord.gg/TWrGWjp
+ IMG| IS RECRUITING: Click to find out more!

[Char Aznable]

What Jack said.

---

#notmyfrankfurt

[Syf]

If you're having trouble with marking targets in group fights then maybe start using this;


Granted, I'm not sure does that only work for the one whom originally started the group or the entirety of its members.
Just some food for thought, really.

[evanz]

someone mentioned dont turn it all of just leave 1 active, use it for the greeting message, thats sounds the best idea

[Sombs]

Wouldn't a cooldown timer between /1 and /2 have been the more clever solution?

[Jack_Henderson]

If you're having trouble with marking targets in group fights then maybe start using this;


Granted, I'm not sure does that only work for the one whom originally started the group or the entirety of its members.
Just some food for thought, really.

Does not give you the #c tag (which gives the grid number and thus the location of the fight).
"/setmsg 1 Attack enemy target #t at locatio #c" or "Need help at #c, shot at by #t" is incredibly helpful.

[Syf]

Hmm.. a'ight. I never used it so I didn't know its function. Now I at least know why that's a problem for some in the heat of a fight.

---

Inferno wuz here.

[Tyria Regalia]

I don't have a dog in this fight, as I never use it. But I watched a smuggler dock on Manhattan today while the person guarding the area couldn't get words out to engage him before he docked. While I believe there shouldn't be a need for semi-automated commands, I certainly have seen evidence of their usefulness first hand.

[Kalhmera]

I don't have a dog in this fight, as I never use it. But I watched a smuggler dock on Manhattan today while the person guarding the area couldn't get words out to engage him before he docked. While I believe there shouldn't be a need for semi-automated commands, I certainly have seen evidence of their usefulness first hand.

[Vendetta]

Unless I'm on my Nomad, I type out my engagements. Gives me a bit more freedom than repeating the same stuff, but as a Nomad it's near impossible to type out standard messages in a relatively quick time. When you have to give an engagement notice and someone is already up in your face because you can't do so cloaked anymore, you're getting shot before you can finish your message. I've shot someone who had the same problem of not being able to type out their engagement fast enough. Set messages are useful in some cases but not every case.

---

Currently unable to consistently be present in the Community due to life constraints.

Youtube

------