Auto-play caps at 100 spins — the loss limit hides at step 4

Auto-play is capped at 100 spins in most Australian-facing casino lobbies, and that cap is the least interesting thing on the settings panel. The loss limit sits four taps below it, preset at a number most players never read, and it is the only control on that screen that stops the session rather than the spin counter. Run the numbers on a 100-spin auto-play at $1 a spin and the cap does almost nothing: it pauses a session that a loss limit should have ended 40 spins earlier.

The 100-spin ceiling is easy to explain. Regulators and platform providers settled on it as a blunt anti-treadmill measure — enough to let a player step away from the screen, not enough to let a slot grind through a payday. What it does not do is limit exposure in any meaningful way. At $1 a spin it is a $100 ceiling. At $5 a spin it is $500. The number of spins is fixed; the amount at risk is not.

What the auto-play panel actually contains

Open the settings on a typical licensed slot and you get a short list, usually in this order:

1. Number of spins (10, 25, 50, 100)
2. Stop if a single win exceeds a set amount
3. Stop if balance increases by a set amount
4. Stop if balance decreases by a set amount
5. Stop on a bonus feature

Step 4 is the loss limit. On the default configuration it is either blank or pre-filled with something like $50 — a figure that means very different things to a $0.20 spinner and a $5 spinner. The field is there, it works, and it is buried under two optional win-based stops that most players will never trigger. A single win stop is a novelty; a loss stop is the seatbelt.

The ordering matters more than it looks. The first control a player touches is the spin count, because it is at the top and it is the thing they came to set. By the time they reach step 4 they have already made the decision they think they came to make. The panel is not designed to hide the loss limit exactly — it is designed to lead with the friendly option and let the uncomfortable one sit lower down.

The default is the problem, not the field

A blank loss limit field is not neutral. It reads as "not applicable" to a player who has never used one, and the auto-play will run to its spin cap regardless of what happens to the balance. A pre-filled number is worse in a subtle way: it looks considered, so players assume it has been calibrated. It hasn't. It is a placeholder sized for a mid-stakes player, and at $0.20 a spin a $50 stop is 250 spins of runway — longer than any auto-play session will last, which makes the limit decorative.

The arithmetic that makes the cap look silly

Take a mid-variance slot at 96.2% RTP and 25% hit frequency, spinning $1 a spin. Over 100 spins the expected loss is $3.80. The standard deviation over that sample is roughly $22, so a run 1.5 standard deviations below expectation — entirely normal, not a disaster — lands you about $37 down. A $50 loss limit survives that. A $20 loss limit, set by a player who actually thought about it, stops the session at spin 60-something and saves the remaining bankroll.

Now run the same slot at $5 a spin. Expected loss over 100 spins is $19, and the 1.5-sigma bad run is around $185. The 100-spin cap allowed every one of those spins. The only control that would have intervened is the loss limit, and if it was left blank the session runs to completion no matter what. The spin cap is a timer. The loss limit is a brake. Only one of them is doing safety work.

There is a version of this where the cap matters: high-variance slots with bonus features that can run for dozens of spins, where a single trigger can eat the whole auto-play before the player looks up. Even then, the cap is protecting attention, not money.

Why the layout survives scrutiny

The obvious question is why regulators who mandated the 100-spin cap didn't mandate a default loss limit alongside it. The answer is that a spin cap is easy to specify and easy to audit — it is a single integer, and either the software enforces it or it doesn't. A loss limit default requires a judgment about what a reasonable loss is, and that judgment scales with stake, session length, and the player's own declared budget. Regulators have generally preferred to require the availability of loss limits rather than prescribe their defaults, which is defensible in principle and leaves the practical outcome to interface design.

The interface design, in turn, is set by product teams who have a commercial interest in longer sessions. That doesn't require conspiracy. Putting the spin count first is the natural order — it is the primary function of the panel. Putting the loss limit fourth is also natural, because it is a stop condition and stop conditions come after the main setting. The problem is that "natural" ordering produces a screen where the control that limits harm is the one most likely to be skipped.

What a better panel looks like

A loss limit that defaults to a number tied to the stake — say, 20× the bet per spin — would make step 4 meaningful without requiring the player to do arithmetic. A panel that asked for the loss limit before the spin count would invert the current psychology. Neither change is technically difficult; both would show up in a session log. The fact that neither is standard across the market tells you where the design priorities sit.

The number to hold onto

The 100-spin cap is the figure everyone quotes, and it is the wrong one. The figure that matters is the loss limit, and on a default panel it is often 0 — meaning no limit at all — or a placeholder like $50 that a $0.20 spinner will never reach in 100 spins. That is the number worth checking before you press start, and it is four taps down.

Which raises a question the industry hasn't answered: if a spin cap is worth mandating because it limits exposure, why is a loss limit default not held to the same standard? The cap limits spins. The limit limits money. Only one of those is the thing players actually lose.