Enemy Failure Diagnosis | Yet Another Zombie Survivors

Use the first unrecoverable problem

Select the one Enemy that first broke the run.
Select what failed: kill time, one contact, available space, or Freeze.
Select the rank that appeared: Base, Elite, or Super Elite when that Enemy has those records.
Change only the recommended squad job, then repeat the same run setup.

This guide covers the current player-facing Enemy records in Full Release 1.0. It does not calculate a result from Arena, difficulty, mode, Horde, or speed inputs. Those conditions can change the encounter, so the answer stays with the stored field you can verify for one Enemy.

Diagnose one Enemy

EnemyFirst unrecoverable failureEnemy rank

Choose the first Enemy that made the run unrecoverable.

Every finite Enemy, failure, and rank answer is expanded below when scripts are unavailable.

Your next correction

Butcher · Base · It survived too long

Default: Inspect Base health: 5,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Butcher at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Inspect this one Enemy

.enemy-diagnosis-interactive { display: none !important; }

All one-Enemy answers

Find one Enemy, rank, and failure

Scripts are off. Use only the answer matching the first Enemy problem that made the run unrecoverable.

Tower

Base · It survived too long

Default: Inspect Base health: 750,000. Give one squad job more damage against arena boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Tower at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Tower at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Tower at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Tower at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

The Devourer

Base · It survived too long

Default: Inspect Base health: 500,000. Give one squad job more damage against arena boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: The Devourer at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: The Devourer at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: The Devourer at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: The Devourer at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Hermit

Base · It survived too long

Default: Inspect Base health: 500,000. Give one squad job more damage against arena boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Hermit at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Hermit at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Hermit at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Hermit at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Chariot

Base · It survived too long

Default: Inspect Base health: 500,000. Give one squad job more damage against arena boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Chariot at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Chariot at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Chariot at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Chariot at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

The Alpha Infected

Base · It survived too long

Default: Inspect Base health: 500,000. Give one squad job more damage against arena boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: The Alpha Infected at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: The Alpha Infected at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: The Alpha Infected at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: The Alpha Infected at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Butcher

Base · It survived too long

Default: Inspect Base health: 5,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Butcher at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 300. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Butcher at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Butcher at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Butcher at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 10,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Butcher at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Butcher at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Butcher at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Butcher at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 50,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Butcher at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 600. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Butcher at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Butcher at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Butcher at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Humongous

Base · It survived too long

Default: Inspect Base health: 5,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Humongous at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Humongous at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Humongous at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Humongous at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 10,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Humongous at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 350. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Humongous at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Humongous at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Humongous at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 50,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Humongous at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Humongous at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Humongous at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Humongous at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Big Mummy

Base · It survived too long

Default: Inspect Base health: 8,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Big Mummy at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 300. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Big Mummy at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Big Mummy at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Big Mummy at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 16,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Big Mummy at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Big Mummy at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Big Mummy at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Big Mummy at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 80,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Big Mummy at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 600. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Big Mummy at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Big Mummy at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Big Mummy at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Juggernaut

Base · It survived too long

Default: Inspect Base health: 10,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Juggernaut at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 300. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Juggernaut at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Juggernaut at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Juggernaut at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 40,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Juggernaut at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Juggernaut at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Juggernaut at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Juggernaut at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 100,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Juggernaut at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 650. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Juggernaut at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Juggernaut at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Juggernaut at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Psion

Base · It survived too long

Default: Inspect Base health: 10,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Psion at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 300. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Psion at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Psion at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Psion at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 30,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Psion at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Psion at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Psion at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Psion at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 75,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Psion at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 600. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Psion at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Psion at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Psion at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Chainsawman

Base · It survived too long

Default: Inspect Base health: 10,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Chainsawman at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 300. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Chainsawman at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Chainsawman at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Chainsawman at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 20,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Chainsawman at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Chainsawman at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Chainsawman at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Chainsawman at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 100,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Chainsawman at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Chainsawman at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Chainsawman at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Chainsawman at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Charger

Base · It survived too long

Default: Inspect Base health: 4,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Charger at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 300. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Charger at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Charger at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Charger at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 8,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Charger at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Charger at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Charger at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Charger at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 40,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Charger at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 600. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Charger at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Charger at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Charger at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Werewolf

Base · It survived too long

Default: Inspect Base health: 6,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Werewolf at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 300. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Werewolf at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Werewolf at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Werewolf at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 10,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Werewolf at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Werewolf at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Werewolf at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Werewolf at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 50,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Werewolf at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 600. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Werewolf at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Werewolf at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Werewolf at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Witch

