Why is the Scarab mission so Frustrating in Halo Wars?

Halo Wars (original) — Scarab mission tips

This is a walkthrough-style commentary on one of the rougher campaign missions in Halo Wars: a stationary super Scarab under construction that sweeps the map with a killing beam. I treat it as a micro-heavy fight where unclear briefing text meets pillar destruction, beam RNG, and an eventual DPS race against the Scarab’s core. Below is what I actually do and what I’ve noticed after playing it on Normal (I usually crank difficulty higher elsewhere, so your beam timing might feel a bit different).

The objective and why it feels unfair

You win by destroying the Scarab. It cannot move, but its beam patrols the map: wherever it detects your units, it fires and wipes them. Your base sits behind some protection at the start, yet the Scarab will gradually chew through nearby pillars until your base can die—mission over if that happens. The in-mission instructions are vague (typical for several Halo Wars missions), so a lot of this is learned by losing units and watching the beam.

Power nodes / pylons

Nodes sit along the ends of the visible power lines on the ground (easy to miss in fog of war). The game marks them optional; I basically treat them as required. Each one you destroy slows the Scarab’s turning and movement so much that controlling the fight gets dramatically easier. There are several on one side of the map; one sits on a kind of “island” and is the most annoying to reach—worth planning a route for when you have breathing room.

Base build and army composition

I lean hard into vehicles—especially Scorpions and Wolverines. Covenant units and phantoms show up across the map; Wolverines’ volley ability is strong in the cramped spaces around the Scarab. The mission gives plenty of resources; I’m comfortable dropping an extra Vehicle Depot to feed production. While besieging the Scarab, keep producing in the background so you don’t stall if you lose a clump of tanks.

Leaders, MAC, and plasma Rhinos

The mission hands you plasma Rhinos. I find them nearly useless on offense here: if I use them at all, I lock them down near the base so they can help blunt raids while the beam is elsewhere. The real army is Scorpions/Wolverines.

Forge stays useful while he’s in the Forge Hog. Once the Scarab destroys Forge’s ride, he’s mostly dead weight outside the hog (same point I make in my Arcadia City piece)—I try to keep him mounted as long as practical.

You get MAC Blast. I save it: it’s expensive and single-shot unless upgraded. Best use is a dense cluster of enemy units, not chip damage.

Heal and repair matters most when the base is about to collapse or when you’re stabilizing a tank push—don’t spray it early if you can hold it for the clutch moment.

Reading the beam and staying alive

Treat this as a micro mission. Stay behind natural cover (rocks and terrain the beam cannot delete). If you’re caught in the open and the beam is closing in, move perpendicular or opposite to its sweep—if you keep units moving, they often survive the pass. It’s acceptable to lose some units; preserving macro (production, nodes, positioning) matters more than saving every Marine.

When attacking the Scarab up close, space gets tight. Keep issuing move orders so tanks don’t idle in the kill zone. If you’re still eating beam wipes after adjusting, go clear more pylons before you commit everything to the core.

Destroying pylons vs. keeping cover

Every pillar the Scarab destroys shrinks usable cover and can snowball into you having nowhere to hide. That tension is part of why the mission feels cruel: you want pylons dead for the slow debuff, but the Scarab’s demolition run also deletes your safety net. I prioritize nodes when I can, and I accept some pillar loss if I’m buying time to mass tanks.

Attacking the Scarab and closing the mission

Primary damage should go to the Scarab itself—there are areas where pillar destruction continues no matter what you park there, so don’t waste the whole army babysying a doomed wall segment. When you’re ready to burn the boss, stagger tanks if needed: I sometimes send two tanks across first because not every tank can clear the beam timing window—chunking the force pauses or dances with the beam so the next wave can group up and keep firing.

With only three or four pylons destroyed, I’ve still been able to micro through and finish—so pylons help a ton but aren’t a strict all-or-nothing gate if your movement is clean.

Weird pillar / wall behavior

I genuinely can’t explain the full beam pattern—sometimes it feels like putting units too close to a wall makes the script glitch and melt pillars “for no reason.” Could be Definitive Edition weirdness; could be me misreading proximity. If the Scarab sticks beating one wall forever, I focus fire on what I can kill and ride out heals/MAC as needed. When in doubt, more pylons and cleaner micro beat guessing the AI.