Quote:
|
Originally Posted by EvilMike
Preceeding it with an exclimation point would work best because that character is almost never used to start lines (unless the line is something like "!!!!!!!!!!!") and is commonly found in similar uses, such as in mIRC scripts. "!vote kick #" seems to be the best, and most simple possible format for such a feature.
|
Yes. An exclamation mark seems perfect to me. Just wanted to make sure it's the right character. Let me state how I plan to have the program read commands. A command initialization begins when a user starts the line with an exclamation mark:
Code:
(spaces/colors are ignored)!vote (parameters [optional parameters])
When a line starts with "!", the program will read the text that follows it (until a space is found or the text ends) and compare it with stored commands. If the text happens to match one of the commands, it will initialize the command and the program will continue to read the parameters (if any), passing them to the function. Then comes some error checking, but let us leave this part out for now. This way, the program will never accept a line such as "!!!!!!!!!!!!!!".
Quote:
|
Originally Posted by EvilMike
I would also assume the !vote command would have other applications, such as "!vote map x". Because of this, AkuKitsune's suggestion of having the command be "kick vote #" isn't really consistant at all.
|
Yes, it has a lot of parameters planned. Let's just say that everything that has been said in this thread is already planned (except for the !info thing). Here are some parameters that follow the !vote command: kick (#), kick (IP), ban (#), ban (IP), skip, next (level filename), open (level filename), etc.
But that is only the !vote command. There are other commands as well.
Quote:
|
Originally Posted by EvilMike
Have commands delivered through normal chat though. If for some reason a player tries to give a nonexistant command or makes a typo, don't make the program say "Invalid command" or something; the lack of a result would tell the player the command didn't work just as well as any error message could.
|
The thing is that if a player enters a non-existing command, no error will be displayed. However, if a player enters an existing command and makes a typo in the parameters, it will have to inform the player that he made a typo and by doing so, it'll also inform him that the command is active. Unlike where there'd be no response, he'd know that the admin has disabled that command.
Quote:
|
Originally Posted by EvilMike
I assume that this feature would be integrated into that program of yours nimrod was showing off last AB. If this is the case, perhaps add an "!info" command or something which returns the server settings, such as time limit, cheat protection, idle kicking, the next map (or whether map voting is enabled), server admins (if that feature is in) and whatever else can be set with that program. Since that would probably take multiple lines, limiting !info to being used every 30 seconds or so would be a good idea to prevent spam.
If this program supports server admins, obviously have commands for kicking and banning, as well as commands to restart the level, go to the next level, set the next level, and a few other basic things.
|
I am always looking for new ideas. I think there will be some sort of admining over jj2 chat. An !adminlogin (password) plus !adminlogout would do. I know you're probably thinking that this isn't a good way as everybody will be able to read the password, but hey
I already have a solution to that.