tevansandClaude Opus 5
592d540910
Installing by manifest URL failed on a remote server: [Module.vanity-delve] validation errors: relationships: systems: ArrayField 0: type: requires is not a valid choice The relationship entry used type: "requires". In Foundry's schema `type` is the PACKAGE type — module, system or world — and the relationship kind is expressed by which array the entry sits in. So the correct value is "system". The entry now also carries VANITY's manifest URL, so Foundry can offer to install the system rather than just refusing. This was never caught because the module had only ever been installed by copying files into Data/modules by hand. The validator that rejected it only runs on the manifest-install path, so every local test passed while the published artifact could not be installed at all — the same shape as the scene-control hook bug, where testing the layer below the interface hid a failure in the interface. 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.