What does the role split actually do?
Zombillion is a live-action survival format in which human players try to complete objectives while volunteer zombies hunt them. The design problem is familiar from team sports: how do you make a mass-participation game tense without letting it become chaotic? The cause is asymmetry. Humans have speed and a shared route; zombies have local knowledge, patience and the ability to reappear. The solution is not more rules but a clear role contract. At zombillion, that contract turns a loose campus game into a repeatable event. The takeaway is that role clarity, not prop quality, carries the experience.
Why human teams need route discipline
Claim: human squads that win tend to behave like a small sports team, not a crowd. Example: a team that stops to argue at a checkpoint gives a zombie volunteer time to close a corridor and split the group. The cause is simple: zombies do not need to catch everyone, only the slowest decision. The solution is a nominated navigator and a rule that the group regroups at every objective. Takeaway: Zombillion rewards communication before speed.
How zombie volunteers set the difficulty
Claim: the zombie role is a calibration tool. Example: an energetic volunteer who sprints at beginners can flatten the game; a passive volunteer who guards one corner can leave a whole zone toothless. The cause is that live events have no difficulty slider; the volunteers are the slider. The solution is a briefing that assigns zones, defines acceptable pursuit and gives volunteers permission to ease off for visibly struggling groups. Takeaway: organisers should treat zombie briefings as seriously as player safety briefings.
What makes the debrief matter
Problem: players remember the ending, not the middle. Cause: a chaotic finish makes a well-designed route feel random. Solution: a short debrief that names a good zombie ambush, a smart human regroup and a safety call. Takeaway: Zombillion’s credibility depends on the final five minutes as much as the first. The role split is the engine; the debrief is the handbrake that keeps it repeatable.
