I’ve run into this a couple of times myself now, and can’t think of a (technical) reason why this is, nor do I found anyone else talking about it so far:
For 99% of the commands that I saw, they need to be posted without the /
in front of them, the one exception being /me
(the alias of pose
)
On quite a lot of other chat-type sites, whispering someone is done with /w
and since I’m used to those, I usually start a whisper (especially when I want to type quickly) with /w some name => ....
only to see it is red, having me pause, think, remember, and fix the issue. It isn’t a big / long problem, and probably gets better with time, but it is still something that is bothering me a little at times, slowing down the RP at times, and possibly make things (a tiny bit) less accessible for newer members.
Now, the basic solution of making aliases for all commands to also include a slash-leading variant, would probably be quite a work, especially since any new alias or command would also need to include that.
Because of this, I would personally suggest a solution that would be more generic and at the same time (hopefully) easier to implement which is to, when the first character of an input is a /
(or a \
and maybe some other symbols like space?), to have the processor ignore that first character and continue processing the 2nd to Xnd characters like normal (and if it isn’t just process like it is now already).
The only other thing that you would have to do, is change the /me
alias of pose
(internally at least) to me
so it keeps working
Personally, I can’t find any other reason the slash would have to be kept in-use, as I doubt there are any slash-leading commands that have a different result than the non-slash variant, that would just be bad design IMO, but if I’m overlooking something, please do clue me in.