XCOM 2 Alien Analysis: Andromedon


HP: 12/15/18/21
Armor: 3/4/4/4
Defense: 10
Dodge: 0
Aim: 70/80/80/80
Mobility: 12/14/14/14 (8/16 on Rookie, 9/18 otherwise)
Damage: 9-11 (+4)
Shred: 2
Crit Chance: 0/10%/10%/10%
Will: 50/85/100/100

Immunities
The Andromedon is immune to all damage over time effects.

I'm not sure why the Andromedon has a unique graphic for its immunities -every other enemy shares the one icon I've been using, if they have immunities listed in-game at all- especially given it's just recycling the icon for the Enemy Within Mec's Absorption Fields ability. It's very strange.

Regardless, the Andromedon is one of a bare handful of enemies that can't be afflicted with Acid. The only other cases, normally, are Codices and Spectres, which is a bit interesting.

This doesn't do much to dissuade tossing Acid Bombs at Andromedons, mind, since they're an extremely efficient way to remove all their Armor. It's kind of too bad there's no Acid Ammo or anything to make it a bit more significant that Andromedons are immune to Acid. It does matter, since you'll never throw an Acid Bomb, knock them to one HP, and then let them die to ongoing damage (Since they're immune to the other two damaging statuses, too), but it doesn't matter much, simply due to how rare Acid is as a concept.

Ah well.

Wall Smash
Can walk directly through destructible terrain freely, destroying it.

I've alluded to this before, but the AI tries to not walk through walls and whatnot if you can't see the units in question. The surprising thing is the Andromedon is the most consistently guilty about failing to cleave to this: for whatever reason, unseen Andromedons are really prone to patrolling straight through walls while their podmates trail in behind through their Koolaid-man entrance. It's not unusual to end up knowing Andromedons are about before you first see one by virtue of finding conspicuous single-tile holes in walls that shouldn't have such holes; if you see one of these holes, an Andromedon is on the map and in fact is probably very close by.

The really weird thing is that Andromedons are actually a lot more conscientious when you can see them, prone to pathing around Cover and other obstacles instead of smashing right through them, even if ramming through a wall would give them an easy flank on one of your soldiers. The final bit of weird to this whole thing is that Andromedons under player control are not careful: if an AI-controlled Andromedon elects to path through a tile containing Low Cover, they will generally hop that Low Cover, leaving it intact. If the player orders a Mind Controlled Andromedon to path through a tile containing Low Cover, they'll always rampage right through it, vaporizing the Cover.

So, uh, if you Dominate an Andromedon, be careful about where you walk them. They're perfectly happy to trample the Cover your squad is using as they faithfully carry out your orders, and the game's line-based visualization of predicted pathing is often not quite accurate to a unit's actual path if it's anything other than an orthogonally straight line: the travel prediction might make it look like the Andromedon will pass beside a piece of Cover, only for issuing the move order to result in them trampling right through it.

Anyway, the Andromedon is the first example of an enemy able to path through walls, and if we ignore Shen's Last Gift will generally be a player's first introduction to the fact that this is even a possibility. It can be a pretty unpleasant surprise, given they have a powerful gun; a first-time player could easily lose someone to a flank they didn't realize was even possible. It's also a bit of a weird introduction to the concept, as all the other wall-smashers have a combination of need for such wall-smashing and obvious narrative justification for such, both coming back to the same idea: sheer size. The Andromedon is the only break from this pattern, and the game doesn't make any effort to justify why the Andromedon can casually ram through walls and not, say, the much larger Berserker. It's a distinctive ability, one of the cooler ones in the game in fact, but the Andromedon's access to Wall Smash is still a bit confusing.

It's less significant of a capability than one might expect, since Andromedons rarely try to leverage it, and the other units that have it are less able to leverage it, interesting more for the potential XCOM 3 might explore with such mechanics than for its implementation in XCOM 2.

Part of the issue is that XCOM 2 trends more toward open spaces in its maps, and more toward relatively 'self-contained' building design: in the prior game, a lot of maps that had buildings set them up as an interconnected series of sealed rooms with few or no windows, where it was easily possible to have an inactive pod just a few tiles away inside another part of the same building. In XCOM 2, buildings are usually fairly open spaces with windows on at least three of the four sides, with any other enclosed spaces separated by a street or something instead of being just the other side of the wall. As such, you rarely have the opportunity to have a fight occurring in a circumstance Andromedons ramming through walls becomes very notable in. Even when you're in urban environments, the map is often designed to minimize the danger: often, a building will have High Cover elements right next to some of its windows, where eg scrambling from inside the building to the wall adjacent to a window won't leave you vulnerable to a flank by a unit going to the corner of the wall, or through the wall.

One of the main map types that hearkens more back to the prior game's design -the Landed UFO mission type, where the UFO internals are reminiscent of Small Scout and Large Scouts from the prior game, meaning a bit of a cramped and labyrinthine mess- is itself rare. It usually at least crops up in the late game, where Andromedons are running about, but it's still easily possible to have a run simply never have Andromedons get a chance to strut their Kool-Aid man routine in an effectual manner.

