5e SRD:Attack Rolls

This material is published under the OGL

Attack Rolls

When you make an attack, your attack roll determines whether the attack hits or misses. To make an attack roll, roll a d20 and add the appropriate modifiers. If the total of the roll plus modifiers equals or exceeds the target's Armor Class (AC), the attack hits. The AC of a character is determined at character creation, whereas the AC of a monster is in its stat block.

Modifiers to the Roll

When a character makes an attack roll, the two most common modifiers to the roll are an ability modifier and the character's proficiency bonus. When a monster makes an attack roll, it uses whatever modifier is provided in its stat block.

Ability Modifier. The ability modifier used for a melee weapon attack is Strength, and the ability modifier used for a ranged weapon attack is Dexterity. Weapons that have the finesse or thrown property break this rule.

Some spells also require an attack roll. The ability modifier used for a spell attack depends on the spellcasting ability of the spellcaster.

Proficiency Bonus. You add your proficiency bonus to your attack roll when you attack using a weapon with which you have proficiency, as well as when you attack with a spell.

Rolling 1 or 20

Sometimes fate blesses or curses a combatant, causing the novice to hit and the veteran to miss.

If the d20 roll for an attack is a 20, the attack hits regardless of any modifiers or the target's AC. This is called a critical hit.

If the d20 roll for an attack is a 1, the attack misses regardless of any modifiers or the target's AC.



Back to Main Page 5e System Reference Document Combat Making an Attack

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: > can i reverse engineer potatOSYep!> and make my own omnidiskNope!
gollark: Or I guess you could compile your whole thing including the license verification to bytecode.
gollark: <@154361670188138496> I mean, kind of. Thing is, OmniDisks\™ are basically only useful for getting around PotatOS sandboxing. So if they can't do that the disk is useless.This sort of "only useful in an environment you fully control" sandboxing is the only workable sort.
gollark: It also contains valid disk IDs for each UUID and disk IDs are unique to each disk and unspoofable.
gollark: The program *on* the disks downloads a license info JSON from the interweb when it runs. This contains the features each UUID is allowed to use.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.