Tweaking 'spamming lag'

[English lad]

Ok I know there are easy solutions to this, typing where, score etc...So please don't just bring those up and say, 'Its not a problem because its easy to avoid' If something is happening in a way that it wasn't intended its a problem, regardless of how easy it is to avoid.

Recently I've spent a while learning some zones a bit better, to the point where I rarely mispamm, and it gets very annoying to be moving through a zone, not having spammed any commands, other than A direction, and get the 'stop spamming message' And then just sit there frozen for awhile. If it happens in PK its a lot worse than annoying. I understand the principle is to stop people from just spamming certain commands, but seriously, if the mud has zones that, if spammed through correctly, cause a 'stop spamming message' to come up, then maybe we can tweak the amount of commands need to trigger it a little?

I have come across only a few occassions of this, but the big was is running west into Val Miran and out the other side, or going east of course the other way. This is a major route, and one that people will be getting chased down a lot, in situations where they really want to be putting in directions as fast as possible.

In short, can we have an extra 10 commands or so before the 'stop spamming message' kicks in.

Thanks

[Deykari]

I tested from running within the entrance of the tombs, heading straight eastwards, with no other inputted commands. I didn't get stopped for spamming. I have never been stopped for spamming for moving, and I have never heard of it either.

Pretty strange.

Dey

[The Forsaken]

If it's a problem for you, use "eeeeeeeeeeeeeeeee" "enter" Instead of "e" "enter" repeditavly.

[Pali]

I keep getting it while training onslaught/chop/bladerush/backpin/pinwheel with a blademaster. Annoying, but hardly difficult to get around.

[Nightmare_from_hell]

Mushclient has a setting where you can have the client automatically enter another command for you after so many identical commands are entered.

Ex: You enter: TRIP 20 times, after the 16th one you could have it enter the command: LOOK to stop you from spamming it.

In essence, this client will make sure that you are never stopped for spamming. (If you aren't checking your WHERE PK every 5 secs or so, you should be thankful you haven't gotten a knife to the back every time. )

[F-3000]

Another nice: "where-ticker" (timer). Or manual imput of "where" (I use kpd-zero for this purpose).