How to use AI for D&D campaign prep without ruining the magic

The thing nobody admits about AI in D&D

Most DMs I know have used ChatGPT or Claude or some other model for campaign prep. Almost none of them admit it on r/DnD because the discourse over there will eat you alive. There's a strong "AI is killing creativity" current in the D&D community right now, and not without reason. A lot of AI-generated D&D content I've seen is genuinely bad. Generic, mushy, full of fantasy-mad-libs nonsense like "the ancient kingdom of Eldoria, where shadows whisper secrets to the wind."

But here's what's also true. I have a job, two kids, and three hours on a Tuesday night to prep for Saturday's session. I don't need AI to write my campaign for me. I need it to do the parts of prep that aren't fun and that nobody at my table will ever know I outsourced.

This is a guide to that. The line between "AI helps me prep faster" and "AI makes my game worse." Where it sits, why it sits there, and the workflow I actually use.

What AI is genuinely good at

Most of the value of AI in D&D prep is administrative. Not creative. The model isn't going to write a better story than you. But it's going to take the friction out of the stuff between the story beats.

Stat block riffs. "Give me a stat block for a CR 5 plant creature with regeneration that's vulnerable to fire." The model spits out a working draft in ten seconds. I tweak the numbers, replace the cliché ability name, and ship it. Saves twenty minutes of looking through Volo's.

NPC drafts at volume. When the party walks into a town, I need eight to twelve named NPCs. Innkeeper, blacksmith, two shopkeepers, a priest, a town guard captain, a few rumormongers. I do not want to write twelve unique character voices from scratch every time. AI gives me a starting roster. I keep the two or three I find interesting and rewrite the rest as needed. None of them are going to win an Emmy. That's fine. They're town flavor.

Random table generation. "Make me a d20 table of weird things found in an abandoned alchemist's shop." AI does this in fifteen seconds. Ten of the entries will be okay, five will be great, and five will be cliché. I keep the fifteen and discard the rest. Net win.

Names. "Give me twenty Dwarvish surnames that don't sound like Tolkien." This is the one task I refuse to do without AI anymore. It's tedious, I'm bad at it, and the model is fine at it.

Boilerplate lore exposition. A village's founding story, the standard religious text of a temple, the published history a player might find in a library. This is content the players will skim once and never reference. It needs to exist and feel real. AI handles it.

Recap summaries. Paste your session notes in, ask for a "Previously on..." paragraph for next session. Done in ninety seconds. I read it before the game starts and tweak as needed. No more dreading the recap.

Encounter math. "Three party members at level 5, average AC 17, what's the right CR mix for a hard encounter?" This isn't even creative, it's just a calculator with a chat interface. Some tools do this better than ChatGPT (Kobold Fight Club, Dungeon Diary's encounter builder with its CR-aware monster selection), but if I'm in a pinch and just need a sanity check, AI is fine.

The pattern across all of these: the work is volume-y, low-creativity, and the player will never know whether I or a model wrote it. Town blacksmiths don't need to be precious.

What AI is terrible at

Now the other side. I've seen a lot of DMs lean into AI for things it absolutely cannot do, and the result is always worse than if they'd just winged it.

Improv at the table. Don't pull out your phone and ask Claude what the BBEG says next. The five seconds of latency, the players staring at you, and the resulting sentence will be the worst version of the line. Improv has to come from your gut. If you panic during a player conversation, give the NPC a tic, take a beat, then keep going. Don't reach for the model.

Major plot reveals. The thing that's going to be the central twist of your campaign? Don't outsource it. Even if you don't tell anyone, you'll know. The reveal won't land for you the way it would if you'd written it yourself. And the players, weirdly, can often tell. The plot beats AI generates have a sameness to them, a kind of structural predictability that bleeds through even after you've rewritten the surface.

Voices and signature NPCs. If an NPC is going to recur for ten sessions and the players will love or hate them by the end, that's a hand-crafted character. Write their motivations, their secret, their voice yourself. AI can give you a rough draft to react against, but the final version has to be yours, because you're the one who has to inhabit them at the table.

Stakes and consequence. "What should happen if the players fail this skill check?" Don't ask the model. The right answer depends on your table, your tone, the season of the campaign, and what the players have invested in. The model doesn't know any of that. It will give you a generic "they take damage and lose a clue" answer that doesn't fit your moment.

Anything where the player's specific actions are the input. Player A bargained the price down. Player B threatened the merchant. Player C is wearing the disguise of a faction member. The right NPC reaction depends on three different in-character variables that aren't in any prompt. Just play it from your head.

The throughline: the players are paying you, in time and attention, for your judgment about what should happen at their table. AI doesn't have that judgment. Use it for the things judgment isn't required for.

The workflow I actually run

Here's how a session prep night usually goes for me. Tuesday, ten p.m., kids asleep, Saturday's game three days out.

Step 1, fifteen minutes. Look at last session's notes. What loose threads are open? What did the party say they wanted to do next? Write a one-sentence intent for the session. "The party investigates the temple basement and finds the warlock's lair." That's it.

Step 2, twenty minutes. Sketch the structure. What scenes will probably happen, in roughly what order, with what stakes? I draw a quick branching diagram. Maybe four to six nodes. Each node has a one-line description and a "what if they go off-script" note.

Step 3, thirty to forty minutes. Use AI for the scaffolding. The temple basement needs three NPCs, two encounters, and some lore. I prompt the model:

Give me three NPCs for a temple basement under a corrupt priest's control. One unwilling cultist who's lost faith, one true believer fanatic, one prisoner who used to be an investigator. Stat them as CR 1/2 to 1, give each a one-line motivation and a one-line secret.

The model writes nine lines of okay material. I rewrite the prisoner because that's the one the party will probably interact with most. Total time saved versus writing from scratch: about an hour.

For encounters I either use Dungeon Diary's encounter builder (because it picks balanced creatures and I don't have to do CR math) or I prompt the AI: "Give me a CR 3 encounter for level 4 party using only SRD monsters, set in a temple basement." Either way, fast.

