Back up Roulette Buddy triggers and move them to another browser
Export your Roulette Buddy trigger settings, protect the destination's existing setup, and check what transfers. Spin history and live streaks are not restored.
Roulette Buddy’s Export Data button saves your trigger setup to a file. You can import that file on another browser or device, but it is not a complete session backup. The export resets each trigger’s current streak to zero and does not include your spin history. Importing replaces the destination’s entire trigger list.
That distinction matters before switching phones, clearing browser data, or trying someone else’s setup. Here is how to preserve the settings you want without mistaking them for a saved record of play.
What the backup contains
A trigger describes a group of numbers and a condition you want the tool to track. The downloaded file preserves those trigger definitions, including their names, selected numbers, conditions, thresholds and active settings. It also includes an export date and file-format version.
The file does not contain the browser’s recent spins, display theme, notification preference or American Roulette setting. Check those preferences separately on the destination. In particular, confirm the wheel setting before entering results involving double zero.
The export creates a copy with current streaks set to zero. It does not reset the streaks in the browser you exported from. Treat the file as a reusable setup, rather than a way to resume the exact point you reached in a previous session.
Export before changing either browser
- Open Roulette Buddy in the browser that has the triggers you want to keep.
- Open Import/Export in the navigation. On a narrow screen, the button is labeled I/E.
- Select Export Data. The button shows the number of triggers being exported.
- Find the downloaded file. Its name begins with
roulette-buddy-backup-and ends in.json. Save an additional copy somewhere you can find again. - If the destination already has a setup you care about, export that browser’s triggers too. Give the two files distinguishable names, keeping the
.jsonextension, so you know which setup each contains.
Leave the source browser’s data intact until you have checked the destination. A file saved on the same device is useful, but will not help if that device is lost and you have no other copy.
Import and verify the replacement
Move the source file to the destination device using your usual file-transfer method. Open Roulette Buddy there, select Import/Export or I/E, then Import Data, and choose the JSON file.
Selecting a valid file replaces the current triggers. There is no merge step. The dialog warns about replacement before you choose the file, but do not expect another confirmation afterward. The success message reports how many triggers were imported.
For a hypothetical example, suppose the destination has three triggers and your backup contains two. After importing, the destination has the two imported triggers, not five. To recover the original three, import the separate destination backup you saved first. Neither operation restores spin history.
Before recording more results, check the imported names, number groups, conditions, thresholds and active settings against the source. Then reload the page and check that the setup remains. The source file’s streak counters start at zero; subsequent results can change the counters as the tool evaluates your triggers. An existing destination spin list is separate from the imported trigger definitions, so seeing old spins does not mean they came from the backup.
If the file will not import
Use an unedited file produced by Roulette Buddy’s Export Data button. A screenshot, a list of roulette numbers, or a renamed document is not the trigger-backup format. The importer checks for a trigger list and required identifying fields, and reports an error when the file cannot be read in the expected format.
If the source browser still has your setup, export a fresh copy and try that file. Preserve the older copy while troubleshooting. For support, note the error message, browser and what you were trying to transfer; avoid sending unrelated files or personal information.
Browser storage is tied to the site and browser context. A new device or a move to a different website address does not automatically bring the old local data with it. Private-browsing data can also disappear when the private session closes, as MDN’s browser-storage documentation explains. A trigger export cannot recover history that was never included in the file.
Keep the record’s meaning clear
This procedure applies to the browser-based Roulette Buddy. For recording watched results in the separate Tink’s Toolchest app, see observed roulette spins and Bulk add. The two workflows serve different purposes; this guide does not establish backup compatibility between them. You can explore the app’s roulette tools and session history on the Toolchest page.
A saved trigger is an observation rule, not evidence that a number is due. MGM’s roulette guide explains that previous spins do not change the next outcome’s likelihood. Backing up settings does not remove the house edge or create a winning prediction. You can practice the entire transfer without placing a wager.