Characters — the PC builder

the engine's own builder contract, as a web tool · formulas from PHB1 via PcBuilder · power slots validated against the p.29 table · export is loader JSON

class

race

level

name

scores — STR · DEX · CON · INT · WIS · CHA

point-buy mode (PHB1 p.17)

level-up increases — PHB1 p.28

true totals — rolled + level + racial + gear + other

armor

shield

start from a template — canonical PCs, fork and customize or edit a saved PC — the game database (version-chained)

Powers — PHB1 p.29 slots

Feats —

Skills —

Retrains — one swap per level-up (PHB1 p.28)

every level-up grants one swap — power or feat (skill swaps wait on a skill-training model). The replacement must be no higher level than the retrain level.

Equipment

weapon

armor item

neck

stat-wired slots only (armor/weapon/neck, PHB1 p.249 enhancement math). An armor item overrides the armor base via its armorTypes — the engine resolves the same way.

options

loader JSON (what the engine reads)

Saved roster — this browser (localStorage) + the game database (every save a version)

Import accepts single unit JSON or an exported roster array. Everything stays in your browser — the site is static.

The builder contract is the CLI's (

--build-pc class:level:STR,DEX,CON,
    INT,WIS,CHA[:armor[:shield]]] --powers ids --equip ids

); this page implements the same math (HP/surges/defenses per PHB1 class traits, the armor and shield tables, p.29 slot validation) and emits the same loader JSON. The power pool, item catalog, and slot table are generated from the repo's verified data corpus at deploy time — they cannot drift. Server-side saves and run requests arrive together at P-E.

Characters — the PC builder

Powers — PHB1 p.29 slots

Feats —

Selections

Skills —

Retrains — one swap per level-up (PHB1 p.28)

Equipment

Saved roster — this browser (localStorage) + the game database (every save a version)