Why Enemy Damage Should Never Scale With Player Count

When a friend joins your co-op game, the encounter has to get harder or it becomes trivial. Almost every team reaches for the same lever: multiply enemy damage by the number of players. It is the wrong lever, and it quietly punishes the exact players you most want to keep.

Start from what each stat controls. Enemy health controls how long a fight lasts. Enemy count controls how busy the fight feels. Enemy damage controls how much a single mistake costs. When you scale damage with headcount, you are not making the fight longer or busier - you are making every individual error more lethal, and errors are not evenly distributed. The strongest player barely notices. The weakest player, the friend who was dragged in and is still learning the controls, now dies to hits they used to survive. The group that scaling was supposed to serve is the group it breaks.

The pattern we ship instead: scale health and count, freeze damage. A useful starting point for a 2-to-more co-op game is enemy health times 1.65 and pack size times 1.15 per step, with enemy damage held flat forever. Time-to-kill stays roughly constant, the screen feels fuller, and a weaker teammate is never squishier than they were solo. In simulation, holding damage flat versus scaling it can nearly halve the wipe rate at the same nominal difficulty - same challenge on paper, very different retention.

The design law underneath is simple: difficulty should come from more to deal with, not from being punished harder for the same mistake. Bigger squads should feel louder and more chaotic, not more fragile.

The law: scale enemy HP x1.65 and add spawns per extra player, and never scale enemy damage. Damage scaling turns headcount into an exponential wipe rate; HP scaling keeps difficulty linear and fair.