Wanderburg Troubleshooting
Pick the right Wanderburg troubleshooting path for launch, crashes, movement stops, boost drain, and report-ready diagnostics.
Quick answer
Version and evidence: Launch-week troubleshooting hub; routes players to symptom-specific pages and keeps unverified fixes out of the main path. Last checked 2026-09-08 by the Wanderburg Wiki maintainer.
Start with the symptom, not with a reinstall. A title-screen exit, a crash during launch, a castle that stops moving, and boost that keeps draining are different problems. Use the path below so your next report includes useful evidence instead of guesses.
Pick your symptom
| Symptom | Start here | Why |
|---|---|---|
| The game exits at title, publisher logo, or startup | Startup and crashes | Checks Windows requirements, launch state, and reversible diagnostics. |
| The castle stops despite movement input | Movement and boost troubleshooting | Public demo reports describe movement stops after turning or during play. |
| Boost keeps draining after release | Movement and boost troubleshooting | A controller report tied boost drain to a level-up moment; no universal fix is confirmed. |
| You are unsure whether the report applies to Early Access | Release guide | Separates demo-era reports from launch-week status. |
Safe first checks
- Confirm whether you are on the demo or Early Access build.
- Record your operating system and input device.
- Change one variable at a time.
- Keep a short clip or screenshot if the issue repeats.
- Avoid copying fixes from unrelated games unless you can explain why they apply.
Report-ready checklist
Before posting to Steam Discussions or Discord, collect the details that make a bug report useful:
- Build context: demo or Early Access, the date you tested, and any visible build or patch label.
- Hardware context: Windows version, Steam Deck or desktop, controller model if used, and whether the input device is wired or wireless.
- Exact trigger: what happened immediately before the issue, such as a sharp turn, a level-up choice, opening a menu, or reaching the title screen.
- Recovery attempt: whether pressing the same input again, restarting the run, verifying files, or changing input devices changed the result.
- Evidence: a short clip, screenshot, or step list is more useful than a broad claim that the game is broken.
What to avoid
Do not stack unrelated fixes before you know the symptom. Reinstalling, changing controller software, disabling Windows accessibility settings, and editing launch options all at once can hide the real trigger. Work in small steps and keep a note of what changed.
If another player reports the same symptom, compare their build, date, and input device before assuming the same cause. A demo-era report may still be useful, but Early Access can change controls, performance, and upgrade behavior.
What is not confirmed yet
No public source currently proves a single universal fix for movement stops, boost drain, or every startup crash. This page will stay conservative until Early Access reports make the patterns clearer.