Auto-Exclude Re-adds the Last Game, 30% Sit Out a Round

Croatia's regulated market has a feature that most players only meet on a bad night: the self-exclusion register. When a player activates it through the Ministry of Finance's central system, the operator is obliged to close the account, stop marketing, and keep it shut for the chosen period. What the register does not do is decide what happens to the game state left behind — the slot session, the tournament ticket, the partially dealt hand. That gap is where a quiet, repeatable behaviour has taken root across several Croatian-facing operators: when an auto-exclusion fires mid-session, the platform re-adds the last game to the player's "recent" or "continue playing" tile the moment the exclusion lapses, and roughly 30% of those returning players sit out the first round or spin before re-engaging. The first number is a compliance problem. The second is a design one, and it is the more interesting of the two.

What auto-exclusion actually does in the Croatian framework

The legal layer is straightforward enough. Under the Gambling Act (Zakon o igrama na sreću) and the ministry's implementing rules, a player can request self-exclusion for a fixed period — commonly 24 hours, seven days, one month, six months, or a year — and the operator must apply it across every brand it holds a Croatian licence for. The register itself is centralised, so a single request should propagate to every legal operator in the market. That part works, at least in principle, and the ministry has been reasonably public about enforcement since the register went live.

Auto-exclusion is the variant that fires without the player asking in the moment. It is triggered by a rule the player set earlier, or by an operator-side threshold: a deposit limit breached, a session-length cap, a loss limit hit, or a pattern the operator's own responsible-gambling model flags. The distinction matters because the player did not press the button at the moment of exclusion. The system did. And systems, unlike people, leave state behind.

When a manual self-exclusion fires, the player has usually decided to stop. When an auto-exclusion fires, the player has often just crossed a line they set for themselves weeks ago and may not have been thinking about. They are mid-session, mid-flow, possibly mid-tournament. The account closes. The question is what the platform remembers.

The state problem nobody scoped

Most casino platforms were built around the assumption that a closed account is an edge case — fraud, chargeback, a player who wants out permanently. The "returning player" experience was designed for the voluntary returner: someone who took a break and came back. Auto-exclusion borrows that same return path, because building a separate one for a regulatory event was nobody's priority in the 2010s.

So the return path does what it always did: it restores the last session. The last game played appears at the top of the lobby, sometimes pre-selected, sometimes as a "continue where you left off" tile. For a player who chose to leave, that is a mild annoyance. For a player whose own limit just ejected them, it is the platform handing back the exact thing they were trying to step away from.

The 30% figure and what it measures

The 30% is not a ministry statistic — the ministry does not publish return-behaviour data at that granularity, and operators are not required to report it. It comes from operator-side analytics shared in aggregate across a small set of Croatian-facing brands, and it measures a specific thing: of players whose auto-exclusion lapsed and who reopened the account within 72 hours, approximately 30% did not place a bet, spin, or enter a hand on their first session back. They logged in, looked, and left — or logged in and closed the tab within a couple of minutes.

That 30% is the group the industry would call "cooled" — players whose exclusion did its job, at least on the first attempt. The other 70% re-engaged, and a meaningful share of them went straight back to the re-added last game. The tile did its work.

Two readings of the 30% are possible and they point in opposite directions. The generous reading: the exclusion worked, the player reflected, and a third of them came back cautious. The less generous reading: the 30% is a floor, not a ceiling, and the re-added last game is actively pulling some of the other 70% back into a session they might otherwise have ended. Without a control group — players whose last game was not re-added — nobody can say which reading is right. That experiment is cheap to run and, as far as I can tell, nobody in the Croatian market has published it.

Why "last game" is the wrong default

The behavioural logic is not subtle. Slot play is heavily state-dependent: the reels, the bet level, the autoplay setting, the near-miss that was on screen when the session cut out. Restoring that exact frame is the strongest possible cue to resume. A neutral lobby — even a lobby with the same games available — is a weaker cue by a wide margin. The difference between "the game is there if you want it" and "your game is waiting for you" is the difference between a menu and a nudge.

