How to Learn D&D Without Reading the Rulebook First

The Player's Handbook is longer than most novels. Nobody sits down and reads it cover to cover before their first game, and the people who tell you they did are the reason the hobby has a reputation for being hard to get into.

Here's the thing that took us a while to accept while building this: the rules are not the hard part. The hard part is the vocabulary. A new player at a table doesn't get stuck because they can't do arithmetic. They get stuck because somebody says "roll initiative" and then "that's a DC 15 Dex save" and then "you're prone, so you have disadvantage," and none of those words mean anything yet, and the moment to ask has passed.

So this is a guide to learning D&D the way people actually learn it, which is badly at first and then suddenly all at once. It also explains what we built to make that first hour less miserable, because we had a lot of new players arriving and the honest answer to "what should I read first" was too long.

Roll a twenty-sided die. Add a number from your character sheet. Compare the total to a target number. If you match or beat it, the thing works.

That's it. That is the engine underneath almost every roll in the game. Attacking a goblin, picking a lock, spotting a trap, resisting a poison, convincing a guard to look the other way — all the same procedure with different numbers plugged in.

Everything else you will eventually learn is an exception to that sentence. Advantage says roll two dice and keep the higher one. A saving throw is the same procedure pointed the other way, resisting something being done to you rather than attempting something yourself. Spell slots put a limited supply on a particular action. None of these matter until the game puts one in front of you, which it will, one at a time.

If you want to arrive with something rather than nothing, learn these and stop:

• Hit points are how much damage you can take before you drop. They're stamina and luck as much as literal wounds. Hitting zero doesn't mean you're dead, it means you're unconscious and in trouble.
• Armour class is one number describing how hard you are to hit. Whoever attacks you has to roll that number or higher. It doesn't reduce damage — it decides whether the hit happens at all.
• Your turn gets you one action plus movement. Attack, cast something, try something clever. Some abilities are quick enough to be free-ish, but the default is one real thing per turn.
• Your bonuses are already on the sheet. You do not have to work out where +7 came from. It came from your Strength, your training, and your weapon, and it will keep coming from there.

That's genuinely enough to play a session. Everything below is what happens next.

D&D has about fifty years of accumulated shorthand, and much of it is bad. "Initiative" is a stat name doing duty as a verb. "Action economy" is a phrase from strategy forums that leaked into the rules conversation. "DC" is an abbreviation of "Difficulty Class," which is itself a jargon term for "the number you need."

We made a decision that annoyed a couple of experienced players in testing: we renamed things in the interface. Turn order instead of initiative. Difficulty instead of DC. Your turn instead of action economy.

The complaint was fair, though. If you learn to play in our game and then sit down at a physical table, you need to know what everyone else is calling these things. So every explanation ends by telling you the real name:

What we call it	What you'll hear at a table
Difficulty	DC, or Difficulty Class
Turn order	Initiative — "roll initiative" means a fight is starting
Your turn	The action economy
Saving throw	Usually shortened to just a save
Armour class	Nearly always just AC
Hit points	HP
Death save	Death saving throw
Opportunity attack	Attack of opportunity, often shortened to AoO
Proficiency	Proficiency bonus, sometimes written PB
Extra damage	No single word — you'll hear them by name, like Sneak Attack

Eighteen concepts have explanations like this. They're the ones that came out of watching where people actually stalled, not the ones that seemed important on paper.

Tooltips have a failure mode everybody has experienced: the thing that was helpful the first time is an irritation the fifth time, and there's usually no way to tell it you've got the message.

Ours count. The first time a concept is relevant to you, you get the full explanation, a few sentences long. The next two times you get a one-line version. After the third, it stops appearing entirely. You never dismiss anything, and there's no checkbox in a settings menu called "I am experienced" that you have to find.

The counting follows your account rather than the browser, and when two devices disagree it takes the higher count. Somebody who learned what a reaction is on their laptop and then opens the game on their phone should not be taught reactions again. Of all the ways this system could have been annoying, that one felt the most patronising.

This seems like the obvious job for the AI. It's already narrating, it's already conversational, and asking it "wait, what's a saving throw?" is exactly the kind of thing language models are good at.

We tried it and backed out. Three reasons, in descending order of how much they mattered.

A language model can be confidently wrong about rules, and a beginner has no way to catch it. If the narrator tells you that concentration works some way it doesn't, you'll believe it, and you'll carry that misunderstanding to your next table. The explanations you see now are written text tied to the specific rule, so they're either right or they're a bug we can fix once.

Second, the numbers. When the game tells you that you need 14 or higher on the die, that number is computed from your actual character against the actual target, not generated. It cannot drift.

Third, and less principled: teaching interrupts the story. The narrator is meant to be describing a room you're standing in. Every sentence it spends on the definition of a bonus action is a sentence not spent on the room.

We limited this to the two places people get stuck, rather than sprinkling question marks across every screen.

Combat. This is where D&D goes from "describe what you do" to a game with turn order and resource management, and it's where new players freeze. Explanations appear on the roll dialog, the action panel, the turn order display, and the reaction prompt. Where you have advantage on a roll, it says so and explains what advantage is, because that's the moment the concept means something rather than an abstract definition.

Making a character. The creator asks you for decisions before you know what any of them do. Choosing a class is choosing what your whole experience of the game feels like, and the interface was previously happy to let you pick one off a list like a drop-down menu.

Reaction prompts get one extra thing: a timer floor. Reactions are the hardest moment for a beginner because someone else's turn stops and you have a few seconds to make a decision about a rule you may have just met. Your first one gives you a full minute, with the countdown visible so nothing happens silently. After you've seen a few, it speeds back up.

Conditions — poisoned, frightened, prone, restrained — are one of the biggest sources of confusion in the game, and they get the least help here. There's a written explanation, but no good place to put it, because the game doesn't yet show you a list of what's currently affecting you. Explaining conditions well requires building that display first. It's the next thing.

We also don't teach the tactical layer at all. Nothing tells you that holding your Rogue's Sneak Attack for a better target is usually right, or that you should probably not be standing next to the wizard. That's judgement, it takes much longer than rules to acquire, and a tooltip that tried to teach it would be insufferable.

Nobody learns D&D by reading about D&D. You learn it by making a bad decision in a fight, watching it go wrong, and understanding the rule retroactively because it just cost you something. Every experienced player has a story about the turn where they finally understood what an opportunity attack was, and it is always the turn they got hit by one.

What software can do is lower the price of the bad decision. Nobody's waiting on you. No one sighs when you ask what a bonus action is for the second time. You can sit on a reaction prompt for a minute working out what it means, and the only thing watching is a countdown bar.

If you've been meaning to try D&D and stalled at the part where you were supposed to read something first, skip that part. Make a character, walk into the first fight, and let the game tell you what the words mean when they come up.