← Search all guides

Beginner guide · Unwanted forward input · Early Access

Shroom and Gloom auto-walk fix: update to Early Access 0.6.39

The character keeps moving forward after you release W, or stops responding to movement input.

THE SHORT ANSWER

Update the Early Access game to 0.6.39 first. Team Lazerbeam says this release fixes auto-walk and not-walking caused by unrecognized input devices. Relaunch with a normal keyboard and mouse; if the bug remains, disconnect extra HID devices one at a time and report the device that reproduces it. Earlier player reports about Razer Tartarus and Swiftpoint profiles are fallback diagnostics, not a current universal fix.

DIAGNOSTIC ORDER

Test one input cause at a time.

  1. Update the Early Access game to 0.6.39 or later, then relaunch it. The official hotfix says unrecognized joysticks and keyboards should no longer register as valid input devices.

  2. Start a new run with only a standard keyboard and mouse connected. Release W after the opening prompt and check whether the character remains still.

  3. If the issue remains, quit completely and disconnect non-standard HID devices before relaunching: gaming keypads, extra controllers, macro pads, CAD mice, and similar peripherals. This is a reversible diagnostic, not a required permanent setup.

  4. If movement is now normal, reconnect one device at a time and retest. That identifies the device or driver injecting the forward input without forcing a full reinstall.

  5. If the bug remains with only keyboard and mouse, open their vendor software and switch to an unmodified default profile. Older player reports document Razer Tartarus and Swiftpoint remap conflicts; they are fallback evidence for pre-0.6.39 or remaining cases.

  6. Only after the input test should you verify game files or reinstall. Reinstalling alone did not clear one older report, so it is a later diagnostic step rather than the first fix.

  7. If none of these checks work, report the keyboard, mouse, every attached HID device, vendor software, display mode, and Early Access build in the current bug thread. The developer asks for the device when a similar issue remains after 0.6.39.

WHAT SUCCESS LOOKS LIKE

After updating and relaunching, the character stays still after you release W. If a remaining input conflict returns when one peripheral is reconnected, record that device and report it instead of treating the older workaround as universal.

VERSION BOUNDARY

The official 0.6.39 hotfix says the majority of auto-walk and not-walking cases caused by unrecognized devices should be fixed, while asking players to report any remaining device-specific case. The Razer Tartarus and Swiftpoint solutions are independent older reports, so this page keeps them as fallback diagnostics.

A useful next routeKnow what saves before you quit