Survive Zombie Arena Zombie Bestiary

Regular Zombie is the baseline for judging every weapon. If a gun cannot clear the slow first-wave body count without forcing reload panic, it should not be trusted for the first pressure spike.

The baseline also teaches spacing. Players who back up too late against basic zombies usually back up even later when faster roles arrive.

Enemy recognition makes the run calmer. Regular bodies are space management, Runners are attention theft, Ashwalkers test early damage, Shades punish late callouts, and Brutes expose teams that cannot focus fire on command. For the regular zombie baseline section, I keep the advice tied to observable play instead of a generic wiki summary.

The bestiary is written like a field notebook because exact internal values are not public. When I write HP estimate or guide taxonomy, I mean it as a practical label for repeated behavior, not a claim that Nectarforge published that number. For the regular zombie baseline section, I keep the advice tied to observable play instead of a generic wiki summary.

Runner is a guide-taxonomy label for the fast low-health pressure that breaks sloppy lanes. It does not need huge HP to cause a wipe; it only needs to split aim and interrupt revives.

Shotgun spread, slow fire, or early callouts solve Runners better than chasing them across the map. Keep the lane line visible and let crossfire do the work.

The bestiary is written like a field notebook because exact internal values are not public. When I write HP estimate or guide taxonomy, I mean it as a practical label for repeated behavior, not a claim that Nectarforge published that number. For the runner pressure read section, I keep the advice tied to observable play instead of a generic wiki summary.

Target priority should change with the wave state. If fast enemies are loose, kill them before farming value. If the lane is stable, burn the armored target before it eats time. If a boss is active, save cooldowns for the moment it pulls the team out of shape. For the runner pressure read section, I keep the advice tied to observable play instead of a generic wiki summary.

Ashwalker is the first serious named check. Destructoid coverage mentions Ashwalkers, and in route planning I treat them as the moment where starter damage stops feeling comfortable.

Focus rifle fire before Ashwalkers touch barricades. If they reach the hold point while players are still reloading, the team usually pays twice: damage taken and lost shooting time.

Target priority should change with the wave state. If fast enemies are loose, kill them before farming value. If the lane is stable, burn the armored target before it eats time. If a boss is active, save cooldowns for the moment it pulls the team out of shape. For the ashwalker first real check section, I keep the advice tied to observable play instead of a generic wiki summary.

Public squads need shared language more than perfect aim. Saying Shade left or Brute center gives the team a single focus point. Silent target switching is how a readable wave turns into four separate emergencies. For the ashwalker first real check section, I keep the advice tied to observable play instead of a generic wiki summary.

Shade is the burst-read enemy. It pressures awareness more than raw DPS because a late Shade callout can turn a stable lane into a sudden revive chain.

Freeze, crossfire, and sonar-style communication matter here. The player who sees Shade first should call it, not silently chase it away from the main firing line.

Public squads need shared language more than perfect aim. Saying Shade left or Brute center gives the team a single focus point. Silent target switching is how a readable wave turns into four separate emergencies. For the shade burst behavior section, I keep the advice tied to observable play instead of a generic wiki summary.

Enemy recognition makes the run calmer. Regular bodies are space management, Runners are attention theft, Ashwalkers test early damage, Shades punish late callouts, and Brutes expose teams that cannot focus fire on command. For the shade burst behavior section, I keep the advice tied to observable play instead of a generic wiki summary.

Brute is slow but expensive to ignore. The estimated 650 HP means one scattered public squad can waste several magazines while the rest of the wave piles behind it.

Heavy Rifle, Arctic Striker, and turret pull are strong answers because they keep Brute pressure readable. Do not let every player swap to the Brute if fast enemies are still leaking.

Enemy recognition makes the run calmer. Regular bodies are space management, Runners are attention theft, Ashwalkers test early damage, Shades punish late callouts, and Brutes expose teams that cannot focus fire on command. For the brute target priority section, I keep the advice tied to observable play instead of a generic wiki summary.

The bestiary is written like a field notebook because exact internal values are not public. When I write HP estimate or guide taxonomy, I mean it as a practical label for repeated behavior, not a claim that Nectarforge published that number. For the brute target priority section, I keep the advice tied to observable play instead of a generic wiki summary.

