 |
slicertool Magician

Joined: 09 Oct 2003 Posts: 459 Location: USA
|
Posted: Wed Feb 22, 2006 9:52 pm
Advanced Spam-out Protection |
Being as you're starting from what is essentially scratch, could you add the ability for the spam-out protection to only allow X number of commands within a specified timeframe and anything else that goes above and beyond that will be cached and sent when the time-out reaches a 'safe' point again.
Example: Our mud only allows something around 5 commands per tick. If you send a command after you have reached that limit, the command you spat out is ignored and the mud responds with a 'Wait.' |
|
|
 |
Tech GURU

Joined: 18 Oct 2000 Posts: 2733 Location: Atlanta, USA
|
Posted: Thu Feb 23, 2006 4:50 pm |
This is something that can easily be handled by a trigger... but I guess it would be more convenient and faster to have built-in support for this.
|
|
_________________ Asati di tempari! |
|
|
 |
|
|