BG3 character sheet
A local browser character-sheet generator with a vendored BG3 save parser. This is a work in progress, not yet a fully accurate save-to-sheet exporter.
Run
npm ci
npm run build
npm start
Open http://127.0.0.1:8765/. Import an .lsv file, select a character, and save a JSON backup. Saves are parsed in a browser worker and are not uploaded. Use a trusted static host when deploying.
Deployments on Vercel record page views through Vercel Web Analytics. It counts visits only: nothing about an imported save is sent, and it is inert outside Vercel, so the local preview reports nothing.
Current limitations
- Live inventory containers determine equipped and carried items when a character owner can be identified. Nested bags are traversed without duplication. Unsupported or ambiguous ownership falls back to upstream attribution.
- Gold uses per-entity stack records with corrected heap offsets. Changed stack bytes are regression-tested; no character-specific values are substituted. Missing attribution leaves gold blank.
- Saved level-up skill selections, expertise, backgrounds and fighting styles are decoded where the build can be uniquely matched. Starting-class saving throws and supported background/racial proficiency grants are applied. Additional feat and temporary-effect grants remain incomplete; see MECHANICS.md.
- Armour and weapon calculations describe base properties; active boosts, conditional effects and some special items require further decoding. Armour class is derived from equipped body armour and shields; unrecognised armour leaves it blank with a warning rather than showing a wrong total.
- Active conditions are imported from each character's status list. Permanent item and flag statuses are left out; the remainder are transcribed from the game's internal ids, so an unusual status may read a little raw.
- Typography uses three self-hosted open-licensed families: Yeseva One for the masthead, Alegreya SC for section headings and Alegreya Sans for labels and figures. Body copy stays on Georgia, and the character name is set in Kalam so it reads as handwriting filled onto a printed form. No third-party font request is made; see THIRD_PARTY.md.
- Experience is shown as progress within the current level, matching the game's own tooltip rather than the cumulative total the save stores. A total past the next threshold shows a level up as ready; only a total below its level's floor withholds the remaining figure instead of guessing.
- Ordinary and pact slots are stored separately. Older JSON backups with
(pact) values migrate automatically when loaded.
- PDF export uses the browser print dialogue. The spell and inventory lists build their columns in the markup rather than with CSS multi-column, which WebKit mis-fragments when printing: Safari laid the second sheet out at roughly twice its height and spilled it onto a third page, while Chrome printed the same markup on two. Long content can still exceed two pages. Turn off browser headers and footers in the dialogue.
Verification
npm test runs adapter regression tests. npm run build rebuilds the browser worker and importer. npm run test:browser runs browser import checks after starting the server; set CHROME_PATH if needed. Browser integration fixtures live in the upstream checkout and are excluded from Git. A fresh clone must obtain those fixtures separately.
Private exports, saves, generated PDFs and preview screenshots are excluded from Git. See THIRD_PARTY.md for the vendored source revision and modifications. The parser is MIT licensed, declared in upstream's pyproject.toml rather than in a LICENSE file and recorded in vendor/bg3-savefile-parser/LICENCE-NOTE.md. The game-data table it ships alongside is Larian's content and is not covered by that grant.
Deploy to Vercel
Import the solnicol/BG3 GitHub repository in Vercel. The committed vercel.json uses npm run build and publishes only dist/. No environment variables, database or server are needed. Parsing remains in the visitor’s browser.
Changes pushed to the connected production branch deploy automatically. The local preview remains available through npm start.