Armored Pressure Zombie is guide taxonomy for the late slow wall. It represents the wave state where single-target sustained DPS and stuns beat random spray.

The team should burn it together during a cooldown window. If half the squad farms small bodies while the armored target walks into the hold, the lane loses all stored space.

The bestiary is written like a field notebook because exact internal values are not public. When I write HP estimate or guide taxonomy, I mean it as a practical label for repeated behavior, not a claim that Nectarforge published that number. For the armored pressure zombie handling section, I keep the advice tied to observable play instead of a generic wiki summary.

Target priority should change with the wave state. If fast enemies are loose, kill them before farming value. If the lane is stable, burn the armored target before it eats time. If a boss is active, save cooldowns for the moment it pulls the team out of shape. For the armored pressure zombie handling section, I keep the advice tied to observable play instead of a generic wiki summary.

Horde Boss is a cooldown plan, not just a giant health bar. Medic sustain, Tactician anchor timing, and late-wave damage windows decide whether the boss dies cleanly or drags the team into a messy next wave.

The boss should be pulled into a line that preserves turret sight and revive access. A boss kill that strands two players is not clean, even if the health bar reaches zero.

Target priority should change with the wave state. If fast enemies are loose, kill them before farming value. If the lane is stable, burn the armored target before it eats time. If a boss is active, save cooldowns for the moment it pulls the team out of shape. For the horde boss cooldown plan section, I keep the advice tied to observable play instead of a generic wiki summary.

Public squads need shared language more than perfect aim. Saying Shade left or Brute center gives the team a single focus point. Silent target switching is how a readable wave turns into four separate emergencies. For the horde boss cooldown plan section, I keep the advice tied to observable play instead of a generic wiki summary.

Read the matrix by role. Fast enemies steal attention, armored enemies steal time, and bosses steal cooldowns. A good squad assigns answers before all three problems arrive together.

Public squads need shared language more than perfect aim. Saying Shade left or Brute center gives the team a single focus point. Silent target switching is how a readable wave turns into four separate emergencies. For the weakness matrix section, I keep the advice tied to observable play instead of a generic wiki summary.

Enemy recognition makes the run calmer. Regular bodies are space management, Runners are attention theft, Ashwalkers test early damage, Shades punish late callouts, and Brutes expose teams that cannot focus fire on command. For the weakness matrix section, I keep the advice tied to observable play instead of a generic wiki summary.

Cash value changes target priority when the wave is under control. During clean waves, high-value bodies help fund the next upgrade. During messy waves, survival priority beats loot efficiency.

The rule I use is simple: stop what can wipe you now, then farm what funds the next spike. Reversing that order makes the run look efficient until it suddenly ends.

Enemy recognition makes the run calmer. Regular bodies are space management, Runners are attention theft, Ashwalkers test early damage, Shades punish late callouts, and Brutes expose teams that cannot focus fire on command. For the cash value and focus order section, I keep the advice tied to observable play instead of a generic wiki summary.

The bestiary is written like a field notebook because exact internal values are not public. When I write HP estimate or guide taxonomy, I mean it as a practical label for repeated behavior, not a claim that Nectarforge published that number. For the cash value and focus order section, I keep the advice tied to observable play instead of a generic wiki summary.

The bestiary separates sourced names from guide labels. Regular Zombie, Ashwalker, and Shade are source-backed; Runner, Brute, armored pressure, and boss labels are practical taxonomy used to explain behavior.

That distinction protects the page from fake authority. When official names or HP values become available, the guide should change labels instead of pretending estimates were official all along.

The bestiary is written like a field notebook because exact internal values are not public. When I write HP estimate or guide taxonomy, I mean it as a practical label for repeated behavior, not a claim that Nectarforge published that number. For the bestiary methodology section, I keep the advice tied to observable play instead of a generic wiki summary.

Target priority should change with the wave state. If fast enemies are loose, kill them before farming value. If the lane is stable, burn the armored target before it eats time. If a boss is active, save cooldowns for the moment it pulls the team out of shape. For the bestiary methodology section, I keep the advice tied to observable play instead of a generic wiki summary.