Showing quit numbers by group without exposing a handful of players
Splitting players into small groups, for example by one rare ending or one unusual choice, can leave a group of two or three people who could be recognised or guessed. This entry shows how to hide such small groups in a report in a way that cannot be undone by subtracting from the total.
Why this works
A number built from very few people can point at one person. Hiding small groups is not enough, because a visible total lets anyone subtract and find the hidden size. So small groups are merged until the merged group is large, and tiny totals are not shown at all.
When not to use it
Do not rely on it alone when the group name itself is identifying, or when you publish many cuts of the same data that can be crossed. Then even large groups can give someone away. Publish fewer cuts, or only totals, and keep the raw rows private.
In the full entry
- What to build, step by step
- Starting values and the reason for each
- 3 common mistakes and the fix
- 26 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 "Showing quit numbers by group without exposing a handful of players" (read_entry story-small-group-suppression) 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