Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="KarinsDad" data-source="post: 5725792" data-attributes="member: 2011">The more I think about it, the more I view the opposing POV as coming up with a new type of interrupt not defined in the rules.II 1: Shield (or Heroic Effort): It may or may not change the trigger.II 2: Bear's Endurance: It cannot change the trigger. It's not that the power might not change the trigger, it's that it is impossible for it to do so.IR: Mind Spike: It cannot change the trigger.Interestingly enough, Shield is worded such that it doesn't indicate that it can change the calculation that leads to the trigger whereas Heroic Effort is worded such that it does indicate that it can change the calculation that leads to the trigger.The phrase "before the trigger resolves" means before the trigger happens, not before something in response to the trigger happens.Combat Challenge is resolved before the marked target shifts away.Shield is resolved before the PC is hit.Bear's Endurance is resolved before the PC goes to zero or lower hit points.I think the confusion comes in here because some triggers are easy to comprehend as interruptable and others are less so. It's easy to comprehend a point in time before the target shifts away as a set point in time that can be interrupted. It's a little harder to comprehend a point in time before the PC actually drops below zero hit points as a set point in time that can be interrupted.Our minds are somewhat pre-conditioned to think "Well, he has already dropped to zero hit points, by changing that, we are going back in time". We are not going back in time. We are interrupting the trigger before it occurs. Just like we are doing so for Combat Challenge.When the resolution of a trigger is interrupted, it means by definition that the trigger hasn't yet happened. The target has not shifted away. Yet. The PC has not been hit. Yet. The PC has not dropped below zero hit points. Yet.It's not just that all of the extra baggage that goes along with dropping to zero hit points hasn't happened, it's that dropping to zero hit points (the trigger itself, just like for every other example) hasn't yet happened. The PC still has the 27 hit points he had before damage was subtracted because he hasn't yet dropped below zero hit points.One has to be consistent and adjudicate all of these the exact same way.The opposing POV is not doing that. They are drawing a new line in the sand where the PC is below zero hit points, but the ramifications of that (like dying) have not yet occurred.That's a new rule. That's changing the fact that the trigger hasn't yet happened because the immediate interrupt is occurring first. The resolution of shifting is that the target actually shifts. The resolution of dropping below zero hit points is that the target is actually below zero hit points. These both (may or may not) occur after resolving the effect of the immediate interrupt, but one has to determine that by applying the effect of the interrupt before applying the rules that resulted in the trigger.</blockquote>

Verification