slaguru666andClaude Opus 5
d47a167fd0
beat.mjs embeds a pack's roster verbatim into every area, so adding beforeInitiative changed the shape of the emitted delve file — and two files from the same seed could carry different structures under identical stamps. The change originates in the packs, not in the generator's composition, so it belongs to catalogVersion rather than GENERATOR_VERSION: the packs are at schema 2 and a file now stamps barrow@2. The note on GENERATOR_VERSION says which stamp owns which kind of change, since that was the ambiguity. README's test counts were still 39 and silent about the adapter suite. 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.4+ for quiet output; on older versions the Forge posts its own cards over DELVE's and the module says so on startup.