LogFAQs > #885665483

I kinda like the idea of a Priority keyword. Idea being that stuff will explicitly resolve in order of ascending priority, with Pre-Battles resolving in order of declaration as usual.

For instance, you could have something like this.

Taunt (Start of Battle, Priority 1, Recharge 2) - Once every three weeks, Dan may taunt a preselected enemy merc. Incensed, they will prioritize taking out Dan above all else. Additionally all of their damaging abilities used this week are redirected to him.

Because it's Priority 1, there's no question it'll resolve properly on higher. The idea is you would then clean up the write-up, explicitly giving an order of resolution on multiple abilities hitting a guy, when needed, and you'd generally give all redirection effects high priority to remove that confusion implicitly.

You could also do something wacky like load the Priority keyword with game mechanics. For instance say you do something like make pretty much all Priority 5 abilities of the damage type, then you could say something like, additionally all of their Priority 5 abilities used this week are redirected to him rather than introducing the "damaging" issue. And if you wanted to make a weird ability that does damage but can't be prevented, you just give it a different priority.
---

No problem!
This is a cute and pop genocide of love!