Check the revised thresholds
Randwerk revised these statistics-based achievements on September 10. Older lists can show substantially higher goals. The distance names switched to meters while the descriptions retained kilometers; check the unit as well as the number.
| Tier | Distance traveled | Bosses killed | Units consumed |
|---|---|---|---|
| 1 | 10 km / 10,000 m | 10 | 1,000 |
| 2 | 100 km / 100,000 m | 25 | 5,000 |
| 3 | 250 km / 250,000 m | 50 | 7,500 |
| 4 | 500 km / 500,000 m | 75 | 10,000 |
| 5 | 1,000 km / 1,000,000 m | 100 | 25,000 |
Vehicle-tier achievements were left unchanged in that announcement. Do not apply the table to a quest that asks for a particular enemy, biome or victory condition: its counter measures something else.
Match the symptom to a dated fix
Victory achievements: the September 10 announcement described a check that could be missed when continuing into Overtime after a win. Randwerk said progress was saved and planned a fix. The following 0.9.9 announcement reported fixes for First Win and All Biomes Won. Read those posts together; the earlier workaround is historical context rather than proof of a current Overtime requirement.
Welcome to the Desert: 0.9.14 specifically reported a fix for this achievement. A report from an older version is not enough to diagnose your current result.
The notes do not document every platform-delivery delay or every possible save state. They also do not justify deleting a save to force a fresh award.
A useful checking sequence
- Identify the exact achievement and its requirement in your current language. Keep a screenshot of its description and progress.
- Compare the installed game version with the relevant fix. Let Steam finish a pending game update before testing again.
- Separate the in-game counter from the Steam achievement badge. Record which one changed and which one did not.
- Repeat the smallest relevant action only when it is reasonable to do so. Record the counter before and after rather than replaying hours with no baseline.
- If the counter meets the stated requirement but the achievement remains locked, keep the version, time and screenshots for a reproducible report through the game’s existing support/community route.
Avoid resetting your progress or editing a save as an initial troubleshooting step. Nothing in the cited fixes requires it. We have not verified a universal manual trigger for previously affected saves.
Is this actually an enemy quest?
A counter that stays at 3/5 can be a classification issue rather than a statistics achievement. If the objective mentions Harvesters, use the bounded community identification note and check the counter after one candidate enemy. That page distinguishes the player report from confirmed patch information.
If you cannot bring up the statistics you used before an update, the Controls and Nitro guide covers the documented shortcut change.
Sources
- Achievement rebalancing · Randwerk · 2026-09-10
- Hotfix 0.9.9 · Randwerk · 2026-09-11
- Hotfix 0.9.14 · Randwerk · 2026-09-21
Our steps and comparisons are editorial guidance. Source verification does not mean these steps have been tested on every game setup.