Why outcomes are computed in advance
Many slots produce their results in real time: a random number generator picks a stopping position on each reel and the game logic works out the win. With five reels of a hundred symbols each, that gives ten billion possible boards, so the return of such a game is estimated by simulation rather than calculated exactly.
Engine takes another route. It requires all game outcomes to be known when the game is published. Since storing every possible board is impractical, a game is defined by a chosen set of outcomes, each with a weight. For the general principle, see how slot machine algorithms work.
What the SDK produces
| File | Contents |
|---|---|
| Index file | The list of modes, with the cost and the files of each |
| Lookup table | One line per outcome: its number, its weight and its payout |
| Game logic file | For each outcome, the events the front end must play |
A game with one mode needs these three files. Each additional mode adds a lookup table and a game logic file.
What happens on a bet
- The server consults the lookup table of the mode being played.
- It selects an outcome with a frequency proportional to its weight.
- It returns the events of that outcome to the front end.
- The front end renders them.
Modes
A mode is a way of playing the game with its own cost and its own outcomes: the base game, or a bonus bought directly, for instance. Each mode has a cost multiplier of at least 1.
Rules the math must follow
| Rule | Value |
|---|---|
| Return to player of each mode | Between 96.0% and 96.7% |
| Number of modes | At most 20 |
| Decimals in payout multipliers | Up to 2 |
| Changes after release | None, except to fix a confirmed bug |
The last rule matters most. Before release you can publish and switch math versions as often as you need. Once the game is live, the math is locked, even for a retune that keeps the same return and the same maximum win.
Maximum win and bet levels
Bet levels are set automatically from your math, mainly the maximum win, and from your star rating. Lowering the maximum win is the main way to obtain higher bet levels. Because the math cannot change after release, this is a decision to make before submitting.
What the SDK does not do
- It does not design the game. The theme, the features and their rhythm come first: see slot game mechanics explained.
- It does not draw or animate anything. The front end and its assets are a separate job.
- It does not earn the rating. Reviewers score art, animation and polish.
The full path from account to release is in the Stake Engine tutorial.
Rules, rates and limits on this page come from Engine's own documentation, read on 13 November 2026. Engine can change them: check the official documentation before you decide.
Have the math and need the game around it?
Art, animation and code from one team. Custom slots from €4,000.
Get a quote