tevansandClaude Opus 5
decb3bf930
Eleven files carried "Private VANITY development material — not for sale or distribution", which contradicted the repo the moment it went public. Two replacements, because the files do two different jobs. core/render.mjs *emits* its footer into every generated delve, so that one now says where the document came from rather than restricting what can be done with it — a generated dungeon belongs to whoever generated it. The project's own documents — DESIGN.md, the paper delve, both playtests, the spike report — read as development notes in a public repo. Samples regenerated so they carry the new line. The worksheet and play sheet never had a footer and still do not; they are the GM's own working documents. Module to 0.1.1: the v0.1.0 zip vendors the old render.mjs and would stamp the stale footer on everything it generated. Cutting a version rather than swapping assets under the existing one. 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.