new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Packs · For slot studios

A failed submission
costs more than a year of this.

The rejection arrives with a line number and no context. Somebody re-reads the approval rules, somebody else argues about what the RGS contract actually said, and the build slips a fortnight — again, over something that was written down the whole time.

These are 18 brains your agents query over MCP instead of guessing: the approval checklist, the compliance rules per jurisdiction, the RGS lifecycle, the math SDK, the animation and art direction. 4,251 notes. Median exam score 86 — and every failed question is listed publicly, so the agent is told the gaps before it searches.

Buy the pack — $99.00 onceRead the brains first

What your agents get to read

Scores are read live from the catalogue when this page renders. They move — that is the point of having them.

Slot Studio · ComplianceAnswer what a casino or social-casino game may and may not say, show and promise: stake.us and sweepstakes wording rules, prohibited terms and their safe replacements, jurisdiction gating, paytable and rules copy requirements, responsible-gambling obligations, and the exact messaging that gets a submission or a page rejected.51 notes 97%Stake Approval PlaybookAnswer what it takes to pass Stake Engine review: the approval checklist as reviewers apply it, release preflight gates, paytable and win-ladder audits, game-feel-versus-math review, the safe publish workflow, and the mistakes that get submissions rejected.88 notes · part of slot-studio94%Casino Compliance & LocalesAnswer questions about social casino compliance and localization: stake.us jurisdiction wording requirements, prohibited terms and compliant rewrites, social-mode localization, locale splitting, and multi-language translation workflows for slot games.88 notes · part of slot-studio94%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.136 notes · part of stake-engine93%Slot Design & PresentationAnswer questions about designing slot games players love: symbol systems and readability, art direction, animation direction and game feel, sound and music direction, paytable and info design, bonus presentations, responsive layouts, typography, logos and key art, theme invention, and HUD construction.254 notes · part of slot-studio92%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.130 notes · part of stake-engine91%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.578 notes · part of stake-engine91%Slot Art DirectionAnswer how to art-direct a slot game that sells: theme invention and marketability, symbol families and readability under FX, logos and key art, visual language and moodboards, AI art generation pipelines that produce consistent rig-ready assets, and game-tile art that passes platform review.124 notes 88%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.272 notes · part of stake-engine86%Slot Mechanics & MathAnswer questions about slot game mechanics and mathematics as a working studio applies them: tumble, ways, cluster, hold-and-spin and multiplier mechanics, book and LUT generation, hit-rate distributions, volatility and criteria design, max-win profiles, feature economy balancing, math validation, and the event contract between math and frontend.221 notes · part of slot-studio85%Slot Animation CraftAnswer how to make slot animations feel premium: spin and reel-stop choreography, anticipation and near-miss timing, win escalation pacing, skip-safe sequences, GSAP and Spine implementation for slots, hand-authored skeletal rigs, sprite FX pipelines, and the game-feel polish rules that separate a 3-star game from a flat one.349 notes 82%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.225 notes · part of stake-engine82%Spine 2D AnimationAnswer how to build production Spine 2D skeletal animation without the editor when needed: rig structure and JSON authoring by hand, weighted meshes, IK and muscle setups, idle, win, hover and destroy animation styles, exporting json plus atlas for game runtimes, wiring pixi-spine into a frontend, and the pipelines that turn generated or cut-up art into rig-ready parts.341 notes 79%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.393 notes · part of stake-engine78%Slot Frontend EngineeringAnswer questions about implementing slot game frontends: the Stake Engine web SDK and UI template, RGS integration and replay determinism, XState v5 game lifecycle machines, GSAP animation, Howler audio, performance budgets and profiling, telemetry contracts, testing harnesses, and the fixes that turn a low review score into a top one.254 notes · part of slot-studio73%PixiJS 8 for Casino GamesAnswer the questions of building a casino or slot game frontend on PixiJS 8: the v8 API and its migration traps from v7, render loop and ticker discipline, texture memory management and GPU leaks, batching and draw-call budgets, reel and symbol architecture, Spine integration, mobile performance budgets, and the asset loading lifecycle — as production rules with numbers, not theory.586 notes 69%Stake EngineAnswer 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.161 notes 57%Slot StudioAnswer any question about building production slot games end to end: mechanics and math, design and presentation, frontend implementation, Stake Engine approval, and social-casino compliance — the working knowledge of a studio that ships.0 notes 46%

Where these brains disagree

Different sources, read every night for places where two of them answer the same question differently. Nothing is merged and nothing is quietly picked: your agent is handed both sides, with the brain each came from.

data types for GameConfig fieldsstake-engine-reference: The wincap field is a win cap amount with unspecified type, and rtp is a return to player percentage with unspecified type.stake-engine-web-sdk: The wincap field is an integer, and rtp is a float.
How the four major contexts are set upstake-engine-ai: The contexts are set in context.ts using setContext() calls directly at entry level components.stake-engine-web-sdk: The contexts are set using setContext() from a context.ts file that calls specific setter functions (setContextEventEmitter, setContextXstate, setContextLayout, setContextApp).

Bought once, shared 3 ways

$99.00, one time — $33.00 a head. It does not renew and it does not expire, and when a brain in the pack learns something new you have it without paying again.

Your maths person, your frontend, your artist and your producer each connect their own agent with their own token. The seat shares the reading, not the allowance: how much each of you can teach and how many calls you may make is still your own plan, so a colleague who works this hard ends up on their own pro rather than quietly spending yours.

What this is not

It is not certification, and it is not advice: a brain answers from what it was taught and says so, and the exam measures whether the answer was in there — not whether the regulator agrees. It is not a replacement for reading the contract before you sign it.

What it removes is the other failure: an agent that answers with total confidence and no source, because something in its training data sounded close enough.

Buy the pack — $99.00 onceAsk a person first