Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Upgrade your account to a Community Supporter account and remove most of the site ads.
Community
General Tabletop Discussion
*Pathfinder & Starfinder
Warden L6 Utility "Bears Endurance"
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="KarinsDad" data-source="post: 5726381" data-attributes="member: 2011"><p>In the first case, you prevent the "shift" of the trigger and resolve the effect, then continue the shift if still applicable.</p><p>In the second case, you prevent the "you are hit" of the trigger and resolve the effect, then continue the hit if still applicable.</p><p>In the third case, you DO NOT prevent the "you drop below zero" of the trigger and resolve the effect, then continue the drop below zero if still applicable.</p><p></p><p>Using your method, the drop below zero is set in stone, the PC then heals and is always in positive hit points. There is no chance that the heal isn't powerful enough because you are forcing the hit points to be below zero before forcing them to be above zero. The hit trigger isn't set in stone. The shift trigger isn't set in stone. But, the drop below zero trigger is set in stone. It always happens with your interpretation.</p><p></p><p>If handled like the other two cases, the damage is calculated, but the PC doesn't take that damage yet because he interrupts the "drops to zero" trigger. Just like the hit is calculated, but the PC doesn't actually get hit yet because he interrupts the "you are hit" trigger.</p><p></p><p>"An immediate interrupt lets you jump in when a certain trigger condition arises, acting <strong>before</strong> the trigger resolves." The resolution of getting hit is getting hit. The resolution of shifting is shifting. The resolution of going below zero hit points is going below zero hit points.</p><p></p><p>This is not talking about other rules resolutions like a result of the trigger's resolution (like taking damage if hit, or dying if dropped below zero), it's talking about the resolution of the trigger itself.</p><p></p><p>It doesn't get any rules clearer than this. You are ignoring this rule in the third case and resolving the act of going below zero by forcing the PC to go below zero before applying the effect (not the resolution of dying or the resolution of going unconscious, but the resolution of going below zero hit points, these are different resolutions).</p><p></p><p>Are you seriously claiming that you are still handling these three triggers the same way when you apply the trigger before proceeding in the third case, but do not do so in the first two cases? Seriously? If so, now you are just arguing to argue. You haven't come up with a single valid reason why people should treat these triggers different, or a single valid explanation as to why your way is not treating them different.</p><p></p><p>This isn't worth arguing. It's obvious that you are throwing in a different way to handle the third case. And, it's obvious that the main immediate interrupt rule disagrees with your interpretation because you are not interrupting the trigger, you are interrupting other game rules (like unconsciousness and dying) which are not part of the trigger. These other rules are ramifications of the trigger occurring, just like taking damage is a potential ramification of getting hit. You are stopping downstream rules, but not the trigger itself in the third case.</p></blockquote><p></p>
[QUOTE="KarinsDad, post: 5726381, member: 2011"] In the first case, you prevent the "shift" of the trigger and resolve the effect, then continue the shift if still applicable. In the second case, you prevent the "you are hit" of the trigger and resolve the effect, then continue the hit if still applicable. In the third case, you DO NOT prevent the "you drop below zero" of the trigger and resolve the effect, then continue the drop below zero if still applicable. Using your method, the drop below zero is set in stone, the PC then heals and is always in positive hit points. There is no chance that the heal isn't powerful enough because you are forcing the hit points to be below zero before forcing them to be above zero. The hit trigger isn't set in stone. The shift trigger isn't set in stone. But, the drop below zero trigger is set in stone. It always happens with your interpretation. If handled like the other two cases, the damage is calculated, but the PC doesn't take that damage yet because he interrupts the "drops to zero" trigger. Just like the hit is calculated, but the PC doesn't actually get hit yet because he interrupts the "you are hit" trigger. "An immediate interrupt lets you jump in when a certain trigger condition arises, acting [b]before[/b] the trigger resolves." The resolution of getting hit is getting hit. The resolution of shifting is shifting. The resolution of going below zero hit points is going below zero hit points. This is not talking about other rules resolutions like a result of the trigger's resolution (like taking damage if hit, or dying if dropped below zero), it's talking about the resolution of the trigger itself. It doesn't get any rules clearer than this. You are ignoring this rule in the third case and resolving the act of going below zero by forcing the PC to go below zero before applying the effect (not the resolution of dying or the resolution of going unconscious, but the resolution of going below zero hit points, these are different resolutions). Are you seriously claiming that you are still handling these three triggers the same way when you apply the trigger before proceeding in the third case, but do not do so in the first two cases? Seriously? If so, now you are just arguing to argue. You haven't come up with a single valid reason why people should treat these triggers different, or a single valid explanation as to why your way is not treating them different. This isn't worth arguing. It's obvious that you are throwing in a different way to handle the third case. And, it's obvious that the main immediate interrupt rule disagrees with your interpretation because you are not interrupting the trigger, you are interrupting other game rules (like unconsciousness and dying) which are not part of the trigger. These other rules are ramifications of the trigger occurring, just like taking damage is a potential ramification of getting hit. You are stopping downstream rules, but not the trigger itself in the third case. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Pathfinder & Starfinder
Warden L6 Utility "Bears Endurance"
Top