Basic Saving Throws and Persistent Damage

[OffRoadSP]

How does persistent damage work with the basic saving throw? Is it doubled/normal/halved/no damage like the regular damage? Precedence would make me believe it would be no persistent damage on a save/crit save, or full persistent damage on a failure/crit fail; however, I cannot find anything explicitly stating that in the CRB, unless I'm missing it...

[shroudb]

you don't roll for a save for persistent.

you roll for a save for the effect causing it IF the effect says so.

as an example,

Acid arrow: it has no save, so if you get hit, you'll be taking that persistent damage until you remove it (flat check dc 15 at the end of your round, or spend 2 actions to roll manually with DC going as low as 10)

Grim tendrils: 2d4 nomral damage +1 peristent bleed. Fort save that says:
"Success The creature takes half the negative damage and no
persistent bleed damage."

so success negates the persistent.

and etc

[OffRoadSP]

So, for a fire mephit's breath weapon:

"...deals 2d4 fire and 1d4 persistent fire damage to each creature within the area (DC 17 basic Reflex save)."

The save would be only for the fire damage, and not the persistent? So on a crit success roll, the PC takes no fire damage but still takes the persistent damage?

[kaid]

I think in that case the reflex save is basically the "to hit roll" so if you save vs that none of it effects you. But if if you got hit with it once you have the persistent effect you can't save to remove it you would have to do the flat roll instead.

[kaid]

Actually on second thought I would need to read the full mephit entry. It may work like alchemists bombs where you may avoid the main effect but you take the persistent effect anyway. I am pretty sure it specifies that wording in the actual ability one way or the other.

[shroudb]

OffRoadSP wrote:

So, for a fire mephit's breath weapon:

"...deals 2d4 fire and 1d4 persistent fire damage to each creature within the area (DC 17 basic Reflex save)."

The save would be only for the fire damage, and not the persistent? So on a crit success roll, the PC takes no fire damage but still takes the persistent damage?

i think that's a badly written creature but yes.

as RAW, you would take the persistent since basic saving throws only deal with the damage of a spell/effect and not with the actual effects that it may cause.

but in 99% of occasions, you only suffer the persistent on a failed save throw, so i guess that's the actual intent of the ability.