Enemy threat triage: verified examples, counters, and retreat plans

Abiotic Factor contains more combat entities than one stable guide can cover in full. The official Entities index changes as sectors and updates add threats, and an enemy's own page is the correct source for its current health, attacks, drops, weaknesses, resistances, and immunities. This page has a narrower job: turn that information into a repeatable decision before a fight.

Four enemies are used as verified examples: Captain, Lab Rat, Exor, and Exor Monk. They show why appearance or faction alone is not enough. A Captain mixes ranged and close pressure, a Lab Rat is documented as neutral, an Exor combines ranged quills with melee, and an Exor Monk teleports after attacks. Applying one generic "enemy strategy" to all four creates avoidable mistakes.

Threat-triage flow

The chart is an original decision aid based on current official entity and damage-system references. It is not a scale map and does not replace the exact statistics on an enemy's own page.

First question: is the entity hostile?

Do not begin with a weapon. Begin with identification. The official Entities index separates combat and non-combat entities, while individual pages can add important behavior such as neutral status. This matters for the Lab Rat. Its current page describes it as a neutral Order soldier. Treating every Order uniform as an immediate hostile target can create a fight that did not need to happen.

The Compendium is also a version-aware source inside the game. Use its colored damage-response indicators after an entity has been identified. Green indicates a weakness, yellow a resistance, and red an immunity according to the current Damage Types reference. An unknown entry is a reason to bring two distinct damage types and preserve an exit, not a reason to invent a weakness.

Verified example: Captain

The current Captain reference describes an Order field officer with a magnum revolver, melee attack, and grenade attack. Captains are often accompanied by other Order soldiers. This means the encounter is not solved by labeling the Captain a ranged target and rushing forward. The squad and the grenade threat must be included in the room plan.

Use solid cover to break the revolver's line of sight and avoid staying grouped around one piece of cover when a grenade is possible. The official page notes that shields can block the Captain's shots and melee attacks, but that does not make a shield a complete answer to a mixed squad or explosive placement. Check the shield's current class and preserve a side route rather than backing into a dead end.

Retreat trigger: leave when the room no longer has a clean line-of-sight break, when another squad joins, or when the backup weapon has become the only remaining option. Recovering behind cover is safer than trying to trade the last hit in the open.

Verified example: Lab Rat

The official Lab Rat page currently classifies the unit as neutral. That is the most important tactical fact. The correct opening is identification and space, not a preemptive attack. This page therefore removes older unsupported claims that Lab Rats are melee-only hostile units that create radioactive spore clouds.

If a Lab Rat becomes involved in combat because of player actions or surrounding events, reassess the actual encounter from its current entity page. Separate it from other units where possible, keep the route objective in mind, and stop escalating if the fight is optional.

Neutral does not mean harmless at close range: the Lab Rat reference documents 1 r/sec of radiation in a small radius around it. Avoid standing next to one without radiation protection, even if you intend to let it pass.

Retreat trigger: disengage when the encounter was not part of the mission or when attacking would pull additional units into a previously safe path.

Verified example: Exor

The Exor is not merely a close-range patrol target. Its current official page describes a burst of quills at range, dodging, and melee attacks when needed. The page also identifies electricity as a weakness. This supports a different plan from the old advice to stun it and take a free damage window.

Use cover against the ranged burst and do not stand still in an open lane. If electric damage is available, verify the selected weapon and its supply before entering the area. The enemy can appear with other Exors or other entities, so counting the group is part of the readiness check. A good damage match does not make crossfire safe.

Retreat trigger: break contact when multiple firing angles remove the cover advantage, bleeding or another status begins to consume the recovery budget, or the electric option cannot finish the planned route.

Verified example: Exor Monk

The Exor Monk's current page documents a long-range energy blast, a short-range melee attack, and teleportation after attacks. It recommends timed lateral movement against the energy blast and notes that ranged or melee approaches can both work. This guide does not add an item interaction that the current entity reference does not document.

Keep enough lateral space to sidestep the energy blast after its animation begins. Narrow corridors make that response less reliable. If closing for melee, preserve room to back away from the short-range attack. After a teleport, reacquire the target before committing to another swing or shot; firing at the old position wastes supply and attention.

Difficulty settings matter. The official page documents different energy-blast behavior in Apocalyptic mode, so advice learned on another difficulty should not be presented as a universal timing rule.

Retreat trigger: leave when the room no longer allows lateral movement, when multiple Monks create overlapping firing angles, or when a teleport repeatedly places the target outside the loadout's safe range.

Build the pre-fight inventory around the failure mode

Repair and load the primary before departure, but count the return path too. A weapon that can win one room and fail before extraction is not ready for the mission. Keep emergency equipment reserved for the retreat condition rather than using it to speed up routine enemies.

Stop conditions before an elite or boss attempt

The four examples above are not a boss roster. For Tarasque, Leyak, Reaper, and other special encounters, use the dedicated guide and current entity page. The same stop-condition method still applies.

Corpse recovery is a separate mission

After a failed fight, do not combine recovery with an immediate rematch. Carry one dependable weapon and enough healing to reach the dropped items. Use the safest known path, recover the items, and leave. Bank the recovered equipment, repair it, and update the threat sheet before another attempt.

If the enemy occupies the corpse location, use cover and timing to retrieve only what can be reached safely. The objective is recovery, not proving the old loadout can still win. This distinction protects both progress and the evidence needed to correct the next plan.

Related guides

• Enemy weakness and damage types
• Weapon comparison method
• Tarasque boss fight guide
• Leyak mechanics and containment
• Night Realm Reaper avoidance