It looks like you're new here. If you want to get involved, click one of these buttons!
What class are you? And by attack I guess you mean to keep attacking your target? If that's the case I would trigger your attack line to send QUEUE ADD EQBAL <your_attack> so when you don't hit because there is no one around it will stop.
For Nexus, I set a trigger on my attack: "You spring forward onto..." to send "maul @tar". After I send "maul" the first time, it just repeats mauling until the target is dead. It's a very simple and not very smart trigger, but it does well enough for my purposes. I don't use Nexus much, mainly Mudlet. So Nexus is just a back up..... basically I'm saying the same thing Rekhyr said, just using different words. :P
Make a variable that keeps track of whether you should be hitting something or not. Set it to true inside the alias you input that runs your initial attack. Trigger off the message outputted to the screen when you attack something like Cailin said. Inside that trigger check if the variable that determines whether you should be hitting something is true. If it is, queue up another attack on the balance queue. Otherwise, don't do anything.Make a trigger that captures when you kills something. I.e. "^You have slain (.*)\.$". Have this trigger set the variable that determines whether your attack trigger should queue up another one to false.