On this page
A score is a design statement
Whatever a game counts is what it is asking you to do. A game that scores time is asking for consistency. A game that scores kills is asking for aggression. A game that scores collection is asking for route quality.
That means reading the scoring metric is the fastest possible way to understand how a game wants to be played — considerably faster than working it out by trial and error.
The five metrics used here
| Metric | Rewards | Punishes | Games |
|---|---|---|---|
| Time survived | Consistency | Optional risk | Survival games |
| Wave or round | Clean clears | Attrition | Wave games |
| Points | Efficiency and combos | Damage taken | Shooters |
| Distance | Sustained accuracy of input | Single mistakes | Runners |
| Collection count | Route quality | Over-caution | Casual collection games |
Notice that two of these punish caution and three reward it. Playing every game the same way means playing at least some of them badly.
Why formulas should be visible
A hidden scoring formula makes improvement guesswork. If you do not know whether accuracy is weighted, you cannot decide whether to take a difficult shot.
Every game on this site states its metric openly on its page, and where a formula combines factors — Zombie Target weights accuracy against hit count — the combination is described in plain language rather than left to be discovered.
This is a design position, not just documentation. A scoring system that has to be reverse-engineered turns a skill game into a puzzle about the game.
Why there is no leaderboard
Zombie Games Hub is a static site with no server. That means there is no way to verify a submitted score, and an unverified leaderboard is a list of whoever edited their browser storage most creatively.
So there is not one. Best results are stored locally, described honestly as 'your best', and the popular games page is built from either editorial selection or your own device's play counts — both clearly labelled as such.
Reading a new game's scoring in thirty seconds
- Check the HUD. What is counted is usually what is scored.
- Check what breaks. If a multiplier resets on damage, damage avoidance is the real goal.
- Check the game-over screen. The stats shown there are what the game considers important.
- Check the personal-best label. It names the primary metric directly.
Why scoring systems get hidden
Plenty of games conceal their formulas. It is worth understanding why, because it explains when hidden scoring is defensible and when it is not.
- To prevent degenerate strategies. If players know exactly what pays, some will find the boring optimum and grind it. Hiding the formula slows that down.
- To preserve mystery. Some designers feel a visible formula makes a game feel mechanical.
- Because it was never designed. The least admirable reason, and probably the most common.
Our position is that the first reason is a design problem in disguise. If a strategy is boring and optimal, hiding it does not fix it — it just makes the game a puzzle about itself. The better fix is to make the boring strategy cost something, which is why Supply Run increases difficulty with every crate collected.
Reading a scoring system you cannot see
For games elsewhere that do not tell you, a short procedure recovers most of it.
- Play a maximally passive run. Avoid everything optional. Note the score.
- Play a maximally aggressive run. Take every risk. Note the score.
- Compare against duration. If the passive run scored proportionally to its length, time is the metric.
- Look for non-linearity. If a slightly longer run scored much more, something is multiplying — usually a chain.
- Test the break. Deliberately take damage at a high score rate. If the rate drops, damage breaks the multiplier.
Four or five runs and you know how to play. It is a reasonable use of time in a game you intend to spend hours on — and a reason to prefer games that simply tell you.
Every metric on the site
The complete list of what each game records, so you can see the range in one place.
| Metric | Games using it | Optimal posture |
|---|---|---|
| Score | Blaster, Hunter, Target, Chase, Infection Zone, Ultimate | Depends on the combo system |
| Wave | Zombie Wave, Last Survivor, Defense, Barricade, Safe House | Clean clears over fast clears |
| Round | Zombie Arena | Build quality over kill count |
| Time survived | Rush, Night Survivor, Swarm, Blackout, Dodge | Maximum caution |
| Distance | Undead Runner, Highway, Sprint, Rooftop, Tunnel, Graveyard | Consistency; avoid optional risk |
| Level / sector | Zombie Escape, Dead City, Emergency Escape | Route quality over speed |
| Collection count | Supply Run, Coin Rush | Calculated aggression |
| Streak | One-Tap Zombie | Timing consistency |
Notice that the optimal posture ranges from 'maximum caution' to 'calculated aggression' depending only on the metric. Playing every game the same way therefore guarantees playing several of them badly, regardless of skill.
Why these scores are stored locally
The absence of a leaderboard is a design decision rather than an omission, and the reasoning is worth setting out because it shapes what the numbers mean.
- A static site cannot verify a score. There is no server. Any number submitted from a browser can be edited in that browser, so an online leaderboard here would rank whoever was most willing to open developer tools.
- An unverifiable leaderboard is worse than none. It looks like information and is not, which makes it actively misleading rather than merely useless.
- Local storage keeps the claim honest. 'Your best' is a statement we can support. 'Ranked 412th worldwide' is not.
- It also keeps the site private. No accounts, no identifiers, nothing transmitted. Your play history is genuinely yours.
The cost is real: you cannot compare yourself to anyone, and you lose your scores if you clear site data or switch browsers. We think that is the right trade for a site with no server, and we say so rather than implying a sync that does not exist.
It also means the benchmarks in our scoring guide are our own internal testing figures rather than aggregated player data. We label them that way for the same reason — see the fact-checking policy for how we handle claims we cannot support.
Key takeaways
- What a game counts is what it is asking you to do.
- Two of the five metrics used here punish caution; three reward it.
- Hidden formulas turn skill games into puzzles about the game. Every formula here is stated.
- There is no leaderboard because a static site cannot verify one.
- The HUD, the break condition and the personal-best label tell you the scoring system in thirty seconds.
- Hiding a formula to prevent a degenerate strategy treats the symptom; making that strategy cost something treats the cause.
- A passive run and an aggressive run, compared against duration, recover most of an unknown scoring system.
- Optimal posture ranges from maximum caution to calculated aggression depending only on the metric.
- A static site cannot verify a submitted score, so an online leaderboard would be misleading rather than useless.