Build a strategy in the Roulette app

The Roulette development app separates the wagers placed on a spin from the rule that chooses the next stake or layout. A reproducible strategy needs both. Custom building and editing are Pro-gated in the audited source.

Start with a playable layout

Choose the wheel first. Place the proposed bets on the table and give every wager an amount. The engine checks whether the placements are legal for that wheel. European first-four and wheel-sector conventions cannot be assumed to work on an American table.

For a small example, one unit on the first dozen and one on the second produces a two-unit opening wager. Its covered hits earn one unit overall; a full miss loses two. The two-dozen guide shows the settlement before any progression is attached.

Choose the transition explicitly

A staking plan uses one fixed even-money bet and changes its amount. The current source includes named plans such as Martingale, D’Alembert, Fibonacci and Paroli. A multi-bet layout is a separate structure; the editor's staking configuration does not silently convert an arbitrary collection of bets into a valid even-money plan.

A layout program can instead use steps and transitions. Define the opening step, what a win, loss or level result does, and when the program resets or stops. A transition based on a settled result affects the following spin. It cannot use a future pocket.

Validate with a short trace

Before a large run, follow a few declared outcomes. Record opening wagers, total stake, returned chips, net result and the next requested wager. Include a loss and a limit stop. A demonstration containing only wins leaves important behavior untested.

The source retains legacy templates alongside newer named plans. The older Fibonacci steps template retreats one position after a win, while the named Fibonacci plan retreats two. A strategy name alone is insufficient to identify the rule.

Save, share and compare carefully

The audited strategy library treats edited or imported copies as custom strategies even if they retain a starter identifier. Sharing or importing a definition does not establish that it is profitable. Preserve its wheel and complete rules when comparing it with another version.

Use app simulations to interpret the saved experiment model and changing layouts for state examples. This page describes source behavior; the website does not offer app-strategy import or promise a public app release. See Pro features for access boundaries.