Stop-Loss and Take-Profit on Stake: Automated Exit Rules That Protect Your Bankroll (2026)

Most bankroll damage on Stake does not come from a single catastrophic spin. It comes from the extra fifteen minutes after a losing streak, or the refusal to cash out after a big hit because the session still feels hot. Stop-loss and take-profit rules are the simplest defense against both failure modes. They convert vague intentions ("I will stop when I am down too much") into hard numbers that either a player or an automation layer can enforce without negotiation. This guide covers how to define, size, and automate stop-loss and take-profit triggers on Stake in 2026, with examples for Dice, Limbo, Mines and slots.

What Stop-Loss and Take-Profit Actually Are

A stop-loss is a predefined loss threshold that ends a session the moment it is crossed. A take-profit is the same idea in the opposite direction: a profit threshold that locks in gains and closes the session. Both exist to protect the bankroll from the two largest psychological traps in casino play: chasing losses and giving back winnings.

On Stake originals, these triggers can be expressed in units, in currency, or as a percentage of the starting session bankroll. The third form is usually the cleanest because it scales with the player and the game. A 20% stop-loss on a $200 session is $40, on a $2,000 session it is $400. Same rule, same discipline, different numbers.

Why Arbitrary Exit Points Fail

Players who rely on feel tend to exit sessions either too early (bored, distracted) or far too late (tilt, sunk-cost reasoning). Neither is random. Both are the predictable result of the brain weighing short-term emotion above long-term bankroll math. A few of the common failure patterns:

• Chasing to break-even after a fast downswing, usually by doubling stake size.
• Refusing to quit after a 3x session because the last five bets all won.
• Moving the stop-loss down mid-session ("I'll stop at -60% instead of -30%").
• Taking micro-profits repeatedly, turning a +40% session into +5% by paper-cutting it to death.

Hard-coded exit rules neutralize these patterns because the decision happens before the session starts, when the player is calm and rational. The session itself becomes an execution problem, not a judgment problem.

Sizing Stop-Loss and Take-Profit

There is no universal correct value, but there are useful reference points based on the volatility of the game being played. The higher the variance, the wider the bands need to be, otherwise normal noise will trigger the stop before the strategy has a chance to play out.

Low-Volatility Games (Dice at 2x, Limbo at 1.5x–2x)

• Stop-loss: 15% to 25% of session bankroll.
• Take-profit: 15% to 30% of session bankroll.
• Session cap: 30 to 60 minutes or 1,000 to 3,000 bets, whichever comes first.

Medium-Volatility Games (Mines 3–5 tiles, Plinko 12–14 rows on Medium)

• Stop-loss: 25% to 35% of session bankroll.
• Take-profit: 30% to 50% of session bankroll.
• Session cap: 500 to 1,500 bets.

High-Volatility Games (Limbo 10x+, Mines 10+ tiles, bonus-buy slots)

• Stop-loss: 35% to 50% of session bankroll.
• Take-profit: 100% or more (double-up rule is common here).
• Session cap: number of spins or bonus buys, not wall-clock time.

Wider bands for higher variance are not a license to risk more; they are a mathematical requirement. A 20% stop-loss on a 100x Limbo target will trigger within dozens of bets even when the strategy is running within expected variance.

Trailing Stops and Tiered Take-Profits

Two small refinements significantly improve the basic framework without adding real complexity.

A trailing stop moves with the session peak. If the session starts at $200, reaches $260, and a 10% trailing stop is set, the effective stop is now $234 rather than the original $160. This locks in the run while still giving it room to breathe. Trailing stops pair well with winning streaks in low-variance games where small edges can compound over time.

Tiered take-profits split the profit target into stages. For example, reduce base bet by 50% once profit hits 25% of bankroll, and close the session entirely at 50%. The first tier protects the gain, the second tier captures it. This is especially useful for Martingale-adjacent progressions where the bet size grows during losing streaks and can give back profits quickly.

Automating Exit Rules on Stake

Manual stop-loss enforcement works exactly as well as the player's discipline on any given evening, which is to say inconsistently. Automation removes the willpower dependency. On Stake originals that support auto-bet natively, the built-in "stop on profit" and "stop on loss" fields already cover the basics. They are stateless per-run, which means they reset each time the player hits start, and they apply only to the currently open game tab.

For cross-game sessions, rolling bankrolls, or rule sets more complex than a fixed number, an external automation layer is needed. SSPilot is designed around this use case: session-level stop-loss and take-profit, trailing stops, time limits, and wager caps that persist across games and survive disconnections. When a threshold is crossed, the bot stops placing new bets and (optionally) sends a Telegram alert with session stats so the player can review the outcome instead of reacting to it live.

• Session-wide (not game-wide) thresholds, so moving from Dice to Limbo does not reset the stop.
• Hard caps that cannot be edited while a session is live, reducing tilt-driven overrides.
• Logging of every triggered exit so patterns become visible across weeks.
• Optional cooldown windows after a stop-loss, preventing immediate re-entry.

Common Mistakes to Avoid

Even well-designed rules fail when applied poorly. A short checklist of the mistakes that show up most often in session logs:

• Setting the stop-loss too tight for the game's variance, causing constant premature exits.
• Treating the take-profit as optional ("I'll stop only if I feel like it").
• Resetting the session bankroll mid-session after a deposit, which silently disables the stop.
• Stacking multiple small sessions back-to-back and ignoring the aggregate loss for the day.
• Using percentage-based stops on a bankroll that fluctuates wildly between sessions.

The daily aggregate matters more than any single session. A player who respects a 25% stop-loss per session but runs six sessions in a row can still be down 60% on the day. A daily loss cap sits above the session cap and closes the door completely once crossed.

Putting It Together: A Minimal Rule Set

A workable default for a Stake player who wants to start applying these rules tonight:

• Define a session bankroll separate from the main wallet (e.g., 5% of total bankroll).
• Set stop-loss at 25% of session bankroll for medium-variance play.
• Set take-profit at 40% with a trailing stop of 15% once profit exceeds 20%.
• Cap the session at 45 minutes or 1,000 bets, whichever hits first.
• Set a daily loss cap at 2 session bankrolls. Once crossed, close the app.

These numbers are not magic. They are starting points that survive contact with variance and are easy enough to follow without a spreadsheet. Tighten or widen them based on the specific game, the personal tolerance for drawdown, and the data from the first ten or twenty tracked sessions.

Final Note on Expectation

No exit rule changes the house edge. Stop-loss and take-profit do not make a negative-EV game positive. What they do is guarantee that when variance swings against a player, the damage is bounded, and when it swings in favor, the gain is actually captured. The casino always has the long-run edge. The player's only real lever is how much they expose to that edge per session. Treat stop-loss and take-profit as exposure controls, not as profit strategies, and gambling stays inside the entertainment budget rather than consuming it.