I wanted to run some ideas about how I'm going to implement automatic razing using eq/bal queues.
Let's assume I have all the triggers set up and correct. If I was just sending queued commands on balance trigger, I'd check if any of my razing variables are sent to on and if they were, I'd send my razing command. Otherwise, I'd send my regular command.
This is a little more complicated if I actually want to utilize serverside queueing, because I want to be able to handle things like defenses being razed/removed before I regain balance.
I figure the general process is something like this. I'll have a variable called queued_command.
Whenever I do an offensive macro, I QUEUE EQBAL the action and also store it in queued_command.
If I see a razeable defense going up, I QUEUE EQBAL the appropriate raze command.
If I see a razeable defense going down, I immediately QUEUE EQBAL a new raze command. If the target has no more razeable defenses, I QUEUE EQBAL the stored queued_command.
If I see a balance or eq regained message, if the last command performed was queued_command, I set queued_command to nil, otherwise, if the last command was a raze command, I QUEUE EQBAL queued_command.
Does this seem reasonable? Is this a total overkill? Am I missing something?
Feedback appreciated.
Thanks
Comments