slaguru666andClaude Opus 5
316716e001
GENERATOR_VERSION had sat at 0.1.0 while the emitted object gained the authored layer and the content model moved under it, so a delve file claimed a generator that no longer existed — both samples say 0.1.0 and only one of them has an authored layer. Nothing gates on the stamp, so this is informational only and old files still load. The comment on it now says what it tracks and when to bump it, which is what stopped it being bumped before. test.mjs read ./content/barrow.json relative to the working directory, so it only ran from inside core/ and crashed from the repo root. It now resolves from the module file, matching build-index.mjs and validate-pack.mjs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.