Gears of War: E-Day is a prequel centered on Emergence Day, the moment the Locust Horde attacks the surface of Sera. The main campaign follows Bravo Squad in the city of Kalona across roughly three days. Its job in the series is to show the disaster as an immediate human event, not to summarize every conflict that follows.
The exact mission order is not public before launch. This page therefore provides a chronology framework rather than invented chapter names, travel times, or cutscene outcomes.
Before E-Day: a world coming out of war
The story begins in a society already marked by conflict. Official coverage places Marcus Fenix and Dom Santiago among COG soldiers before the Locust become the enemy that defines their lives. The opening context matters because equipment, command structures, and public expectations belong to a world that believes it understands warfare.
Do not assume “before Gears 1” means peaceful. The campaign’s visual language and military presence reflect earlier fighting and damaged communities. At the same time, later-series knowledge should not be used to fill every blank. A character’s future rank or weapon preference does not prove what they have on the morning of the attack.
For notes or a walkthrough after release, label this first period pre-emergence and end it only when the game explicitly marks the Locust assault. That avoids mixing tutorial action with the first confirmed E-Day sequence.
Day one: the Locust threat becomes real
Emergence Day is the point at which Locust forces erupt from underground and attack surface cities. In Kalona, Marcus, Dom, and their squad confront an opponent the COG did not prepare for. Official story descriptions emphasize terror and uncertainty: even a standard Drone is meant to feel physically dangerous rather than like routine battlefield fodder.
The first day should be recorded through objective text and time cues from the game. Trailer cuts are edited for presentation, so their shot order is not a mission chronology. A scene in daylight followed by one at night can suggest passage of time, but it cannot establish two adjacent chapters.
The Prototype Lancer belongs to this origin period. Official material explains that the familiar chainsaw concept is kit-bashed on the battlefield. That makes its creation a campaign event, but it does not justify publishing an exact mission or crafting sequence until players can verify it in the shipping build.
The three-day Kalona campaign frame
Xbox’s official campaign feature describes the main action as spanning three days in and around Kalona. This tight frame gives the story urgency: characters are responding to a city-scale collapse while information and supplies are limited.
Use the three-day statement as the outer frame, not as permission to assign every revealed scene to Day One, Two, or Three. A launch-quality timeline needs one of the following for each placement:
- An on-screen date or time card.
- Dialogue that establishes elapsed time.
- A mission log with chronological ordering.
- An official chapter description that names the day.
If none exists, list the event under “order not yet confirmed.” That is more useful than a confident but false timeline that later pages copy.
Relationship to the original Gears of War
E-Day takes place years before the original Gears of War campaign. It explains formative experiences for Marcus and Dom and the beginning of humanity’s war with the Locust. It is not AppID-linked DLC for an older game: Steam AppID 3010850 is the standalone E-Day base product.
Mechanics also should not be used as chronological proof. A weapon or enemy returning from a later-released game can exist earlier in the fiction, but a modern control feature is a design decision, not necessarily a lore event. Keep story chronology separate from release chronology and gameplay-system evolution.
The separate Multiplayer Beta, AppID 4059240, is a test product. Its maps and rewards can inform multiplayer pages, but playing a Beta match does not add a campaign event to the canon timeline.
What the timeline does not confirm
Pre-release sources do not provide the complete chapter count, mission names, every location, a minute-by-minute route, or all character outcomes. They also do not prove that the campaign never leaves Kalona; “spanning three days in Kalona” is the published premise, while exact boundaries must come from the game.
Avoid using achievements as a substitute before release. Store achievements can change, contain spoilers, or remain hidden. The audit intentionally launch-gates a full walkthrough, collectibles guide, and achievements guide until AppID 3010850 has a verifiable public build.
Build a reliable personal story log
During a first playthrough, record the displayed chapter name, current squad, objective, location card, and any explicit time marker at each transition. Keep optional conversations separate from mandatory events. If playing co-op, note whose perspective triggers a scene rather than assuming all four players see identical positioning.
For spoiler control, write summaries after finishing a chapter and avoid placing outcomes in headings. Link a character entry to the first non-spoiler introduction, not to a late-game revelation. When a patch changes a mission, add the build date; do not silently rewrite the historical sequence.
Timeline FAQ
How long does the story cover?
The official campaign presentation says the central Kalona story spans three days. That is a narrative timeframe, not a promised playtime estimate.
Is E-Day a remake of Gears of War?
No. It is a standalone prequel about Emergence Day and the earlier lives of Marcus and Dom.
Does the Multiplayer Beta reveal Campaign chronology?
No. It is a separate multiplayer test application and should not be used to establish campaign events.