Create a Campaign → Path → Node

RPGLMS content is a tree. A House (the course) holds Campaigns (units); a Campaign holds Paths (chapters); each path holds Nodes (lessons); and each node is a run of Checks (lesson steps) closed by an Engagement quiz. Any authenticated user, including Free, can create a course and author this tree by hand; only AI generation requires an upgrade.

There are two doors

Which questions you’re asked depends on where you started, and each door has already answered “which course” by the time you tap it:

• Create House (Course) — from a top-level surface (My Houses, Base Camp, the drawer). Mints a new course and its first unit. Four steps.
• Create Campaign (Unit) — from a course’s own screen. Files a new unit into the course you’re standing in. The same steps minus the course act: two.

Everything below walks the first door.

Step 1 — the House

1. Open My Houses and start a new course

   Go to My Houses and tap the create control, or Create House (Course) from the empty state (“No Houses yet”). The screen lists Active Houses and Archived Houses, and it is the only place an archived course can be reached and un-archived.

2. Name the course and say what it covers

   The first step is headed What you’re teaching — “What this House is called, what it covers, and who it is for.” Enter a House Name, then its Subject and Audience.

   The course’s name is the only name in the hierarchy you write by hand. A unit has no title field at all: its Framing Concept is its identity, just as a Path’s Guiding Question is the Path’s.

   Capture pendingThe first step of Create House (Course) showing the House Name, Subject and Audience fields1440 × 900 · 16:10

3. Set the Lore, or leave the default

   The last thing on this step is Lore — “The Lore your new House plays in — edit it to make it yours.” It opens showing the built-in world, read-only and badged as the default; editing it opens the Lore editor and the result is attached to the course when it’s minted.

   Lore belongs to the course, which is why it’s asked here and not on the unit step: one world all year, and every unit plays inside it. A course with no Lore authored plays in the Default world — a legal state, not an unfinished one. See Setup & Use Lore.

Step 2 — how you want to build it

1. Pick manual or the wizard

   How you want to build it — “Author the campaign yourself, or answer a few questions and let the wizard propose one for you to review.” Two cards:

   • Build it myself — you author every step. This is the route the rest of this page follows.
   • Build it with the wizard — the wizard opens with a learning-path request already written for you to review before anything is saved. See Build a whole campaign with AI.

   Tapping a card both chooses and advances, but Next stays available, so going Back and carrying on without re-tapping works.

   If you don’t have AI access the wizard card renders locked rather than hidden — it explains the gate and links to the upgrade, so you learn it here instead of hitting a refusal three screens later.

   Capture pendingThe create stepper's How you want to build it step with the Build it myself and Build it with the wizard cards1440 × 900 · 16:10

Step 3 — the Campaign

1. Give the unit its framing concept

   What you’re teaching — “The concept this campaign is built around.” The Framing Concept is the one required field, and it is the unit’s identity on every surface that names it.

   There is no Title, Subject, Audience or House field here. All four are the House’s; this step asks only what this unit is about.

   Capture pendingThe Campaign step showing the Framing Concept field under the What you're teaching heading1440 × 900 · 16:10

2. Write the Quest

   The story — “The Quest this campaign tells, and the opening your students read.” The Quest is the unit’s narrative, distinct from the course’s Lore: the quest type and tone are picker pills on the opening’s lead-in line, then the opening itself is a fill-in-the-blank passage, then the Boss is built as a character mad-lib.

   Picking a course settles the setting and settles nothing about the arc — so two units sharing one Lore can play very differently.

   Capture pendingThe story section showing the quest type and tone pills above the opening's blanks1440 × 900 · 16:10

3. Add vocabulary (manual only)

   A Vocabulary field follows on the manual route. It’s hidden on the wizard route on purpose — the wizard writes a unit’s vocabulary, so asking for it first would be asking you to do work you just delegated.

Step 4 — the first class

