This has always bothered me, though I never got around to posting about it.

When you have a command like Say(msg as text|null), you can type into the command line exactly what you wish to say:

Say Hello world!

However, with a command like Kick(target as text|null, reason as text|null), you can't simply type the command with the name of the target like you would with Say, even if you have no reason message to send with the Kick. You have to type an open quotation before the target's name before it will accept the command parameter and execute the command. If you try typing the command like you would for Say, absolutely nothing happens:

Kick Xooxer

That's bad. Something should happen. Error message, proper usage info, something! In order to get the command to work at all, you have to start the target's name with a quote:

Kick "Xooxer

This is highly unintuitive for non-developers. Unless you know this special case, the command will appear to not function.

This open quote is not necessary, even if you have multiple parameters that can't be null. If the person neglects to add the proper set of quotes to seperate all the required parameters, the usage info should inform them of the mistake (or it used to, haven't tested).

If a person types in a command with multiple parameters, adds text directly after it without the quotes, DS should consider all the text following the command to be the input for the first parameter. The only time you should *have* to enter quotes is when you want to add more than one parameter to the command, and then you must use all but the last quote for it to work.

Requiring that the open quote be typed on any multi-parameter command, no matter how many parameters are required or are provided by the player, is not intuitive, logical or neccessary.

Please remove this restriction, and only neccessitate quotes when quotes are really neccessary.

~X