D&D Core Rules: The Complete Reference
Dungeons & Dragons operates on a foundation of interlocking mechanical systems — dice, character statistics, narrative judgment — that can look bewildering from the outside but reveal a surprisingly coherent logic once the structure is visible. This page covers the core rules as published in the 5th Edition framework, the most widely played version of D&D since Wizards of the Coast released it in 2014. The goal is a clean, usable reference: what the rules are, how they interact, and where the hard calls happen.
Definition and scope
The "core rules" of D&D refer to the mechanical framework governing how actions, conflicts, and consequences resolve at the table. In 5th Edition, those rules are distributed across three primary volumes — the Player's Handbook, the Dungeon Master's Guide, and the Monster Manual — though Wizards of the Coast also maintains a free subset called the Systems Reference Document (SRD), released under a Creative Commons license, which covers a substantial portion of the core rules without requiring purchase.
The scope is deliberately broad. The rules govern combat, exploration, and social interaction — the three "pillars" named explicitly in the Dungeon Master's Guide (p. 8). Within those pillars, the rules address character creation (ability scores, race, class, background), task resolution (the d20 roll system), resource management (spell slots, hit points, short and long rests), and the adjudication of fictional events. What the rules do not govern is the story itself. That remains the shared province of the Dungeon Master and the players.
For a fuller picture of how D&D's different rule categories fit together, the scope goes deeper than any single page can hold.
How it works
The engine underneath almost everything in D&D is the d20 Test: roll a 20-sided die, add a relevant modifier, compare the result to a target number. That's it. The variations — ability checks, attack rolls, saving throws — are applications of the same underlying structure.
The core resolution sequence works like this:
- The Dungeon Master calls for a roll when the outcome of an action is uncertain and consequential.
- The player rolls a d20 and adds the appropriate ability modifier (Strength, Dexterity, Constitution, Intelligence, Wisdom, or Charisma — each ranging from −5 to +5 at typical play levels).
- Proficiency bonus is added if the character is proficient in the relevant skill, tool, or weapon. In 5th Edition, this bonus ranges from +2 at 1st level to +6 at 20th level.
- The total is compared to a Difficulty Class (DC) for checks, or an Armor Class (AC) for attacks. Meet or beat the number: success. Fall short: failure.
Advantage and Disadvantage sit on top of this system as a clean binary modifier. Instead of stacking numerical bonuses, a character either rolls 2d20 and takes the higher result (Advantage) or rolls 2d20 and takes the lower (Disadvantage). The design choice is elegant and fast — it eliminates the modifier-stacking arithmetic that slowed earlier editions.
The full mechanical walkthrough covers the d20 system, action economy, and the rest structure in considerably more detail.
Common scenarios
The rules get their real workout in specific table situations. Three come up constantly:
Contested rolls. When two characters act against each other — one tries to shove, the other resists; one attempts to hide, the other searches — neither rolls against a fixed DC. Instead, both roll the relevant check and compare totals. Ties go to the character whose action is being resisted.
Concentration. A large portion of spells in 5th Edition require the caster to maintain Concentration, limiting active spell effects to one at a time. Taking damage while concentrating triggers a Constitution saving throw (DC 10 or half the damage taken, whichever is higher). This single mechanic shapes nearly every high-level combat encounter.
Death and dying. At 0 hit points, a character falls unconscious and begins making Death Saving Throws — rolling a d20 each turn, with no modifiers. Three successes: stabilization. Three failures: death. Rolling a 1 counts as 2 failures; rolling a 20 returns the character to 1 hit point immediately. The system creates genuine tension without requiring permanent character retirement every time someone gets unlucky.
The D&D frequently asked questions page addresses the edge cases that come up most often around these mechanics, including stacking conditions and multiclass interactions.
Decision boundaries
The rules are explicit in some areas and deliberately silent in others — and knowing which is which is the actual skill the Dungeon Master develops.
Rules as Written (RAW) vs. Rules as Intended (RAI) is a distinction the D&D community uses constantly. RAW refers to the literal text of the published rules. RAI refers to the evident design intent, often clarified through Wizards of the Coast's official Sage Advice Compendium, which is updated periodically and available free at sageadvice.eu and through the Wizards website.
The Dungeon Master's Guide (p. 235) states explicitly: "The D&D rules help you and the other players have a good time, but the rules aren't in charge." This isn't a loophole — it's a structural design choice. The DM functions as a final arbiter, and the rules provide a default framework rather than a binding contract.
Where RAW and RAI diverge most sharply:
- Spell interaction edge cases, particularly involving teleportation and barriers
- Multiclass spellcasting, which requires combining spell slot tables from two classes
- Object interaction rules, which the written rules describe in roughly 100 words despite covering an enormous range of fictional situations
The rule of thumb: when the written rule produces an absurd outcome, the DM calls a reasonable alternative. When the written rule produces a surprising-but-coherent outcome, it usually stands. That judgment call — knowing which kind of surprising the result is — is what getting help at the table looks like in practice.