Content pack and world packs
The content pack
A read-only SQLite database of everything the character builder, the workshop and the Dungeon Master can reach beyond the SRD: about 1,800 spells, 2,000 items, 3,200 monsters, 220 subclasses, 74 lineages, 140 feats and 52 backgrounds, built from Open5e in three layers (Open5e v1, an Open5e v2 backfill including SRD 5.2, and an authored expanded layer stored under generic names). Every server release attaches it as open5e.sqlite.gz; the Docker image and the apps carry it. A host install builds it with node scripts/import-open5e.mjs or points CONTENT_DB_PATH at the downloaded file.
Every option the pack adds names its book in the builder (races grouped by book, "From Adventurer's Guide" groups, the source on each spell tile), and the pack's SRD 5.2 rows are not offered to the 2014 rules engine. Without a pack the server boots on the bundled SRD 5.1 data and the builder says "content pack missing" instead of "nothing matched". Players will find most spells, subclasses and monsters absent.
Bundled data
Independent of the pack: the 13 SRD classes and 13 SRD backgrounds, 31 races, the 36 genre classes and 36 genre backgrounds that belong to the seven settings, all 319 SRD spells with their parsed mechanics, and the whole SRD 5.1 as the rulebook (/rulebook, also a book button at the table). These ship inside the server and the apps.
Homebrew
Homebrew entries are rows owned by a user, made in the workshop's Homebrew tool or a ruleset, and merged into every picker with a flag. They live in the database, not the pack, and travel in workshop bundles.
World packs
A world pack (a campaign plugin) is one JSON manifest that renames the rules into a setting: races, classes, backgrounds, spells, items, features, monsters, factions, locations, hooks, a glossary, name seeds, and a paragraph of flavour that steers the narrator. It is a pure name mapping: sheets keep the canonical names underneath, so a character crosses worlds intact. A pack can carry art, a cover and a picture for each race, class, background, monster, place and faction, inside the manifest (256 KB per picture, 16 MB per manifest).
- Choosing one: at campaign creation, from the packs installed on the server. The cover shows in the creator and the lobby; a monster's picture leads bestiary tiles; a race or class picture stands in as a portrait until one is painted.
- Installing: Admin, Campaign plugins, browse the registry and install. Only administrators install. The default registry lists 27 community packs with full art sets; another registry URL, or
off, is a setting. - Making one: a workshop's Plugin tool builds a pack with guided setup and catalogue pickers, then downloads it or installs it on this server. See The workshop.
- Prepared worlds in the registry install as workshops, with maps, cast and lore ready to import.
Installed packs live under data/worlds/; the one bundled pack is original work. A pack that names a rights holder carries an unofficial-work notice wherever it shows.
Licences
The application is MIT. Rules data derives from the SRD 5.1 under CC-BY-4.0; the imported documents' licences (CC-BY, OGL, other open content) are listed on the server's /licenses page from the pack itself. Expanded options are original wording. Sound library recordings are public domain or under attribution licences, each credited on the same page. The full statement is in the repository's LICENSES.md.