| Claxon |
That's a good question.
Things caused by the same source (untyped bonuses) do not stack. However, these are two different types of penalties. I'm honestly not sure how it should be run.
Honestly though, the save DC for stunning fist is usually so low I find very few monks actually make use of it.
Edit: Or I could read this
Stunning Fist (Ex): At 1st level, the monk gains Stunning Fist as a bonus feat, even if he does not meet the prerequisites. At 4th level, and every 4 levels thereafter, the monk gains the ability to apply a new condition to the target of his Stunning Fist. This condition replaces stunning the target for 1 round, and a successful saving throw still negates the effect. At 4th level, he can choose to make the target fatigued. At 8th level, he can make the target sickened for 1 minute. At 12th level, he can make the target staggered for 1d6+1 rounds. At 16th level, he can permanently blind or deafen the target. At 20th level, he can paralyze the target for 1d6+1 rounds. The monk must choose which condition will apply before the attack roll is made. These effects do not stack with themselves (a creature sickened by Stunning Fist cannot become nauseated if hit by Stunning Fist again), but additional hits do increase the duration.
| Sandslice |
So if one is hit by Stunning Fist fatigued 2 times he will not become exhaused.
But if he is hit 1 time by fatigued and 1 time sickened? Both applies, or they considered "stunning fist" conditions and therfor dont stack with each other?
Both apply, because "Stunning Fist" is not a condition. Stunning Fist is the ability that is causing conditions. The reason the non-stacking line is there is that some of the conditions added by Stunning Fist usually stack with themselves.
| Claxon |
DarkPhoenixx wrote:Both apply, because "Stunning Fist" is not a condition. Stunning Fist is the ability that is causing conditions. The reason the non-stacking line is there is that some of the conditions added by Stunning Fist usually stack with themselves.So if one is hit by Stunning Fist fatigued 2 times he will not become exhaused.
But if he is hit 1 time by fatigued and 1 time sickened? Both applies, or they considered "stunning fist" conditions and therfor dont stack with each other?
Um, I think you mean only one applies because of the specific text of stunning fist description.
| Sandslice |
Sandslice wrote:Um, I think you mean only one applies because of the specific text of stunning fist description.DarkPhoenixx wrote:Both apply, because "Stunning Fist" is not a condition. Stunning Fist is the ability that is causing conditions. The reason the non-stacking line is there is that some of the conditions added by Stunning Fist usually stack with themselves.So if one is hit by Stunning Fist fatigued 2 times he will not become exhaused.
But if he is hit 1 time by fatigued and 1 time sickened? Both applies, or they considered "stunning fist" conditions and therfor dont stack with each other?
No, I mean both.
1. Fatigued and sickened are not on the same condition-tree. Fatigued and exhausted are; and sickened and nauseated are (apparently.) Normally, conditions on the same condition-tree stack if a second effect is applied while the first is active (eg, two fatigues make an exhausted,) unless noted.
Conditions on different condition-trees can apply separately at the same time unless noted:
"If more than one condition affects a character, apply them all. If effects can't combine, apply the most severe effect."
Fatigued and sickened actually affect different aspects of the character with no overlap. Fatigued is a penalty to Strength and Dexterity; sickened to hit, damage, saves, and checks.
2. Stunning Fist is an "unless noted," with respect to stacking the same status with multiple Stunning Fists. Examples:
-SF Sickened -> SF Fatigue: Target is sickened and fatigued.
-SF Sickened -> SF Sickened: Target is still only sickened (non-stacking,) but the condition gains 10 rounds of duration.
3. There IS a question of whether SF conditions stack with non-SF conditions.
-Ray of sickening -> SF Sickened: Target is nauseated?
| Kayerloth |
I'm not sure if that's what the text implies or not. It is a bit unclear to me.
Honestly, I wouldn't worry about it too much because the chances that you would succeed at landing two stunning fist attempts is likely rather small (due to low DC).
While the DC may in fact be low (on the one character I did have it on it wasn't what I'd call insanely hard, but it wasn't particularly low either which might have had something to do with his Wisdom/cleric levels ;)). Equally likely that unless used against only arcane casters the foes good Fort save will be as much a contributor as a low DC.