Base · It survived too long

Default: Inspect Base health: 2,500. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Witch at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 0. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Witch at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Witch at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Witch at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 5,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Witch at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Witch at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Witch at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Witch at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 25,000. Give one squad job more damage against boss targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Witch at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 600. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Witch at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Witch at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Witch at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

The Worm

Base · It survived too long

Default: Inspect Base health: 0. Do not tune the squad from this Enemy field; use the Arena event response, then repeat that Arena.

Reason: A Map event’s complete hazard result can live outside its Enemy record.

Premise: The Worm is a Map event with only a Base Enemy row, and the event itself caused the loss.

Cost: This diagnosis cannot turn the event record into a complete damage, movement, or control result.

Alternative: If a spawned Enemy caused the first unrecoverable problem, select that Enemy instead.

Base · One contact hit too hard

Default: Inspect Base damage: 0. Do not tune the squad from this Enemy field; use the Arena event response, then repeat that Arena.

Reason: A Map event’s complete hazard result can live outside its Enemy record.

Premise: The Worm is a Map event with only a Base Enemy row, and the event itself caused the loss.

Cost: This diagnosis cannot turn the event record into a complete damage, movement, or control result.

Alternative: If a spawned Enemy caused the first unrecoverable problem, select that Enemy instead.

Base · It closed the available space

Default: Inspect Base movement factor: 0. Do not tune the squad from this Enemy field; use the Arena event response, then repeat that Arena.

Reason: A Map event’s complete hazard result can live outside its Enemy record.

Premise: The Worm is a Map event with only a Base Enemy row, and the event itself caused the loss.

Cost: This diagnosis cannot turn the event record into a complete damage, movement, or control result.

Alternative: If a spawned Enemy caused the first unrecoverable problem, select that Enemy instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Do not tune the squad from this Enemy field; use the Arena event response, then repeat that Arena.

Reason: A Map event’s complete hazard result can live outside its Enemy record.

Premise: The Worm is a Map event with only a Base Enemy row, and the event itself caused the loss.

Cost: This diagnosis cannot turn the event record into a complete damage, movement, or control result.

Alternative: If a spawned Enemy caused the first unrecoverable problem, select that Enemy instead.

The Contamination

Base · It survived too long

Default: Inspect Base health: 0. Do not tune the squad from this Enemy field; use the Arena event response, then repeat that Arena.

Reason: A Map event’s complete hazard result can live outside its Enemy record.

Premise: The Contamination is a Map event with only a Base Enemy row, and the event itself caused the loss.

Cost: This diagnosis cannot turn the event record into a complete damage, movement, or control result.

Alternative: If a spawned Enemy caused the first unrecoverable problem, select that Enemy instead.

Base · One contact hit too hard

Default: Inspect Base damage: 0. Do not tune the squad from this Enemy field; use the Arena event response, then repeat that Arena.

Reason: A Map event’s complete hazard result can live outside its Enemy record.

Premise: The Contamination is a Map event with only a Base Enemy row, and the event itself caused the loss.

Cost: This diagnosis cannot turn the event record into a complete damage, movement, or control result.

Alternative: If a spawned Enemy caused the first unrecoverable problem, select that Enemy instead.

Base · It closed the available space

Default: Inspect Base movement factor: 0. Do not tune the squad from this Enemy field; use the Arena event response, then repeat that Arena.

Reason: A Map event’s complete hazard result can live outside its Enemy record.

Premise: The Contamination is a Map event with only a Base Enemy row, and the event itself caused the loss.

Cost: This diagnosis cannot turn the event record into a complete damage, movement, or control result.

Alternative: If a spawned Enemy caused the first unrecoverable problem, select that Enemy instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Do not tune the squad from this Enemy field; use the Arena event response, then repeat that Arena.

Reason: A Map event’s complete hazard result can live outside its Enemy record.

Premise: The Contamination is a Map event with only a Base Enemy row, and the event itself caused the loss.

Cost: This diagnosis cannot turn the event record into a complete damage, movement, or control result.

Alternative: If a spawned Enemy caused the first unrecoverable problem, select that Enemy instead.

Basic Zombie

Base · It survived too long

Default: Inspect Base health: 120. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Basic Zombie at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 100. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Basic Zombie at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Basic Zombie at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Basic Zombie at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 1,200. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Basic Zombie at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Basic Zombie at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.5. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Basic Zombie at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Basic Zombie at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Basic Zombie at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Basic Zombie at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Basic Zombie at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Basic Zombie at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