Overall, I'm actually okay with this, as it's very much a byproduct of XCOM 2 having clearly learned from the problems of the prior game. Stuff like more windows and better Cover adjacent to windows is XCOM 2 carefully cutting away some of the worst line-of-sight jank from the prior game and also limiting a player's ability to unknowingly take a reasonable-looking Cover position only to be flanked from halfway down the street. I'd rather Andromedons had more opportunity to use this quality in a threatening way, but I'm completely sympathetic to the fact that the game didn't end up that way.

Maybe XCOM 3 will balance those concerns successfully. It'd be cool if it did.

Robot Battlesuit
See next enemy entry.

The Andromedon's most distinctive, memorable ability.

But that's for later in the post.

Fist Strike
A melee attack that does 7-10 damage, with +4 damage on a crit, wrecking the target's Cover as well as nearby destructible terrain, but operating at -15 Aim relative to the Andromedon's gun. This melee attack also has a chance of knocking the target back, up to 3 tiles away, assuming it hits.

Note that the area in which Fist Strike vaporizes destructible objects is huge, much larger than you would intuitively expect from the visuals. It clears out roughly two tiles in every direction, and even vaporizes the floor underneath the Andromedon, even though the visual of the punch seems like it should only clear out something like 3 individual tiles the punch is visually passing through, or at most all the tiles immediately around the Andromedon. As such, even if it misses it will often put the target in a lot of danger, especially since under most conditions Andromedons are guaranteed to be their pod's leader and therefore go before the rest of their pod, often ensuring there are follow-up attackers to take advantage.

Also note that this melee attack is not a move-and-melee attack, and so keeping a reasonable distance is adequate to avoid getting punched. Also, even though it wrecks destructible objects in an area around the Andromedon, it does not hit any units aside its actual target. You should generally avoid clumping around an Andromedon regardless, but it can for example be okay to have Fortress soldiers huddling close to each other in indestructible Cover.

Like Mutons, Andromedons are obsessive about using their melee attack if they can do so on a given turn, and will often abandon Cover in pursuit of a punch if you place a soldier nearby them. On the one hand, Andromedons are much better able to survive this reckless behavior than Mutons, but on the other hand it's actually a lot less threatening than Mutons going for the Bayonet: no possibility of Stun or Unconsciousness, no worrying about Execute, and on top of that Andromedons are much more prone to missing. It hurts if it does hit, you shouldn't treat it as a non-threat, but in a bad situation it's absolutely worth distracting an Andromedon by placing a soldier in punching distance: it does less damage than their gun, doesn't Shred Armor (Which is pretty consistently relevant given Warden Armor includes Armor), and will usually distract them from Acid Blob if you're concerned about that. (You should be concerned about that)

This also means Bladestorm/Retribution is quite relevant against Andromedons, since it's fairly easy to bait them into provoking a strike. This is especially useful to keep in mind if you've got the Katana, since it can't miss, ignores their considerable Armor, and does good enough damage it's not that hard to weaken them to the point of a Katana Bladestorm strike finishing them. Indeed, a Blademaster Bladestorm Ranger wielding a Katana can simply Slash into an Andromedon, as they will die on any difficulty short of Legendary... and even on Legendary, you only need one of your two +1 rolls to trigger to kill them. And if a Breakthrough is boosting the Katana (ie having Improved Swords or Improved Beam Weapons) then even a Legendary Andromedon always dies!

Without the Katana, Bladestorm/Retribution shenanigans are still useful to keep in mind, but not nearly so incredibly helpful against Andromedons. Templar Bladestorms don't have to worry about missing, but they do have to worry about Armor: it's Parry that's the primary reason it can be worth getting a Bladestorm Templar in an Andromedon's face, not Bladestorm itself.

Also keep in mind that Fist Strike will automatically instantly detonate any explosive terrain elements in its radius. It's a bad idea to use vehicles for Cover while in punching distance of an Andromedon unless you have Fortress... but on the flpside, if you do have Fortress, baiting them into blowing up a car on themselves can be pretty nice! A Parrying Templar may even be able to set this situation up completely safely, no worrying about the punch itself landing.

Acid Blob
Lobs a single Acid Blob, which does 4-6 damage to all units in a 3x3 area with 3 Shred and inflicts Acid Burn, as well as creating randomly-placed acid clouds that will inflict Acid Burn to units that pass through them. One charge.

A really situational mechanical point to note is that the Acid Blob attack works differently from your own Acid Grenade. The Acid Grenade does full damage to Acid-immune units, such as the Andromedon or a Codex, and merely fails to apply the Acid status to such units. The Acid Blob will instead do no damage whatsoever to Acid-immune targets. This does mean the Hazmat Suit is even more relevant against Andromedons than you might first expect, but the primary situation this is something you need to actually pay attention to is if you Mind Control an Andromedon, as the target preview will not make it obvious that Acid Blob is pointless against Acid-immune enemies: it will still highlight them in red. So if you ever find yourself considering lobbing an Acid Blob at a clump of Codices... yeah, don't do that.

