Wanderburg Modules

Build 0.9.9 confirms a growing set of named Wanderburg modules, but the official sources currently support a change guide rather than a complete module database. Use this page to see which modules changed after launch and what each change lets you test in a current run; do not read it as a best-module ranking.

Current official module record

Module or system	Latest confirmed change through 0.9.9	Practical reading
Front Barracks	0.9.7 raised active base damage from 200 to 250; 0.9.9 fixed diminishing-damage upgrades and buffed the active ability	Re-test both its active attack and upgrade scaling; older launch footage can understate it
Top Electric Mage	0.9.7 increased passive base damage per upgrade and the active stun duration	Its documented signal is damage scaling plus control, not a guaranteed tier position
Side Ballista	0.9.9 nerfed the automatic attack and buffed the active ability	Compare active timing with passive output instead of judging only the auto attack
Force Mage	0.9.9 made the active ability cancel incoming projectiles	Treat it as a documented projectile-response option when that threat is present
Ram	0.9.6 improved behavior and fixed Tier 3 visuals; 0.9.8 fixed inconsistent damage	Re-test damage on 0.9.9 before using launch-era numbers or conclusions
Top Mortar	0.9.6 reduced the active projectile count	Old demo or pre-hotfix clips may show a different active pattern
Fire Mage	0.9.6 increased Firestorm damage	The buff is confirmed; the full current value and relative rank are not published in the note
Back Turret	0.9.6 nerfed it	Treat launch-day recommendations as version-bound
Ground Fire	0.9.6 improved performance	This is a performance record, not a documented damage adjustment

The 0.9.9 post also says Wizard Crew automatic attacks now slow targets for three seconds and all allied melee units move faster toward targets. Those are related build-system changes, but the announcement calls Wizard Crew a crew rather than a module. Keeping the labels separate avoids turning every named combat element into the wrong entity type.

How to evaluate a module in the current build

Start with the problem in the next encounter. Projectile pressure gives Force Mage's documented active effect a clear test. A Side Ballista offer should be judged with its changed active/passive balance in mind. Front Barracks deserves a fresh test because two separate hotfixes changed its active output and fixed upgrade scaling.

Then record the build, biome, difficulty, upgrade level, and whether the result came from an automatic or active effect. One successful run is evidence for that run, not a universal tier. Repeating the same observation under comparable conditions is what can later support a build guide.

Finally, check the announcement date before copying a video. Wanderburg moved from 0.9.6 to 0.9.9 in four days, and several of the same systems changed more than once. A useful current recommendation needs both a version and a reproducible situation.

What the official record does not yet prove

The patch notes do not provide a complete module roster, every base value, every upgrade branch, unlock requirements, offer weights, or all interactions. They also do not establish the best module or strongest build. Those gaps are intentional boundaries on this page, not invitations to infer missing data.

Follow modules across more than one hotfix

Front Barracks is the clearest example of why a single patch summary is not enough. Version 0.9.7 increased its active base damage. Version 0.9.9 then fixed diminishing-damage upgrades and buffed the active ability again. A guide based only on the first change can still miss how upgrades behave in the current build.

Spider-related notes show a different sequence. Version 0.9.7 increased Spider movement speed, while 0.9.9 made the player vehicle faster in early or base levels but nerfed speed upgrades. Those lines concern a vehicle and its upgrades, not automatically a module. They belong in progression, but they are a useful warning against combining every balance noun into one module tier list.

Ram combines behavior, presentation, and damage fixes across 0.9.6 and 0.9.8. Ground Fire has a performance change rather than a published damage change. These distinctions matter when a player says something was “buffed” or “fixed”: the official record may describe consistency, visuals, control, or performance without changing combat strength.

Build a reproducible module note

Use one line for the setup: build, vehicle, biome, difficulty, module tier, and relevant upgrades. Use a second line for the question: automatic damage, active effect, control, targeting, movement, or stability. Use a third line for the observed result and whether it repeated. This format is compact enough to maintain after another hotfix.

When comparing two modules, keep the encounter and surrounding build as similar as the run allows. Roguelike variation prevents a laboratory-perfect comparison, so state the limitation instead of converting one outcome into a precise ranking. A qualitative role can still be useful when it is tied to a visible effect: Force Mage responding to projectiles is a stronger claim than a universal letter grade.

For a correction, prefer a current-game screenshot or short recording that shows the build and effect. Add an official announcement when the claim is a documented change. Community evidence can support repeatable behavior, but it should remain labelled as testing until an official source confirms a value or mechanic.

For the broader unlock structure, read Vehicles, Biomes, and Unlocks. For first-run decision rules, use the Beginner Guide. When a later patch changes a named module, the dated record belongs in Updates before this summary is revised.

Sources and version boundary

The modular arsenal and persistent-unlock descriptions come from the official Steam store page. Every named change above comes from the official 0.9.6–0.9.9 announcements, checked September 12, 2026. This page does not use demo values as current Early Access data.