Run the app
The table, wheel geometry and sounds live in this HTML. Shop and Insights load from the adjacent client and assets folders. Three.js is loaded from ../lib/three.module.js, then ../lib/three.module.min.js or ../lib/three.min.js, followed by pinned CDN fallbacks. No build step is required.
For local use, put this app and real.html in one folder. Put Three.js in a sibling lib folder. Serve their parent directory with python3 -m http.server 8000, then open the app at http://localhost:8000/rou/. The tested engine version is Three.js r169. Its module file is standalone. Newer distributions may also require their companion core file.
The 30-second round
00–20: place wagers. 20–27: bets lock, the view moves down, and the ball spins. 27–30: the winning pocket is highlighted and returns are credited. Rounds use wall-clock slots, including after a background tab resumes. Each wagered round settles at most once; missed empty rounds are skipped. Joining during a locked round keeps the table visible until the next betting window.
Inside & outside bets
Click a number for a straight bet. Hover or focus the lines and intersections for splits and corners. Click a number column's bottom border for its three-number street bet (11:1). Click the bottom-border intersection between adjacent number columns for the six-number line bet (5:1). For example, the bottom border of 1 covers 1/2/3; the bottom intersection between 1 and 4 covers 1/2/3/4/5/6. Chips sit on those same borders and intersections. On narrow screens, swipe horizontally within the table to reach every number; tap the chip stack to choose a denomination. Beside zero are zero splits, the two trios, and first four. Outside bets cover dozens, columns, color, parity, and low/high.
| Straight up · 1 number | 35:1 |
| Split · 2 numbers | 17:1 |
| Street / trio · 3 numbers | 11:1 |
| Corner / first four · 4 numbers | 8:1 |
| Six line · 6 numbers | 5:1 |
| Dozen / column · 12 numbers | 2:1 |
| Color / parity / low-high | 1:1 |
Winning returns include the original stake. Zero loses all even-money outside bets. French mode displays a racetrack in wheel order. Tap a named sector or wheel number to place its complete wager immediately. Neighbours range from 0 to 5 each side, defaulting to 3. Track chips show only inside wagers covering each number, including shared splits and corners; outside wagers keep their chips in the shared outside region; the total wager counts each stake once. Traditional called bets are: Voisins (9 units), Tiers (6), Orphelins (5), and Jeu zéro (4). It does not enable la partage or en prison. The displayed chip is one unit; called bets reserve their entire cost atomically. Tap the overlapping chip stack to reveal all 12 denominations, then select one to collapse the chooser.
Using a phone
Phones use the desktop composition in landscape from the login screen onward. The app fills the visible landscape viewport with a complete betting screen and a separate full-screen wheel screen. Graphics preserve their proportions. Pages allow vertical navigation, with horizontal scrolling disabled. The spacer above the betting table is removed. Wide view also requests fullscreen and native landscape locking. If native orientation lock is unavailable, the app rotates its own viewport. The same chip controls, bankroll sidebar, and shared outside bets remain available.
Recorded spins & timing
Real-life results are recorded data, played against GMT+8 time. No request is needed at spin time. A 20,160-row feed spans one week. Longer feeds continue from the anchored Sunday; shorter feeds have unavailable periods until repeat on a later Sunday. Source changes, feed replacement, and clock adjustment are blocked while wagers are outstanding. A source switch during a locked round takes effect next round. RNG uses unbiased rejection sampling from the browser's cryptographic pseudo-random generator.
Ball motion
At each new spin, the rotor reverses its previous direction and the ivory-colored ball launches the other way. The rotor continues turning through capture, payout, and betting; the captured ball stays in its pocket until the next launch. The reversal uses a short smooth change of speed. The seven-second spin uses 240 physics steps per second: rolling drag, radial descent, gravity, sphere contact against the actual brass deflector faces, and collisions against moving pocket frets. Each rotor pocket has a recessed floor and sloped inner, outer, and side walls; the ball rebounds from the same triangles used to render them, with friction and progressively damped impacts until it rests inside the pocket. Launches pass through the deflector ring; friction, low deflector restitution, and gravity scaled to the wheel dimensions produce short, low rebounds. A separate visual random seed varies the rotor travel and landing position around the complete wheel, without changing the RNG or recorded result. Payout occupies the final three seconds. The approach is guided toward the previously chosen or recorded pocket, then the ball enters a gravity-driven contact simulation for the final 1.9 seconds. The seven-second schedule determines presentation timing. This is a physics-inspired presentation of the outcome, not a physical outcome generator.
Bankroll & Google
New players start with 10,000 play credits. Guest bankroll and pending wagers are saved on this device and restored on the next visit. After a completed losing round, a bankroll at or below zero receives 2,500 credits. Credits are separate from session winnings. Google sessions read and write a versioned JSON bankroll in the app's private Drive app-data folder. Outstanding wagers are included so a saved pending round can settle after reconnection. Tokens remain in memory. If permission expires or a save fails, a visible status asks you to reconnect or retry. Unsaved changes can be lost if you close the page. Use one active Google session at a time; revision checks reject conflicting saved sessions.
Client-side balances and preloaded real-life results are inspectable and editable. This standalone app is a play-credit simulation and is not a trusted real-money ledger.
Reference documentation: Three.js · Google Identity Services · Drive app data.