khunkwai wrote:
Quote:
I think (IMO here) that {Interrupt} is interrupting the effect, not the performance of the action. Think about a Defend, which is an {Interrupt}. It interrupts the damage, but not the performance of the attack.
Right so Abate should not impact anything that stops the attack reaching the target. It should impact only the effect of the attack Damage and Conditions
So Perhaps Abate should be updated to identify Metas it can not impact : such as Range / Area / Etc.
I actually disagree with that. I really don't have any issue with it hitting Range or Area and invalidating targets. I would view it (in the Range example, say) as putting a wider force field shell and slowing the missile. I would get pretty highly narrative at this point, I imagine, but I'm ok with that myself.
However, I do like the idea of it not being a free for all on which rune gets hit, because it makes Abate very strong, as you say. I don't like "I'm Abating and targeting specific runes". I like the idea of the "right most rune". It puts the onus for the Abate-resistance on the attacker to construct his rune chain well. It will probably make Range and Maintain be the first in the chain (you want some effect, and are willing to sacrifice something like an Amplify).
Interesting side effect, laying an Open allows your buddies to protect your chain from Abates (though I can't think of a situation where it would work like this in practice off the top of my head). Same with Cannibalize