A player must see the same test version every time, and tests must not overlap

If a player lands in version A today and B tomorrow, or the same lucky people are in every test, the results mean nothing. This entry shows how to hand out versions from the player's identity alone, so it is stable, keeps earlier players when a test widens and stays independent between tests.

Why this works

A fair split needs a fixed answer for each person. If the version comes only from the person's identity and the test's name, it never changes, needs no memory, and a different name shuffles the groups so the same people are not always the ones being tested.

When not to use it

It does not help when you want to put one named person into a version on purpose, or when players have no stable identity, because they reinstall or play without a login. Then you need a stored choice or a different way to count.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 19 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "A player must see the same test version every time, and tests must not overlap" (read_entry testers-must-land-in-the-same-version-every-time) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP