mozg.betaSign in

explore / Game development / mozg

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-04 · trained 65%

since last sitting: +3 newly passed — this brain is learning

Ask it things like

answers 20/30 on its latest exam
In what units does the RGS API represent monetary amounts?Currencies & Display✓
How does the RGS determine what bet amounts are valid for a game?Round Lifecycle & Math Model✓
Where does the mathematical fairness of a slot game's outcomes come from?Round Lifecycle & Math Model✓
What does the authenticate endpoint return?Wallet Endpoints & Session✓
Can the RGS URL be hardcoded into your game binary?Wallet Endpoints & Session✓
What is the first API call you must make when a game loads?Wallet Endpoints & Session✓
What is the minimum quality rating required to launch a game on Stake Engine?Approval Requirements✓
What restricted phrases must be replaced in games on stake.us?Approval Requirements✓

What is inside

asking this brain searches all 6
Stake Engine · AI integrationAnswer how to use Stake Engine's own AI tooling: what its MCP server exposes, how to connect it, and what the Hayden agent is for.38 notes86%Stake Engine · ApprovalAnswer what a game must satisfy before Stake Engine will approve it: the submission checklist, the maths requirements, the frontend requirements, the RGS requirements, the game tile specification and the quality bar — including the things that get a submission rejected.142 notes63%Stake Engine · Math SDKAnswer questions about building a game's mathematics with the Math SDK: the game format and state machine, how board, lines, ways, cluster, scatter and tumble wins are calculated, how betmodes and distributions are configured, what simulation produces, and which files the toolchain reads and writes.528 notes81%Stake Engine · ReferenceAnswer the flat factual questions: which currencies are supported and how their minor units work, the required game dimensions, the supported languages, what social mode changes, and the structure of the URLs a game is launched with.83 notes92%Stake Engine · RGS APIAnswer questions about the RGS wallet endpoints exactly as they are specified: authenticate, balance, play, end-round, bet-replay and event — the HTTP method and path of each, every request field with its type and whether it is required, the response shape, the error cases, and how amounts are expressed in minor currency units.92 notes88%Stake Engine · Web SDKAnswer questions about building the game frontend with the Web SDK: the file structure of a game, how context and state are shared, how events from the maths are consumed and animated, the UI components provided, and how Storybook is used to develop them.185 notes66%
use this brain
# sign in to get a token
$ claude mcp add --transport http mozg \
https://mozg.sh/mcp --header "Authorization: Bearer …"
> use mozg/stake-engine — …
Get a token

Use this brain

Sign in and add it, and every agent you have connected can read it — nothing to download, and it stays current as the author updates it.

Sign in to add it

What it can answer

30 checks
65%
✓Wallet Endpoints & Session5 / 5
✓Approval Requirements3 / 3
▲Round Lifecycle & Math Model3 / 6
▲Currencies & Display2 / 4
✓Error Handling2 / 2
▲Frontend Event Consumption2 / 3
▲Launch Configuration2 / 5
▲Social Mode (stake.us)1 / 2
exam badge — share this score →

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.