Skip to content
Partially verified

Wanderburg All Biomes Won Achievement Not Unlocking: Criteria and Fix History

What All Biomes Won actually requires, how Overtime affected its historical trigger, what hotfix 0.9.9 changed, and how to investigate a save that remains locked.

Wanderburg All Biomes Won Achievement Not Unlocking: Criteria and Fix History

Reviewed
Scope
Dated evidence; no installed-build testing

If All Biomes Won is not unlocking, first confirm that you have recorded a real win in every required biome rather than merely unlocking, entering, or reaching each one. A historical achievement bug also matters: the developer said the win achievements were only checked when a player chose not to continue into Overtime after winning. Hotfix 0.9.9 later listed both First Win and All Biomes Won as fixed.

That patch note confirms a historical code fix, but it does not establish that every previously affected save will display the achievement immediately or retroactively. If your achievement is still locked, the most defensible retry is to update the game, identify any biome for which you cannot confirm a normal win, win there again, and decline Overtime. Do not erase your save or disable Steam Cloud on the assumption that either action is an official fix.

Wanderburg overworld with Golden Dunes selected and nearby land entrances

Use the map to identify the land before recording a win; selecting a node is not achievement completion.

Separate biome access from biome wins

The achievement concerns wins across the biome set. Several nearby progression states can look complete without proving that requirement:

  • Unlocking a biome is not the same as winning in it.
  • Entering or playing a biome is not the same as reaching its win state.
  • Defeating part of a run does not establish that its final win check was recorded.
  • Continuing into Overtime after a win was specifically connected to the historical trigger problem.
  • Unlocking the First Win achievement does not prove that every biome has a stored win.

Some achievement lists use the name All Lands won!, while the official 0.9.9 notes call the affected achievement All Biomes Won. Treat those labels as references to the all-areas win milestone, but use the exact name displayed in your own Steam achievement panel when documenting a problem.

Because the achievement notices do not document a dependable per-biome achievement tracker, build a small manual checklist. For every biome visible on your account, record whether it is merely accessible, whether you remember reaching a win there, and whether that win ended without entering Overtime. If additional Lands remain locked, wins in only the available Lands do not establish all-biomes completion. Finish the remaining Land progression and use the full required set shown by your installed game; the achievement notices do not publish a reliable complete biome count here. Mark uncertain entries as uncertain instead of treating map access as proof.

The official achievement-rebalancing announcement said affected progress was saved. That is useful reassurance about the historical bug, but it should not be stretched into a promise about exactly when Steam will show the unlock. The announcement did not document a manual synchronization command, an exact retroactive trigger sequence, or a guaranteed popup on the first launch after the fix.

The official fix history

The September 10 achievement notice

On September 10, 2026, the developer publicly described an outstanding issue with You Won! and All Biomes Won!. According to that notice, these achievements were checked only when a player did not go into Overtime after winning. The team said a fix was planned for the next update but still required testing. It also stated that progress was being saved and that the achievement would be triggered in the future.

This gives the historical failure path a clear boundary: the problematic sequence was winning and then entering Overtime. It does not show that Overtime invalidated the actual biome win or erased all progression. The problem was the achievement check associated with that sequence.

Hotfix 0.9.9

The official 0.9.9 hotfix, posted on September 11, included the line that the First Win and All Biomes Won achievements were fixed. This is the clearest official statement about the bug. It supersedes older advice that described the issue as still waiting for a patch.

However, “fixed” in a patch list describes the game change shipped in that build. It does not prove the state of an individual Steam account, confirm that an older save has already retriggered, or explain whether a previously affected player must complete another win. For that reason, use 0.9.9 as the historical fix point, not as proof that every later report must be user error.

Hotfix 0.9.14 is about a different achievement

Hotfix 0.9.14 lists a fix for Welcome to the Desert. That achievement concerns unlocking the Desert biome and is not the same as All Biomes Won. Do not use the later Desert fix as evidence that the all-biomes win trigger was changed again.

A dated player discussion about the Desert achievement also describes starting fresh on another device with Steam Cloud disabled. That is an individual observation about Welcome to the Desert, not an official All Biomes Won recovery procedure. Applying it here could create save-management risk without addressing the relevant trigger.

Use a clean non-Overtime retry

