WCS Issue

[James420]

While replacing my WCS server commands, I've noticed something about the CustomCommands feature. Even if you don't include a * wild card at the very end. It'll still trigger if there is something after your custom command. This is a problem to me because I need a custom command for /stats and /stats <user>, so I need one to be exact, and one that accepts a wild card after the command. Is this just a bug, or is it suppose to handle it like that? If so, doesn't seem to make much sense.

[James420]

Nvm, I guess I'll have to have just one custom command for them both and have the bot tell the difference. Although, it still doesn't make much sense for you to have added the option of using a * wild card at the end if it's always forced anyways...

[sIrMoOn]

i believe the * option is for multiple commands with the same beginning.  like, set up a handler for /user* and the bot will see /username, /usernickname, /usericon, or any other command starting with /user.  if you leave off the asterisk, only typing /user will trigger the bot.  whether you use a * or not your bot always gets everything after the space; those are the parameters to the function.

/user - works
/user* - works
/user * - same as /user, so pointless (like you've found out)