Wanderburg Guides

Wanderburg Guides gives you a practical first-run route: consume nearby targets, grow the castle, choose modules for the next threat, and use the current Steam build when checking a problem. Start with the beginner guide for the run loop, then use the performance guide only when a technical symptom interrupts play. The launch-day 0.9.6 hotfix is the current build marker for this first release of the library.

Start with what the official game actually says

Wanderburg describes itself as a minimalist open-world roguelike about Castles on Wheels. The official site frames the player task in a compact sequence: consume, grow bigger, upgrade modules, survive, unlock weapons, and explore a procedurally generated map. The Steam description adds the combat-facing version of that pitch: drive the moving castle into battle, devour villages, assemble siege machinery, and grow with each defeated stronghold.

That sequence is useful because it gives every first run a purpose. A small fortress is not just a character with a health bar; movement, the space the fortress occupies, and what it can absorb are part of the run. Growth changes the risk profile. A larger target can be attractive because it promises progress, but it is also a cue to reconsider whether the current fortress is ready for the encounter.

Turn that loop into a quick checklist: find a target you can safely consume, decide which threat the next module must answer, keep enough room to move, and reassess before pushing into a larger fortress. The game is in Early Access, so the best value of this checklist is that it still works when a patch changes a damage value, an enemy mix, or a module selection.

For the direct first-run explanation, open the Wanderburg beginner guide. It builds from the official loop and marks the points where a player should stop treating a description as a guarantee and start checking the current build.

Read build-sensitive advice as dated field notes

The initial content is verified against the 0.9.6 hotfix published on September 8, 2026. That announcement changed Grassland enemy composition, reduced the Dark Tower health on Difficulty 1, adjusted several offensive tools, and addressed technical issues. Those changes are not a complete balance model, but they show why dates matter. A statement about early pressure or a particular tool can be correct for the launch hotfix and wrong after the next one.

When you read a page here, use three markers together:

1. Verified on build tells you the build boundary the page was checked against.
2. Updated date tells you when the editorial review happened.
3. Source links show whether the statement is an official fact, a documented hotfix item, or a cautious player-facing interpretation.

This makes a practical distinction. “Steam lists Windows PC as the confirmed platform” is a store fact. “Ground Fire performance improved in 0.9.6” is a launch-hotfix fact. “This will always be the strongest way to play” is neither, unless it is supported by repeatable testing and a current version note. The first-release library excludes that third kind of claim.

The performance and fixes guide is the right next page for a crash, stutter, visual, or controller-adjacent concern. It separates the official 0.9.6 changes from safe troubleshooting checks and explains why the retired demo cannot be used as a current reproduction environment.

Use the library in the order of your problem

New players usually have one of four questions, and each needs a different kind of answer. If the question is “what am I trying to do during a run?”, begin with the core-loop guide. If it is “why is the game behaving badly on my machine?”, use the performance record. If it is “where can I get it, what platform is confirmed, and is the demo still available?”, move to Release & Steam. If it is “what changed at launch?”, read Updates.

This task-first route is intentionally smaller than a navigation bar that exposes every game noun at once. A long header can be helpful once a roster or item database is complete. At launch, it more often turns an uncertain detail into an apparent fact. The primary navigation instead keeps the durable player tasks visible: learn the run, verify release availability, and monitor changes.

The guide pages also avoid making a historical test build look like the current product. The official announcement says the Steam demo was retired at launch because it no longer represented the Early Access release. If a search result, video, or old community post refers to the demo, check Demo & Playtest Status before applying its advice to the live game.

Turn early runs into better future runs

The official material identifies modules, vehicles, artifacts, and captains as persistent options. Use each run to learn one useful relationship: which tool solved the immediate danger, which target created the next opportunity, and which new option changed a later decision. A short note after a run turns unlocks into a personal build reference instead of a collection of names.

For launch build 0.9.6, the current notes give several useful anchors: Grassland 1 now has health pickups; Grassland 3 plus Dark Forest 2 and 3 use fewer, stronger enemies; and Difficulty 1 Dark Tower health moved from 12,000 to 10,000. These are concrete reasons to read the current encounter and choose for the threat in front of the castle rather than blindly copying an older route.

The same page of notes records a reduced Top Mortar active-projectile count, nerfs to Back Turret and Tankbert, and increased Fire Mage Firestorm damage. Treat those as a first experiment list: if one appears in a run, notice how it helps the current problem and compare the result after the run. The Updates hub keeps the dated change record handy, while the reference page collects the official community and language links for questions that need the live service rather than a build opinion.

Sources, corrections, and the next check

The first-run model on this page comes from the official Wanderburg site and the Wanderburg Steam store page. The current technical boundary comes from the 0.9.6 Steam Community hotfix. All were checked on September 9, 2026.

If an official update changes a fact on this page, or if a source link has moved, send the correction to support@wanderburgguide.wiki with the URL and the version or date you observed. Corrections are more useful when they distinguish a verified fact from a personal build preference. That keeps this field manual practical for the next player instead of merely longer.