The short version. A Stake Engine game is a set of pre-simulated rounds (books) weighted by a lookup table, played by a static front end through Engine's RGS. Here's every term you'll meet, in a line each.
Math
- Book
- One pre-simulated round: its ID, its ordered events and its payout multiplier.
- Library
- All the books from a simulation run.
- Events (book events)
- The ordered actions in a book, returned to the front end to animate. Anything not in the events can't be shown to the player.
- Lookup table (LUT)
- A CSV per mode with one row per book: simulation number, weight and payout. Weights set how often each round is picked.
- Index file
index.json, which lists each mode's name, cost, books file and lookup table.- Bet mode
- A playable option with its own cost, RTP, max win and files, such as a 1× base mode and a 100× bonus buy.
- Cost multiplier
- A mode's price as a multiple of the base bet.
- Criteria, distributions and quotas
- The math SDK's split of a mode into outcome classes (zero wins, base wins, features, win cap), each with a share of the simulations.
- Win cap
- A mode's maximum payout multiplier, its max win.
- Force file
- A record of which book IDs match which outcomes, for analysis and for finding specific rounds.
- Optimization
- Re-weighting the lookup table so a mode hits its RTP and hit-rate targets.
- RTP
- Return to player: a mode's expected payout divided by its cost. On Stake Engine, every mode must be between 96.0% and 96.7%.
- Hit rate
- The share of rounds that pay anything.
- PAR sheet
- A spreadsheet of a game's hit rates and RTP contributions, written by the math SDK's analysis step.
- CVaR, ETL and tail probability
- Risk measures of how bad the worst outcomes are for an operator. They set a game's bet limits.
Platform
- Engine
- Stake Engine's current name in its own docs and site.
- Studio
- Engine's developer dashboard, where you upload, publish, test and submit games (older docs call it the ACP).
- Team (provider)
- Your developer account on Engine, which games and payouts belong to.
- RGS
- The remote gaming server: Engine's API for sessions, bets, rounds and payouts.
- Front end
- The game's static web build, which plays the rounds the RGS picks.
- Version
- A frozen publish of the math or the front end. A submission pairs one of each.
- Replay
- Loading a past round by game, version, mode and event ID, without a session. Mandatory for approval.
- Bet-level template
- Engine's assigned minimum, maximum and default bets for a game, based on its risk.
- 2-Star and 3-Star limits
- Risk tiers that set a game's maximum exposure and bet size.
- Star rating
- Reviewers' 0 to 3 star score, which decides whether a game is published and where it's featured.
- Social mode
social=true: stake.us sweepstakes wording and currencies.- XGC, XSC, XEC
- Stake Gold Coin, Stake Cash and Stake Euro Cash, the social currencies.
- Engine Insights
- Engine's analytics, which also order New Releases.
- Engine network
- Operators other than Stake that can carry a game.
- GGR
- Gross gaming revenue: total bets minus total wins. Developer pay is a share of it.
For how these fit together, start with How a Stake Engine game works.
Sources: Engine docs and the Stake Engine math and web SDK docs. Checked October 22, 2026.