Multi-resolution test view
Run your game side by side at seven built-in resolutions plus any custom size. Every frame is its own session, so QA sees exactly what players will.
The desktop app wraps a production-grade local game server around your math files and your front bundle. Point it at a folder; start spinning.
A drop-in /api/rgs/<game>/wallet server. It reads index.json, lookup tables and books_*.jsonl.zst straight from disk. Books are indexed once per mode, with weighted RNG via binary search, so a wallet call costs microseconds, not a round-trip.
lgs · serving my-game · https://localhost POST /wallet/authenticate 200 POST /wallet/play 200 · 90µs { mode: "base", eventId: 2041, win: 25.00 }
Run your game side by side at seven built-in resolutions plus any custom size. Every frame is its own session, so QA sees exactly what players will.
Server-sent events push every spin to the test view, with per-frame bet history and a last-event strip. The view updates the instant a spin lands.
Pin any (mode, eventId), replay a saved outcome, and keep notable rounds. Min, average and max wins are picked automatically for each mode.
A bundled CA installs into your user trust store. Your game runs on https without browser warnings or manual certificate work.
Share profiles, saved rounds and bookmarks across your team through cloud workspaces, live over SSE.
Push immutable math snapshots with content-addressed dedup: a books file unchanged between revisions is never re-uploaded. Every push gets an RTP diff against the previous revision.
Saved rounds reference (revision, mode, eventId), so a math change never invalidates a bookmark. Replay any recorded round exactly as it happened.
Math is generated by simulations, so the real workflow is CI pushing a revision. The CLI authenticates with a scoped API token and uploads only changed blobs.