From level to strength

The baseline coefficients are ZombieLevelBase = 0.9 and ZombieLevelAdd = 0.1. Let $F_{32}$ mean rounding to float32, and $\operatorname{fma}_{32}(x,y,z)$ mean a fused $xy+z$ followed by that rounding. Decimal truncation and the level curve are

Define the integer bounds $a=\operatorname{clamp}(\lfloor q\rfloor,1,10)$ and $b=\operatorname{clamp}(\lceil q\rceil,1,10)$. If $a=b$, every instruction requests that level. Otherwise, let $d=u\bmod100$ for the next integer draw and calculate

The fractional part therefore selects between adjacent integer levels; it is not itself the stored entity level. In the baseline, the request becomes fixed at $[10,10]$ from level 91.¹1Float32 level requestsThe native chain uses fused multiply-add with the float32 base/add coefficients, decimal truncation, a cap of 10, then floor/ceil clamped to 1–10. When those bounds differ, the upper choice is accepted when the integer residue is below the float32 fractional part multiplied by 100. The default inputs 2 and 3 both produce approximately 1.100000024 and accept residues 0–10.0x101d4561c · 0x101b3a27c

Float32 cannot represent every decimal exactly. Inputs 2 and 3 both reach approximately 1.100000024 after the native truncation sequence, and their slightly-above-10 threshold accepts residues 0–10. The view below exposes every ordinary level, its bounds, threshold, and accepted residues.

This residue test belongs to ordinary spawn instructions. Modern portal children use the same level bounds but a separate global floating-point draw path.

Creation can apply level-module modifiers before storing the effective level $\ell$. ZombieMaxLevel defaults to $-1$, so its clamp is inactive unless overridden. The ordinary definitions do not impose a five-level cap.

For a non-Zomboss entity in DangerRoom, both multipliers come from the shared ZombieLevelStats vector, using index $\ell-1$. This path does not read the type’s own level-stat vector. Penny’s Pursuit uses a separate Rift configuration; NewPVP has another shared-table branch.

The Endless gameplay reference

Health examples, including the wave-construction view, use the following ten-level Endless reference by default.

Both columns are relative to level 1. The attack column is a reported relative value; $a_\ell$ in the bite formula below is the separate native AttackLevel input. Substituting a final damage ratio for that input would count the additional level factor twice.

The five-row DangerRoom table and its replacement

DefaultDangerRoomProps contains five rows: both HitPointsLevel and AttackLevel are 1, 2, 3, 4.5, and 5. A missing index returns multiplier 1; it neither repeats the last row nor extrapolates a growth formula. The generator’s request range of 1–10 and this table’s length are independent inputs.²2Shared table lookup and missing rowsThe non-Zomboss DangerRoom lookup uses the shared ZombieLevelStats vector at effective entity level minus one. The bundled vector has five rows and a missing row returns multiplier 1; neccd.zls can replace the ordered pairs. The adopted ten-level Endless reference is reported gameplay data. Its attack column is a reported ratio, kept separate from the native AttackLevel input. Rift and NewPVP have separate table-selection branches; NewPVP's player-facing identity is unresolved. The level-module ZombieMaxLevel default is -1, and the ordinary definitions omit an override.0x1019938a0 · 0x101993af8 · 0x101d6db00 · 0x100fd8a10 · 0x10067f50c

neccd.zls can replace the entire ordered vector with attack/health pairs. Row order determines which effective level reads each pair. Replacing the table does not require changing the level curve, and a module-level override does not create a missing table row.

The other tables use different progressions:

• Penny’s Pursuit uses the Rift path. Its table has 19 rows, with levels 9–19 declaring 11–21 in both fields.
• Across 140 files, the main-level five-row sequence appears in 916 of 1,050 declarations. It is common, but other per-type declarations differ.
• The NewPVP table matches the reported Battlez values through level 8, then declares 10 and 20 at levels 9–10.
• The legacy PvP comparison matches through level 4 but includes a fifth row of 5. LocalDiyZombieStatsDefault shares Rift’s first eight values and adds 11 and 12.

The reported level-10 health multiplier of 100,000 is representable through the replacement path. Stored body and helmet HP remain distinct from the signed 32-bit value reported to wave scheduling: that reporting path can saturate.

With other health modifiers neutral, the resource values give

when a helmet is present. The implementation also accounts for module modifiers and existing health-reduction factors.

The chewing-rate getter chooses its base rate $E$ in this priority order:

1. Positive EatDPSRatio times maximum body HP.
2. Otherwise, positive instance m_extraEatDPS.
3. Otherwise, positive instance m_baseEatDPS.
4. Otherwise, the property EatDPS.

For the base bite implementation, let $a_\ell$ denote the native AttackLevel field. With other target/type modifiers neutral,

Here $v_{\mathrm{attack}}$ is the condition-dependent attack-pace factor and $\Delta t$ is game-clock delta. The table’s attack multiplier is therefore only one factor; a fixed EatDPS is not the complete final bite rate. Specialized subclass attacks can use other implementations.³3The base chewing-rate chainThe rate getter first uses a positive EatDPSRatio multiplied by maximum body health, then positive extraEatDPS, then positive baseEatDPS, then the property EatDPS. The base bite path multiplies this selected rate by the attack-table multiplier, attack pace, frame time, and 1 + 0.2 × (effective level - 1), with further condition/type modifiers and a nonnegative clamp.0x1019b55b0 · 0x10199f658

For a neutral level-5 mummy_armor1, declared body/helmet HP 270/370 becomes 4050/5550 with the reported health multiplier 15. Reported attack is 2 relative to level 1; this does not determine the native bite rate.

For comparison, the five-row DangerRoom table gives 1350/1850 HP. Its EatDPS = 100, native attack multiplier 5, and level factor 1.8 produce 900 damage per game second at attack pace 1. The view lets you switch between the Endless reference and this DangerRoom-table calculation.

On the first true leader mark, current body HP is multiplied by LeaderStrengthenRate and the result becomes maximum body HP. The baseline rate is 2. A present helmet is strengthened separately with its existing armor-health reduction factor reapplied and a nonnegative clamp; its resulting current HP also becomes its maximum.

Repeating the true mark does not multiply again, and a false call does not undo the earlier operation. This path changes neither $\ell$ nor the cached attack-table multiplier. For the fixed-EatDPS conehead above, the adopted health reference gives a neutral leader result of 8100/11100 HP. In the bundled-table comparison, the result is 2700/3700 HP while the calculated bite rate remains 900. A type using EatDPSRatio can instead gain bite damage indirectly through its larger maximum body HP.

The leader update changes its overlay as combined body/helmet health falls through approximately 67% and 33% of the combined maximum. Those transitions do not heal it. A qualifying leader at $X<232$ in the ordinary five-row layout enters a retreat path, starts a 2.3-game-second countdown, and requests removal when it expires.⁴4Leader marking and retreatFirst marking scales current body HP and stores it as maximum HP; helmet handling also accounts for its reduction factor. Repeated true marking does not repeat this operation. This path does not change the entity level or directly multiply cached attack. Overlay thresholds use combined maximum body/helmet health. The ordinary retreat threshold is X < 232 with a 2.3-game-second countdown.0x1019afe48 · 0x10199a84c