BUILD PRINCIPLE
Give every upgrade one job
Wanderburg is an Early Access roguelike about a moving, modular fortress. The official store describes a loop of consuming villages and smaller fortresses, expanding the castle, mounting siege modules, and unlocking more vehicles, artifacts, and captains between runs. Because the map, offered modules, and later balance can change, a reliable build guide needs an order of decisions rather than one perfect final screenshot.
Start by naming the problem that ends your current run: too many targets, incoming projectiles, weak boss damage, poor positioning, or insufficient recovery. Choose one primary module whose documented behavior answers that problem. Upgrade that engine, add one different layer that covers its weakness, and only then spend on extra synergy. A build assembled in that order remains useful when the exact rarity or preferred module does not appear.
Wanderburg 0.9.14 upgrade order
Use the same five-step order after every meaningful choice. It prevents a common failure pattern: collecting several exciting modules while none receives enough support to solve the encounter that is already approaching.
- Choose the immediate combat jobPick crowd coverage, active boss damage, projectile control, ally pressure, or automatic damage according to what is currently stopping the run—not according to the last thumbnail you saw.
- Upgrade the primary engineFavor upgrades that strengthen the module's documented role. More Electric Mage targets improve crowd coverage; Side Ballista's current strength is its buffed active ability rather than the auto attack nerfed in 0.9.9.
- Add a different layerIf damage is working but projectiles end the run, add Force Mage control. If groups disappear but bosses stall, add an active burst option instead of another group-only upgrade.
- Price sustain using current valuesRepair Wrench now heals a flat 25 HP, not 25 percent. Compare 25 with current max health and incoming damage before treating it as the backbone of a high-health run.
- Measure before the next rerollTurn on the optional damage numbers added in 0.9.13, change one important choice, and compare a familiar encounter. Spend a reroll when every offered option misses the job—not simply because the favorite icon is absent.
Four current Wanderburg build paths and their fallback
Electric Mage target chain
Version 0.9.14 raises the automatic attack from five to seven base targets and says upgrades add more targets. Prioritize those target upgrades when repeated groups are the problem. The patch also improved Roaming Storm reliability.
Do not overextend: extra targets do not prove better single-target boss damage. When a large enemy becomes the blocker, pair the Mage with an active burst module or stop spending solely on chain size.
Fallback: Wizard Crew gives a documented three-second slow, while Side Arms offers faster automatic pressure if Electric Mage never appears.
Side Ballista or Front Barracks
Hotfix 0.9.9 nerfed Side Ballista's automatic attack and buffed its active ability. If you select it, prioritize the active shot's useful damage and cadence rather than assuming an old auto-attack build still describes the module.
Front Barracks had diminishing-damage upgrades fixed and its active ability buffed. It is a second current active path that also benefits from the official allied-melee movement improvement.
Fallback: Side Arms received both rarity-based damage buffs in 0.9.10 and a base auto-attack speed change from 3.0 to 2.5 seconds in 0.9.13.
Force Mage and summon support
Force Mage's active ability cancels incoming projectiles in the current official notes. Use it when projectile pressure, not raw health, is the repeatable cause of failure. Wizard Crew's automatic attacks slow targets for three seconds.
Allied units were already invincible; 0.9.14 additionally makes them immune to fire, stun, and knockback. That removes several disruption risks, while the 0.9.9 notes say allied melee units move toward targets faster.
Fallback: if offers do not support a full ally package, keep the control piece and add a separate automatic or active damage engine rather than spending rerolls to force the unavailable theme.
Side Arms automatic baseline
Side Arms is the clearest current automatic-damage alternative because official notes document stronger rarity scaling for active and automatic attacks, followed by the faster 2.5-second base automatic attack in 0.9.13.
Use it when attention is needed for driving and active defensive timing. Then add control or focused burst according to the first encounter it cannot finish cleanly.
Fallback: Electric Mage takes the automatic slot when groups are the specific blocker; Side Ballista takes the active slot when priority targets matter more than unattended pressure.
How to spend module, artifact, and reroll choices
Wanderburg separates new Module Rerolls from Artifact Rerolls. Hotfix 0.9.10 says every six unlocked Modules grant one New Module Reroll, and every six unlocked Artifacts grant one Artifact Reroll. Version 0.9.14 separately adds a second Artifact Reroll from the start. Keep those currencies conceptually separate: unlocking six modules does not justify wasting an artifact reroll, and the second starting artifact reroll does not guarantee the missing combat module.
The offer has a current job
Take the option when it strengthens the chosen engine or covers the weakness that just caused damage. A less glamorous answer can be better than an on-theme icon with no immediate purpose.
Every option duplicates a solved job
Spend when all offers add more of what the build already does while movement, projectiles, boss damage, or recovery remains uncovered.
The next encounter changed the problem
A crowd path can pivot into active boss damage; an active build can add steady automatic pressure. Preserve the working core and change the unsupported layer.
The number belongs to an earlier patch
Repair Wrench 25%, Electric Mage five base targets, and Side Arms 3.0-second base attacks are pre-0.9.14 values, not current build inputs.
Boss, Overtime, and sustain adjustments
Do not treat the boss as a larger version of the previous group. Version 0.9.14 says some larger enemies no longer take percentage-based damage from boss explosion damage, and the game now zooms out slightly during boss fights. If a build's clear depended on spreading effects or explosion percentages, add a direct active answer before committing to the boss.
Version 0.9.13 guarantees that bosses drop at least 50 Silver, but a reward floor is not evidence that an early boss is safe. Use the decision flow first: confirm the primary engine, cover its weakness, and keep enough control or movement to maintain useful uptime. A guaranteed reward only matters if the fortress survives to collect it.
Overtime advice is especially version-sensitive. The official 0.9.13 notes changed Grassland, Desert, and Darkforest Overtime and added a late-game Epic Red Overtime Metzler, while 0.9.14 adjusted stun resistances for Overtime enemies. A control build that feels reliable in the regular biome may need more direct damage later; do not describe one stun or slow result as a permanent lock.
For sustain, compare Repair Wrench's flat 25 HP with the fortress's actual health and the damage still getting through. Grassland 1 received health pickups in 0.9.6, so a first-biome route may have environmental recovery that a later biome does not mirror. Choose sustain for the run in front of you, not for a percentage value removed from the game.
A practical first-run and next-run record
Turn on damage numbers for one familiar encounter. Write down the biome, difficulty, primary module, one major upgrade, one support choice, and the encounter that ended the run. On the next attempt, change one of those decisions. This modest record uses the 0.9.13 display feature as a learning tool and makes later patch comparisons possible.
Persistent unlocks widen the option pool, but more options do not remove the need for an order. The store page identifies modules, vehicles, artifacts, and captains as between-run unlocks. Track which new choice changes an early weakness, and remember that every six Module or Artifact unlocks now also advances a different reroll count.
The result is a Wanderburg build method that can survive unlucky offers: select a job, strengthen one engine, cover one weakness, measure, and pivot. That is less dramatic than a nine-build tier list, but it tells you what to do when your preferred rare item never appears—and which old number to ignore after the next hotfix.
Wanderburg build guide FAQ
What is the best Wanderburg build in 0.9.14?
There is no official permanent best build. In 0.9.14, choose a primary job first: Electric Mage for groups, Side Ballista or Front Barracks for active burst, Force Mage and Wizard Crew for control, or Side Arms for steady automatic pressure. Then cover the weakness the next encounter exposes.
What should I upgrade first in Wanderburg?
Upgrade the module that already answers your immediate threat, then add movement or control, then sustain. Avoid spending early upgrades across several modules that all perform the same job.
Is Electric Mage good in Wanderburg 0.9.14?
Official 0.9.14 notes raised its automatic attack from five to seven base targets and say upgrades add more targets. That makes it a current crowd option, but it is not proof of the best single-target boss build.
Does Repair Wrench heal 25 percent in Wanderburg?
Not in 0.9.14. The official hotfix changed Repair Wrench from 25% healing to a flat 25 HP heal, so older percentage-based sustain advice is outdated.
Sources checked
- Wanderburg on Steam ↗
Official Randwerk listing used for Early Access status, the consume-and-grow loop, modular siege arsenal, procedural runs, and persistent module, vehicle, artifact, and captain unlocks.
- Official Wanderburg news and hotfix log ↗
Official 0.9.6–0.9.14 announcements used for every named balance value and mechanic on this page, including Electric Mage targets, Side Arms speed, allied-unit immunity, rerolls, and Repair Wrench healing.
- Official Early Access roadmap announcement ↗
The September 30 roadmap is used only to establish that balance, performance, and content will continue changing. It is not treated as a promise of a specific unannounced build.