Search results

And it doesn't grant any rule authority to perform an action after the trigger happens. Your method is completely indistinguishable from immediate reactions.

Yes it has. All of these other things you talk about, unconscious, falling prone, etc, etc, are not the trigger. Dropping your hit points is the trigger and nothing else. This is the part you fail to understand. This is the idea you keep conflating with a bunch of other stuff. Once you drop...

As soon as you drop your hit points the trigger has finished.

You will drop your hit points first. This is the event that allows bear's endurance to be used. However, bear's endurnace has to be executed before you drop your hit points because its an interrupt. So you rewind. You don't drop your hit points and instead execute bear's endurance. After that...

You have two logical statements that will always be true given the exact same events. Trigger below 0 hp happens. Do you turn to p260 of the Rules Compendium and execute that effect? Or do you turn to the book/page for Bear's Endurance and execute that effect? You cannot make any assumptions...

It's because they have the same trigger. Rules Compendium p260 "When an adventurer's hit points drop to 0 or fewer, he or she falls unconscious and is dying." There's no method to determine which one goes first. None. The best you can say is they both happen at the same time.

All of these things happen at the exact same time as being hit. The only way to execute the effect before the trigger finishes is to execute it before the hit statement. It did arise, however the player interrupted it. Just because he doesn't drop to zero any more doesn't mean the trigger...

And the only way it can jump in before the trigger finishes is to be executed before the hit statement.

I'm using the definition of trigger from the source material. Rules Compendium p195 again... "A trigger is an action, an event, or an effect that allows the use of a triggered action." In my example being hit is what allowed bear's endurance to be used. You and others seem to think there's...

The final order of events would be: Ally uses power. Warden moves 7. Warden gains healing from bear's endurance. Warden takes 30 damage after falling. Taking 30 damage is the event that causes bear's endurance to trigger.

You keep conflating things. Rules Compendium p. 229 "Conditions are states imposed on creatures by various effects." Conditions and effects are different despite having a close relationship. For example, an effect can have multiple conditions or none at all. They are still different from...

Disagree. The event that is triggering bear's endurance is getting hit. Dropping below zero is a condition, not an event. In fact, dropping below zero is the condition that causes the hit statement to become the trigger. Also, being hit isn't an action in and of itself. It's only part of an action.

Yes.

Maybe they didn't. Doesn't really matter. The hit statement is still the trigger.

Rules Compendium p195 "A trigger is an action, an event or an effect that allows the use of the triggered action." So yes, some can be invalidated while others are not. If the above said "A trigger is an action that allows the use of the triggered action" I would agree but its more then just...

The hit statement is the trigger. That's what you're missing. The effect from bear's endurance is executed before the trigger because its an interrupt. This means he is attacked, then healed, then hit. The conditional bonus (+1 bloodied targets) is not applied to the hit statement, its applied...

If bite misses you lose all of the damage. However, one raking charge attack can miss and the other can hit.

DracoSuave is the closest to being right. Let me demonstrate. Let's assume the warden is at 9 HP with a healing surge value of 10. Take the following basic melee attack power. Attack: Melee 1 (one creature); +10 vs AC Hit: 1d10 + 8 damage. The attack statement is executed and the result is...

My players get to retry the encounter when I TPK them. I just hand wave it and no one minds. I never throw them a bone and mercilessly try to kill them every chance I get without worrying about the campaign ending prematurely.

I go one step further and use 4e rules. You can only drop one down to 8. The rest are 10 or above.