Skip to content

Writing a campaign frame

A campaign frame is a premise any table can pick up and play: the pitch you read aloud, the tone and themes, what makes the setting different, the trouble that starts the first session, and the questions to ask at session zero. You write it without a world, then share it and print it.

  1. Open Campaign frames (it’s in the command menu, or go to /app/frames).

  2. Choose Start a frame.

  3. Pick an outline:

    • Official outline (recommended): every part the Daggerheart SRD lists for a frame, in its order, plus a campaign map. Remove what you don’t need.
    • Blank: just the pitch and session zero. Add the rest as you go.
  4. Give it a title and choose Start writing. The editor opens.

On the left is the outline: At a glance, then every section in reading order. The part you choose opens in the middle. On the right, Checks and the Guide (on a phone, these open from the buttons under the header).

Everything saves as you go; the header says Saved, Saving… or Unsaved changes.

What a reader sees first, on the frame’s card and at the top of its page:

  • Title: short and memorable. Darrington Press’s licence doesn’t allow “Daggerheart” (or their other trademarks) in a frame’s title or a section’s title, so the editor stops you publishing with one. Every frame’s pages say “Daggerheart™ Compatible” for you.
  • Concept: one sentence that sums the frame up.
  • Complexity: how far the frame’s rules move from the core game, from 1 Light to 4 Heavy. Choose it again to leave it unset.
  • Tone and Themes: a few words each. Type one and press return.
  • Touchstones: films, books, games and music with the same feel, with what to take from each.
  • Cover: choose an image from your library, then click or drag where its subject is. The card and the page’s header crop around that point.
  • Credits: co-authors, the cover artist, and anyone else to thank.

Each section has a title, and three settings:

  • Who reads it: Everyone, or GM only. GM-only sections never reach players: not on the frame’s page, not in a player’s print, not at the table.
  • Optional: a table can switch it off for their campaign.
  • Starts a new page: in print, it opens on a fresh page.

Write in the box below them. Type / for headings, lists, tables, columns, read-aloud text, sidebars, rules boxes, stat blocks and links to the SRD. Dice notation like 2d12 becomes a roll.

Reorder sections by dragging the handle beside each one in the outline. With a keyboard: focus the handle, press Space, move with the arrow keys, and press Space again.

Add a section from the bottom of the outline: one of your own, or a part of the official outline you removed, which goes back where the outline has it.

Remove a section with Remove at the top of it. Published versions keep theirs.

The session zero section has a list of questions. For each one, choose:

  • Who sees it: everyone, or the GM only.
  • Who answers: The table (one answer) or Each player.
  • Lines to answer on: how much room the printed worksheet leaves.

Drag questions into order the same way as sections. Changing a question’s wording keeps it the same question, so a table’s answers stay with it.

Every field and section has a lightbulb. Choose it to open a tip about that part: what it’s for, what to ask yourself, what to watch for, and, where the SRD describes the part, its own line. The Guide tab lists every tip in outline order.

The tips follow the campaign-frame advice in the Daggerheart Homebrew Kit (Darrington Press), in PostRoll’s own words, with a link to the Kit.

Know your way around already? Hide tips in the header. The editor remembers it in this browser.

The Checks tab keeps a running list as you write:

  • Suggestions follow the shape the Homebrew Kit suggests: a pitch that reads aloud in one go, three to six tone words, two or more touchstones, at least three session-zero questions, and so on. Take them or leave them.
  • Stops publishing: a Darrington Press trademark in the title or a section title. Rename it to publish.

Go to it takes you to the field or section a check is about.

  1. Choose Publish in the header. Everything is saved first.

  2. Read what changed since the last version.

  3. Choose a version number. The suggested one says what kind of change it is: fixes and small changes (1.0.1), something added (1.1.0), or something removed or reworked (2.0.0). You can type another, as long as it’s newer.

  4. Add notes for the tables that use the frame, if you like, and choose Publish.

A published version is fixed: everyone reading it reads exactly that. Your next change opens a new draft, and the frame’s page offers every version in its version picker.

Change the same part in two tabs, or on two devices, and the editor asks before anything is lost: Keep my changes saves yours over the other copy, Take theirs shows the frame as it is now. If the connection drops, your changes stay on the page and are sent again when it’s back.

The gear in the header opens the frame’s settings: who reads its GM sections (see Sharing a frame), content warnings, its licence, and retiring or deleting it. They aren’t part of a version, so a change reaches every reader at once.

Write | Design at the top switches to designing the frame’s printed pages, and Export PDF prints it, or saves it as a PDF, from your browser.