The brief was a tool in Foundry that generates everything on a click and injects
it as a new dungeon. Previously the module could only stage a delve authored at
the desk, and the only way in was a console command — an API with a button glued
on, which is why it looked like nothing was there.
The ⛏ button now opens a form (theme, areas, depth, heroes, deadliness, density,
greed, clock, ending, seed, and whether to build maps and roll encounters), and
Raise the dungeon builds the lot in about five seconds:
• a folder per document type, named for the dungeon
• one scene per area, walls and lighting placed, via the VANITY Forge
• encounter actors, foldered rather than scattered across the world
• a JournalEntry — GM truth, a page per area, the ending — which is the
adventure, and is written to be read cold
The journal is the deliverable. Scenes without it are a pile of maps.
Generating is cheap, so removing had to be. Every document DELVE creates is
stamped with a dungeonId, and a 🗑 button lists what it built and deletes one
dungeon entirely — confirming with exact counts first, and never deleting the
scene the GM is standing in. Colour is not an identifier: it is a Color object,
and a GM may recolour a folder.
Verified live: two dungeons raised from the form and the API, then one removed
cleanly at -3 scenes, -10 actors, -1 journal, -3 folders with nothing else
touched.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
26 lines
1.0 KiB
Markdown
26 lines
1.0 KiB
Markdown
# DELVE — Foundry module
|
|
|
|
Install by copying this directory to `Data/modules/vanity-delve/`, then copying the generator
|
|
into it:
|
|
|
|
cp -R ../core foundry-module/module/core
|
|
|
|
`module/core/` is a verbatim copy of `core/`. It is not vendored in git because the standalone
|
|
generator is the source of truth — if the copy ever needs editing to run inside Foundry, the
|
|
portability claim in DESIGN.md §4 is false.
|
|
|
|
## Using it
|
|
|
|
The ⛏ button in the token controls opens the Forge. Set the parameters, press **Raise the
|
|
dungeon**, and it builds — in one folder per document type:
|
|
|
|
* one scene per area, walls and lighting placed, via the VANITY Forge
|
|
* encounter actors, foldered rather than scattered
|
|
* a JournalEntry: GM truth, one page per area, the ending — this is the adventure
|
|
|
|
Every document is stamped with a `dungeonId`, so the 🗑 button removes a whole dungeon and
|
|
nothing else.
|
|
|
|
Requires the VANITY system **0.10.5+** for quiet output; on older versions the Forge posts its
|
|
own cards over DELVE's and the module says so on startup.
|