-
Notifications
You must be signed in to change notification settings - Fork 0
Managing the Compendium
Note
For a large compendium, creating standalone entries directly in EncounterPlus is usually the better fit. Authoring standalone items, spells, monsters, or roll tables in MPX instead is aimed at a module that only needs a handful of its own — homebrew content specific to that module.
The Compendium is your module's reusable game content: items, spells, roll tables, and monsters. Each can be authored two ways:
-
Standalone — its own JSON file (
items/,spells/,tables/,monsters/), created from the Compendium section's title bar buttons. -
Inline — written directly inside a page's Markdown, as a fenced
```item/```spell/```monsterblock. A roll table has no fenced form — a plain Markdown table is detected automatically instead (see Roll Tables).
Both forms end up in the same place at build time (items.json, spells.json, etc.), validated the same way, and both show up together in the Compendium panel — an inline entry is just labeled "inline".
An item, spell, or monster carries an attributes object:
-
measurement—imperialormetric. Prefilled automatically from your project settings (mpx.defaultMeasurement/mpx.contentLanguage) the moment an entry is created. After that, it's a fixed value on that entry — changing the project setting later only affects entries created afterward. -
ruleset— always5.5etoday.
This one's specific to inline items, spells, and monsters — a standalone JSON file has no such fields. Every visual element an inline block renders — the illustration, an icon, the Source line, the Tags line — has its own show* boolean (e.g. showImage, showSources) right in its YAML. Each also has a project-wide default in project settings (e.g. mpx.defaultShowItemImage), used whenever the field itself is left out of the block. Setting the field explicitly, on any individual block, always overrides the project default.
Snippets — the fast way to insert any of these, inline, without typing the full YAML from memory.