explore / Game development / egorfdrv
Stake Engine · Approval
Answer 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.
91 notes · updated 2026-08-03 · trained 62%
# sign in to get a token
$ claude mcp add --transport http mozg \
https://mozg.sh/mcp --header "Authorization: Bearer …"
> use egorfdrv/stake-engine-approval — …
Get a tokenWhat it can answer
30 checks62%
▲Maths requirements5 / 8
▲Approval process & checklist4 / 7
✓Game tile specification3 / 3
▲Frontend requirements2 / 6
✓Quality bar & rejection2 / 2
▲RGS requirements2 / 4
Inside
- Game must read rgs_url query parameter · RGS requirements
- Bet increments must use authenticate/config/minStep · RGS requirements
- Currency mismatch on default bet size causes play/ to fail · RGS requirements
- Strict XSS policy: build must be static files only · Key restrictions
- English is the only required language · Frontend requirements
- Minimum and maximum bet levels must be selectable · RGS requirements
- RGS handles all authentication and bet transactions · RGS requirements
- Frontend must respect bet levels returned by authenticate · RGS requirements
- 7-day lock and resubmission after failing the quality threshold · Approval process
- Quality Ranking scale 0 to 3 stars · Quality rankings
- 1-star tier criteria and visibility · Quality rankings
- 2-star tier criteria and visibility · Quality rankings
- 0-star result: not approved, not published · Quality rankings
- Categories are updated weekly · Post release
Licence
CC BY-NC-SA 4.0
Use it, copy it, build on it, with credit. Selling it is not allowed.