SRD 5.2 Clarified for 2024 Table Policy and Common DM Rulings

1. What SRD 5.2 is for your table

SRD 5.2 is the baseline ruleset many groups lean on when they want a common ground for character options, spells, monsters, and mechanics. Treat it as the playable “core” that’s intended to be broadly shareable and usable across third‑party content; in practice, that means you can fairly assume players know how core spells, classes, and combat rules work and build table policy around them. My practical take: if it’s in SRD 5.2, default to allowing it unless you have a campaign reason not to.

2. Table policy: baseline vs. campaign exceptions

Make a one‑page table policy that names SRD 5.2 as your baseline and lists explicit exceptions (homebrew banned, certain magic items restricted, etc.). Players appreciate a clear scope: say “SRD 5.2 allowed; 3rd‑party allowed with DM approval; X, Y, Z banned.” Keep the policy physically on the table or in your campaign doc so you don’t waste 20 minutes at session zero hashing whether a particular cantrip is kosher.

3. Character options: what to allow straight‑from‑SRD

Allow races, classes, class features, and subclass options that appear in SRD 5.2 without extra approval. That means popular staples, fighter, cleric, rogue, core subclass options, can be assumed legal at signup. If you want to allow non‑SRD subclasses, require players to bring a printout or link and give a quick yes/no based on power level; don’t let niche homebrew slow character creation.

4. Spells, concentration, and ritual casting rulings

Use SRD spell text as authoritative at the table: ranges, durations, and concentration rules are nonnegotiable unless you announce a change. For concentration disputes, run them as follows: declare when concentration is required, track damage/events that force saves, and resolve saves immediately, no retroactive fiddling. For rituals, if SRD marks a spell as a ritual, allow the free ritual casting rule; if a player wants a class to add ritual access, require a clear feature or a house‑rule.

5. Magic items: what SRD covers and how to police attunement

SRD 5.2 includes a core set of magic items and guidance on attunement; treat attunement slots and rarity as table policy to prevent escalation. If an SRD item feels table‑breaking (e.g., guaranteed flight at low level), require attunement or a quest to acquire it. My rule of thumb: preserve the item’s flavor but delay full access, use attunement and staged upgrades so players earn the power instead of instantly breaking encounters.

6. Monsters and CR: use SRD stat blocks, but tune encounters

SRD stat blocks are your go‑to for monsters and tactics; use them for expected behavior and abilities. Don’t treat Challenge Rating as gospel, CR is rough math. If an SRD creature steamrolls your party, adjust hit points, minion counts, or tactics on the fly rather than retooling entire adventures mid‑session. Keep note of adjustments for future balance.

7. Combat edge cases: grappling, shove, opportunity attacks

Apply SRD combat rules for grapples, shoves, and opportunity attacks as written but call rulings fast. For grapple disputes: require a single contested check (Athletics vs. Athletics/Acrobatics) and move on; for shove, use the SRD’s push or knock prone outcomes, don’t open a rules debate unless it affects narrative stakes. Opportunity attacks? Use the SRD’s trigger (leaving reach) and stick to it; if you home‑rule differently, announce it before combat starts.

8. Skill and ability checks: DC setting and passive checks

Set DCs using SRD guidance: easy/moderate/hard anchors are your friends when improvising. Use passive checks for common tasks (Perception, Investigation) to avoid metagame fishing: announce that passive Perception will be used when appropriate and never retroactively apply it. When players contest your DC, explain your logic (terrain, lighting, distraction) briefly and move on, consistency beats pedantry.

9. Resting, healing, and downtime

Use SRD short‑rest and long‑rest rules as default: short rests recover hit dice and certain class features; long rests restore HP and spell slots as specified. If your campaign needs a grittier cadence, announce adjustments at the campaign start (for example, “long rest requires 8 hours safe camp or half healing only”). For healing potions and magic healing found in SRD, treat inventory and economy seriously, don’t handwave consumables away.

10. Third‑party content and licensing awareness

SRD 5.2 exists so creators and DMs have a shared rule language, and most groups accept SRD options as “table legal.” That said, make a simple rule for third‑party content: require either SRD parity (the option mirrors SRD mechanics) or prior DM approval. Practically, that keeps balance intact while allowing creativity; if a published third‑party subclass looks untested, ask for a writeup of mechanics and banlist entries before allowing it at your table.

11. Handling conflicts between SRD text and published adventure text

When SRD mechanics and a module’s printed wording differ, pick one policy and stick with it for that campaign: either run the module’s text as written or normalise to SRD language. In my sessions I default to module text for story beats and SRD mechanics for system mechanics, flip only if the module’s wording breaks the flow or makes a player’s choice meaningless. Document the decision in your session zero notes so later disputes are settled without drama.

12. Practical table rulings for common arguments

Train players on quick‑resolution methods: a single reroll (DM’s discretion), a 30‑second rules lookup, or a deferred fix at the end of the session. For disputes about whether something is “in the SRD,” ask the player to show the exact wording; if they can’t, rule conservatively in favor of game pace. My favorite trick: a “one‑time rewind” rule, if a ruling blows up a crucial scene, you can rewind one previous move per campaign to restore fairness.