Quick answer
Before reusing an old route or loadout, check your version, server choice, objective rules and current controls. The reviewed changes below cover 1.0.1.4 through 1.0.2.0.
Which changes could invalidate an old habit?
| If you last played before… | Recheck this | Practical consequence |
|---|---|---|
| 1.0.1.4 · October 14 | Password rooms and audio-output selection | An old claim that private rooms are unavailable is dated. |
| 1.0.1.7 · October 16 | Party invitations and joining together | Use a party for group entry rather than assuming manual room entry is the only option. |
| 1.0.1.8 · October 17 | Draco/ARP; Crashout name; Chain Snatch scoring | Revisit a weapon list, reward name and friendly-chain scoring assumption. |
| 1.0.2.0 · October 23 | Official EAC servers and preferred Quick Play mode | Note the session type when comparing connection results. |
| 1.0.2.0 · October 23 | The Strip buildings/sightlines, Mall door removal, shotgun nerf | Repeat route and equipment comparisons before carrying an old conclusion forward. |
| 1.0.2.0 · October 23 | Claymores disappear when their owner dies | Do not assume your placed device remains after that death. |
What should you check in the first five minutes back?
Keep your earlier saved session as a dated comparison. You can create a new record for the return session instead of treating an old configuration as a current recommendation.
Why do old clips and new matches disagree?
Version differences can change what a clip demonstrates. A friendly-chain recovery that raised the team score before 1.0.1.8 is not the announced rule after that update. A bomber name in an older reward guide can refer to what a later menu calls Crashout. Neither difference automatically makes the old recording dishonest.
Compare the date, mode, map and build before copying a tactic. The 1.0.2.0 notes explicitly describe map changes, so a former line of sight or exit can be a poor reference even if the creator's aim settings are unchanged. A text changelog identifies what to investigate; it does not draw the new route for you.
For a current observation that disagrees with a patch, preserve the sequence and relevant settings. A custom room and a public server may differ in the conditions you are comparing. Describe the difference rather than assigning a cause from one match.
Which announced features should stay off your checklist?
The 1.0.2.0 developer note mentions character customization, prestige, more skins and maps as future content. That wording is a plan, not proof that each feature is available in the installed build. Check subsequent announcements before treating a missing planned menu as a malfunction.
This page is a dated return brief. Open reviewed announcements for later material and the term reference for an unfamiliar warning. If the game fails before you can play, follow the symptom-specific guide rather than repeating every return check.
A good first return session ends with a usable baseline: the version you joined, a working setup and one changed habit to revisit. You do not need to relearn every map or copy every new weapon recommendation in one evening.
Evidence, sources & revision notes
Version & evidence scope: Prepared October 25, 2026. Official changes through 1.0.2.0 and dated community observations are distinguished from suggested exercises; no independent client tests. How we verify ↗
Did this help you take the next step?
Send details to the editor ↗