quote:
Originally posted by Orgrim Doomhammer
well, it was because of Stuffplug's commands being blocked by scripts like Message Customizer (I think this is due to colour codes at the beginning of messages), so I'd like to stop it whenever the "!" is typed
In that case you should not stop scripts at all...
Instead, scripts should never block commands. This means that any script should always return the complete message back when they do not detect a command in it processed by themselfs. And that means either returning the complete unedited message, or not use the
return command at all.
If there are scripts, like Message Customizer, which always manipulate the message, then this again means it is a bug in those scripts, and should be fixed instead (to not manipulate the message if they are commands).
However.... There is also another way of dealing this and it would be a way easier way for everybody. Because there are extremely many scripts which use "!" commands also, they too will not function properly with scripts like Message Customizer. And it all comes down to reconizing commands.
And that is the exact reason why one should always use commands starting with "/" and not commands starting with "!", "^", or whatever other format (and I hope everybody who made/published a script using such commands reads this).
This, even includes, imho, StuffPlug. In short: the method of StuffPlug of using "!" commands will actually break many scripts. It is also not what the Plus! user is used too since proper commands start with "/". Thus using "!" commands is not only bad for all those scripts developpers, it is also not good for StuffPlug, since many people will have problems with it.
Hence: StuffPlug should use "/" commands too....
Otherwise, disable all scripts (manually) which will break command lines.
quote:
Originally posted by SpunkyLoveMuff
I think that may be being built into Message Customizer (It SHOULD already be IMO) or it can be added quite easily with an if statement
tbh, there is nothing to be fixed. "!"-commands are actually not commands, but just text. That is how Plus! deals with it and that should be the way any other script developper should deal with it.
So, Message Customizer is actually correct in not dealing them as commands.
One can not expect that all scripts are made compatible with all kinds of rogue plugins, addons, scripts, etc which do not follow the
standard.
The solution is extremely simple: follow the standard: commands start with "/", anything else are not considered commands.
/ 