1. Name your first Party and publish

   The last step creates the course’s first Party (cohort) and carries the Ready to Play toggle — “When on, students in this campaign can enter it. Turn it off to keep authoring without anyone playing what you have so far.”

   A Party enrols in the House, so this step belongs to the door that mints one. Filing a unit into an existing course skips it (that course already has its classes) and carries the publish toggle on the unit step instead.

   Clear the name if you don’t want a class yet.

2. Create, and take the join code

   Tap Create. The server mints the course, its first unit, the Lore and the first party in one transaction, then hands you the join code, large enough to read across a room and one tap from the clipboard. One code covers every unit of the course, now and later.

   You then land on the new House — the course page. (On the wizard route you land in the Builder instead, with the wizard already waiting.)

   

The builder

Open a unit and you get the Builder — that unit’s whole structure on one canvas, under a stack of header bands:

1. The locator — which course you’re building in (tap to switch units), and a Lore door to the course’s world.
2. The unit — its framing concept, its quest type, and whether it’s published. Its ⋮ menu holds Edit, AI Wizard, Trash, Restore points and Delete.
3. Vocabulary — expands to its list.
4. Sources — expands to its list.

Below them, the Paths divider lists the chapters, each with its mob and node count. Every row expands in place, so you can work down from the unit to a single node without leaving the page — the order the rest of this guide follows.

Add a path

1. Add a Path from the builder canvas

   On the Paths divider row, tap the + Add control. The Create Path sheet opens.

2. Fill the path form

   The required field is the Guiding Question — it’s the path’s headline in both the builder and the student view. Below it, a single section headed This Path’s Story composes the path’s region, boss/mob, and story together as one fill-in-the-blank passage. Its subtitle spells out the contract: one word per blank, tap a highlighted word to change it, and the passage becomes the description your students read. There’s no separate Description field or two-stage boss/mob picker; this passage text is the path’s Description. You can still set an optional Prerequisite path.

   Under the Guiding Question sit four story token pickers — character, place, force, and vocabulary. Connecting a token binds a name rather than typing one: it resolves into the prose wherever it appears and renders highlighted, so renaming a character once updates every passage that references it.

   

Add a node

1. Open the path to see its nodes

   Expanding a path swaps its summary for a Nodes list. Each node carries its Published state and two count chips, Checks and Questions, so you can see which nodes still need work.

2. Add a Node to the path

   Expand the path and tap Add Node in the Nodes section header (or use the path’s ⋮ menu). The Create Node sheet opens.

3. Fill the node form

   The required field is the Learning Objective — it becomes the node’s title. Optionally set a Prerequisite, a Due Date (Optional), and a published toggle (drip-feed nodes by publishing them when you’re ready).

4. Build its checks and write the Engagement

   Open the node to reveal its Checks section and, under it, the Engagement. The Engagement holds the node’s Questions between an optional intro and outro (Edit Engagement Story); questions are covered in Authoring quizzes. The Checks are the subject of their own page, Build a node’s checks.

Trash, restore points and undoing a delete

Nothing you delete or let the AI overwrite is gone straight away.

• Trash keeps deleted work for 30 days. What you delete from a campaign, such as a path, a node, a check or a question, waits in the campaign’s Trash, with the progress students made on it. Delete something and a Moved to Trash message appears with an Undo; once it has gone, open Trash from the unit’s ⋮ menu. The sheet is headed Deleted from this campaign. Each row says what it was, how long ago it was deleted, how many students have progress there, and what removed it (Teacher, AI save, Restore or Removed). Restore puts it back with its students’ progress; Delete forever removes it for good, and that cannot be undone.
• Restore points are kept before every AI save, the last 10. Open Restore points from the same menu: the sheet is headed Before each AI save, and restoring one (after a Restore this point? confirmation) puts the campaign back as it was then. The receipt after an AI save also carries Undo this save, which does the same for that one save.
• A deleted campaign waits 30 days too, in the House’s Deleted campaigns. See The House page.

Restore points are separate from the wizard’s own Step back, which undoes the wizard’s last few moves inside one session. See Generate objects with the AI Wizard.