explore / Game development / egorfdrv

Stake Engine

Answer any question about building and shipping a slot game on Stake Engine: the RGS wallet endpoints and how a round is served, how the maths model is built and simulated, how the frontend consumes its events, what approval requires, and the platform facts a game is launched with — currencies, dimensions, languages and URL structure.

29 notes · updated 2026-08-03 · trained 45%

use this brain

# sign in to get a token

$ claude mcp add --transport http mozg \

https://mozg.sh/mcp --header "Authorization: Bearer …"

> use egorfdrv/stake-engine — …

Get a token

What it can answer

30 checks

45^%

▲Math model & simulation6 / 8

▲RGS API & round lifecycle3 / 7

▲Frontend event consumption2 / 6

▲Launch context & platform facts2 / 4

✕Approval & submission0 / 4

✕Architecture fundamentals0 / 1

Inside

Wincap is the per-bet-mode maximum single-round win · Game flow
Bet modes each have their own math model, LUT and book · Game flow
Book id and payoutMultiplier mismatches cause validation errors · Game flow
Stake Engine is stateless — no round history stored · Platform overview
Where RGS, LUT and book questions are documented · Brain routing
RGS selects pre-generated outcomes, never calculates wins live · Platform overview
LUT CSV format: sim_id, weight, payoutMultiplier · Game flow
Book line required fields: id, payoutMultiplier, events · Game flow
Multiplier granularity limited to 0.01x · Game flow
Weighted random selection algorithm used by the RGS · Game flow
Two files per bet mode: LUT (.csv) and Book (.jsonl.zst) · Game flow
Popular Stake Engine frontend stack: Svelte 5 + PixiJS 8 + GSAP · Platform overview
All game logic runs client-side; only server contact is the RGS API · Game flow
Static build is the only hard frontend requirement · Game flow

Licence

CC BY-NC-SA 4.0

Use it, copy it, build on it, with credit. Selling it is not allowed.