Reply to thread

Message

<blockquote data-quote="Guest 6801328" data-source="post: 7316073">Wow.&nbsp; You are really bending over backwards to make this sound complicated.&quot;I cast Feather Fall.&quot;&quot;You can't...you're inside a silence spell.&quot;&quot;Oh.&nbsp; When I come out of the silence spell I try to cast it.&quot;&quot;Ok.&nbsp; You're about 80 feet above the ground, floating down.&quot;&quot;Cool.&quot;Uh, yeah.You keep trying to argue this thing that I'm not arguing.&nbsp; You think my reading of the Feather Fall spell is not just a different ruling but actually wrong, so you keep making these analogies asking why I would change other rules to make things harder for players.&nbsp; (Such as forcing your character to go around one side rather than the other.)Since I don't accept that I'm reading the Feather Fall spell wrong, why would that line of reasoning be productive?&nbsp; Obviously I'm not going to think that your attempts at analogies make any sense at all.See?&nbsp; There you go again.&nbsp; We're not even debating the same thing anymore.And the rest of your post continues in this same vein...We are debating (I thought...?) whether one or both interpretations of Feather Fall are correct, not whether changing the rules to penalize players is a good thing to do.I'm going to summarize my position as succinctly as possible:1) Based on the language of Feather Fall I conclude that Feather Fall is supposed to be used as a reaction to a discrete event, which is that somebody &quot;falls&quot;.&nbsp; I don't believe it is meant to apply to the ongoing process of falling, especially since a spell that does work that way, Counterspell, uses language that very specifically does allow it.&nbsp; The absence of that language in Feather Fall speaks, I believe, to the designers' intent.2) In cases where a player cannot respond immediately to a fall, such as starting inside a Silence spell, or trying to cast it on somebody else who starts out of range but falls into range, I would allow it to be used as soon as possible.&nbsp; In other words, &quot;react to the situation as soon as you can&quot;.&nbsp; Yes, that raises some paradoxes, and I could easily justify saying, &quot;Sorry, that's not how Feather Fall is written so you can't do that...&quot; but I'd rather be lenient and not be a dick.3) If somebody wanted to get fancy and time their Feather Fall to go off just before they land I would require an additional roll. You know, &quot;greater risk, greater reward&quot; and all.&nbsp; I think acrobatics is appropriate because that is kind of exactly what acrobats do: time landings.&nbsp; I'm not sure (yet) exactly what penalty I would impose for failure.&nbsp; Maybe stunned for 1 round for each 60' or something.</blockquote>

[QUOTE="Guest 6801328, post: 7316073"] Wow. You are really bending over backwards to make this sound complicated. "I cast Feather Fall." "You can't...you're inside a silence spell." "Oh. When I come out of the silence spell I try to cast it." "Ok. You're about 80 feet above the ground, floating down." "Cool." Uh, yeah. You keep trying to argue this thing that I'm not arguing. You think my reading of the Feather Fall spell is not just a different ruling but actually [I]wrong[/I], so you keep making these analogies asking why I would change other rules to make things harder for players. (Such as forcing your character to go around one side rather than the other.) Since I don't accept that I'm reading the Feather Fall spell wrong, why would that line of reasoning be productive? Obviously I'm not going to think that your attempts at analogies make any sense at all. See? There you go again. We're not even debating the same thing anymore. And the rest of your post continues in this same vein... [B][/B] We are debating (I thought...?) whether one or both interpretations of Feather Fall are correct, not whether changing the rules to penalize players is a good thing to do. I'm going to summarize my position as succinctly as possible: 1) Based on the language of Feather Fall I conclude that Feather Fall is supposed to be used as a reaction to a discrete event, which is that somebody "falls". I don't believe it is meant to apply to the ongoing process of falling, especially since a spell that [I]does[/I] work that way, Counterspell, uses language that very specifically does allow it. The absence of that language in Feather Fall speaks, I believe, to the designers' intent. 2) In cases where a player cannot respond immediately to a fall, such as starting inside a Silence spell, or trying to cast it on somebody else who starts out of range but falls into range, I would allow it to be used as soon as possible. In other words, "react to the situation as soon as you can". Yes, that raises some paradoxes, and I could easily justify saying, "Sorry, that's not how Feather Fall is written so you can't do that..." but I'd rather be lenient and not be a dick. 3) If somebody wanted to get fancy and time their Feather Fall to go off just before they land I would require an additional roll. You know, "greater risk, greater reward" and all. I think acrobatics is appropriate because that is kind of exactly what acrobats do: time landings. I'm not sure (yet) exactly what penalty I would impose for failure. Maybe stunned for 1 round for each 60' or something. [/QUOTE]

Verification