Aliens Fireteam Elite 2 Bots and Solo Guide

The bots in Aliens Fireteam Elite 2 are companion AI intended to support a squad when human players are unavailable, but the collected sources do not yet provide a complete official behavior manual. Launch notes confirm fixes for seven companion Bot perks in multiplayer, improved healing behavior on high difficulty, and several mission-specific Bot problems. Exact Bot classes, weapon loadouts, revive priorities, and objective logic are unverified.

What the launch notes confirm

Daybreak’s Day-1 notes mention fixes to seven companion Bot perks in multiplayer and state that Bots do not run out of heals as quickly on high difficulty. They also list a science-lab lockout fix, an A-Pose fix, and a correction so Poison Station gas no longer affects Bots. These are concrete launch-state changes, but they do not form a full list of Bot commands or priorities.

The notes also reference specific campaign situations such as Colony Mission 3 and Banshee Down. A patch reference tells us where a problem was fixed, not that the Bot follows a particular route in every run. Treat any broader behavior claim as unverified unless the live game or an official guide demonstrates it.

Bot classes and weapons

The Horde preview describes Alpha, Beta, and Gamma synth companions. Because that detail comes from a preview, the names and their final launch roles should be marked “preview observation” or unverified until the released interface confirms them. The collected official sources do not provide a complete Bot class table or weapon inventory.

Do not assign a Bot a Medic, Hunter, Machinist, Marauder, or Duelist identity merely because the player’s fireteam uses that class. Record the exact name, weapon, ability, and behavior shown in-game. If a Bot can switch equipment or role, document the condition instead of presenting one observed loadout as universal.

Healing and revives

The Day-1 notes specifically improve Bot healing behavior on high difficulty and fix Medic client and revive interactions. That supports the practical expectation that high-difficulty solo play received launch attention. It does not confirm how often a Bot heals, whether it prioritizes the lowest-health player, or whether it can always revive under pressure.

For a reliable test, reduce one player’s health, place the team in a known combat state, and record whether the Bot heals, retreats, revives, or continues shooting. Repeat with different distances and objectives. Exact cooldowns, priority rules, and failure conditions remain unverified.

Mission behavior and stuck states

The science-lab lockout and A-Pose fixes show that companion behavior can be affected by mission scripting and animation state. Poison Station gas no longer affecting Bots is another example of a class ability interacting with AI rules. These fixes are useful when diagnosing a run, but they do not prove that every navigation problem has been resolved.

When a Bot appears stuck, first check whether the objective has advanced, whether a door or interaction is waiting, and whether the AI is returning from a revive or combat state. Capture the mission, objective, difficulty, player count, and exact location before reporting a repeatable issue. Avoid turning one unusual path into a guaranteed behavior claim.

How to test Bots fairly

Compare the same mission with the same class, weapons, difficulty, and objective while changing only the number of human players. Record damage contribution only if the game exposes it clearly, and separately record healing, revives, ammo use, target selection, and objective progress. A Bot can be valuable for completing an objective even if its damage is lower than a human player’s.

Horde is a particularly useful test because waves create repeatable pressure, but preview descriptions of Alpha, Beta, and Gamma must remain distinct from launch-confirmed facts. The embedded preview video is context, not proof of final AI behavior. Update this page when direct launch footage or official notes clarify the companion roster.

Current solo recommendation

Solo players should choose a class they can operate consistently and plan around Bot support rather than assume the AI will solve every role. Medic, Machinist, Hunter, Marauder, Duelist, and Specialist have confirmed player-facing identities, but no source proves which is best with Bots. That conclusion is therefore unverified.

The confirmed fixes come from Daybreak’s Day-1 patch notes; companion names and preview behavior come from AvP Galaxy’s Horde preview. Any final Bot roster, weapon list, revive rule, or objective priority must be verified in the released game.