Choose campaign
Open the campaign selector and choose the campaign you want DNDMind to use. If it says No active campaigns, click New or restore one from Archived.
The active campaign appears at the top.
Campaign areaTable guide
Learn the exact workflow: choose a campaign, turn on the right context, send a focused prompt, review sources and tools, then save the useful card.
5 min
Setup
7
Modes
14+
Prompts
First 5 Minutes
Open the campaign selector and choose the campaign you want DNDMind to use. If it says No active campaigns, click New or restore one from Archived.
The active campaign appears at the top.
Campaign areaReview or update character level, HP, AC, class, and notes.
Encounter prompts can account for party strength.
Notes areaSearch SRD rules at the top, or upload and paste campaign lore, homebrew, and notes below.
Rules questions can return citations, and campaign notes become searchable.
Campaign areaAdd major facts, rumors, theories, retcons, and unresolved hooks as proposed continuity.
Canon stays separate from ideas that are only possible or suspected.
Notes areaPaste raw notes, save them, then summarize.
NPCs, quests, locations, and hooks become campaign memory.
Notes areaPick a mode, set context toggles, and send a command.
DNDMind answers with text, sources, tool results, or cards.
Command ConsoleUse suggested actions on character, NPC, quest, location, encounter, hook, session, or continuity cards.
Characters can join the party list. Other useful cards become campaign memory or proposed continuity.
Chat workspaceCheck citations, tool results, and saved cards before using them at the table.
You can see what DNDMind used and decide what to keep.
Chat workspaceTutorial
Goal
Generate and save one useful encounter using campaign memory and party context.
Expected result
The center workspace shows an Encounter Briefing, tool result, memory or citation context, and a structured encounter card.
Screen Map
Choose, create, edit, archive, or restore campaigns; open Rules and Campaign Knowledge; navigate app areas; and return to this manual. On phones, use the Campaign tab.
Read the chat timeline, generated cards, citations, tool results, and save actions. On phones, use the Chat tab.
Use combat, saved encounters, continuity, dice, tonight's prep, session notes, party details, and campaign memory. On phones, use the Notes tab.
Type your request, choose a mode, set context toggles, use Spark, and send.
Decide the kind of AI task. Use Rules for sourced rules answers, Encounter for combat design, NPC for non-player characters, Character for party-ready characters, Recap for campaign history, Summarize for notes, and Auto when the task mixes categories.
Decide what information the AI can use. Turn on Campaign Memory for saved story context and continuity, Party Info for party-aware answers, and Rules for citations from ready-to-use documents.
Type the instruction you want DNDMind to perform, then click Send. Specific prompts produce better cards and fewer follow-up questions.
Reusable results such as characters, NPCs, quests, locations, encounters, and summaries. Save character cards to the party list and save other useful cards as campaign memory.
Calculations or app actions performed by the system, such as dice rolls, rules search, memory search, and encounter checks.
Source references showing which knowledge entry or campaign memory DNDMind used for the answer.
Sources
Campaign Knowledge is where you add source text for the active campaign: rules, lore, NPCs, locations, quests, homebrew, or session notes. DNDMind can search these entries and cite them when the matching context toggle is enabled.
Built-in 2014 SRD 5.1 rules search for quick cited lookups, separate from your campaign notes.
Searchable SRD monster stat blocks that can be copied into encounter plans or active combat.
Rules references for cited rulings, such as advantage, conditions, actions, spells, or table procedures.
Custom table rules, house mechanics, custom monsters, custom items, or setting-specific mechanics.
Names, motives, secrets, relationships, recurring behavior, and hooks tied to campaign characters.
Places, factions, dangers, clues, rumors, and details the party may return to later.
Objectives, status, complications, rewards, unresolved hooks, and what changed during play.
Factions, history, gods, politics, prophecies, and world truths that should stay consistent.
Raw or cleaned notes from play that should become searchable campaign context.
Supported uploads are .txt and .md files up to 2 MB. Pasted notes work too.
Rules
Rules references you want cited in answers.
Session Notes
Raw notes from play that should become searchable context.
NPC
Non-player character details, secrets, relationships, and hooks.
Location
Places, points of interest, hazards, and clues.
Quest
Objectives, status, complications, and rewards.
Campaign Lore
Factions, history, world facts, rumors, and long-running truths.
Built-In References
The top of Campaign Knowledge includes the imported 2014 SRD 5.1 rules corpus. SRD results are global official references; Campaign Knowledge entries are your campaign's own material.
Use terms like advantage, cover, concentration, opportunity attack, or death saves. Click Use when you want that citation in the command console.
Browse common SRD actions, bonus actions, reactions, conditions, concentration, and turn-economy references.
Search by name, type, size, or CR range. Review AC, HP, XP, ability scores, traits, actions, reactions, legendary actions, and citation details.
Copies the selected monster into the encounter plan you are editing.
Copies the selected monster into active combat with HP, AC, traits, actions, and source details.
Search a rules phrase, review matching SRD entries, then click Use to place that citation into the command console before sending your question.
Adding a monster copies its SRD stats into an encounter or combat. Later HP and note changes do not edit the SRD library.
Campaign Truth
Continuity is the campaign truth board. Use it to separate canon facts from proposed ideas, rumors, theories, retcons, contradictions, and unresolved hooks.
A confirmed truth, such as who holds a title or what happened to an NPC.
Something that happened at a known point in the campaign.
An unresolved thread the party may pursue.
Something characters heard but have not confirmed.
A player or DM theory that should not be treated as canon yet.
A change in a faction's goal, power, leadership, or relationship.
An intentional correction to earlier continuity.
A warning that two pieces of campaign information may conflict.
Saves a new continuity record for review without making it canon.
Marks a proposed record as established campaign truth.
Marks a hook, rumor, theory, contradiction, or retcon as settled.
Hides a record from the active continuity list.
Compares a recap, reveal, or new idea against saved continuity records.
Save a record as proposed first, then canonize only when you are sure it is established at the table. The checker can flag likely conflicts, but the DM still decides what is true.
Live Table State
Combat is a lightweight initiative and table-state tracker. Use it to manage active fights, add party members, add NPCs or monsters, track HP, mark conditions, record concentration, and move through turns.
Creates active combat for the current campaign or session.
Copies party characters into combat as snapshots.
Adds a manual combatant when you do not need the SRD monster library.
Moves backward or forward through initiative and rounds.
Updates HP, temp HP, AC, conditions, concentration, death saves, and notes.
Ends active combat and clears the combat panel.
Open a saved encounter and click Start Combat to snapshot the current party and encounter lineup into active combat.
DNDMind can use active combat as context, but it does not automatically apply damage, end conditions, or sync combat HP back to party characters.
Sources
Context toggles control what information DNDMind may use for the next answer. They do not erase or change saved data; they only shape the prompt you are about to send.
Use when
Turn on for cited rules answers from ready-to-use rules entries.
Skip when
Turn off for freeform story, brainstorming, or answers that do not need rules lookup.
Use when
Turn on when saved NPCs, quests, locations, summaries, continuity, or notes should matter.
Skip when
Turn off when you want a fresh idea that does not depend on this campaign.
Use when
Turn on for encounter balance, tactics, difficulty, or character-aware advice.
Skip when
Turn off when the party is not relevant to the answer.
Use when
Turn on when custom rules or house mechanics should affect the answer.
Skip when
Turn off when you want standard rules or story context only.
Use Rules mode with Rules on. Add Homebrew only when custom rules should affect the ruling.
Use Encounter mode with Campaign Memory and Party Info on.
Use NPC or Auto mode with Campaign Memory on when the answer should fit your campaign.
Use Character mode with Campaign Memory on when a backup PC, rival, or hireling should fit the campaign.
Use Recap mode with Campaign Memory on when you want a table-ready summary of what happened so far.
Use Auto with only the context you need so the answer stays flexible.
Notes Area
The party list helps DNDMind understand who is at the table. Keep it current before asking for encounter balance, tactical advice, character-aware scenes, or party-specific recaps.
Add a player character with name, class, race, level, HP, AC, initiative, passive perception, and notes.
Update character details when levels, AC, class, race, or table notes change.
Track current HP and temporary HP during play so encounter advice can reflect current danger.
Review character progress and add short progress notes tied to the active session.
Quickly increase a character's level after advancement.
Move a character out of the active party list when they leave the table.
Notes Area
My Local Sessions is where you write and save notes for the current browser profile. Session notes are your running table record; Campaign Knowledge is source material you intentionally add for lookup and citations.
Stores the selected session notes for this browser profile.
Turns session notes into a recap and extracted campaign memory.
Removes generated memory tied to the selected session, while keeping the session notes.
Clears both the selected session notes and generated memory.
Deletes the selected saved session and generated memory tied to it.
If the app shows this message, your browser has a temporary copy of the notes you are typing. Click Save when you want them stored as a session.
Beginner Workflow
Step 1
Create Campaign
Where
Campaign area -> Campaign
Do
Expected result
The campaign appears in the selector and its name appears at the top.
Why it matters
DNDMind uses the active campaign to scope memory, sessions, and generated content.
Step 2
Add Party
Where
Notes area -> Party
Do
Expected result
Party members appear in the party list and encounter answers reference party strength.
Why it matters
Party context helps DNDMind tune difficulty and avoid encounters that are too weak or too punishing.
Step 3
Add Campaign Knowledge
Where
Campaign area -> Campaign Knowledge
Do
Expected result
Rules answers include citations from the ready-to-use document.
Why it matters
Campaign Knowledge gives DNDMind source text instead of relying on unsupported memory.
Step 4
Add Session Notes
Where
Notes area -> My Local Sessions
Do
Expected result
The summary appears with extracted campaign objects and useful memory entries.
Why it matters
Session notes turn table events into future context that DNDMind can retrieve.
Step 5
Track Continuity
Where
Notes area -> Continuity
Do
Expected result
DNDMind can keep canon separate from rumors, theories, and draft ideas when Campaign Memory is enabled.
Why it matters
Continuity prevents a useful brainstorm from accidentally becoming campaign truth.
Step 6
Run Combat
Where
Notes area -> Combat
Do
Expected result
DNDMind can see the active fight and offer advice based on the current table state.
Why it matters
Combat is a DM-managed tracker. It helps with live decisions without secretly changing party sheets or monster library records.
Step 7
Ask AI
Where
Bottom Command Console
Do
Expected result
The center workspace shows a response, and may include citations, tool results, or a structured card.
Why it matters
Mode plus context tells DNDMind what kind of answer to produce and which information is allowed.
Step 8
Use Tools
Where
Command Console or Notes area -> Dice
Do
Expected result
The response includes a tool result with the calculation, search result, or action summary.
Why it matters
Tool results make operational work visible so you can trust what happened during play.
Step 9
Save Cards
Where
Chat workspace -> Structured Card
Do
Expected result
Saved characters join the party list. Other saved cards become reusable campaign memory.
Why it matters
Saving is what turns a one-off AI answer into campaign material DNDMind can reuse later.
Step 10
Review Answers
Where
Chat workspace
Do
Expected result
You keep only the content that fits your campaign.
Why it matters
DNDMind is a co-pilot. The DM still decides what becomes true at the table.
Practice Cards
Try This Now
Mode: Rules
Toggles: Rules ON, Campaign Memory optional, Party Info OFF
Prompt to copy
How does advantage work?
Expected result: DNDMind gives a concise rules answer with citations from ready-to-use rules.
Try This Now
Mode: Auto
Toggles: Campaign Memory ON
Prompt to copy
Check whether this reveal contradicts canon: Captain Vey died before Session 4.
Expected result: DNDMind points out related continuity records or likely conflicts for the DM to judge.
Try This Now
Mode: NPC
Toggles: Campaign Memory ON, Party Info optional
Prompt to copy
Generate a suspicious NPC connected to Captain Vey.
Expected result: DNDMind returns an NPC card with role, personality, motivation, secret, and quest hook.
Try This Now
Mode: Character
Toggles: Campaign Memory ON, Party Info optional
Prompt to copy
Generate a level 3 adventurer tied to this campaign who could work as a backup PC, rival, or hireling.
Expected result: DNDMind returns a character card. Save Character adds it to the party list.
Try This Now
Mode: Encounter
Toggles: Campaign Memory ON, Party Info ON
Prompt to copy
Create a medium encounter for this party involving the Ashen Knives.
Expected result: DNDMind returns an encounter briefing, tool result, and structured encounter card.
Try This Now
Mode: Auto
Toggles: Campaign Memory ON, Party Info ON
Prompt to copy
What should the current monster do, given the party HP and conditions?
Expected result: DNDMind uses the active combat snapshot to suggest a table-ready move.
Try This Now
Mode: Summarize
Toggles: Campaign Memory ON
Prompt to copy
Summarize these session notes and extract NPCs, quests, locations, and hooks.
Expected result: DNDMind returns a session summary card and extracted campaign objects to review.
Try This Now
Mode: Auto
Toggles: No context required
Prompt to copy
Roll 1d20+5 for perception.
Expected result: DNDMind shows the roll result and tool trace in the response.
Try This Now
Mode: Recap
Toggles: Campaign Memory ON
Prompt to copy
Recap the campaign so far and list the unresolved hooks.
Expected result: DNDMind returns a table-ready recap based on saved campaign memory.
Try This Now
Mode: Auto
Toggles: Campaign Memory ON
Prompt to copy
Search campaign memory for Captain Vey.
Expected result: DNDMind returns matching memory with citations or context references.
Command Modes
Best for
Mixed tasks and session prep.
Example prompt
Prepare tonight's opening scene based on last session.
Best for
Rules questions that need citations.
Example prompt
How does advantage work?
Best for
Combat and challenge design.
Example prompt
Create a hard ambush for my level 3 party.
Best for
Non-player characters, motives, secrets, and relationship hooks.
Example prompt
Generate a suspicious tavern keeper.
Best for
Backup player characters, rivals, hirelings, and party-ready allies.
Example prompt
Generate a level 3 adventurer tied to this campaign.
Best for
A table-ready recap from saved campaign memory.
Example prompt
Recap the campaign so far and list the open hooks.
Best for
Session notes and extracted hooks.
Example prompt
Summarize this session and extract unresolved hooks.
Structured Cards
Some NPC, character, and encounter cards can include a generated image. Images are optional; you can still save and use the card without one.
Saved Material
Campaign Memory is where saved NPCs, quests, locations, hooks, encounters, and summaries live. Delete saved memory only when you no longer want DNDMind to use it.
Saved encounters appear in their own section and can be deleted when they are no longer useful.
Saved cards become reusable memory that DNDMind can search when Campaign Memory is on.
Hooks can be marked open, rumor, lead, active, resolved, or dropped as the campaign changes.
Summaries and extracted session details can become campaign memory after you summarize notes.
Available, but not currently urgent.
Heard about, but not confirmed.
The party has a usable next step.
Important right now.
Answered or completed.
No longer planned for play.
Copy And Run
Prompt
How should I open tonight's session?
Prompt
What happened at Blackwater Mine?
Prompt
Generate a suspicious NPC connected to Captain Vey.
Prompt
Generate a level 3 adventurer tied to this campaign who could work as a backup PC, rival, or hireling.
Prompt
Create a medium encounter for this party involving the Ashen Knives.
Prompt
Search the SRD monster library for CR 1 undead.
Prompt
What should the current monster do, given the party HP and conditions?
Prompt
Turn this recap into proposed continuity records, but do not canonize anything yet.
Prompt
Check whether this reveal contradicts canon: Captain Vey died before Session 4.
Prompt
Recap the campaign so far and list the unresolved hooks.
Prompt
Roll 1d20+5 for perception.
Prompt
Summarize these session notes and extract NPCs, quests, and hooks.
Prompt
Search campaign memory for Captain Vey.
Prompt
Make this encounter harder but keep it fair.
Browser Sessions
You do not need an account. The browser keeps a local profile for your sessions.
Another browser or incognito window may show a different session list.
Clearing browser storage may hide sessions tied to the previous browser profile.
Use the same browser profile during a campaign so your saved sessions are easy to find.
Table Rhythm
Fix Fast
Problem
Cause
Rules context is off, no rules documents are ready to use, or the prompt did not ask for a sourced ruling.
Fix
Problem
Cause
Homebrew is off, or the custom rule was added as the wrong document type.
Fix
Problem
Cause
The file may be the wrong type, too large, empty, or missing a clear title.
Fix
Problem
Cause
You may be using a different browser, incognito window, or local browser profile.
Fix
Problem
Cause
No campaign has been created yet, or all campaigns are currently archived.
Fix
Problem
Cause
The active campaign has little saved memory, or Campaign Memory is off.
Fix
Problem
Cause
The rumor may be saved in broad campaign memory, or a continuity record may have been canonized too early.
Fix
Problem
Cause
Your proposed text matches an existing canon record, retcon, contradiction, or timing marker.
Fix
Problem
Cause
Party Info is off or party members are missing details.
Fix
Problem
Cause
Combatants are snapshots. Updating HP or conditions inside combat does not update the saved party character.
Fix
Problem
Cause
There may be no active encounter edit form, no active combat, or no SRD monster matching the search filters.
Fix
Problem
Cause
The active campaign is not the one you intended.
Fix
Problem
Cause
The campaign was moved out of the active list, but it was not deleted.
Fix
Problem
Cause
Image generation may be off, busy, or unavailable for that card type.
Fix
Problem
Cause
Clear Session Memory removed generated memory tied to the selected session.
Fix
Problem
Cause
The app may need an AI provider setting changed by the person running it.
Fix
Plain Language
The campaign currently selected in the Campaign area.
A campaign moved out of the active list but still available to restore later.
Source text added to a campaign so DNDMind can search and cite it.
Saved notes, NPCs, quests, locations, encounters, and summaries DNDMind can use later.
Mark a proposed continuity record as established campaign truth.
A copy of party or monster state used inside active combat. Changes there do not automatically update the original party character or SRD monster.
The stricter campaign truth layer for facts, timeline events, hooks, rumors, theories, faction developments, retcons, and contradictions.
A tool that compares a recap, reveal, or new idea against saved continuity records.
A switch that controls which saved information DNDMind may use for the next prompt.
A local browser copy of session notes while you type.
Searchable SRD monster stat blocks that can be copied into encounter plans or active combat.
A continuity record saved for review but not yet treated as canon.
An intentional correction to earlier campaign continuity.
The System Reference Document rules content used by the built-in rules and monster references.
A mode button that tells DNDMind what kind of answer to produce.
A generated character, NPC, quest, location, encounter, or summary that you can save.
An unresolved thread, rumor, lead, or active plot point saved in campaign memory.
A visible result from an action such as a dice roll, rules search, homebrew search, or memory search.
A source reference attached to an answer so you can see where context came from.
The prompt helper that drafts a request for the current mode and context.
The browser-based identity used to keep sessions separate.