For lore, I ask for the history of the temple. The model gives me 400 words of standard fantasy temple history. I cut it to 80, change two names, and that's now what's in the books the party finds.

Step 4, fifteen minutes. Hand-craft the parts that matter. The corrupt priest is the big bad of this arc. I write his actual dialogue, his moment of revelation, his secret reason for what he's doing. This part is mine, no AI.

Step 5, ten minutes. Write the recap. "Previously on..." paragraph for opening the session. AI drafts it from my session notes, I tweak it.

Total prep: about an hour and forty minutes. Without AI it would have been three to four hours. The quality is the same or better, because I'm spending the saved time on the parts the players actually feel.

Campaign-aware AI versus generic AI

One specific thing I want to call out, because it's the difference between AI prep that works and AI prep that produces slop.

When you ask ChatGPT for an NPC, it has zero context about your campaign. It doesn't know that the city of Brassgate is ruled by an oligarchy of merchant houses, that the Veilkeepers are a faction the party hates, or that one of the party members is secretly a tiefling in disguise. The NPC it generates will be generic because the model is generic.

You can fix this by stuffing context into every prompt. "In my campaign, Brassgate is ruled by..." But that gets old fast, and you'll inevitably forget some piece of context, and the NPC will have a name that contradicts your established naming convention or a faction allegiance that breaks your map.

The better approach is using a tool that already has your campaign in memory. This is something we built Dungeon Diary around, specifically. When the AI generates an NPC, it has access to your existing settlements, factions, lore, and even other NPCs you've already created. It uses vector embeddings on your campaign data so the AI's NPC actually fits the world you've built. The dwarf merchant in Brassgate who sells blacksmithing tools knows about the merchant houses, picks one to be aligned with, and references the right faction conflicts.

This isn't magic. It's just retrieval augmented generation, the same technique enterprise AI products use. But for D&D specifically it's the difference between "AI gave me a generic dwarf" and "AI gave me a dwarf who feels like he was always part of my campaign."

You can replicate a weaker version of this with raw ChatGPT by maintaining a campaign bible document and pasting relevant sections into every prompt. It works, it's just more friction. The choice is yours.

A few honest caveats

I'm not arguing every DM should use AI. If you genuinely enjoy writing twelve named NPCs from scratch, do that. The point isn't to optimize prep time below some threshold. The point is to spend your prep time on the parts of the game you most enjoy and that most affect the table.

I'm also not arguing AI is going to replace DMs. I've seen experiments where an AI runs the DM role end to end. They're impressive demos and bad games. The DM job is improvisation under pressure with full context about five specific humans at a table. We're nowhere near AI doing that well, and I'm not sure we'll get there in a decade. But that's a separate post.

What I am arguing: the question "should I use AI for D&D prep" has a clear answer if you separate the boring 80 percent of prep from the 20 percent where your judgment matters. AI for the 80, you for the 20. That's the rule, and it's been holding up at my table for two years.

If you want to try this with a tool built for it, Dungeon Diary is what I'd reach for. The AI generation is campaign-aware out of the box, and the encounter builder, NPC tracker, and quest chains are designed to give you the structure to plug AI output into without it feeling like a mess. But honestly, even with raw ChatGPT and a Notion doc, you can get most of the way there. The workflow is what matters, not the tool.

Either way, stop pretending AI either solves D&D or ruins it. Both of those takes are too tidy. The truth is in the middle, like usual.