Patrols

The game stores countdown values, but it reduces them using the current countdown speed. A stored value of 80 therefore does not guarantee an 80-second wait. At 1.60× it falls 60% faster, and the speed can change again as mission progress, squad size, position, or other mission conditions change.

For estimates, track how fast the timer is currently falling rather than treating the stored value as seconds.

Difficulty and faction select a baseline value from the current D1–D10 table used by ordinary Patrol lane initialization. The initialization path randomizes from a 2-second lower bound and can apply additional live/profile scaling before the lane countdown is written.

Read the table as baseline tuning, not as a guaranteed spawn interval or a guaranteed maximum starting countdown. After initialization, live Patrol modifiers keep changing how quickly the stored countdown falls, and a due lane still has to pass the later admission and placement checks.

Several independent factors combine to control how quickly each Patrol timer falls. The current build confirms both the timer consumers and the current patrol tuning. The gameplay-facing names of two inputs remain unresolved, but their current numeric effects can still be stated directly.

While a deployed SEAF contingent is active, ordinary enemy Patrol and reinforcement countdowns run at no less than 1.60× speed. Other countdown modifiers are calculated first. If their combined speed already exceeds 1.60×, the SEAF minimum has no additional effect.

This is a temporary effect tied to the active SEAF deployment, not a fixed bonus for the entire operation. The game enables it after an eligible deployment and removes it when that deployment state resets. A field report also observed the faster countdowns disappear when SEAF soldiers died or despawned.

Once the deployment quota is met, the controller can reset the active state when its counted surviving force falls below 34% of the configured target. A target of six and a count of two would meet that condition, but the game can substitute counts in some cases. Two living soldiers is therefore not a guaranteed cutoff for every squad or deployment.

The minimum stops applying on subsequent countdown updates when the SEAF state resets. It does not force an immediate spawn, bypass enemy capacity checks, or change Patrol placement. The same minimum applies to ordinary enemy reinforcements; see reinforcement timing.

Evidence: Code confirmed for the active-state gate, both countdown floors, and the conditional casualty reset. Live supported by a member report; a controlled before-and-after measurement has not been documented.

Select the active factors to calculate how quickly an ordinary Patrol countdown drains. The selected factors multiply together, then any active minimum countdown speed is applied.

Current code still indexes the Patrol timing modifier by active Helldiver count. The exact multipliers below are retained values supported by the unchanged current consumer.

When qualifying areas overlap, the strongest active effect is used rather than adding the curves together. An area can therefore change Patrol countdown speed without becoming the place the next Patrol approaches from. The approach is chosen later, after a timer is due.

The game keeps eight ordinary Patrol timing groups. Each active group can hold up to four independent lane countdowns at once. Multiple lanes have been seen active in the same group, so there is not one Patrol timer per player or one timer for the whole mission.

One lane is confirmed as the base ordinary Patrol channel. Other lanes can coexist, but their exact gameplay roles remain unresolved.

The ordinary lane gate first compares the live Patrol category count with the current Patrol target. It does not read the separate Encounter category count, so Encounter activity does not directly freeze the lane countdown.

The interaction happens when a lane is ready to spawn. The game adds the selected Patrol's quantity, in-flight spawn occupancy, and active enemy capacity usage. On the normal path, a total above 100 rejects the attempt and resets that lane to the five-second retry. The separate timed Patrol scheduler also reads the same active-enemy capacity and applies its own 100-unit capacity gate.

Instrumented combat captures confirm that Encounter units participate in this occupancy. In one capture, 64 encounter + 8 patrol + 2 guard-group enemies = 74, matching the shared capacity value of 74. Another capture had 46 encounter + 1 guard-group + 12 battle-group enemies = 59, matching a capacity value of 59.

The practical result is conditional suppression rather than a universal Encounter lock. A small Encounter can leave enough capacity for another Patrol; a large Encounter or other accumulated AI population can keep due Patrols from being admitted until occupancy falls again.

A separate Patrol timer can also create groups classified as Patrol, while the Traveler timer can create other roaming groups that may look like patrols in play. Different roaming groups can therefore overlap without sharing one countdown.

The game shuffles possible mission locations, removes locations that are not allowed, then checks that the remaining options are far enough from the relevant player before choosing an approach.

Retained tests show that active outpost- and nest-style locations are important preferred approaches. The current build still does not safely identify every possible location as an outpost, nest, objective, or POI in this path, so the full category list remains unresolved.

Timer expiry begins the next stage; it does not guarantee an immediate squad. The game filters the available Patrol groups for the current mission, adjusts how likely each group is, resolves the exact enemies, checks population limits, chooses the approach, and then tries to place the spawn.

The Enemy Constellations & Composition report covers group composition, variants, and specialist replacements in detail.