Ok i need some way to deal with freakign aeon. Yes i sip quicksilver when it's stripped and all that good suttf. BUT when aeon dose hit this is what happens. I have ot turn the sytem off before the damn thing shoots a million and two comands and screws me over. Then cure it manually which by the time thats done its either back again or i am dead. So if anyone could it would be greately appriciated

what system are you using or what do you have for triggers?

I have a simple boolean (variable that I only switched between true or false) which is basically AeonGotMeDown. Most of my system's triggers check the status of this variable. If its true, none of my curing will fire, and will instead stack up (my system is set to store up to 10 possible afflictions for each curing balance, with additional priority slots for the especially nasty things that can fudge up said balances). If its false, then my curing triggers fire as normal.

Without the stacking, it should still be a relatively useful method, just have to watch for any afflictions you get while your system is paused for Aeon, but its still better than having to shut down your whole system like that. It'll just be a little tedious for you to go through and add that bit of code into every single trigger script that requires it.

I don't see the problem with switching off, curing manually, switching on and diagnosing. It really isn't that much slower, and saves having to learn how to code .

The quick and dirty way of dealing with Aeon is with the speedwalk. It's that thing that collects your input and sends it one bit at a time over a certain interval. The idea is simple enough: when Aeon hits you send the cure command for it, set the speedwalk delay to however long you want your system to stay gagged, and place a certain command on the speedwalk. You need the OnPluginSend callback, which should check for that certain command you placed on the speedwalk and clear the thing, resetting the delay to whatever it was originally, so this works best in a plugin.

What happens in this case is when Aeon hits, your cure leaves for the server, but any other commands that you or your system issue will be queued up on the speedwalk. The very first command on it will be that "special" one, and if you use OnPluginSend in the manner described above, all the queued commands will be cleared as soon as the "special" goes off. Then your system can resume to send commands as usual, as the speedwalk is only active while there's something in it. If you don't want to loose the queued commands then you can define some procedure for resending them, though a well designed system should be able to recover after a pause on its own without any trouble.

An alternative to using OnPluginSend is to just define a macro that you can tap and fire an alias to clear the speedwalk manually. Actually having an alias like that is a good idea in any case.