How to run a dice bot on Stake without pasting scripts

The old way to automate Stake dice was to find a script on a forum, paste it into a bot page, and trust that whoever wrote it wasn't harvesting your session token. DiceStrats replaces that with a browser side panel that runs on your own logged-in Stake tab. Here's the full setup, start to finish.

What you need

• Chrome, Brave or Edge (any Chromium browser with side-panel support).
• A Stake account, logged in, on stake.com or any Stake mirror (stake.jp, stake.bet, stake1xxx.com …). If you don't have one yet, sign up with the DICESTRATS promo code — it unlocks rakeback and is what keeps DiceStrats free.
• A DiceStrats account (free — email + password, takes a minute).

Step 1 — Install the extension

1. Download the zip from the install section and unzip it anywhere.
2. Open chrome://extensions, turn on Developer mode (top-right), click Load unpacked, and pick the unzipped dicestrats-extension folder.
3. Pin the ⬢ DiceStrats icon from the puzzle-piece menu so it's one click away.

Step 2 — Open Stake and the side panel

Open a Stake tab and log in as normal. Click the DiceStrats icon: the side panel opens on the right and asks you to sign in to DiceStrats. Once signed in the header shows Connected next to your Stake username and VIP tier — that means the bridge has found your tab. If it says "No open Stake tab", make sure the Stake tab is in the same window and press F5 on it.

Your Stake session token is read by the extension inside your browser and used to place bets — it is never sent to DiceStrats servers. You can verify this in DevTools → Network: all bets go straight to Stake's own API.

Step 3 — Pick a strategy

Three ways to get one:

• Community tab — browse the marketplace, click Add on a strategy. Creator strategies are protected: you see the name, win chance, leaderboard stats and five risk stages, not the internal conditions.
• Install code — someone sends you a DS1:… code; paste it in the Add box.
• Create tab — build your own with condition steps (on loss ×2, on win reset, every N bets switch chance…) or write it in code mode.

Not sure which family to pick? Read Stake dice strategies explained first.

Step 4 — Choose a risk stage and set your exits

Every marketplace strategy has five risk stages. Each stage is a base bet sized against a balance; stage 1 is the most conservative, stage 5 is aggressive. Pick the one whose base bet is small relative to your balance — the strategy description usually tells you the intended balance per stage.

Then, before anything else, fill in:

• Stop-loss — the drawdown at which the bot stops. Non-negotiable.
• Take-profit — where you want it to stop and hand you the win.
• Vault amount — profit gets moved to the Stake vault automatically once it reaches this. Vaulted funds are out of reach of the next losing streak.

Optional but useful: seed rotation (new client seed every N bets / losses / wins) and a max-bet cap.

Step 5 — Start, and watch the chart

Hit Start. The panel shows the live profit chart, bets per second, elapsed time, and the wagered total. The bet loop runs in the side panel, so it keeps running while you browse other tabs — but it stops if the Stake tab is closed. If you want it to survive the panel being toggled, use the pop-out button to run it in its own small window.

Finished runs are reported to the leaderboard (profit, wagered, bet count, whether it busted) so the marketplace stats reflect real sessions, red ones included.

Troubleshooting

• "Stake tab not responding" — reload the Stake tab (F5) and click Start again. The bridge re-injects automatically on the next command.
• Extension out of date banner — re-download the zip, unzip over the old folder, then click Reload on the extension card in chrome://extensions.
• Bets rejected with "insufficient balance" — you're on the wrong currency. Pick the wallet with funds in the panel's currency selector.
• Nothing happens on a mirror domain — check you're on the latest extension; mirror support was expanded to the full stake1xxx / stake3xxx ranges in v0.1.2.