Reply to thread

Message

<blockquote data-quote="Ovinomancer" data-source="post: 6906683" data-attributes="member: 16814">Yes, and no.&nbsp; Reactions cannot interrupt their trigger unless they specifically say so.&nbsp; Both counterspell and shield are examples of reactions that can interrupt their trigger because they say so.&nbsp; No others come to mind at the moment outside of monster reactions, which are varied.But trigger != action.&nbsp; A trigger must be a clearly defined and noticeable event.&nbsp; I wouldn't allow any &quot;starts to...&quot; triggers because that's clearly defined.&nbsp; But attacking someone is, so I'd allow that as a trigger.&nbsp; So, if you Ready to strike at the foe if they attack someone, you react immediately after they make an attack -- even if they get multiple attacks.&nbsp; In effect, you interrupt their multi attack or attack action.&nbsp; So, then, the issue is what you allow as definable triggers.&nbsp; As I said above, I'd never allow a &quot;starts to...&quot; trigger.&nbsp; I'd allow a &quot;majes somatic gestures&quot; and you'd react before they finish casting, but wouldn't be able to id the spell beforehand because those gestures aren't complete.&nbsp; If you want to ID the spell, you have to wait until casting is complete, and then you can't stop it because it's done.So, can't interrupt triggers unless specifically stated; and triggers must be definable and clear events that can be noticed.&nbsp; That's it, everything else is rulings and opinion.</blockquote>

[QUOTE="Ovinomancer, post: 6906683, member: 16814"] Yes, and no. Reactions cannot interrupt their trigger unless they specifically say so. Both counterspell and shield are examples of reactions that can interrupt their trigger because they say so. No others come to mind at the moment outside of monster reactions, which are varied. But trigger != action. A trigger must be a clearly defined and noticeable event. I wouldn't allow any "starts to..." triggers because that's clearly defined. But attacking someone is, so I'd allow that as a trigger. So, if you Ready to strike at the foe if they attack someone, you react immediately after they make an attack -- even if they get multiple attacks. In effect, you interrupt their multi attack or attack action. So, then, the issue is what you allow as definable triggers. As I said above, I'd never allow a "starts to..." trigger. I'd allow a "majes somatic gestures" and you'd react before they finish casting, but wouldn't be able to id the spell beforehand because those gestures aren't complete. If you want to ID the spell, you have to wait until casting is complete, and then you can't stop it because it's done. So, can't interrupt triggers unless specifically stated; and triggers must be definable and clear events that can be noticed. That's it, everything else is rulings and opinion. [/QUOTE]

Verification