ROULETTE TOOL User Guide / README =================== Thank you for using Roulette Tool. SYSTEM REQUIREMENTS ------------------- - Windows 10 or Windows 11 - Google Chrome installed - Active internet connection Python or any other development software is NOT required. INSTALLATION ------------ 1. Run the Roulette Tool Setup executable included with the release. 2. Follow the installation steps. 3. Start Roulette Tool using the desktop shortcut or Start Menu shortcut. Installing a newer version over an existing installation should normally keep your personal Roulette Tool data. FIRST START ----------- When Roulette Tool starts for the first time, it automatically creates its own local data folders and dedicated Chrome profiles. Select Shuffle or Stake in the casino selection screen before the main Tool starts. Log in to the selected casino in its dedicated scraper browser when required. Table availability, direct links and calibrations depend on the selected casino. The Tool will start: - The main Roulette Tool interface - The BOT Runner - The Live Tracker / Scraper browser On the first start, the scraper browser may require you to log in to the website manually. Your login session is stored locally in the dedicated browser profile, so you should normally only need to do this once. Do not manually reuse the dedicated BOT / scraper Chrome profiles for normal browsing while Roulette Tool is running. LIVE TRACKER ------------ The Live Tracker collects roulette results used by the Tool's monitoring, trigger and strategy systems. After the scraper browser has loaded correctly and you are logged in, check the Live Tracker status in the main Tool. Do not close the scraper browser while Roulette Tool is running. If the Live Tracker is not receiving new results, automated triggers and BOT actions cannot reliably continue until live data is available again. CALIBRATION ----------- Before using LIVE BETTING on a table, the table must be calibrated. Use the CALIBRATION button in the main Tool. Follow the calibration wizard carefully. Calibration is stored separately for each casino and supported table. Calibrate the countdown timer area as well as chips and betting positions. Include the coloured countdown circle and its large central number in the timer area. Some tables use a Real Play entry button; Stake normally does not. Only configure an entry button when that table actually uses one. When copying a calibration, verify the copied timer area and remove any unnecessary Real Play control. You can: - Create a new calibration - Copy a calibration to another similar table - Fine-tune individual calibration points visually - Preview saved calibration points - Adjust chip values - Adjust the default racetrack neighbor count - Save a backup copy of all calibrations Always use Preview Saved to verify the calibration before using LIVE BETTING. CALIBRATION BACKUPS ------------------- The Calibration Overlay includes a Save Calibrations button. Use this button to create an extra copy of the complete calibration file in a location you choose, for example Documents, Desktop, cloud storage or an external drive. The active calibration file is stored under: Shuffle: %LOCALAPPDATA%\Roulette Tool\calibration\bot_calibration.json Stake: %LOCALAPPDATA%\Roulette Tool\calibration\stake\bot_calibration.json The backup does not replace or modify the active calibration file. It is recommended to create a new backup after important calibration changes or after calibrating additional tables. If the active calibration file ever needs to be restored manually, close Roulette Tool first before replacing the file in the calibration folder, then restart the Tool and verify the calibration with Preview Saved. SHARED CALIBRATION FILES ------------------------ A bot_calibration.json file may be shared with another user as a starting point. Important: a shared calibration is not guaranteed to match another computer. Calibration can be affected by: - Screen resolution - Windows display scaling - Browser zoom - Browser window size and position - Roulette table layout or provider interface changes Before using LIVE BETTING with a shared calibration file: 1. Make a backup of your current calibrations. 2. Close Roulette Tool before manually replacing the calibration file. 3. Restart Roulette Tool. 4. Verify all important points with Preview Saved. 5. Test the table in DRY RUN first. 6. If any mouse position is inaccurate, run the Calibration wizard again and save a calibration for that computer. Never assume that a calibration created on another system is safe for LIVE BETTING without checking it first. STRATEGIES AND TRIGGER LISTS --------------------------- Use Trigger Settings or New strategy in Advanced Strategy Creator to create a strategy. The Creator includes Select list, synchronized with Settings and Monitor. New strategy saves to the selected list and starts with Advanced rules OFF. Choose its name, initial bet target, base stake and initial consecutive-loss threshold. Create separate lists, for example for different starting stakes, and select the list you want to use. The selected list is synchronized between Monitor and Settings in both directions. Changing lists is blocked while a Runner strategy is active. ATH remains shared when changing lists. Strategy export includes lists and their associated strategies. During import, review the available strategy selection and choose what you want to restore. Back up your configuration before importing or making major changes. ADVANCED STRATEGY CREATOR ------------------------- The Advanced Strategy Creator compiles supported text instructions into strategy rules. It is a phrase-based compiler: arbitrary wording and every possible scenario are not supported. Use the separate Advanced_Strategy_Creator_Keywords.docx reference for English keywords, actions, conditions and examples. Download it from the website if needed. The Creator supports the progressions available in Settings / Progression Focus: - Martingale - Grand Martingale - Super Martingale - Fibonacci - Lucas - Trippingale - Padovan - Hollandish - D'Alembert Flat, Paroli and Reverse D'Alembert are additional choices. Lucas starts at two base units. Check the reference for each progression's win behavior. A named progression step and a configured strategy level are different concepts: "next progression step" changes the stake sequence; "next level" selects the next configured level. Example: Bet 0.10 on black Use Martingale Start after 15 consecutive losses on black After loss wait for 2 more consecutive losses on black then next progression step After win wait for new trigger In this example: 1. The existing initial trigger waits for 15 consecutive black losses. 2. The Runner prepares the first $0.10 wager for an open betting window. 3. If that wager loses, the Runner pauses betting and keeps receiving results normally. 4. It waits for two NEW consecutive black losses. The played loss is not counted again. 5. After the extra trigger is reached, the next Martingale wager is $0.20. 6. A played win ends the session and returns to waiting for a new initial trigger. The extra wait belongs to the Runner. The Monitor continues its normal operation. During the extra wait there are no wagers, no P/L entries and no progression steps. A repeated gameId is not counted twice, and another table's results do not satisfy the wait. The session remains reserved; this is not an instruction to start another strategy. Timer checks and other execution checks still apply before the next wager. Additional waits can use consecutive or total wins/losses, or a number of spins, with the supported targets described in the keyword reference. A "Start after" instruction is a shortcut for the existing consecutive-loss trigger in Settings; other initial conditions should be configured through Settings. Compile the instructions, inspect the resulting rules, then use Test & Debug. Use actual roulette numbers 0-36 for tests involving additional triggers or multiple bet locations. Observation-only spins must not change the simulated P/L or progression. Unknown or contradictory instructions must be corrected before saving. Save the rules and enable Advanced rules for the strategy before use. The Condition Audit helps check supported conditions; also test the full sequence in DRY RUN. PHASE PLANS AND VISUAL BUILDER ------------------------------ In Advanced Strategy Creator, choose Phase plan as the execution model. Configure phases with their own Bet instructions, base stakes, progression, win/loss transitions and extra waits. Multiple Bet lines create multiple locations. The visual blocks and phase text represent the same plan; compile text edits before saving. Existing text-rule strategies remain available in the other execution model. The initial trigger stays in Settings. Phase 1 starts after it fires. Later phases can have entry waits; repeating phases can wait after a win or loss. The Runner counts these waits from normally received, unique gameId results. Observation spins do not place wagers, alter P/L or advance the progression. Reset choices cover stake, progression, phase counters, current phase or the full session. Full-session reset means ending this session and waiting for the initial trigger. Session P/L and total played bets remain intact during phase changes. Optional session limits cover loss, profit, played bets and progression step. Zero disables a limit. Limits override phase transitions. A loss limit is checked after settlement and cannot cap the loss of a wager already placed. Choose either Wait for initial trigger or Stop strategy when a limit is reached. Stop strategy blocks fresh starts for that casino/strategy until Clear strategy stop is used in the Creator. Clearing the stop does not place a bet or enable LIVE. Use actual roulette numbers 0-36 to test phase plans. Phase simulations begin after the initial Settings trigger. Each spin shows the phase, wait progress, wager, net result, P/L and next action. Expand a spin to see detailed targets. Use Load two-phase example as a starting point and consult the updated keyword document. Existing interruption protection cannot be overridden by a reset policy. Partial real wagers are never replayed. After execution interruption, choose: - Restart plan: phase 1 at the next fresh initial trigger. - Restart phase: the interrupted phase at its initial stake at that trigger, with its old progression/wait counters cleared and no extra entry wait. - Stop strategy: block fresh starts until you clear the stop. These choices apply after automatic unwagered skips or settled partial wagers. Changing the phase configuration invalidates an interrupted-phase checkpoint. An emergency stop still requires manual re-arming. PARTIAL PAYOUTS IN ADVANCED STRATEGIES -------------------------------------- A complete Advanced wager can produce a partial payout. Example: $10 total wager and $8 returned is PARTIAL, with actual net P/L of -$2. No return is LOSS. A return equal to the wager is PARTIAL with zero net P/L. A return above the wager is WIN. PARTIAL is a separate strategy event. It does not add a win or loss to the strategy counters or fire WIN/LOSS rules. Consecutive win/loss streaks reset. The actual net P/L and played-bet count are still recorded and stop limits apply. Choose After partial payout in a phase plan, or the Partial payout event in a classic rule. Actions include Repeat bet, Next progression step and Back 1 progression step. The default keeps the same stake and progression step. Text examples: After partial repeat bet After partial next progression step After partial go back 1 progression In phase text, use On partial instead of After partial. Moving back a progression step is different from selecting an earlier configured strategy level. Use actual roulette numbers in tests so payouts can be calculated correctly. PARTIAL payout is different from an incompletely placed wager. Existing execution protection still prevents replaying an interrupted real-bet sequence. TRIGGER MONITOR --------------- The Trigger Monitor watches the selected tables and strategies and shows their current trigger status. Typical statuses include: - NEUTRAL - CLOSE TO - ACTIVE CLOSE TO means the monitored strategy is approaching its configured trigger condition. ACTIVE means the trigger condition has been reached. The Monitor includes one Auto start BOT selector: OFF | ACTIVE | CLOSE TO Only one mode can be selected at a time. OFF: - The BOT is not started automatically by the Trigger Monitor. ACTIVE: - The BOT is automatically started when a fresh monitored trigger reaches ACTIVE. CLOSE TO: - The BOT is automatically started earlier, when a fresh monitored trigger reaches CLOSE TO. - Selecting CLOSE TO makes a separate ACTIVE auto-start selection unnecessary. Auto Start only uses fresh monitor updates; an old status that was already visible before the mode was armed is not intended to start a new BOT run by itself. Starting the BOT from the Monitor does not by itself bypass the Runner's LIVE BETTING setting or safety checks. MANUAL TABLES / EXECUTE ----------------------- Auto Start uses tables with a direct URL for the selected casino. Tables without a direct URL require manual opening and an Execute action. 1. Open the Runner Browser from the Tool. 2. Open the required table yourself through the casino lobby. 3. Enter its betting board and verify that the table has a saved calibration. 4. Click Execute on the matching CLOSE TO / ACTIVE trigger. Showing ACTIVE or CLOSE TO does not automatically execute a manual table. LIVE BETTING must be enabled for real wagers; DRY RUN does not place real bets. The manually opened browser remains open after the strategy finishes. Automatic BOT tables use a separate browser window. Only one strategy runs at a time. DRY RUN AND LIVE BETTING ------------------------ DRY RUN: - Uses the real trigger and strategy logic - Processes live roulette results - Does NOT place real bets - Has its own separate P/L history and graph LIVE BETTING: - Uses the same strategy logic - Places bets automatically using the calibrated table - Records actual Runner session P/L separately from DRY RUN It is strongly recommended to test every new strategy in DRY RUN first. Changing the LIVE BETTING setting does not undo bets already sent. Never use the LIVE switch to repeat an interrupted betting sequence. BOT RUNNER ---------- The BOT Runner handles the automated betting process. Before placing a betting sequence, the Runner checks: - Whether the correct table is available - Whether the table is ready - Whether the betting round appears open - Whether the calibrated chip selection row is available when required - Whether the table appears obstructed by a popup or unexpected screen If the table is not safe to use, the Runner blocks betting instead of clicking blindly. The Runner uses the calibrated chip values to build efficient bet combinations and attempts to avoid unnecessary chip switching while placing a sequence. Do not move the mouse or manually interact with the roulette table while the BOT is actively placing bets. INTERRUPTIONS AND INCOMPLETE BETS --------------------------------- Recovery depends on whether any wager clicks have already been sent. If no wager has been sent, a failed readiness/timer check can skip the run, close the automatic table browser and leave the Runner ready for a fresh trigger. The Runner application itself should remain open. If only part of a wager sequence was sent, the Runner must not replay the full plan. It waits for the result for the emitted wagers, records that partial result, and discards the old strategy plan rather than continuing its progression. The Runner's log reports the state and whether LIVE mode is armed. Do not assume a click was accepted by the casino merely because it appears in the log. Check casino bet history when acceptance or settlement is uncertain. Never manually repeat an incomplete sequence while its result is still pending. Other errors may require manual correction. Read the Runner log before re-arming LIVE BETTING. EMERGENCY STOP -------------- Press ESC at any time to immediately stop further BOT mouse clicks, including while the roulette Chrome window has focus. ESC is a hard emergency stop. It is different from a normal recoverable SAFETY BLOCK: - Pending BOT clicks are cancelled. - LIVE BETTING is switched OFF. - The interrupted run is discarded rather than automatically resumed. After an ESC emergency stop, re-enable LIVE BETTING only when you are ready to re-arm the Runner for a new trigger/run. POPUPS / OBSTRUCTIONS --------------------- The Runner includes a Popup Guard. If the normal roulette table is obstructed, the Runner can stop betting and attempt conservative recovery. If manual action is required, close the popup yourself and allow the table to return to its normal state. Never manually place roulette bets while the Runner is in the middle of an automated betting sequence. SESSION / DRY RUN GRAPHS ------------------------ The BOT Runner contains separate SESSION and DRY RUN P/L histories. Use the SESSION / DRY RUN selector above the graph to switch between them. The graph shows: - The cumulative P/L over settled BOT spins - The real maximum / $0 / real minimum values on the left axis - The current P/L at the top-right of the graph - Total wager and bet count at the top-left of the graph Move the mouse over the graph line to inspect an individual settled spin. Example hover information: Spin 4 • WIN +$0.40 • P/L +$0.20 This means: - Spin 4 produced a +$0.40 net result - The cumulative P/L immediately after Spin 4 was +$0.20 The graph can also be saved. The saved graph data and SVG snapshot use the same session history. Reset only resets the graph/P&L history currently selected in the SESSION / DRY RUN switch. IMPORTANT SAFETY NOTES ---------------------- - Always verify the calibration before enabling LIVE BETTING. - Test new strategies and progressions in DRY RUN first. - Do not move or resize the roulette table/browser after calibration unless you recalibrate or verify the saved calibration. - Do not manually click or move the mouse over the roulette table while the BOT is actively placing bets. - Keep the Live Tracker running and verify that new results are being received. - Treat SAFETY BLOCKS as a warning that the table or environment must be checked before resuming LIVE BETTING. - Use ESC immediately if you need to stop all pending BOT clicks. - Never assume automated betting is error-free. Monitor the Tool during use. CLOSE ALL --------- Use the CLOSE ALL button in the main Tool to shut down the Roulette Tool components. This is the recommended way to close the application. USER DATA --------- Your personal Roulette Tool data is stored locally under: %LOCALAPPDATA%\Roulette Tool\ This includes items such as: - Database data - Calibration profiles - Dedicated browser profiles - Runtime settings These files are not part of the installer and remain specific to your Windows user account. Important calibration data is stored inside the calibration subfolder. Keeping an external calibration backup is recommended. UPDATES / REINSTALLATION ------------------------ Installing a newer version over an existing installation should not remove the personal data stored under: %LOCALAPPDATA%\Roulette Tool\ Even so, it is recommended to use Save Calibrations before a major update or reinstall if your table calibrations are important. If you intentionally want a completely clean installation, remove the existing Roulette Tool user-data folder manually after uninstalling the application. Removing this folder also removes locally stored Roulette Tool settings, calibrations and dedicated browser-profile data. DISCLAIMER ---------- Roulette Tool is automation and analysis software. Roulette involves financial risk and outcomes are random. No strategy, tracker, trigger, progression, or automated system can guarantee a profit. You are responsible for: - The strategies you configure - The bets placed through LIVE BETTING - Checking that the correct table and calibration are being used - Monitoring automated operation - Complying with the rules and terms of the websites and services you use Use the software at your own risk.