Before the first zombie

The 16 standard worlds all list DangerRoomJitteredWaveGenerator. They provide different zombie pools, but the ordinary description builder reads its point parameters from the shared DangerRoomPropertySheet, rather than the generator object's local point declarations.¹1The shared inputsThe ordinary description builder reads point fields from the shared DangerRoomPropertySheet. The response setter writes server-supplied values into that same object. The local generator declarations are a separate set of fields; they are not the point inputs consumed by this builder.0x101ab6840 · 0x101d6db00

The world still matters: it supplies the basic zombie, the pool of selectable types, and any additional designers. Modern, Renai, Steam, and Tale even declare a local wave increment of 20, but this builder does not read that local field. Its shared increment remains the input to the formula.

Our example settings are 100 starting points, a fixed wave increment of 30, and a per-level increment of 5. The wave-count settings are MinWaveCount = 5, MaxWaveCount = 15, WaveAddEach = 1, and WaveAddInterval = 10: one extra wave per ten displayed levels.

Let $L$ denote the displayed level and $w$ a zero-based wave index. The stored progress value is $L-1$. In the example schedule, multiples of 5 select Boss files. The ordinary-level views below therefore cover $L\in\{1,\ldots,149\}$ with $L\bmod5\ne0$.²2Which level number?The designer getter returns the stored progress value plus one. The filename helper chooses the Boss variant when the displayed number is divisible by the shared BossInterval, whose bundled value is 5. The inspected post-victory continuation branch loads a next level only below 150. The explorer therefore offers ordinary numbers from 1–149; this client branch does not establish a universal server admission rule.0x101d6ca84 · 0x101d4a4e8 · 0x101c360dc

Levels 1–9 have 5 waves, level 36 has 8, and level 49 has 9. The formula reaches the cap of 15 at level 100; since that number selects a Boss file, level 101 is the first ordinary level at the cap. Point budgets continue growing afterward.³3Wave count and flag spacingThe description builder uses MinWaveCount, MaxWaveCount, WaveAddEach, and WaveAddInterval. The inspected constructor defaults are 6, 15, 1, and 5. This guide uses the supplied gameplay wave settings 5, 15, 1, and 10. Within the resulting 5–15-wave range, the target group count is 1 below 7 waves, 2 below 12, and 3 otherwise. The resulting spacing equals the wave count divided by that target, rounded up.0x101ab6840 · 0x101d4a7e8

For $w=0,\ldots,N(L)-1$, define the increment $\Delta$ and base budget $P$:

Within one level, the base budgets form an arithmetic progression. Increasing $L$ changes its slope; the first wave remains at 100 points.⁴4The underlying budgetThe shared constructor supplies StartingPoints = 100, BasePointIncrementPerWave = 30, and BasePointIncrementPerLevel = 5. The description builder adds the combined per-wave increment once for each zero-based wave index.0x101ab6840 · 0x101d4a7e8

Within the 5–15-wave range, the target group count $g$ determines the regular flag spacing $s$:³

The filler budget $B$ is:

A regular flag boundary occurs whenever the one-based wave number is a multiple of $s$. The last wave also receives the larger budget even when its group is shorter. These markers describe the wave plan; they do not yet count an extra flag zombie.

The logical OR matters: a wave that is both final and at a regular flag boundary receives one multiplier, not two. The next wave still follows the unboosted progression.⁵5One boost at either boundaryThe materialization path multiplies the base budget by 2.5 when the wave is at a regular flag boundary or is final. It applies the multiplier once even when both conditions hold. The product uses float32 arithmetic and is truncated to an integer. The next wave continues from the unboosted base progression.0x101ce8a54

The ordinary filler spends $B$ using each selected type's WavePointCost. This is neither a zombie count nor a total-health cap. Unspendable points may remain; extra leaders and separate flag actions are added elsewhere. World-specific processing can then replace or supplement the generated roster.⁶6What the budget pays forThe weighted filler consumes points using each selected type’s WavePointCost. Extra leaders are appended after normal filling; the flag zombie is installed as a separate action. Eighties can replace instructions in postprocessing without repeating the ordinary budget check. The budget therefore describes one stage of construction, not a final zombie count or total-health cap.0x101ce7f08 · 0x101c79bec · 0x101ce4f5c

At a flag boundary or the final wave, installation can add a separate flag-zombie action. It has its own default spacing and does not pay its cost from $B$. World processing and extra leaders likewise operate at different stages. The health total used by the wave clock is sampled only after these actions have created and placed their entities.

The next question is how the game chooses that roster: which types are selected, and how do their costs and weights determine the next zombie?