Follow this sequence before treating the locked achievement as a continuing bug:

  1. Confirm the exact locked achievement. Open the Steam achievement list and distinguish All Biomes Won or All Lands won from First Win and Welcome to the Desert. A locked Desert unlock is a separate issue with a separate patch history.

  2. Confirm that the installation includes the historical fix. Hotfix 0.9.9 is the documented All Biomes Won fix. The Steam listing checked on October 9 shows 0.9.14 as the latest regular update displayed on the store page, but a store listing does not verify the build installed on your machine. Let Steam finish any pending Wanderburg update before retrying.

  3. Create a biome-by-biome record. List each biome available on your save. For every entry, separate “unlocked,” “played,” and “won.” If you cannot confidently mark the last state, that biome is the best retry candidate.

  4. Prioritize wins completed through Overtime. If you remember choosing Overtime after winning in a biome during the affected period, retry that biome before repeating clearly recorded normal wins. This directly addresses the failure path named by the developer.

  5. Reach the normal win state. The relevant condition is a win, not simply reaching the biome, spending time there, or making progress toward it. Avoid substituting an unlock objective for the required completed run.

  6. Decline Overtime for the diagnostic attempt. Once the game recognizes the win, take the branch that ends the successful run instead of continuing. This recreates the path that the developer said was checked even before the fix and removes the historical Overtime interaction from the test.

  7. Check both game progression and Steam. After the completed run returns control normally, inspect the Steam achievement state. Do not rely only on whether a notification appeared; the achievement panel itself is the more useful state to record.

  8. Repeat only where the record is uncertain. If one normal retry does not unlock it, work through biomes that lack a confirmed post-fix, non-Overtime win. Replaying a biome that already has strong evidence of a valid win is less useful than resolving a gap in the checklist.

This procedure is intentionally narrow. It does not require a particular captain, build, module order, difficulty strategy, or farming route. Those choices may determine whether you can finish a run, but the achievement notices does not identify them as part of the All Biomes Won trigger.

Interpret the result without overclaiming

A few outcomes point to different next steps:

Observed stateWhat it establishesAppropriate response
A biome is accessible but has no confirmed winProgression access exists, but the achievement condition remains unprovenComplete a normal win there and decline Overtime
A win was followed by Overtime during the affected periodThe run matches the officially described historical failure pathRetry that biome outside Overtime on an updated build
Every required Land is unlocked and has a confirmed post-fix normal winThe evidence appears to satisfy the documented criterion; wins in only currently available Lands are insufficientPreserve the save and prepare a focused bug report
Welcome to the Desert is lockedA different unlock achievement may be affectedDo not treat it as proof that All Biomes Won uses the same trigger
First Win is unlocked but All Biomes Won is lockedAt least one win registered, not necessarily the full biome setAudit the per-biome checklist rather than repeating the first area automatically

Do not infer a current global bug from one locked account. Conversely, do not assume that the 0.9.9 note proves your particular save has synchronized correctly. The useful question is whether a fully updated installation still leaves the achievement locked after each biome has a defensible normal-win record.

Avoid destructive or irrelevant fixes

Keep the existing save and Steam Cloud state intact while diagnosing. The official notices do not instruct players to delete local progress, create a new account, disable cloud synchronization, or reinstall on another computer for All Biomes Won. Those actions can obscure the original state and make a report harder to evaluate.

Also avoid spending time on unrelated achievement counters. Distance travelled, vehicles destroyed, units consumed, and bosses destroyed are separate cumulative achievement chains. Their rebalanced thresholds do not define the All Biomes Won condition. Raising those totals will not prove that a missing biome win was recorded.

Do not remain in Overtime merely to generate another check. The historical evidence says the opposite: entering Overtime was the path associated with missed checks before 0.9.9. For a controlled retry, end the run after the normal win.

Build a useful bug report

If the achievement remains locked after confirmed normal wins across every required Land, including previously locked Lands, on an updated installation, record the mismatch without modifying the save. A useful report should contain:

  • The exact Steam achievement name shown as locked.
  • The installed game version, if the game exposes it.
  • A list of the biomes available on the save.
  • Which biomes were won again after updating.
  • Confirmation that Overtime was declined on those diagnostic wins.
  • Whether First Win and the individual biome-unlock achievements are locked or unlocked.
  • The approximate date of the earliest affected wins, especially if they occurred before hotfix 0.9.9.
  • A screenshot of the locked Steam achievement and any available completion state inside the game.

Keep observed facts separate from conclusions. For example, report “All listed biomes were won again without entering Overtime, but Steam still shows the achievement as locked,” rather than asserting that progress was erased. The former gives the developer a reproducible state; the latter claims a cause that the achievement notices do not establish.

Your practical endpoint is therefore clear: verify the correct achievement, update past 0.9.9, audit wins rather than unlocks, retry uncertain or historically Overtime-affected biomes without continuing, and preserve evidence if the locked state remains. That tests the documented criterion and historical failure path without risking the save or pretending that an old patch note guarantees the state of every current account.