Outside being heavy on Fortress soldiers and/or lucky with Hazmat Vests, though, Acid Blob is generally the single most dangerous thing an Andromedon can do. It can't miss, Shreds so much Armor you might as well treat it as infinite Shred (Especially if you don't have SPARKs), and will do a minimum of 5 damage per unarmored target between the initial impact damage and the Acid Burn getting a minimum of 1 turn of damage even if you rush to heal everyone. As Andromedons endeavor to target Acid Blob at grouped-up soldiers, this can easily turn into 15+ damage done in one action. That's a lot of damage, easily exceeding what their gun can do, and with only a bare handful of enemies that can readily expect to exceed it, all of which are more limited encounters. Even with Warden Armor, that just drags it down to 12 damage from the Acid Blob per se, which is still better than a non-crit from their gun...

It's generally best to kill or disable an Andromedon before it can act, between its powerful and accurate gun plus access to Acid Blob. Notably, while Andromedons overall prefer punching to other actions, if they don't start right next to someone they're still sometimes willing to use Acid Blob over going for a punch. Don't treat punch-range soldiers as a completely reliable distraction -honestly, I don't even treat directly adjacent soldiers as a fully reliable distraction. I've yet to see an Andromedon use Acid Blob when someone punchable was already adjacent, but I don't have a large enough sample size to be certain they'll never use Acid Blob if someone is adjacent. So if you use a Parrying Templar to try to distract an Andromedon... don't be terribly surprised if it breaks out the Acid Blob anyway.

The actual animation for Acid Blob is a bit confusing. The concept is that the Andromedon is venting some of the caustic fluid in its suit as a makeshift attack, which is sensible enough, but then the animation is that the Andromedon points its gun slightly upward, charges it for a couple seconds, and then the blob of acid shoots out at an appropriate angle. I'm not entirely sure there's an appropriately-placed tube or anything to draw such a connection, but even if there is it's still pretty weird. Using a weapon that's designed to fire some kind of laser-looking thing to instead gather caustic fluid into a blob and then launch it as a grenade is a pretty weird scenario; I'd really expect the fluid to be released some other way, from something more directly attached to the suit itself.

I'm unsure if this is a cobbled-together last-minute animation or something actual thought was put into and janky in the final product for other reasons. While the base game wasn't blatantly rushed like War of the Chosen was, there's a few bits and pieces concentrated toward the late game that suggest the game was, in fact, rushed a bit; it wouldn't surprise me if the animation strangeness here is an example of such.

But it could just as easily be that the devs just didn't think it was strange.


The Andromedon is the single most difficult to kill enemy in the entire game short of the Chosen and the endgame 'boss' enemies. Aside high-end Chosen and high-difficulty Avatars, no other enemy in the game has comparable Armor while still being able to make use of Cover, and the Andromedon has some innate Defense to boot, giving them an alarming 50 Defense when standing in High Cover. Being immune to all damage over time effects further contributes; in conjunction with not being susceptible to Bluescreen Rounds, your peak damage potential against an Andromedon is noticeably lower than against literally every other enemy in the game, since no damage-boosting Ammo works against them. Chosen and Alien Rulers will still take more shots to kill thanks to their raw HP advantage, but that's really it for enemies inarguably slower to die than an Andromedon.

The Andromedon is also part of the trifecta of endgame enemies that you normally only encounter one per pod, are ridiculously hard to kill, are able to smash through walls as they move, and hit very hard. It should always be one of your highest-priority targets, and indeed is probably the single best target in the game for lobbing terrain-wrecking explosives at, since it has incredible Armor while also taking Cover. Shredding their Armor while wrecking their Cover is very important if you want to reliably kill them in a timely manner: try to get Plasma Grenades online before they show up.

As Andromedons rip through the HP and Armor of your soldiers fairly effortlessly, it's quite important to kill them quickly. They're not quite as lethal as a Sectopod or a Gatekeeper, but it's a lot more important to leverage the pressure you put on them right away: if you take out an Andromedon's Cover but fail to kill it, it's going to run to a new position, and if you're out of explosives at that point you may be unable to do anything to force hits on it. In fact, if you end up with the last move of the turn being your explosives-hurler, you may well want to hold off on tossing it until next turn so you can properly leverage blowing their area up.

Archons were your early warning that the game was going to get serious soon: Andromedons are the game getting serious now.

