Wanderburg Controls & Movement Guide
Troubleshoot a castle that stops moving or boost that keeps draining. Separate demo reports from diagnostic checks before changing your setup.
Quick answer
If your castle stops moving or boost continues draining after release, first record whether it happens after a sharp turn or a level-up. Both patterns appear in Wanderburg's demo discussion. There is no universal confirmed fix in that thread, and the reports are not limited to keyboards. Movement reports
Match the symptom before changing settings
| Symptom | What players reported | Useful detail to record |
|---|---|---|
| Castle stops despite forward input | The original February 27 post describes repeated throttle presses to resume movement. | Whether it happens on open ground or near another castle. |
| Movement fails after turning | A March 27 reply associates it with a sharp turn on keyboard and mouse. | The direction and inputs immediately before the stop. |
| Boost drains after releasing input | A March 29 Xbox wireless controller report describes boosting when a level-up occurs. | Whether the level-up interrupted an active boost. |
These are player observations, not a proven shared cause. Another reply reports similar stopping on Steam Deck; that is not a compatibility certification for the device. Full discussion
A short, reversible diagnostic sequence
The following checks are diagnostic suggestions, not fixes demonstrated by the thread.
- Identify your version. Record demo or main game, the date and any visible build number. Keep a recent Early Access report separate from an older demo report.
- Identify the active input. Note keyboard and mouse, controller model, wired or wireless connection, and any remapping software you knowingly use. Test one input device at a time if practical.
- Observe the trigger. In a fresh attempt, note whether forward motion stops after turning, after leveling up, or without either event. Do not change multiple settings while trying to reproduce it.
- For stuck boost, try releasing and pressing the boost input once. The original poster said pressing boost stopped the drain in their case. That is a recovery to test, not a guarantee for other versions or controllers.
- Compare the result. If it continues, capture a short clip showing the inputs and the moment motion or boost changes. Add the reproduction steps to a bug report rather than repeatedly reinstalling without new information.
Is Windows Sticky Keys the cause?
It was suggested by one commenter, but other participants disputed it. A controller report also describes unwanted boost drain. Check accessibility settings only if they are relevant to your own input behavior; do not present disabling Sticky Keys as a confirmed Wanderburg-wide fix. Replies
Next step: submit a useful report
Include the game version, operating system, input device, any remapping, the last action before failure and whether the issue repeats. Describe movement stopping and boost draining separately if only one occurs. Avoid adding an assumed cause such as collision, grappling or a broken keyboard unless you have isolated it.
A title-screen or publisher-logo exit is a different failure from movement stopping during play. For launch availability and the Windows requirements, check the release guide.