Horde Siege in Gears of War: E-Day offers three announced mission shapes: Blitz, Siege, and a ten-wave Horde playlist. They use the same larger ecosystem—three squads on a map, class progression, Energy, R.I.G. objectives, optional activities, and extraction—but ask for different time and risk commitments.
Choose the shape before choosing a build. A strong plan for a short objective run can run out of resources in ten waves, while a slow endurance setup can waste the opening of Blitz.
Blitz: learn the loop in a short session
Blitz is the shortest published mission format, built around one or two objectives and an approximate twenty-minute target. It is the natural place to learn objective verbs, Energy spending, COG-tag recovery, and extraction without committing to a full hour.
Short does not mean consequence-free. Optional activities can still pull the squad away from the main route, and mission-found Weapon Parts still depend on successful extraction. Decide at deployment whether the run is for learning, class XP, or a specific optional signal. Trying to do all three can erase the time advantage.
Use one purchase checkpoint after the opening read and one regroup before extraction. If the squad spends longer debating a cache than completing the objective, simplify the loadout on the next run.
Siege: a multi-objective route
The middle format, Siege, uses roughly four to six objectives and an approximate forty-minute target. It tests travel and recovery as well as individual encounters. A good squad must carry resources from one problem into the next rather than treating each R.I.G. marker as a fresh start.
At every transition, check squad lives, ammunition, equipment, Energy, and the next two routes. Assign one player to read the R.I.G. while the others secure the area. When optional objectives appear, estimate the return path as well as the distance outward.
Siege is also where class coverage becomes easier to evaluate. If revives repeatedly fail, Medic support or better tag recovery may matter. If protected enemies stop every advance, a Breacher lane or coordinated precision fire may solve the actual bottleneck. Change the response, not just the damage number.
Ten-wave Horde: plan for endurance
The long Horde format is announced as ten waves with an approximate sixty-minute target. It should be approached as a resource arc. Early waves establish positions and spending discipline; later pressure tests whether the squad preserved answers for heavier threats and extraction.
Agree on a fallback before wave one. Identify which turret positions help the defense, where a Heavy Weapon carrier can move without blocking the team, and which cache remains reachable if the main lane collapses. Do not detach every turret weapon simply because carrying it is possible.
Between waves, reload, recover the formation, and name the next purchase. Pooled Energy makes silent personal spending especially costly over a long mission. One weak purchase does not lose the run, but repeated uncoordinated spending can leave no answer for a late Invasion Event.
Objectives are selected from a shared vocabulary
The official mission system includes Secure, Calibrate, Repair, Defend, and Horde objective patterns. A playlist length describes how many problems the squad expects, not the exact order. Procedural elements, optional activity, enemy pressure, and modifiers make a static “mission one route” unreliable.
Translate each verb immediately. Secure means control the occupied space; Calibrate requires coordinated movement between points; Repair needs component recovery and protection; Defend rewards lane control; Horde asks for sustained wave planning. The dedicated objectives guide covers those verbs in depth.
If the R.I.G. instruction conflicts with a remembered Beta route, follow the current objective. The base game announces three Horde maps at launch, while the public Beta centers on Golden Quarter.
Difficulty changes the commitment
Mission length and difficulty are separate selections. Ensign, Gear, and the class-level recommendations on higher settings help the group match readiness to risk. A short high-difficulty Blitz can demand more coordination than a lower-difficulty long run.
Use the first attempt to establish a baseline. Move up only after the squad can complete objectives, recover tags, and extract without relying on accidental rescue from another squad. Class level alone does not replace map reading or communication.
Multiple squads share the battlefield
Horde Siege supports up to twelve players arranged as three squads of four. Other squads may create activity, revive a fallen Gear by collecting tags, or compete indirectly for attention and space. Your squad still owns its objective decisions and lives.
Do not assume another squad will clear the extraction zone or recover a bad push. Use map pings and visible activity as information, not a guarantee. If a global Invasion Event changes systems across the map, recheck the route instead of continuing an obsolete plan.
Match a mission to the group’s goal
Choose Blitz for onboarding, a limited session, or a focused mechanics test. Choose Siege when the group wants a fuller route with several objective transitions. Choose ten-wave Horde for an endurance plan with deliberate progression and resource management.
The published durations are design targets, not timers or guaranteed completion lengths. Matchmaking, wipes, optional activities, difficulty, and player familiarity can extend a run. Leave enough real-world time to finish extraction; quitting after collecting Weapon Parts defeats the persistent reward loop.
Mission FAQ
Does Blitz remove extraction?
No official source says it does. Extraction is part of the Horde Siege mission loop, and collected Weapon Parts require a successful exit.
Is ten-wave Horde the only “real” Horde mode?
No. Blitz and Siege are official formats designed for different commitments within Horde Siege.
Are the approximate durations strict limits?
No. They are published target lengths and can vary with difficulty, objectives, and the squad.