Wanderburg Gameplay and Progression

Wanderburg's current Early Access loop connects three kinds of progress: build a modular castle during a run, unlock more options between runs, and complete account-wide milestones across repeated attempts. This section starts with what Build 0.9.9 and the official Steam records can verify, then marks the details that still need direct gameplay testing.

Choose the system you need

Use the Achievements guide for all 26 public Steam achievements, including the September 10 threshold reductions and the victory-trigger fix in 0.9.9. Use Modules for the named pieces of the arsenal changed in official hotfixes. Use Vehicles, Biomes, and Unlocks when you want to separate confirmed progression milestones from unlock steps that the official pages do not yet document.

The Beginner Guide remains the starting point for the consume, grow, choose, and reassess loop. The Updates timeline is the source of truth when a new hotfix changes one of the systems summarized here.

Understand the three progression layers

During a run, the Steam description says that consumed villages and smaller fortresses feed the castle's growth. New siege modules and structures expand the moving fortress, while the current encounter and biome determine which option is useful now. This is the run layer: it is temporary, tactical, and especially sensitive to balance updates.

Between runs, the same official description names modules, vehicles, artifacts, and captains as unlockable options that widen future strategy. That establishes persistent variety, but it does not publish a complete roster or every unlock condition. This guide therefore records confirmed names and milestones without filling gaps from memory, demo footage, or an undated tier list.

Across the account, Steam achievements track distance travelled, units consumed, vehicles destroyed, bosses destroyed, biome access, vehicle unlocks, and victories. These counters are the clearest public progression record because their current thresholds are visible and Randwerk documented their first post-launch rebalance.

Read Build 0.9.9 as a moving snapshot

The launch sequence changed quickly. Hotfix 0.9.7 adjusted Front Barracks, Top Electric Mage, Spider movement, and late-overtime crowd control. Hotfix 0.9.8 changed Ram behavior, Nitro recovery, Desert Overtime, controller driving, and the Graphics API mode. Hotfix 0.9.9 then adjusted Front Barracks, Side Ballista, Force Mage, Wizard Crew, Tower, Spider, allied melee movement, Grassland Difficulty 2, and boss tombstone rewards.

That history supports specific facts, not a permanent tier list. A module buff tells you what changed; it does not prove that the module wins every run. A vehicle movement change tells you that older handling advice needs review; it does not publish the vehicle's full unlock route. Every page in this section uses that distinction.

What is deliberately not claimed yet

There is no “best build” page in this release because the official patch notes do not establish a repeatable strongest setup. Complete artifact and captain catalogs, exact vehicle unlock steps, and boss strategies also need current-build gameplay evidence. Those pages become useful only when they can answer what to do, how to reproduce it, and which build was tested.

For now, use the named module changes as test prompts, the achievement list as a measurable checklist, and the progression page as a map of confirmed systems. If your live game disagrees with a value here, first confirm the displayed build, then compare it with the official Steam announcements.

Turn one run into useful evidence

Begin by writing down the displayed build before the run. This matters because Steam can download a hotfix between sessions, and two runs that look identical may use different balance. Add the vehicle, biome, difficulty, and one module or upgrade that you intend to observe. A short, focused question—whether Force Mage cancels the projectile you expect, for example—is easier to verify than a general impression that a build feels strong.

During the run, separate automatic effects from active abilities. The 0.9.9 notes distinguish Side Ballista's automatic attack from its active ability and do the same kind of specific work for Front Barracks. If those effects are combined into one result, the observation cannot tell you which change mattered. Note the encounter and result without assuming that every later biome behaves the same way.

After the run, check whether a persistent milestone appeared. An achievement can confirm that Steam recognized a biome, vehicle, victory, or cumulative threshold; a changed loadout can confirm that a new option is available. Neither one automatically explains the hidden condition that produced it. Report what happened in sequence and leave the causal claim open until it repeats.

This small record has two uses. It helps you make the next run more deliberate, and it creates the kind of evidence that can support future build or unlock guides. A screenshot of a result is useful; a screenshot plus build, conditions, and a repeatable sequence is much stronger.

Decide whether an old guide still applies

First identify its date and label: demo, playtest, launch, or a numbered Early Access build. General descriptions of steering a growing castle and adding modules can remain useful. Damage numbers, upgrade scaling, handling, Nitro behavior, achievement thresholds, and crash workarounds are patch-sensitive.

Next compare the topic with the update timeline. Front Barracks changed in both 0.9.7 and 0.9.9. Spider movement was increased and then its speed upgrades were reduced. Graphics API handling changed on consecutive hotfixes. These examples show why “newer than the demo” is not precise enough; advice should match the latest relevant change.

Finally, prefer the narrowest supported conclusion. If an official note says an active ability was buffed, record the buff. Do not silently turn it into “best module.” If an achievement confirms that a biome unlocked, record the milestone. Do not infer the entire unlock route. This discipline lets the Wiki expand without losing the source-aware quality of its first release.

Sources and version boundary

The system descriptions come from the official Steam store page. Achievement names and conditions come from Steam Global Achievements. Version changes come from the official announcement feed. All three were checked on September 12, 2026 against Build 0.9.9.