Skip to content

Materials markup

A Materials page is Markdown with a few tricks of its own. Everything below can be typed or made with the editor’s toolbar.

What How to write
Section and subsection ## Title, ### Title
Bold, italic **bold**, *italic*
Lists - item, 1. item
Table | A | B |, a line | --- | --- |, rows
Link to a page [[Title]], [[Title|label]]
Link to a section [[Title#Section]], [[Title#Section#Subsection]]
Link to an NPC, a monster, an item [[Goblin]], [[Mayor Holt|the mayor]]
Link to a website [text](https://…)
A web link without an address (add it later) [the old map]()
GM block :::gm Caption … :::
Read aloud :::read … :::
Coloured text :red[text] (and orange, green, blue, purple)

A line break shows as one, extra empty lines stay. A link by name finds its page or record when the page is saved; a link to something that does not exist yet is dashed — make the NPC, encounter, item or page from it, or point it at an existing page. A section link reads short — as the section’s heading — and tells the whole path in its hint. Images are inserted with the Image button.

## N2. The Old Carp Inn
:::read
Rain drums on the roof. Somewhere below, a door creaks.
:::
The host is [[Mayor Holt|the mayor]]. Upstairs: [[Brightwater#N2. The Old Carp Inn#N2L. Guest rooms|N2L]].
:::gm Secret
The miller is :red[a vampire's thrall].
:::

A ready adventure (a PDF, a text) can be marked up with any AI agent:

  1. Copy the instruction below, give it to the agent and attach the adventure file.
  2. The agent returns the list of pages and their texts.
  3. Create the pages empty — title, folder and tags, in the order of the list — so the links between them find their targets.
  4. Open each page, choose Edit and paste its text.
  5. Insert the images where the agent left [Image: …] notes, and make NPCs and encounters from the dashed links.
You turn the text of a tabletop role-playing adventure into pages of "Materials" in the app Metagame.party — the GM's
notes in Markdown. The attached file is the adventure. Keep all of its content: do not shorten, retell or invent
anything. Write in the adventure's language.
WHAT TO RETURN. First the list of pages in order: folder, title, tags. Then the pages; before each a line
<!-- file: <Folder>/<Title>.md -->, then
---
visibility: gm-only
tags: [tag-1, tag-2]
---
and the page's text. No ids.
HOW TO SPLIT. Folders: "Chapter 1", "Chapter 2"… for the story; "Places" for locations (nested: "Places/Brightwater");
"NPCs" for characters with much text; "Reference" for tables and appendices. One page is one chapter, one location or
one important character, no longer than ~15,000 characters. The introduction is a page "Overview" at the root.
TITLES. 1–120 characters, none of / \ : * ? " < > | [ ] # ^, unique. Keep the adventure's keys: "N2. The Old Carp Inn".
MARKUP. Sections ##, subsections ### (keyed rooms are ### inside the ## of their building); no # or ####. Paragraphs
separated by an empty line; **bold**, *italic*, lists, GitHub tables. Text to read aloud goes into
:::read
…
:::
Everything the players must not know goes into
:::gm Caption
…
:::
(each block closed with a line :::). A danger may be coloured :red[text] (red, orange, green, blue, purple).
LINKS by name only: [[Page title]], [[Title|label]], [[Page#Section]], [[Page#Section#Subsection|N2L]], [[NPC name]],
[[Goblin]] (SRD monsters and spells by their name in the reference in the adventure's language); a website is
[text](https://…). Link the first mention on a page. No page:, npc: or ids.
IMAGES — do not insert; where one goes write *[Image: map of the mill]*. Do not copy stat blocks of SRD monsters — link
by name; write the stats of the adventure's own creatures as a table or a list.
CHECK: all content is there; every :::gm and :::read is closed; titles follow the rules and match the links; no HTML,
no # or #### headings, no ids and no invented links.