The Train

Base · It survived too long

Default: Inspect Base health: 0. Do not tune the squad from this Enemy field; use the Arena event response, then repeat that Arena.

Reason: A Map event’s complete hazard result can live outside its Enemy record.

Premise: The Train is a Map event with only a Base Enemy row, and the event itself caused the loss.

Cost: This diagnosis cannot turn the event record into a complete damage, movement, or control result.

Alternative: If a spawned Enemy caused the first unrecoverable problem, select that Enemy instead.

Base · One contact hit too hard

Default: Inspect Base damage: 0. Do not tune the squad from this Enemy field; use the Arena event response, then repeat that Arena.

Reason: A Map event’s complete hazard result can live outside its Enemy record.

Premise: The Train is a Map event with only a Base Enemy row, and the event itself caused the loss.

Cost: This diagnosis cannot turn the event record into a complete damage, movement, or control result.

Alternative: If a spawned Enemy caused the first unrecoverable problem, select that Enemy instead.

Base · It closed the available space

Default: Inspect Base movement factor: 0. Do not tune the squad from this Enemy field; use the Arena event response, then repeat that Arena.

Reason: A Map event’s complete hazard result can live outside its Enemy record.

Premise: The Train is a Map event with only a Base Enemy row, and the event itself caused the loss.

Cost: This diagnosis cannot turn the event record into a complete damage, movement, or control result.

Alternative: If a spawned Enemy caused the first unrecoverable problem, select that Enemy instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Do not tune the squad from this Enemy field; use the Arena event response, then repeat that Arena.

Reason: A Map event’s complete hazard result can live outside its Enemy record.

Premise: The Train is a Map event with only a Base Enemy row, and the event itself caused the loss.

Cost: This diagnosis cannot turn the event record into a complete damage, movement, or control result.

Alternative: If a spawned Enemy caused the first unrecoverable problem, select that Enemy instead.

VRer Shield

Base · It survived too long

Default: Inspect Base health: 10,000. Give one squad job more damage against spawned unit targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: VRer Shield at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 0. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: VRer Shield at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.85. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: VRer Shield at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: VRer Shield at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 80. Give one squad job more damage against spawned unit targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: VRer Shield at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 300. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: VRer Shield at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: VRer Shield at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: VRer Shield at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against spawned unit targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: VRer Shield at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: VRer Shield at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: VRer Shield at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: VRer Shield at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Scarab

Base · It survived too long

Default: Inspect Base health: 40. Give one squad job more damage against spawned unit targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Scarab at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Scarab at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.85. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Scarab at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Scarab at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 80. Give one squad job more damage against spawned unit targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Scarab at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 300. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Scarab at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Scarab at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Scarab at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 500. Give one squad job more damage against spawned unit targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Scarab at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Scarab at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Scarab at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Scarab at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Blisterer

Base · It survived too long

Default: Inspect Base health: 450. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Blisterer at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Blisterer at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.75. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Blisterer at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Blisterer at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Blisterer at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 300. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Blisterer at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Blisterer at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Blisterer at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Blisterer at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Blisterer at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Blisterer at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Blisterer at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Boomer

Base · It survived too long

Default: Inspect Base health: 250. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Boomer at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Boomer at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.75. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Boomer at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Boomer at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 2,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Boomer at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Boomer at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Boomer at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Boomer at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Boomer at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Boomer at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Boomer at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Boomer at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Fat Worm

Base · It survived too long

Default: Inspect Base health: 250. Give one squad job more damage against spawned unit targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Fat Worm at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Fat Worm at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.8. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Fat Worm at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Fat Worm at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 2,000. Give one squad job more damage against spawned unit targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Fat Worm at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Fat Worm at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Fat Worm at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Fat Worm at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against spawned unit targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Fat Worm at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Fat Worm at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Fat Worm at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Fat Worm at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Horrid

Base · It survived too long

Default: Inspect Base health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Horrid at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 250. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Horrid at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.8. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Horrid at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Horrid at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 2,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Horrid at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Horrid at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Horrid at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Horrid at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Horrid at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Horrid at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Horrid at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Horrid at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Firefrighter

Base · It survived too long

Default: Inspect Base health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Firefrighter at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Firefrighter at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Firefrighter at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Firefrighter at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 2,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Firefrighter at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Firefrighter at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Firefrighter at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Firefrighter at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Firefrighter at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Firefrighter at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Firefrighter at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.5. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Firefrighter at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Fly

