First off, command "spam," and command queuing, which is best covered under 5.A and 2.F
Stacking commands so that you shout something 30 times is considered spam.
Spam is like noise pollution on the MOO and is not allowed. Granted, our
keys do 'sometimes' get stuck, but repeat incidents are bogus.
5.A. Abusing by stacking commands
Stacking commands in the lines of disarm/flee/pickpocket etc, is not
allowed on the MOO. In reality you could only attempt these actions once
every few seconds. Players should not and will not be permitted to proceed
with this type of actions. Repetitive and unnecessary stacking causes lag,
and no one wants that.
These two can be combined and should read, instead that any form of command should not be repetitively used. As currently it is unclear and references specific commands and saying things. A proposed revision might read.
5.A. Abusing by stacking/spamming commands
Stacking or spamming of any commands are not allowed on the MOO. In reality you could only attempt these actions once every few seconds. Players should not and will not be permitted to proceed with actions repetitively. Repetitive and unnecessary stacking causes lag, and no one wants that.
As it has been explained to me on numerous occasions, unnecessary commands should be avoided. Even when flavorful.
Consequences of this, no more making it rain for strippers, and having massive piles of money on the floor. No more small pool gambling. No dropping mass amounts of similar items swiftly. No quickly ordering drinks and handing them out rapidly as a bartender. As these would all fall under the use of stacking or spamming similar commands rapidly.
Next rule that needs revision, under the clarifications I have received by staff on xhelp.
I have asked at times if I can use triggers or macros to reorganize or display information in an altered way without interacting with the client. Essentially to program some accessibility features that would enable me to say cut down on clutter so that my eye strain doesn't get worse as I'm playing. Or to aide with OOC memory issues. Things like using a clientside script to grab a crate destination and display in a task list on the side of my screen. Or to setup a timer that just notifies me of how long has passed since I did crates. However, I have been told that this sort of accessibility macro falls under being against the rules, without being told which rule, but for this instance I am assuming the rule it is against is 4.C. Which reads.
4.C. (Mis)use of triggers and macros
Client side triggers or macros are not permitted for any purpose of
automating character activities or to provide rapid responses to MOO
output. Client side triggers and macros may not be used to allow your
character to perform activities in your absence, wether you be AFK or just
off window. In-MOO support for both is available (type @macros) and can be
used to your benefit while you are present and actively playing the game.
Effective immediately, single action hotkeys (e.g. - that let you press a
letter on your keyboard and a whole 'east' or 'west' or 'north' or 'south',
etc is input and sent for you) are banned. This includes the mushclient
feature where the number pad lets you navigate around.
And should instead, be a blanket ban of and and all client side triggers, macros, alias' or scripts. Not merely ones which interact with the game itself, or perform activities automatically. As this seems to be more in line with the stated and assumed policy than just simply ones which perform actions. I'm not going to attempt to rewrite this one, but the rule as written is very clearly different from the policy as has been stated to me on a couple occasions by staff.
In my personal use I go to the @rules for explicit descriptions of what is and isn't allowed. I've read through them numerous times. And when something like these situations come up I get a little awkward. Because I am the sort of person who looks at rules and reads them explicitly and expressly as they are written. And when staff imply that I'm trying to violate rules that aren't there, or that I am stupid and not reading them correctly, I tend to nod, go along with policy, and slowly begin to distrust the rules as written as being completely accurate. So it may be a good idea, at least in my opinion, for senior staff to go through the @rules, and check and make sure that all of the rules are explicitly in line with policy as is being stated by staff.