Quick answer
Compare account level, the selected weapon challenge and cosmetic progress separately. Preserve before/after evidence before deleting files or assuming a permanent reset.
Which progress value actually changed?
| What changed | Capture this | Do not assume |
|---|---|---|
| Account level appears lower | Level before the match, end-of-match display and next menu | That a different attachment requirement must also have reset. |
| A weapon is unavailable | Exact weapon, current level and lock text | That a launch-week secondary unlock list guarantees the current requirement. |
| An attachment counter differs | Weapon, attachment, printed condition and before/after count | That every kill in every session counts. |
| A cosmetic remains locked | The exact skin requirement and selected weapon | That account level alone earns it. |
| A loadout seems missing | Selected slot, equipped weapon and build | That a saved setup and earned progression are the same record. |
What did the developer say about earlier level resets?
In an October 12 discussion, players reported falling levels and lost access to unlocks. A developer-tagged reply described progress not catching up with the server and promised a fix. Other replies disputed that explanation or continued reporting unexpected values. This is a historical exchange, not a diagnosis of every present-day case.
Patch 1.0.10 separately reports fixes to progression display at the end of a match and loadout presets not saving. A corrected display, a synchronized account and a restored preset are different outcomes. Record which one you observed rather than collapsing them into “everything reset.”
The thread supports preserving a before-and-after report. It does not support a guarantee that waiting, restarting or editing a file will restore a particular account. Do not use another player's old reassurance as proof your current data is intact.
What can you check without destroying useful evidence?
A planned comparison is not a reason to spend hours farming an unreliable counter. Stop once you have a clear repeat case. Bot or custom-room credit remains a separate rule to establish; a missing increment alone cannot prove a global progression reset.
Which actions should you avoid as a first response?
Avoid deleting unknown save or configuration folders, downloading replacement progression files or making multiple resets before recording the evidence. These actions can erase the setup and sequence needed to explain the fault. There is no verified local save path or universal reset procedure provided here.
Steam file verification checks installation integrity; it is not an account-progress restoration service. An explicit account restriction likewise belongs to its issuer's support route. If the fault is simply a wrong selected slot, use the current equipment screen to correct it before treating the result as missing ownership.
Keep a blank progress comparison card and use the evidence submission guidance for a correction or case report. The progression guide explains the three tracks so the report names the right one.
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 ↗