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!