5e SRD:Saving Throws

This material is published under the OGL

Saving Throws

A saving throw—also called a save—represents an attempt to resist a spell, a trap, a poison, a disease, or a similar threat. You don't normally decide to make a saving throw; you are forced to make one because your character or monster is at risk of harm.

To make a saving throw, roll a d20 and add the appropriate ability modifier. For example, you use your Dexterity modifier for a Dexterity saving throw.

A saving throw can be modified by a situational bonus or penalty and can be affected by advantage and disadvantage, as determined by the GM.

Each class gives proficiency in at least two saving throws. The wizard, for example, is proficient in Intelligence saves. As with skill proficiencies, proficiency in a saving throw lets a character add his or her proficiency bonus to saving throws made using a particular ability score. Some monsters have saving throw proficiencies as well.

The Difficulty Class for a saving throw is determined by the effect that causes it. For example, the DC for a saving throw allowed by a spell is determined by the caster's spellcasting ability and proficiency bonus. The result of a successful or failed saving throw is also detailed in the effect that allows the save. Usually, a successful save means that a creature suffers no harm, or reduced harm, from an effect.



Back to Main Page 5e System Reference Document

Open Game Content (place problems on the discussion page).
This is part of the 5e System Reference Document. It is covered by the Open Game License v1.0a, rather than the GNU Free Documentation License 1.3. To distinguish it, these items will have this notice. If you see any page that contains SRD material and does not show this license statement, please contact an admin so that this license statement can be added. It is our intent to work within this license in good faith.
gollark: Also, minor but probably important QoL thing: please make it so that you can click the license key to copy it to clipboards like you can with peripheral names.
gollark: It's more a thing of random BIOS additions and making compatibility with potatOS more annoying.
gollark: I like the websocket chatbox idea, but please don't add the event conversion thing as yet another background coroutine.
gollark: Real OS dev is very hard. Bodging together other work is ez.
gollark: Anyway, I don't think most of the comments are very passive aggressive, though I'm always up for improvements.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.