-
Notifications
You must be signed in to change notification settings - Fork 0
Creating Module Content Maps and Encounters
Unlike a page or group, MPX doesn't let you author a map or encounter's own content — that's built inside the EncounterPlus app itself (placing tokens, setting the grid, adding combatants). What MPX manages is a reference: a small file pointing to a .zip you've exported from EncounterPlus, which gets bundled into your module at build time.
In EncounterPlus, export the map or encounter you want to include — this produces a .zip file. Save it somewhere you can find it.
In the Module section's title bar, click Create Map Reference or Create Encounter Reference. A prompt asks for a name (pre-filled with "New map" or "New encounter", which you can keep or replace) — confirm it, and MPX creates maps/<slug>.json (or encounters/<slug>.json) and opens it.
{
"name": "Lighthouse Interior",
"slug": "lighthouse-interior",
"rank": 0,
"parent": "",
"path": "maps/lighthouse-interior.zip",
"descr": ""
}| Field | Required | Format | Purpose |
|---|---|---|---|
name |
Yes | Text | Display name in the Module tree. This can differ from the name set inside the EncounterPlus export itself — MPX's own name wins. |
slug |
Yes | lowercase, digits, hyphens only | Generated from name at creation. |
rank |
Yes | Number | Order among its siblings. |
parent |
No | A page's or group's slug, or empty |
Nest under that page or group, or leave empty. A map or encounter can't be a parent. |
path |
Yes |
maps/<file>.zip or encounters/<file>.zip
|
Where your exported .zip lives, relative to the project root. |
descr |
No | Text | A short description, shown in the Module tree alongside the entry. |
Move the .zip you exported into the project's maps/ (or encounters/) folder, matching the path field exactly — same file name, same folder.
That covers your module's structure. Move on to Managing the Compendium for items, spells, roll tables, and monsters.