Halo Campaign Evolved Launch & Co-op Checklist

Before the party loads, write down four things: each platform, the first host, the route you are starting, and the stopping point you want to verify. The released game supports the rebuilt original campaign and three Operation: Meteorite missions, so the group should agree on the route before invitations turn into a long session. A shared plan prevents a campaign choice from being mistaken for a missing save or a party error.

Use the unmodified first mission as the baseline. Let the group learn the rebuilt space, the changed weapon and vehicle options, and the new sightlines without stacking Skulls. If the mission feels different from remembered Halo CE, that is useful information: record the landmark and the changed decision before adding a challenge modifier.

The checklist is intentionally ordered from access to evidence. A playable build and party prove that the session can start; one short mission proves the route; a post-mission profile check proves that shared progression reached the people who played. Only after those three steps should the group spend time on a longer campaign or a challenge run.

• AgreePlatform, host, campaign path, and stopping point.
• BaselineRun one clean mission before Skulls or speed goals.
• VerifyCheck mission credit on every profile before continuing.

If the party cannot start, stay in the before-session layer: confirm the playable update, account sign-in, platform list, privacy settings, and invitations. Do not change difficulty or campaign path yet. The online campaign supports up to four players with crossplay, while console split-screen is a two-player local route; choosing the correct format is part of the setup rather than a combat fix.

If the party starts but progression is uncertain, stop after one mission. Have the first host remain stable, let one player reconnect early if that is the test, and inspect mission select or completion state on every profile. A short controlled check is more useful than playing several missions and discovering later that one account did not receive the expected result.

If a familiar Halo CE route breaks, treat the room as rebuilt evidence. Refined spaces, added weapons, hijacking, and the drivable Wraith change the available answers. Return to the last shared landmark, test one new option, and keep Skulls off until the clean route is understandable. This preserves a recoverable comparison instead of mixing route change with modifier pressure.

• Party errorStay in account, platform, and invite checks.
• Save errorStop after one mission and inspect every profile.
• Route errorRead the rebuilt space before changing the challenge state.

The campaign has 39 physical Skull pickups and three automatic menu unlocks—Adaptation, Reload, and Armistice—awarded with Campaign Remix after any two physical pickups. That split matters for planning: a player looking for a location should choose a mission, while a player checking a modifier should first confirm the unlock state rather than searching for a nonexistent map pickup.

Run one Skull after the clean mission route is repeatable. Keep the same host, difficulty, mission, and weapon plan, then record the first changed enemy, weapon, or environment behavior. Stacking several modifiers at once removes the baseline you need to decide whether the new route is fun, fair, or simply unclear.

When the session ends, preserve the shortest useful note: mission, party format, modifier, checkpoint, and the result each profile shows. That record makes the next attempt cheaper and gives a future location or mission guide a concrete handoff instead of a vague “co-op did not save” report.

• UnlockSeparate physical pickups from automatic menu Skulls.
• Change oneUse one modifier after the clean route works.
• RecordKeep mission, party, modifier, checkpoint, and profile result.