Wanderburg build guide: three starting plans
Compare ram, fire and troop plans, with launch-patch changes and clear trade-offs.
Quick answer: start with one damage plan and one way to recover your position. The three plans below are starting experiments, not a tested strongest-build ranking.
Three build starting points
The community build guide documents ram, fire and barracks ideas from the Demo. We use those as historical leads, with launch-week changes below. Exact performance in Early Access remains unmeasured here.
| Plan | Starting pieces | What to check during a run |
|---|---|---|
| Ram approach and retreat | Ram plus a movement option | Can you leave after contact, or are you spending all movement on the approach? |
| Fire pressure | Fire Mage with a recovery or escape option | Can you maintain useful attack range without taking more damage than you deal? |
| Troop support | Side Barracks, progressing toward Front Barracks | Do you still have an answer when your troops fail to clear a path? |
Pick one plan for a run rather than treating this as a shopping list for a single loadout. The unlock requirements show what you can pursue next.
Add a captain deliberately
Our editorial approach is to test the basic module plan before adding a difficult captain penalty. For a summon experiment, Empress is a candidate because launch reporting describes increased friendly-unit production with reduced speed. If switching to cannons instead, compare Patchy's outgoing bonus against his incoming-damage penalty. See the sourced captain table.
Adapt old advice to the launch patch
The official 0.9.8 notes say Nitro regeneration starts 0.5 seconds after boosting and Ram damage inconsistency was fixed. Do not base a movement plan on repeatedly tapping boost to exploit regeneration.
Earlier launch fixes strengthened Firestorm and Front Barrack's active attack. That is a reason to revisit an old demonstration, not proof that either plan now wins every matchup.
Compare the result
Keep the same map and difficulty, change one piece, and note where the run became difficult. Record whether you lost health, space, or damage uptime first. That gives the next purchase a specific purpose.
Save the loadout and version in the build notebook. A useful result includes the failure as well as the successful combo; a screenshot of a large damage number alone does not establish reliability.
Sources & corrections
Community Demo build guide; current patch links in article ↗Written with AI assistance from linked sources. Gameplay suggestions are editorial guidance, not results from our own playtest. Report a correction.