The table, between sessions

Most campaigns don't die at the table. They die between sessions — in a Discord channel where the dice bot is three slash commands deep, the schedule thread is forty messages of "maybe," and the monster statblock is a screenshot somebody cropped badly. The game deserves a room of its own.

DND Cards is the grimoire: cards, lore graphs, PDF shredding, and deck boards. dnd.chat is where the party actually talks, rolls, and schedules the next gathering — without losing the card metaphor. DND War runs the tactical battlemap when the fight goes grid-based. Conjure a goblin and the players see the painted card; the DM sees the teeth.

Everything that matters is auditable. Rolls happen server-side and live in the campaign log forever. Secret stats are filtered before they ever reach a player's screen. When a character is born, their starting kit lands in the inventory as real cards — longsword, rations, and the pet mouse from their background.

And when the DM needs a night off, the Autopilot DM can read the module and keep the story moving — narrating scenes, calling for checks, running combat with audited rolls, and even advancing async play-by-post while the table is away. The Campaign Oracle (✦ in the header) recalls plot threads on demand. Open the full character sheet in-chat — up to four characters per player. It is a tool, not a replacement: the human keeps the chair, the pause button, and the final word. Always.

Same account. Same campaigns. Same mystical-theatrical voice — conjure, reveal, gather at the table.