Quote:
Originally Posted by DustyPorViva
I only imagine that this would be a pretty exhausting list. Right now I imagine they have a predefined few levels(what is it, 0-20?) of /listen. That means all they have to do for commands is a simple check: if (clientr.verbose > x) sendMsg();
However, if there is nearly an option for every command, that's a lot of work for the scripters AND players. Probably the most ideal case for players would be an option to load the options of the current listens and just work from there. Case remains for staff though -- that's a hell of a lot of options to keep track of.
Still a good idea, I'm sure.
|
I think Nullify was suggesting groupings, apposed to 'an option of nearly every command'. Some groups I've thought about could be:
Monster Spawning/Item Creation, or simply Creation - would only apply to some staff e.g. EM's, Dev's;
Damage Caused, like when you zap someone with lightning wall or your burn someone with your flaming sword also when it's done to you. Includes dmg caused from status effects e.g. you make x convulse and throw up);
Status Effects, when you poison/blind etc or receive it