Operators know this, which is why the "continue playing" tile exists in the first place. It is a retention feature, and a good one, for voluntary returners. The problem is that auto-exclusion inherits it by default rather than by decision.

Where the re-add comes from, technically

In most platform architectures the "recent games" or "resume" module reads from a session-state table keyed to the player ID. When the account closes, the row is not deleted — it is flagged inactive. When the account reopens, the module reads the flag, sees a recent game, and renders the tile. No one wrote a rule that says "do not re-add after a regulatory exclusion." The rule simply was not written, because the module predates auto-exclusion as a common event.

The fix is a single conditional: if the account closure reason is a self-exclusion or auto-exclusion event, suppress the resume tile for the first session after return, or until the player has made an explicit choice. That is a few lines of logic in most stacks. The reason it is not universal is not technical difficulty — it is that the resume tile is a revenue feature, and suppressing it for a subset of returning players looks, on a dashboard, like a conversion loss. Nobody wants to be the product manager who argued for it.

The tournament and multi-table edge cases

Slots are the easy case. Poker and tournament formats are messier. A player auto-excluded mid-tournament leaves a stack blinded off, and the platform has to decide whether to refund, forfeit, or hold the seat. Croatian operators handle this inconsistently. Some refund the buy-in minus fees; some let the stack blind off and pay out whatever it finishes with; some void the entry entirely. The player often does not learn which until they return, and the return screen — again — tends to surface the tournament first.

For a player whose exclusion was triggered by a loss limit, seeing a live tournament seat waiting is close to the worst possible greeting. It is a sunk cost with a countdown attached.

What a better return path looks like

The design principle is simple: an auto-exclusion should end in a neutral state, not a restored one. Concretely, that means four things.

Suppress the resume tile for the first session. Not permanently — the player can find the game in the lobby — but not pre-selected, not at the top, not framed as "yours." A neutral lobby is the correct default after a regulatory closure.

Surface the exclusion history, not the game. The first screen after return should state plainly when the exclusion fired, why (limit type, not a judgment), and when it lapsed. That is information the player is entitled to and rarely gets. It also reframes the return as a checkpoint rather than a resumption.

Re-prompt the limits. An auto-exclusion usually means a limit was hit. The return screen is the natural moment to ask whether the player wants to keep, tighten, or extend that limit. Most platforms bury this in account settings; it belongs on the return path.

Log the return event for the regulator. If the ministry is going to supervise auto-exclusion meaningfully, it needs to know how often players return within 24, 72, and 168 hours, and what they do on the first session. That data exists inside operators. Publishing it in aggregate would settle the 30% question and give the market a benchmark.

The counter-argument, fairly stated

There is a real argument against all of this: over-engineering the return path can feel punitive, and players who feel patronised churn to unregulated sites. Croatia's black-market problem is not trivial, and every friction point on a legal operator is a point in favour of an illegal one. The 30% who sit out a round are, in this view, evidence that the current system mostly works — the exclusion fires, most players pause, and the ones who return are adults making a choice.

That argument has weight, but it conflates two different frictions. Suppressing a resume tile is not the same as blocking access. The game is still there. The player can still play. What changes is that the platform stops prompting — and prompting a player who has just been auto-ejected by their own limit is not a neutral act. It is a design choice with a behavioural effect, and the 30% figure suggests the effect is not small.

The open question for the Croatian market

The ministry has been willing to enforce the register's hard edges — account closure, marketing bans, cross-operator propagation — and less willing to regulate the soft edges, which is where return-path design lives. That is probably correct in principle: prescriptive UI rules age badly. But it leaves the resume tile in the hands of product teams whose incentives point one way.

So the question is not whether auto-exclusion should re-add the last game. It clearly should not, at least not by default, and the fix is trivial. The question is who decides. If operators will not run the control experiment — re-add versus neutral lobby, measured on 72-hour return and 30-day play intensity — then the ministry eventually will, and it will do so with a rule rather than a nudge. The 30% who sit out a round are the market's best argument that the current default is survivable. They are also the reason nobody has bothered to check whether it is optimal.