Andromedons are actually one of the cooler Domination targets in the game, able to soak a tremendous amount of punishment from most enemies (Most enemies don't have Shred, or are reluctant to use their source of Shred, so their Armor tends to go farther than you might expect), dish out decent damage, keep up with your team wherever they might go, and punch holes in walls for you on demand by simply waltzing through them. It's entirely possible for an Andromedon to be Dominated in the first pod you encounter and survive all the way to the end of the mission with you, having contributed quite effectively and regularly throughout. Their Will is high enough you can't pull it off reliably, but it can still be worth fishing for once in a given fight.

Mind, Dominating an Andromedon has its risks, specifically how it interacts with what happens when an Andromedon dies...

Andromedon Shell
HP: 14/14/18/21
Armor: 0
Defense: 0
Dodge: 0
Aim: 75 (60 in practice)
Mobility: 12/12/15/15 (8/16 on Rookie and Regular, 10/20 otherwise)
Damage: 7-10 (+4)
Shred: 0
Crit Chance: 0/15%/0/0
Will: 50
Tech: 80

No, I didn't mess up the crit chance portion of the table. The files give no crit chance to the Andromedon Shell outside Regular difficulty, and 15% on Regular. I'm assuming that's not the intended pattern and it was just overlooked because enemy crit chances are invisible and you almost never get punched by a Shell anyway. By a similar token its lower difficulty HP is inconsistent with the live Andromedon's HP, even though its higher difficulty HP is identical. More evidence the dev team's focus was on playtesting Commander and Legendary...

Robot Battlesuit
Replaces an Andromedon when the Andromedon dies. Immune to Acid.

So yeah. On top of all their conventional durability, Andromedons don't even properly die when you kill them!

Mechanically, the Shell is 100% a brand-new unit, which has assorted kind of weird implications. For one thing, it means status effects don't persist; this mostly isn't very important, as the suite of immunities across both forms is such that not many statuses could be applied to a live Andromedon and then expect to persist to the Shell (You can Dominate an Andromedon, but not a Shell, same for Disorientation, etc), but Stun and, if you have Alien Hunters, Freeze, are both very notable exceptions. If you have a live Andromedon frozen or Stunned, you may wish to hold off on killing it just yet, so you don't let loose the Shell before your team is ready to kill it. Holo Targeting is also something that can affect both forms but is lost in transition, which I don't consider a notable exception because Shells are so easy to hit and Andromedons show up so late in a run your squad should generally be getting 100% hit chances against the Shell regardless, but it's still something to keep in mind when planning your turn, especially if you're either not fond of prioritizing Scopes/Perception PCSes or have had particularly bad luck in a run when it comes to them.

The other relatively significant mechanics point to keep in mind is that there is no 'carry-over' when it comes to damage. Killing an Andromedon with a 10-damage attack will result in a full-health Shell regardless of whether the live Andromedon had 10 hit points or 1 hit point when you shot it, and more pressingly multi-shot actions can be wasted if they're overkill: using Chain Shot on an Andromedon with 1 HP won't result in the second shot re-targeting to the Shell, it'll just waste Chain Shot, putting it on cooldown with no possibility of benefit. Banish backed by Annihilate is an exception, of course (Though the animation end of things copes poorly), but otherwise you shouldn't be careless with multi-shot actions. (Well, if you're playing the base game, you can be pretty free with Rapid Fire, given it has no cooldown there... but in War of the Chosen it has a 5-turn cooldown, so you need to pay attention and avoid wasting it)

A more narrow point to keep in mind is that killing the live Andromedon counts as a kill for eg Serial, Reaper-the-skill, Soul Harvest, etc, even though the Shell keeps going. This slightly bumps up the relevance of Serial and Reaper-the-skill once Andromedons start showing up, since even a single pod can produce a 4-kill-streak if you line things up right. It also means Andromedons slightly increase your average experience gain -to the best of my knowledge, they provide one kill of experience per form, with no Lost-type reduction in experience awarded per target.

Also a little weird is that a live Andromedon can drop loot when initially killed, rather than the loot being assigned to the Shell. Indeed, Shells are one of the only mid-mission-generation enemies that can't roll for droppable loot!

Anyway, this is why Dominating a live Andromedon can end badly: because when it dies, you'll end up with the Shell under enemy control! This is particularly problematic in the base game, as an Andromedon dying during the enemy turn will result in the Shell getting an immediate full turn. Much like Codex cloning, War of the Chosen fixes this so a Shell spawned during the enemy turn doesn't take action until the following enemy turn, thankfully. Indeed, in War of the Chosen Andromedons are arguably one of the best Domination targets, as the Andromedon corpse is not dropped until the Shell dies: as such, where normally Domination is costing you the corpse unless you do shenanigans to lose control before it dies, in the Andromedon's case it's actually ideal to have it die while Dominated in War of the Chosen.

Incidentally, Andromedons are another good scout for revealing Burrowed Chryssalids, since they take negligible damage from Chryssalids, don't get infected, and even have innate Defense to reduce the odds of being hit in the first place. The opportunity isn't prone to cropping up, but if you get that situation it's great to take advantage. 

Anyway, the icon above is actually used in-game for the Andromedon Shell's suite of immunities, but said suite of immunities is literally just...

Mechanical Chassis
This unit is a robot, rendering it immune to Poison, Fire, and Chryssalid Poison as well as most psionic or mental effects (Including that it will never Panic or be rendered Unconscious), but susceptible to anti-robot effects and impossible to heal with Medikits.

... that it's a robot, but also immune to Acid like the live Andromedon. I'm not sure why the devs didn't just give the Shell Mechanical Chassis and the Andromedon Immunities ability/icon with the latter specifying their Acid immunity. 

In any event, the Andromedon turning into a robot on death gives it a unique and rather strange relationship to Bluescreen Rounds (And other anti-robot measures, I guess), as they help quite a lot... against its vastly less threatening stage. If you brought Bluescreen Rounds for other reasons, sure, go ahead and try to arrange for them to be pointed at the Shell instead of its living self, but if you're seeing Andromedons listed by the Shadow Chamber, that shouldn't be a motive to equip Bluescreen Rounds. Take AP Rounds or even Tracer Rounds, instead, they'll actually help with the dangerous first stage.

The Shell is also mildly interesting as robots go for completely lacking Armor. Every other unit that is susceptible to hacking and so on has at least one point of Armor on all difficulties, usually multiple. It's especially surprising given that the live Andromedon is one of the most heavily Armored units in the game. You'd tend to expect the Shell to be similarly Armored, maybe inherit whatever Armor the live Andromedon had when it was killed, but nah, Shells always have 0 Armor. I'm curious if this was primarily a technical decision ("We want to have Armor inherit, but can't figure out how to get the engine to cooperate in a sane way") or if the dev team just thought it made sense for the Shell to be lacking Armor due to its catastrophic battle damage.

Whatever the case, Andromedon Shells are also another example of a robot enemy that can actually flee in response to casualties... but you could be forgiven for thinking Shells are a fearless exception, as they only rarely run, even if you have a habit of leaving them alive for a turn. I suspect this has to do with them being, mechanically, a wholly separate pod from anything else, rather than considering themselves to be a part of the pod the Andromedon was attached to when alive, as my experience is that enemies are prone to running in response to their pod taking severe casualties, and only rarely retreat in response to other pods taking severe casualties. Whatever the reason, don't just assume a Shell is going to stick it out and charge your forces: it usually will, but not always.

Admittedly a Shell isn't a big enough danger for it to be a big problem for them to go join another pod, typically, but it's still generally better to take it out instead of letting it get away.

Hardened
Does not use Cover, but is never considered to be in the open.

A semi-regular janky situation to keep in mind is that if a live Andromedon is killed while in High Cover, the resulting Shell will cease to be visible to anyone who isn't more or less flanking its position, since the Shell won't be using the peek-out mechanics. If you're not keeping this point in mind and kill an Andromedon with accuracy-bypassing effects (Or raw luck) you can find yourself unable to follow up and kill the Shell, potentially creating problems if one soldier is in easy punching reach. This is one reason it's generally best to chuck Plasma Grenades or similar at an Andromedon: to minimize the odds of its Shell being protected from your squad.

An additional weird wrinkle to it is that the Shell will actually start out in a kind of inactive state if none of your squad can see it. You can tell because it actually has both walk and run animations: in spite of by definition being a product of violence, you can end up with a Shell walking casually out as its first action, noticing your squad, and spending its second action point in a running animation. This can happen even if other enemies are around and can see your squad, in fact! Which makes it a little less dangerous to kill an Andromedon in High Cover, assuming none of your squad will have sight on the resulting Shell.

Regardless, this is important to keep in mind if you were keeping a Bluescreen Rounds soldier in reserve, waiting for other soldiers to kill the Andromedon before bringing the Bluescreen to bear on its Shell. Either blast their Cover as part of the process or make sure the Bluescreen Rounds soldier isn't relying on the Andromedon peeking out to get a line of fire.

Outside this particular weirdness, the Shell isn't any more prone than other Hardened enemies to hiding itself, and in fact is somewhat less prone to doing so since it retains...

Wall Smash
Can walk directly through destructible terrain freely, destroying it.

... this, of course.

Unlike an Andromedon whose pilot still lives, a Shell will always trample through everything in its way, never hopping over Cover or the like. This makes them hilariously prone to screwing up their allies' Cover, which is one reason why it's generally better to focus on the live Andromedon but shift its Shell to a lower priority: the Shell is a lot more likely to accidentally help your squad.

Shells are also just generally more prone to picking smashing-oriented paths. Live Andromedons can run though a wall to get a flanking position, but will often react to eg finding themselves on the other side of ADVENT walls by staying on their side, taking potshots through the laser-fenced windows. The Shell will inevitably charge right on in, punching a hole and potentially ripping into a soldier's Cover, exposing them to fire from other enemies.

It's good to get in the habit of identifying and prioritizing indestructible Cover when Shells are a concern.

Overall, though, not too different from the live Andromedon's access to the same.

Acid Trail
As the Andromedon Shell walks, each tile it passes through is filled with a cloud of acid that will inflict Acid Burn on units that pass through while the cloud still lingers. These acid clouds last exactly one turn, and do not move.

I assume this is meant to be dripping out of the cockpit area, since that smashes open and fluids are animated as leaking from it.

Most of the time, this is more flavor than anything else. It's rare you'll need to path a soldier through the Acid trail in the one turn it lasts, even if you're very fond of melee combatants and don't have Acid immunity on said melee combatants.

Do note you can't sneak through a line trailed by a Shell regardless of its exact pathing. A Shell walking diagonally will produce a trail you might intuitively expect to be able to slide through unaffected by going diagonally at a right angle to the trail (ie if the Shell went East-West, you would walk North-South), but you'll still end up considered passing through an Acid tile. I'm... not entirely sure how the game achieves this, honestly, as the game is, for all other purposes, happy to treat walking through a corner as not interacting with the other two tiles sharing the corner being walked through, including that with other cloud-producing effects you can sidle right past two clouds by cutting through the corner between them. This really seems to be some Acid Trail-specific special behavior.

Still, this is surprisingly rare in its relevancy, and somewhat comedically the Shell only leaves Acid behind it. Killing a Shell will result in it visually collapsing into its tile, spilling acid everywhere, but mechanically there won't be any Acid produced, not even in its own tile: this is part of why Acid Trail is often irrelevant, as killing the Shell will basically always provide a path through its trail even if it happened to cut off a chokepoint.

It's too bad it's so ignorable a mechanic. I really like the flavor of it, but it just... basically doesn't matter. It doesn't help that Acid has no immediate affects: walking through and then having a Medikit used on the individual (Such as remotely via a Specialist's Medical Protocol) will clear the Acid before it has the chance to do anything at all. You'd think walking through Acid would Shred Armor or something, but nope...

Fist Strike
The Andromedon Shell's only attack is a melee attack, wrecking the target's Cover as well as nearby destructible terrain, but with a -15 Aim penalty. This melee attack also has a chance of knocking the target back, up to 3 tiles away, assuming it hits.

This makes Shells even more predictable than live Andromedons: if a single soldier is in reach to move and then punch, the Shell will always try to do exactly that. Simple, because that's their only direct tool for contributing to a fight.

Since they also retain the just-immediately-punch-if-adjacent behavior, Shells are also even more easily trivialized by Parry Templar, Untouchable soldiers, or even using Suppression to slash their hit chance to 10%!


The Shell itself is massively less threatening than a live Andromedon, having lost use of the firearm (Its power source visibly stops glowing, and the gun breaks) and also lost access to the Acid Blob attack. As the melee attack is still not a move-and-melee attack, it's entirely possible for the Andromedon Shell to be unable to reach any of your people on its first turn in existence. And given its high HP is its primary protection, it's fairly easy to kill it at your leisure, regardless of your squad composition. While a live Andromedon is generally a high priority target, its Shell is often better to put off until you've dealt with ranged and move-and-melee threats in the area.

It's still got enough HP to soak a decent amount of punishment, and for a first-time player who doesn't know about the Shell gimmick it can be quite a nasty surprise to just barely pull off killing the Andromedon, only to have its Shell go on to punch someone's lights out, so don't treat it like a complete non-threat, but so long as it isn't in anyone's face it can be put off. And depending on who is in its face, it may still be acceptable to put it off...

It's also one of the more easily hacked robots in the game. Whether you want to shut it down to make it even easier to ignore, or take control of it for your own ends, you've got good odds of things working out. Just remember to account for its Acid trail, particularly in confined spaces: you may be accidentally laying walls of Acid that make it a bad idea to send people places you'd intended to send them. Consider moving it last, to minimize the problems posed by this, especially if it isn't in punching range of anything anyway. Also remember that the Shell isn't a particularly great combatant, especially since many late-game enemies have 10 Defense and so the Shell needs to win a coin-flip to hit anything. It can still be good for demolishing Cover and other environmental features, though, not to mention for distracting enemies. The AI likes to take higher-percentage shots, so the Shell tends to draw disproportionate fire due to its lacking Defense, and then stays up longer than a similarly-durable Cover-using unit since it's never considered to be in the open. So it's a pretty solid distraction, probably the best of the hackable enemies as a matter of fact, especially since leaving it alive to de-hack and turn on you isn't that threatening.


Unsurprisingly, the Shell does not have a separate Autopsy, and as noted earlier you don't see an Andromedon corpse drop until the Shell is destroyed. (Which, mind, doesn't matter much unless you're playing with mods that modify the corpse retrieval mechanics, since it's not possible to knock the Shell Unconscious or otherwise kill the first stage and end up not looting the body in a loot-possible mission. It's only Domination that makes it matter at all, by default)

Anyway, the Andromedon's Autopsy has the rather bizarre effect of unlocking Proximity Mines, as opposed to the Acid Grenade you would logically expect to get from Autopsying an enemy that has what amounts to an Acid Grenade as an attack. I'm genuinely surprised the devs didn't simply swap Proximity Mines with Acid Grenades, in terms of acquisition.

Regardless, Proximity Mines are actually surprisingly good, so this is a decent Autopsy to somewhat prioritize. The fact that Proximity Mines are fairly Supply-intensive is often not much of an issue, since Andromedons are generally showing up in the phase of the game where Supplies are largely ceasing to be a serious limiter.

This is good, because Andromedons are uncommon enough and show up late enough you'll generally not hit the Instant threshold, even in the base game, demanding you actually spend lab time on it if you want it. It's nice to have a worthwhile payoff for expending real lab time.

A bit of a hit to the relevancy of Proximity Mines in War of the Chosen is the Chosen loot researches, as they tend to be arriving in the late game and are much better researches to prioritize. It's entirely possible to end up unable to justify spending lab time on the Andromedon Autopsy because you're busy with Shadow Projects and Chosen Loot -and Alien Ruler Autopsies, if you have Alien Hunters and turn on Integrated DLC- right up until suddenly you're ready to launch the final missions. I mean, you'll usually be able to keep stalling if you want, but I, at least, am usually impatient to win the game by that point.

In any event, Andromedon corpses have no use outside their Autopsy, so you might as well sell all such corpses once you've performed the Autopsy anytime you swing by the Black Market.


On a different note, here's a minor oddity or error: an Andromedon will always have its glass casing completely shatter as part of transitioning to the Shell form, yet the Autopsy graphic goes with the usual corpse effect of the glass just having fractures and whatnot. Most of the Autopsy icons are slightly questionable, but the Andromedon's particularly stands out in this regard.

More interestingly, the Autopsy art has a much smaller glass casing than the 3D model. I suspect the Andromedon's design was roughly determined, the Autopsy icon made, and then the people doing the 3D end of things wanted to have the visible floppy alien body and so expanded how much of the graphic is glass so it was more visible once it was in Shell mode, with nobody thinking to update the Autopsy art appropriately. Among other points, the series of nodules running up the sides of the front look very out of place on the 3D graphic, where they're sitting atop glass, but fit smoothly into the Autopsy graphic where the glass covers much less.

-----------------------------------------

The Andromedon is interesting in that while XCOM 2 is not a Terror From the Deep remake the way a lot of people were historically expecting, it's very obviously pulling from Terror From the Deep anyway. Specifically, the Calcinite, which was also handled as a green mystery (Well, in the Andromedon's case the green is just its glass casing, not the being inside, but still) encased in a diving suit that had a powerful melee attack. They're even both creatures for whom Earth's atmosphere seems to be a hostile environment. The details are very different, but the inspiration is fairly obvious, and it's worth pointing out that the Calcinite was a land-only Terror Unit in spite of being in a diving suit, so it actually makes perfect sense for a Calcinite-inspired enemy to be in this game that lacks underwater combat.

The specifics of the suit's design are of course drawing heavy inspiration from Bioshock's Big Daddies, made blatant by the Autopsy's code-name being 'Levine', as in Ken Levine, that guy everyone associates with the Bioshock series. I can squint and sort-of-kind-of see the logic ("Calcinites are in diving suits, Big Daddies are drawing inspiration from diving suits, it's the same thing!"), but I don't think it's a particularly great decision. The Big Daddy's design is patterned after old diving suits, meant to look like something that might've been made decades ago, which doesn't mesh well with XCOM 2 trying for a modern approach to making alien gear look futuristic, and much of the Big Daddy's effectiveness is rooted in the combination of the first-person perspective and their role as a protector of Little Sisters, which XCOM 2 of course doesn't replicate either element. The Andromedon's design isn't bad, but I think using Big Daddies as the foundation for the design is one of the stranger, poorer possibilities the team could've gone with.

Ah well.

Regardless, it's interesting that the Andromedon is drawing inspiration from the Calcinite, particularly in conjunction with some secondary elements, such as how the Alien HQ ultimately turns out to be an underwater facility. You know, like T'leth. Among other points, it strongly suggests that XCOM 3 isn't going to be a Terror From the Deep remake, especially in conjunction with some of the game's elements suggesting XCOM 3 is going to be drawing inspiration from Apocalypse.

I do find it strange that the game didn't make the Andromedon Autopsy be your source for third-tier melee weapon upgrades. It would've completed the reference (Autopsying a Calcinite was a necessary step to unlocking non-stun melee weapons in Terror From the Deep), and it would've been less bizarrely out of place than the Archon's staff somehow inspiring third-tier melee weapons. Like yeah, the Andromedon's massive punch would be weird for turning into a flaming sword, but the Archon's melee attack is just bashing the enemy with a metal stick, so it's not like it makes any more sense.

Regardless, the Andromedon is a fairly unique enemy idea with a reasonably solid execution. I enjoy how it subverts a lot of expectations and makes reasonably logical sense for how its mechanics grow out of its aesthetic/concept, and it's very solidly designed for the purpose of being a late-game enemy that's genuinely challenging. In a lot of ways it could be viewed as the Muton Elite 2.0: you've got an enemy that uses Cover while having defenses normally provided to enemies that can't use Cover, with one of the highest damage scores in the game and a vicious ability to grenade your troops. Only where the Muton Elite was frustrating and boring, the Andromedon is an interesting enemy to face off against, forcing you to adjust your strategies instead of getting irritated by the ridiculous Defense-stacking of the late game that occurred in the previous game and that there was little in the way of actual tactics or strategy to fight against.

The Andromedon benefits a lot from the fact that it's essentially a new concept, for all that it's clearly inspired by the Calcinite. I've said this before, but part of my frustration with the previous game's alien designs mechanically, narratively, and aesthetically, was that many of them were 'this is supposed to be this competently executed thing from classic X-COM, only we got rid of everything that made it good and didn't replace it with something equally competent but very different'. By a similar token, some of the returning Aliens in XCOM 2 suffer from being a returning Alien: several of the Berserker's issues wouldn't stand out nearly so much if the previous game hadn't also had a Berserker that didn't make much sense to connect to this Berserker model. The Andromedon sidesteps a lot of those issues simply by virtue of being new.

That it's just plain one of the best-executed bits of base XCOM 2 on nearly every level is just icing on the metaphorical cake.

The primary negative thing I have to say is that I'm not a fan of the Gray-ish design to the being in the shell. Sectoids are already Grays, even if the Firaxis games seem to have completely forgotten/missed that. It really should've been something more immediately visually distinctive, or a deliberate connection been made: I would've found it a cute touch if the game implied the Andromedon was actually an Aquatoid, which would've also made the loose semblance to Sectoids a feature of the design, furthering the Calcinite-reference-connection. (Calcinites are one of the two Terror Units that Aquatoids use in Terror From the Deep) As-is, it just bugs me.

Still, that's a comparatively minor gripe, and I suspect that this is less 'it was designed to look like a Gray and nobody noticed the problem' and more 'the design needed to be rag-dollable, which meant it needed to be basically humanoid, and it's not surprising an alien humanoid that could be crammed into an Andromedon ended up looking Gray-ish'. That's an understandable sort of oversight.

The other thing that bugs me is the pilot has some kind of rebreather or gas mask or whatever. The game is pretty consistent about implying the inside of the suit represents the environment the pilot naturally lives in and more specifically the atmosphere they breathe. So... why do they have further breathing assistance?

I'm not sure if this is just a straight-up error or if perhaps the Andromedon concept underwent a shift that didn't end up reflected in the art. The latter wouldn't be at all surprising given how the glass casing was clearly clunkily expanded after the design was essentially finalized; maybe at some point the pilot was supposed to survive the initial suit damage, with the rebreather explaining how they can function outside the suit for a bit? I could easily imagine they'd intended for the pilot to act separately from the suit while still trapped inside the broken suit (Maybe it would've started using psionic abilities while the Shell wandered around punching people), or pull itself out of the suit once it broke so you now had two different enemies to deal with, and either way abandoned the concept due to finding it a significant technical hurdle. In that scenario, the rebreather would be an artifact of intended plans falling through, not an entirely inexplicable decision.

It'd still be weird either way, mind, as I'd expect the pilot to put the rebreather on in response to the suit breaking, and it seems unlikely they designed a no-mask model, designed an animation for it putting on the mask, and then switched solely to the masked model once they'd given up on the relevance of the mask.

I could just be unaware of a bizarre technical limitation, though.

Narratively, it's a bit disappointing that we never get any context on what's up with Andromedons. What's the in-universe reason Andromedons didn't show up in the initial invasion? What's their society like? Their relationship to the Ethereals? Is there an in-universe reason for their late deployment, or is that just a gameplay thing you're supposed to ignore? Given Ethereal biological engineering ability, why are they carted around in alien astronaut suits instead of modified to function fine on Earth?

Most of the aliens are pretty light on details, admittedly, but the Andromedon is the only alien where I can't think of anything resembling worldbuilding related to them. This is one area where their newness is actually a bit of an issue: a lot of returning aliens have more to them than XCOM 2 itself provides because the game broadly expects you to assume anything said in the prior game applies if it hasn't been clearly overruled, with some secondary supplementation from the callbacks to classic X-COM implying further information. The Andromedon being a callback to Calcinites is cool and all, but the nature of the differences known and the changed context means it doesn't make sense to assume Calcinite info carries over to Andromedon... not that Calcinites had much info to work with, mind.

As XCOM 2 doesn't have anything equivalent to the Uber Ethereal trash-talking all its minions at the end of the game, Andromedons are basically one big question mark.

And I'm unconvinced XCOM 3 will delve deeper into them...

----------------------------------------------------

Next time, we get to the first 'boss' enemy of the game: the Sectopod.

See you then.

Comments

  1. I've been getting back into XCOM 2, and having a blast. Your blog is exactly the kind of detailed guide/deep dive about the game I've been looking for. The talk about narrative and worldbuilding is also a great bonus as I too noticed a few things... not quite holding up after some scrutiny.

    ReplyDelete
    Replies
    1. Glad you're enjoying both the game and the blog posts.

      Delete

Post a Comment

Popular Posts