quote:
Originally posted by CookieRevised
And that is the exact problem. A script should not be fixed to include all kinds of random things other people come up with to start their commands.
I believe the !command (wasn't that adviced at some point?) has become common just as the /command, that's why i asked to consider ignoring sentences starting with those (and by further reading i found the / can't be used in all cases) in message formatting scripts. We can't stop ppl making scripts with whatever fantasy command, but i think it would be wise to have standards for what is an acceptable command start and what isn't. Afterall you can't expect scripters to rule out every possible beginning...just the two common ones should do.
quote:
There should not be !commands, ^commands, $commands, commands ending with "!", etc. Commands should always start with "/", as Menthix said.
The scripts which use anything other than /commands without any proper need should be fixed, not the scripts which only interpret /commands.
I agree there should be one unified start of commands, but i do fear that will lead to problems too (what if two add-ons use the exact same command?)
Let's look at it from another way/other possible solution (wich i thought of first before the ignoring certain chars in scripts):
If ! is used to start a command, is it possible to ignore any formatting before that? I fear that will be a problem as a sentence can also end with an ! I have done some testing with formatcodes and /commands (put in format tag, type command), this results in the command not beeing executed aswell. Now if all commands would start with / can formatting be ignored if put infront of that (regardless wether or not this was put in manually as i did)? If that is possible we end with the problem what if all add-ons could use /commands and two add-ons want the exact same one?
Confusing huh, but that's how i came to ask what i asked inhere.
/ 
