Quote:Why would you want that anyway?For example, if I need a shortcut that isn't listed. Or that is described in full command's help string. Or if I'm developing a plugin and absolutely must have numerous debug commands, but I don't want to mess up the /help list.
Permissions is not the point in my case. My point is the ability to make a command that will not be listed, yet which will be usable.
More than that, I might need the ability to have multiple help lines for a single command bind!
For example, I have Portals plugin. I need commands for swapping portal selection mode, for creating a portal entrance and for creating a portal exit. Now, in my mind, the ideal set of commands would be:
/portal mode
/portal enter (name)
/portal exit (name)
But I can't bind something to "/portal xxx", as far as I remember. Therefore I'm forced to either make "/pmode", "/penter" and "/pexit" commands OR make a "/portal" command and handle different cases through command split manually. First option works fine, but looks kinda ugly, the second one left me with no way to document it for /help properly (in your system). And is somewhat messy in terms of dealing with permissions, should I want to have different.
So, let's think about another way to handle it, so I could have both multiple discriptions and hidden commands.
Perhaps, it might be better if we'll work it around so I could even assign different functions to "/portal enter (name)" and "/portal exit (name)" automagically. And different permissions. We really might use some support for multi-word commands.