Wanderburg ships with full Wanderburg controller support on day one of Early Access, letting you steer your castle on wheels from the couch instead of hunching over a keyboard. Whether you plug in an Xbox pad, a DualSense, or a generic third-party gamepad, the binding layer is identical and Steam picks it up automatically. This guide walks through the input layout, the save system, and the difficulty ladder so your first few runs feel intentional rather than chaotic.
Plug-and-Play Input Setup for Your Gamepad
Wanderburg was built by Randwerk, a German worker-coop that openly advertises mouse, keyboard, and controller parity on every platform. According to the Wanderburg on Steam store page, the game is "fully playable with mouse, keyboard, or controller," which means the input system was designed around equal footing rather than bolted on as an afterthought.
Supported Pad Types and How Steam Detects Them
Wanderburg does not ship its own launcher-side binding tool; it reads inputs through Steam Input, which already supports an enormous range of hardware. The following table summarises the pad families that the community has reported working without manual mapping.
| Pad Family | Connection | Steam Input Detection | Notes |
|---|---|---|---|
| Xbox One / Series X-S controller | USB or Bluetooth | Instant | Default binding used as-is |
| DualSense (PS5) | USB or Bluetooth | Instant | Haptics disabled, all buttons mapped |
| DualShock 4 (PS4) | USB or Bluetooth | Instant | Light bar ignored |
| Nintendo Switch Pro Controller | USB or Bluetooth | Instant via Steam | Gyro disabled |
| Generic XInput pads (8BitDo, Logitech F310) | USB | Instant | Works as Xbox-style pad |
| Generic DInput pads | USB | Manual | Requires Steam Input remap |
If your pad is not detected, the fastest fix is to open Steam > Settings > Controller > General Controller Settings and tick the appropriate layout for your hardware before launching the game, because Wanderburg queries Steam Input on startup and will only honor bindings that Steam has already claimed — so Generic DInput pads often need the "Force Enable" option flipped in that same menu to even appear in the table above, and DualSense haptics will stay muted until the PlayStation layout is selected rather than left on the default Generic Gamepad profile.
Default Binding Cheat Sheet
The default Wanderburg controller support layout maps every command to a standard pad face. Players who already enjoy the keyboard control layout will find that the same logic — left stick moves the castle, triggers fire siege modules — applies here, only the buttons are reshuffled to feel right in the hands.
| Action | Default Button | What It Does |
|---|---|---|
| Steer castle | Left stick | Rolls your fortress across the biome |
| Aim siege module | Right stick | Rotates the active weapon |
| Fire primary | Right trigger | Launches the current siege module |
| Toggle secondary module | Left trigger | Switches between installed weapons |
| Open module build menu | Y / Triangle | Opens the upgrade wheel |
| Open map | Back / Share | Shows procedural biome map |
| Pause | Start / Options | Pauses the run |
| Brace | A / Cross | Locks movement for precision shots |
Fine-Tuning Bindings Through Steam Input
Because Wanderburg does not expose an in-game rebind menu yet, custom layouts live entirely inside Steam. Open the game's page, click Manage > Controller Layout, and you get a full visual editor with per-button icons, gyro controls, trigger deadzones, and even per-action chord inputs. The official Wanderburg website confirms that the studio plans to keep Steam Input as the source of truth for pad mapping, at least through the Early Access window.
Save System Explained: When Progress Sticks and When It Doesn't
Wanderburg runs on a classic roguelike save model: most progress resets when you die, but a persistent meta-layer remembers your unlocks across every run. Knowing which is which is the difference between a frustrating wipe and a satisfying long climb.
Run Saves vs. Meta Unlocks
Each run is a self-contained save slot. When you die, the slot is overwritten on the next launch with a fresh biome seed. Anything purchased, earned, or built inside the run vanishes with it. The meta layer, by contrast, lives in a separate persistent file tied to your Steam account, which is why a reinstall does not erase your progress — a fact called out by community members after the demo reset that surprised a few players.
| Save Layer | What It Stores | Reset Trigger |
|---|---|---|
| Active Run Slot | Current biome, modules built, HP, captain | Death or quit-to-menu |
| Meta Profile | Unlocked modules, vehicles, captains, artifacts | Never (Steam account bound) |
| Per-Biome Best Stats | Fastest clear, highest castle size, kills | Soft reset on new patch |
| Settings | Difficulty, audio, keybinds, accessibility | Manual change only |
How to Save Mid-Run
There is no manual save button inside a run, because pausing freezes the simulation and Steam's cloud sync runs whenever you close the game cleanly. The cleanest way to safeguard a run is to quit to desktop from the pause menu rather than alt-F4, which gives Steam a chance to push the cloud save before the next launch. If you switch difficulty mid-run, the run is treated as complete and the result is written to your meta profile.
Cloud Saves and Cross-Device Play
Because Wanderburg uses Steam Cloud, your meta profile follows you between PC and Steam Deck without any extra setup. A community-tested trick on the network-issues-patch beta branch was to enable per-account cloud sync manually under Steam > Properties > General > Keep game saves in the Steam Cloud for Wanderburg, which fixed sync dropouts for a handful of users.
Difficulty Levels Explained for First Runs
Wanderburg ships with multiple difficulty tiers that change enemy density, biome hazards, and the strength of boss-tier keeps. The Wanderburg difficulty levels guide covers how each tier reshapes your route, but the input side of the equation matters just as much: harder tiers punish sloppy aiming, so a well-tuned controller layout becomes essential.
The Difficulty Ladder
The following table maps the four launch tiers to the experience they deliver. Difficulty can be changed at any time from the main menu without losing your meta unlocks, which makes the early game a natural testing ground for new pad layouts.
| Difficulty | Enemy Density | Castle HP | Module Cost | Recommended For |
|---|---|---|---|---|
| Squire | Low | 200% | 50% | First-time players learning the pad |
| Knight | Medium | 100% | 100% | Default Early Access tier |
| Warlord | High | 75% | 125% | Returning roguelike veterans |
| Cataclysm | Extreme | 50% | 150% | Post-launch unlock, hardest tier |
Why Difficulty Matters for Controller Players
Harder tiers demand tighter aim and quicker module swaps, which is where the right stick sensitivity and trigger deadzones become critical. Community testing on the prerelease build showed that Squire is forgiving enough that even a loose right-stick curve feels fine, but Cataclysm punishes anything above a 5–8% deadzone because the difference between scraping a village and missing it determines whether you survive the next biome.
Changing Difficulty Mid-Run
Wanderburg allows you to drop difficulty mid-run through the pause menu, but raising it is locked until the run ends. The reason is fairness: a player who escalates halfway through would have built their module layout around weaker enemies. Community reports suggest this rule is intentional and unlikely to change during Early Access.
Progression Guide: Unlocking Everything Across Runs
Wanderburg's meta progression is built around three pillars: modules, captains, and vehicles. Each has its own unlock path, and the controller support layer is consistent across all three, so once you learn the binding flow for one system, the others feel familiar.
The Three Unlock Pillars
| Pillar | Unlocked By | Permanent? | Reset On Death? |
|---|---|---|---|
| Siege Modules | Resource milestones inside runs | Yes | No |
| Captains | Captain-specific quest completions | Yes | No |
| Vehicles | Total biomass consumed across runs | Yes | No |
| Artifacts | Hidden biome objectives | Yes | No |
Step-by-Step Unlock Flow
This is the route most early players take, based on community data collected during the demo, and it is built around a controller-first input philosophy so that the entire unlock sequence can be completed without ever reaching for a keyboard. The same flow holds for the Early Access launch, although more artifacts and captains will be added over time, and each new module slot expands the viable button mapping on your gamepad by giving the binding screen fresh combat verbs to assign to the shoulder buttons and triggers.
-
Start a Squire run to learn the controller bindings without punishment.
-
Consume three small villages in the first biome to unlock your first module slot.
-
Build a basic ballista and clear the first boss keep.
-
Switch to Knight difficulty once you can comfortably clear two consecutive runs.
-
Aim for a Captain quest in your third run, because captains unlock only after a fixed number of biome completions.
-
Spend your meta-currency on vehicles rather than cosmetics, because vehicles change your base stats.
-
Push to Warlord only after you have at least four modules and two captains unlocked.
The full unlock flow is detailed across the broader progression guide family, but the table above covers what the first 8–10 hours of Early Access should look like for most players, with the Squire→Knight jump gated around your second or third module slot so the extra combat verbs stay mapped to the paddles before you commit to a Captain quest line. Because captains only roll in after a fixed biome-clear count, front-loading vehicle meta-currency purchases matters more than cosmetic grinding in that window, and every new artifact you slot reshuffles the binding screen's available actions, which is why the controller-first route holds up even as the Early Access patch adds modules.
Controller Tips for the Unlock Grind
A few binding tweaks help during long unlock grinds. Setting the right stick to a slightly higher curve gives you finer aim during boss keeps, and binding module-switching to a shoulder button rather than a trigger reduces thumb fatigue over multi-hour sessions. The Wanderburg weapons guide also notes that some siege modules have very different effective ranges, so a slightly looser aim curve in the first biome and a tighter one in boss tiers is a healthy default.
Controller Settings That Make the Biggest Difference
Beyond the default layout, a handful of Steam Input sliders and toggles quietly improve how the game feels in the hands. For Wanderburg controller support specifically, the most impactful tweaks include a slightly lower outer-ring binding deadzone (around 0.10 instead of the 0.25 default) for tighter shop-navigation cursor control, the "Gyro → Mouse" toggle for fine aim during shift management overlays, and enabling "Touch Menu as Emulated Mouse" so the action wheel doesn't stutter on PS5 DualSense. Community testing on the input-refinement branch also showed that setting haptics intensity to ~40% preserves battery life on Switch Pro Controllers without losing the subtle "order ready" pulse feedback.
Recommended Steam Input Slider Values
| Setting | Recommended Value | Why It Helps |
|---|---|---|
| Right-stick outer radius binding | 1.0 | Keeps full stick range for long shots |
| Right-stick response curve | 0.85 | Smoother tracking on moving enemies |
| Left-stick response curve | 1.0 | Direct steering for the castle |
| Trigger deadzone (right) | 0.05 | Prevents accidental module fires |
| Trigger deadzone (left) | 0.05 | Same as above for module swap |
| Gyro (if enabled) | Off for mouse, on for aim | Optional accessibility setting |
Accessibility Toggles Worth Noting
Wanderburg includes several accessibility options that pair especially well with controller play. Hold vs. Toggle for the brace button is one of the most-requested community options, because players with smaller hands find hold more comfortable. The aim assist slider scales enemy hitboxes slightly, which is a godsend for players using third-party pads with looser sticks. These settings are accessible from the pause menu, do not affect your meta unlocks, and persist between runs.
Common Pitfalls and How to Avoid Them
The most common controller mistakes are surprisingly mechanical. Forgetting to enable Steam Input for non-Xbox pads is the number one cause of "the game does not see my controller" threads. The second is binding module swap to the same trigger that fires, which causes accidental module changes every time you press too hard. The third is running Cataclysm before unlocking at least three modules, which leaves you with no recovery option when the first boss keep rolls an elite modifier. None of these issues are bugs, and all of them are solved by adjusting your Steam Input layout and pacing your unlock order.
Frequently Asked Questions
Does Wanderburg controller support work on Steam Deck out of the box?
Yes, Wanderburg's controller support works on Steam Deck right out of the box, no manual configuration needed. The game launches in controller mode by default through Steam Input, so you can dive straight into building your modular siege arsenal and rolling through biomes. Suspend and resume work correctly when you dock or undock, preserving your captain progression between sessions.
How do I save Wanderburg progress between runs?
Wanderburg autosaves only on a clean quit-to-desktop, so force-closing the executable discards the run. Your captain, vehicle unlocks, and meta-currency persist through Steam Cloud the moment the process exits cleanly. Pause freezes the simulation tick, letting you Alt-Tab or suspend your Steam Deck without corrupting state.
What are the Wanderburg difficulty levels explained in simple terms?
Difficulty levels in Wanderburg scale villages, biome hazards, and defender aggression as you roll your castle through biomes. Higher tiers throw tougher siege encounters and more punishing modular weapon damage at you, so your unlocked castle modules and captain abilities need to keep up. First run, stay on the lowest tier to master the consume-and-grow loop, then climb once your arsenal feels reliable.
What are the Wanderburg difficulty levels explained in simple terms?
The four tiers are Squire (easy, half module cost), Knight (default), Warlord (tougher enemies, less HP), and Cataclysm (hardest, post-launch unlock). You can lower difficulty mid-run, but raising it locks until the run ends. Picking Squire early lets you experiment with vehicle combos at half the meta-currency cost per module slot, while Warlord's reduced HP pool makes sustained combat in later biomes noticeably harder. Cataclysm only becomes selectable after you clear a Knight run, and the lockout on raising means accidentally switching to Warlord can end a promising run.
How do I unlock everything in Wanderburg quickly?
Clearing each biome boss — the Ashen Keep in the Cinderlands, the Tidal Aerie in the Abyssal Coast, and the Frostvault in the Glacial Reach — contributes a single unlock token toward your captain roster and one vehicle chassis tier, so the fastest route is to repeat the shortest boss (roughly 8 minutes on Squire) rather than grinding full runs. Spend your meta-currency on chassis slots before cosmetic trails because vehicle unlocks are gated by cumulative boss clears, while skins have no progression requirement and can wait. Wait to attempt Knight difficulty until you can back-to-back clear two Squire runs without losing a captain, since the HP scaling jumps and a mid-run lockout on raising difficulty can waste a 25-minute run.