Reply to thread

Message

<blockquote data-quote="W'rkncacnter" data-source="post: 9310392" data-attributes="member: 7033455">i've been considering 3 options for stunning assault here:1. make it so a creature only needs to save when they take their con score in damage in a turn. so a 20 con creature only needs to save against stunning assault if you dealt at least 20 damage to it, and has to make 2 saves if you dealt at least 40 damage to it. this should make it harder to impose multiple saves against stun against a single creature, and was discussed earlier.2. make it a condition ladder. on a failed save, a creature with no conditions becomes rattled, or a rattled creature becomes slowed, or a slowed creature becomes stunned. makes it harder to stun a creature, and makes it basically impossible to stun multiple in a single turn without help from other party members. this is basically both flavors of the &quot;don't make it stunned immediately&quot; idea at once.3. throw out the entire idea of stunning assault and make it fit the tradition better by having it impose a level of strife on a failed save instead of the stunned condition. you could call it terrible assault or something. still pretty painful (especially for casters and especially from fighters), but not as debilitating as the stunned condition.</blockquote>

[QUOTE="W'rkncacnter, post: 9310392, member: 7033455"] i've been considering 3 options for stunning assault here: 1. make it so a creature only needs to save when they take their con score in damage in a turn. so a 20 con creature only needs to save against stunning assault if you dealt at least 20 damage to it, and has to make 2 saves if you dealt at least 40 damage to it. this should make it harder to impose multiple saves against stun against a single creature, and was discussed earlier. 2. make it a condition ladder. on a failed save, a creature with no conditions becomes rattled, or a rattled creature becomes slowed, or a slowed creature becomes stunned. makes it harder to stun a creature, and makes it basically impossible to stun multiple in a single turn without help from other party members. this is basically both flavors of the "don't make it stunned immediately" idea at once. 3. throw out the entire idea of stunning assault and make it fit the tradition better by having it impose a level of strife on a failed save instead of the stunned condition. you could call it terrible assault or something. still pretty painful (especially for casters and especially from fighters), but not as debilitating as the stunned condition. [/QUOTE]

Verification