Repository navigation
v0.0.51
Saved workspaces can now open their readable builds when another entry is damaged, and stages show a notice when they were saved with a different game-data version. Passive-tree class starts and point budgets, skill types and weapon conditions now use the loaded catalogs. The WASM JSON schema version is now 21.
Breaking changes
- The WASM JSON schema version is now 21 (was 20). WASM callers and frontends that check the handshake must expect 21 and use the matching engine build and contract, including the new
dataInfo()export. (#365)
Added
- Stages record the game-data version when created or edited and show a notice when it differs from the loaded data. Legacy saves still open, and viewing a stage leaves its saved data version unchanged. (#365)
Changed
- Passive-tree class starts, default travel attributes and point budgets come from the engine and tree metadata. A point budget that cannot be determined shows as unavailable. (#363)
- Weapon conditions follow the loaded weapon catalog. An unknown weapon flag keeps the generic one-handed/two-handed and melee/ranged properties and reports a diagnostic; unsupported type-specific damage remains diagnosed. (#362)
Fixed
- An unreadable saved build, stage or baseline no longer prevents the rest of the workspace from opening. A recovery notice offers the original data for download and pauses automatic saving. Invalid imported workspace files are still rejected as a whole, preserving the current workspace. (#363)
For developers
- Skill types map to engine bits by name, so reordered or larger tables retain their meaning. Missing named types are diagnosed and their scoped rules match no skills. (#361)
- The new WASM
dataInfo()export returns the loaded game-data version, passive-tree label and locales. The engine owns the tree-label mapping and rejects unknown game-version families or mismatched tree metadata before replacing active data. (#365) - Data bumps report per-build, per-stat output changes against a recorded PoBR snapshot. PoB2 reference gates run only when the reference game version matches the loaded data; otherwise they report the mismatch. (#364)
mise run data:acceptruns multi-version smoke checks, corpus calculations, a strict display audit and the data-bump browser smoke test, then reports each result. (#366)
Internal
- Removed the obsolete separate
support_displayinput; gem descriptions use the game and locale packages. The package pins remaingame/0.5.5.5-3andlocale/0.5.5.5-4, with the same runtime identity. (#360) - Updated locale release instructions to review
expect.packagepins before publication, verify the immutable Release and then update PoBR's lock. (#367)
Full diff: v0.0.50...v0.0.51
PoBR WASM v0.0.51
Data: 0.5.5.5; JSON schema: 21; source commit: db166f1.
Build source fingerprint: a1d32366879eb98204a7ffb4dbee6a542204c80880f61c7e62e2a50d01c8c8e6.
| Component | Raw bytes | gzip bytes (level 9) |
|---|---|---|
| pobr_wasm.js | 36833 | 4831 |
| pobr_wasm_bg.wasm | 7643655 | 2814499 |
| Data bundle (80 files) | 83755286 | 6539268 |
| Disk / transfer comparison | MiB |
|---|---|
| PoBR WASM + JS + compressed data | 13.561 |
| pob-web measured reference (same compression convention) | 4.949 |
| PoBR gzip transfer estimate (WASM + JS + data) | 8.925 |
| pob-web gzip transfer estimate (WASM + JS + data) | 4.763 |
| Complete release archive (also includes types, docs, example) | 8.917 |
PoBR / measured reference: 2.74x; gzip transfer: 1.87x.
Reference: krauthaufen/pob-web. Measured from hash-verified deployed Lua WASM, JS and Lua/data bundle. Deployment revision unknown; wrapper source revision does not identify the binary/data. Data is gzip level 9; runtime transfer estimates also gzip WASM/JS. Different datasets and supported mechanics; not a feature-parity or runtime-memory claim.
The reference is Lua WASM + JS + compressed PoB Lua code/data; PoBR compiles calculation code into WASM.
PoBR includes every JSON from the Web data manifest, including catalogs, localization and derived data.
These scopes and supported mechanics differ. This is a size report, not a performance or parity gate.
gzip estimates assume server compression for JS/WASM; the data file is already compressed.
Disk and compressed transfer sizes do not measure runtime memory.