Bertini's Vault
Build a D&D 5e character on the web, then import it into Foundry VTT with a
short code.
Building a character inside Foundry is already solved — Plutonium ships a
complete in-Foundry creator. This is for everything away from the table: in a
browser, saved to an account, with a cheatsheet for actually playing.
Offline use, local files and an installed application are the downloadable
product's job, not this one's. See
Relationship to El Faro del Alba.
How the import works
A build travels as a list of 5etools references, not as character data. The
Foundry module resolves each reference through Plutonium,
which returns the real dnd5e document — with working activities, damage and
icons, because we never build the item ourselves.
Layout
apps/web the builder wizard
apps/worker the store: saves a build, returns it by code, keeps accounts
apps/foundry-module resolves a build's references into a real actor
apps/api legacy dataset BFF, being retired
packages/vetools-ref reference triples, sources, 2014/2024 split
packages/vetools-index the browsing index shipped with the app
packages/contracts CharacterBuild and ImportPayload
packages/domain 5e rules and derivations
packages/foundry-exporter legacy, fabricates items, being replaced
packages/data-engine legacy catalog, superseded by vetools-index
scripts/ templates/ styles/ the legacy root Foundry module
apps/foundry-module is the working import path, and has been since it created
its first actors on 2026-08-24. The legacy root module still ships beside it and
still declares the same module id in the root module.json; retiring it is
open work, tracked in ARCHITECTURE-PLAN.md.
Verifying
corepack pnpm mvp:verify
Builds the shared packages, runs every suite, and regenerates the Foundry
fixtures. It passes from a clean checkout.
Individual entrypoints: verify:env, packages:build, web:verify,
foundry:verify, release:ready.
Regenerating data
Both generated artifacts come from a Plutonium install:
node scripts/extract-vetools-sources.mjs <plutonium>/js/Bundle.js <out.mjs>
corepack pnpm vetools:index <plutonium>/data
Requirements
Plutonium 2.17.2 requires Foundry v14, dnd5e 5.3.x and lib-wrapper.
apps/foundry-module/module.json targets exactly that: Foundry 14 verified,
dnd5e 5.3.0 minimum and 5.3.3 verified, with Plutonium declared as required.
Verified against a live install — Foundry v14.367, dnd5e 5.3.3.
The root module.json is the legacy module and still declares Foundry 12-13.
It is not the import path.
