How we test a slot before it goes live

A slot that pays the wrong amount even once in a million spins is a broken slot. Here is the routine every Nocturn Play game goes through before an operator can put real money on it.

1. The maths is written first, and on its own

The part of a game that decides outcomes (reel strips, symbol weights, paytable, feature rules) is a standalone module with no graphics in it. The art comes later and only displays what the maths decided. That separation is what makes everything below possible.

2. Recorded rounds, replayed exactly

For each game the maths author records a set of rounds: the exact random numbers consumed and the exact outcome they produced, including bonus rounds and free-spin steps. When the game is installed on our server, we replay every recorded round and compare the result field by field: the win, the final grid, the coins, the multipliers, the state carried into the next free spin.

For our four launch slots that is 356 recorded rounds across the four RTP settings, and all 356 came back identical. If even one differed, the game would not ship, because it would mean the server is not running the game that was designed.

3. Millions of spins per setting

Then we simulate. Three million paid spins and 300,000 feature buys per RTP setting, per game, through the same code path the live server uses, with a cryptographic random generator. We check that the measured RTP lands within its statistical margin of the target, that the hit rate is stable across settings, and that the 5,000× ceiling is applied correctly when it's reached. On Gold Rush Outlaws it was reached 96 times in 300,000 bought features at the 96% setting, every time paid at exactly 5,000×. The full numbers are in our RTP guide.

4. The browser never decides anything

In live play, the player's device sends the bet and receives the result. It never runs the maths, never holds the RTP setting and never touches the balance. The balance lives in the casino's wallet: we debit the stake first and only play the round if the debit succeeds; then we credit the win. If the credit fails because of a network problem, it is retried until it lands, so a win is never lost.

5. One round at a time

A session can only have one round in progress. Double clicks, two open tabs or a flaky connection can't create two debits for one spin.

This is the boring part of making slots, and it's the part we're proudest of. Operators can check any round of their players in the Nocturn Play back office. Studios selling through SoftAggregator go through the same routine before their games reach the slots API.