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

Reply to thread

Message: <blockquote data-quote="Hriston" data-source="post: 6691631" data-attributes="member: 6787503">I'm confused. At that point have you been hit twice? <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile    :)"  data-smilie="1"data-shortname=":)" />So you're saying that you become aware of the threat after you've been hit. That's not what the rules say.So an alarm going off in the present is an alarm going off in the past? I don't buy it. I would counter your statement, however, by saying that there is no measurable period of time during which you have been hit and yet you are unaware of your attacker. The two events are meant to coincide precisely.Let's back up a moment, shall we? The actual wording of the rule is that, "when you make an attack, you give away your location when the attack hits or misses." An attack is a d20 roll that determines whether your attack hits or misses. The question is, what does the attack roll represent in the fiction? Does it represent the moment the bullet pierces the victim's body? Or does it represent the assassin's attempt to aim and fire his weapon? I would argue for the latter. It's not a matter of being hit (or missed) by the bullet itself, but rather of the attack being determined to be a hit or a miss. This is why Shield works.No causality is given in the rules, only the coincidence of making the attack and giving away your position.I wouldn't get too hung up on cause and effect. The rules aren't written that way. If it says, Y happens when X happens, it just means that X and Y happen at the same time, not that X caused Y and so really happened first. Believe it or not, that would be overthinking it.</blockquote>

Verification