Base · It survived too long

Default: Inspect Base health: 2. Give one squad job more damage against spawned unit targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Fly at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 150. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Fly at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Fly at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Fly at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 1,000. Give one squad job more damage against spawned unit targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Fly at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 300. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Fly at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Fly at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Fly at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against spawned unit targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Fly at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Fly at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Fly at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 0.75. Stop treating Freeze as full-strength control for this Enemy; clear it before the control window becomes necessary.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Fly at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Mummy

Base · It survived too long

Default: Inspect Base health: 600. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Mummy at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Mummy at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.5. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Mummy at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Mummy at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 3,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Mummy at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Mummy at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Mummy at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Mummy at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Mummy at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Mummy at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Mummy at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Mummy at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Bricklayer

Base · It survived too long

Default: Inspect Base health: 350. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Bricklayer at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Bricklayer at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Bricklayer at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Bricklayer at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 2,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Bricklayer at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Bricklayer at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Bricklayer at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Bricklayer at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Bricklayer at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Bricklayer at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Bricklayer at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Bricklayer at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Wendigo

Base · It survived too long

Default: Inspect Base health: 800. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Wendigo at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 150. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Wendigo at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.85. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Wendigo at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Wendigo at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 1,800. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Wendigo at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 250. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Wendigo at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Wendigo at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Wendigo at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Wendigo at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Wendigo at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Wendigo at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Wendigo at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Relevant

Base · It survived too long

Default: Inspect Base health: 1,250. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Relevant at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 250. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Relevant at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.9. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Relevant at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Relevant at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 2,500. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Relevant at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Relevant at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Relevant at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Relevant at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Relevant at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Relevant at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Relevant at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Relevant at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Runner

Base · It survived too long

Default: Inspect Base health: 120. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Runner at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 120. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Runner at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.85. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Runner at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Runner at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 1,300. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Runner at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Runner at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Runner at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Runner at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Runner at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Runner at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Runner at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Runner at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Screamer

Base · It survived too long

Default: Inspect Base health: 500. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Screamer at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 120. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Screamer at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.85. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Screamer at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Screamer at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 2,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Screamer at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Screamer at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Screamer at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Screamer at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Screamer at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Screamer at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Screamer at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Screamer at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Spider

Base · It survived too long

Default: Inspect Base health: 160. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Spider at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 150. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Spider at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.85. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Spider at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Spider at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 1,400. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Spider at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Spider at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 0.9. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Spider at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Spider at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Spider at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Spider at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Spider at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Spider at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Spitter

Base · It survived too long

Default: Inspect Base health: 200. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Spitter at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 150. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Spitter at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Spitter at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Spitter at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 2,250. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Spitter at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 250. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Spitter at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Spitter at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Spitter at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Spitter at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Spitter at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Spitter at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Spitter at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Desert Spitter

Base · It survived too long

Default: Inspect Base health: 250. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Desert Spitter at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 150. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Desert Spitter at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Desert Spitter at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Desert Spitter at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 2,250. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Desert Spitter at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 250. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Desert Spitter at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Desert Spitter at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Desert Spitter at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Desert Spitter at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Desert Spitter at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Desert Spitter at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Desert Spitter at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Droner

Base · It survived too long

Default: Inspect Base health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Droner at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 0. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Droner at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.9. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Droner at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Droner at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 2,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Droner at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 0. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Droner at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Droner at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Droner at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Droner at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 0. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Droner at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Droner at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Droner at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Derailer

Base · It survived too long

Default: Inspect Base health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Derailer at Base rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Base · One contact hit too hard

Default: Inspect Base damage: 200. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Derailer at Base rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Base · It closed the available space

Default: Inspect Base movement factor: 0.9. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Derailer at Base rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Base · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Derailer at Base rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Elite · It survived too long

Default: Inspect Elite health: 2,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Derailer at Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Elite · One contact hit too hard

Default: Inspect Elite damage: 400. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Derailer at Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Elite · It closed the available space

Default: Inspect Elite movement factor: 1.1. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Derailer at Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Derailer at Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Super Elite · It survived too long

Default: Inspect Super Elite health: 1,000. Give one squad job more damage against horde targets, then repeat the same run setup.

Reason: Health is the stored field tied directly to how much damage this rank must take.

Premise: Derailer at Super Elite rank was the first target that survived long enough to break the run.

Cost: Changing one squad job gives up part of its current role, and this stored value is not an Arena or difficulty calculation.

Alternative: If the target died on time but forced a bad position, diagnose lost space instead.

Super Elite · One contact hit too hard

Default: Inspect Super Elite damage: 500. Protect the squad from the next contact before repeating the same run setup.

Reason: Damage is the stored field tied directly to one registered hit from this rank.

Premise: Derailer at Super Elite rank caused the first contact loss; this does not estimate later run scaling.

Cost: Adding protection gives up damage or control somewhere else in the squad.

Alternative: If repeated hits, not one hit, caused the loss, inspect this Enemy’s attack interval on the Enemy page.

Super Elite · It closed the available space

Default: Inspect Super Elite movement factor: 1.25. Clear this Enemy earlier in the wave instead of waiting until it reaches the squad.

Reason: The rank movement factor is the stored field tied to how its movement changes at this rank.

Premise: Derailer at Super Elite rank was the first Enemy to close the usable lane.

Cost: Earlier focus can leave less damage for another active target.

Alternative: If the lane stayed open until Freeze failed, diagnose the control failure instead.

Super Elite · Freeze did not hold it

Default: Inspect Freeze factor: 1. Keep Freeze as the tested control, but change only its timing before changing the run setup.

Reason: Freeze has its own stored response factor; it does not stand in for knockback, penetration, or instant kill.

Premise: Derailer at Super Elite rank was the first control failure, and Freeze was the effect that failed.

Cost: This answer covers Freeze only and does not infer a response for another control effect.

Alternative: If knockback was the failed effect, open this Enemy and inspect its separate Knockback factor.

Open the default single-Enemy record

Read the result

The first line is the action. It names one stored field and one correction to test. Reason explains why that field matches the selected failure. Premise tells you when the answer applies. Cost names what the correction gives up. Alternative tells you when to change the failure instead of forcing the current answer.

Keep the run setup fixed for the next test. If you change the Arena, difficulty, mode, Horde level, squad, and diagnosis at once, you will not know which change fixed the loss.

Know the rank boundary

Base, Elite, and Super Elite are stored rows inside one Enemy record. They are not three Enemies and they are not a universal strength ranking. The selected row supplies health, damage, and movement factor. Freeze response belongs to the Enemy and remains independent of knockback, penetration, and instant kill.

For , Base health is 5,000, Elite health is 10,000, and Super Elite health is 50,000. Those are stored records, not an exact forecast for a chosen run setup.

Handle special records

Arena bosses expose only Base in this diagnosis. Their Enemy detail also keeps difficulty-specific health and tempo in Difficulty I, II, then III order; use that table when the selected threat is the final Arena boss.

Direct timed Super Elite spawns occur only in Endurance. A populated Super Elite row on another category does not prove that it will appear through this timed spawn path.

Map events also expose only Base here. A zero damage value in an Enemy record does not prove the Arena event is harmless because the event’s own rules can own its damage. Use the linked Arena hazard guide for that event instead.

Use the Enemy page

Each answer opens the selected record at Enemies. The detail keeps its complete rank rows, attack interval, movement values, control responses, mode caps, Arena-boss rows, and Arena/mode/wave appearances in one dialog.

Use that page for the alternative named by the diagnosis. If one hit was not the problem, inspect attack interval separately. If knockback failed, inspect Knockback factor instead of treating the Freeze result as a general control label.

FAQ

Why does the guide not calculate the exact health for my run?

The current Enemy records do not provide a complete result for arbitrary Arena, difficulty, mode, Horde, and speed choices. The guide therefore uses stored Enemy fields and leaves run conditions separate.

Does a higher rank always explain the loss?

No. Rank changes stored fields, but the first unrecoverable failure still decides which field matters. A movement or control problem is not answered by health alone.

What if two Enemies were on screen?

Choose the first one that made recovery impossible. Diagnose its field and repeat the same setup. If the first problem changes, run the guide again for that one Enemy.

Is Freeze factor also the Knockback factor?

No. They are separate stored responses. This guide uses Freeze for the control-failure branch; the selected Enemy detail shows Knockback separately.

What to Check After an Enemy Ends Your Run

Use the first unrecoverable problem

Diagnose one Enemy

Find the field tied to the loss

Butcher · Base · It survived too long

Read the result

Know the rank boundary

Handle special records

Use the Enemy page

FAQ

Why does the guide not calculate the exact health for my run?

Does a higher rank always explain the loss?

What if two Enemies were on screen?

Is Freeze factor also the Knockback factor?