First, separate three different problems
A. You joined a lobby but cannot start playing. This is a join/session issue. A player separately reported becoming stuck after entering a friend’s room using an invite or room code. The initial forum report alone does not identify its technical cause. Do not replace that missing explanation with invented router-port instructions.
B. Combat works, but inputs stop responding between fights. This resembles the older equipment-room and potion-selection reports. In the cited thread, some players could navigate during combat but became stuck in the staging area.
C. Movement works but the gamepad and keyboard disagree about the selection. One participant reported that a controller appeared to be holding an information view open; changing to keyboard permitted the group to continue that particular demo session. This may not match your controller or game build.
Low-risk checks without inventing a fix
- Record the current game version and whether this is demo or full game. A 2025 demo workaround should never be sold as a verified launch-build fix.
- Ask whether the issue affects host, guest or both. In the historical report, changing the host did not always resolve the affected player’s input. Note the role of every player.
- Check whether the game window has focus. A player reported that opening the Windows start/menu and returning to the game restored input for one session. It is safe to try once, but it is not a developer-authored permanent fix.
- If an input device appears stuck, try the alternative device you already have. A demo player reported controller-to-keyboard selection restored control in the equipment room. Do not unplug equipment during an active save transition, and do not promise a result.
- Have everyone check that updates are installed. The developer shipped a November 2025 demo fix. Use the current game files rather than downgrading to a historical demo build.
- If still stuck, report the exact stage. Include whether you can move during battle, whether potion selection is blocked, which controller is connected, Windows/macOS version, who hosted and whether you joined via invite or code. Post to the official Steam forum.
What the 2025 thread actually established
Multiple people described an input lock. The developer requested detailed reproduction conditions and shipped an update. One player said the update resolved the issue for their machine. Another later said switching window focus helped, and a different player described a controller state problem that stopped after they used keyboard input. This is useful history, but not a single proven root cause. It does not establish a general “press Windows key to fix Chained Beasts” rule.
What about multiplayer networking?
The Steam store lists online co-op and cross-platform features. If you can enter a lobby but cannot move, the observed symptom might be input synchronization, a local control state or something else. Without logs or a developer explanation for your exact build, no specific firewall, router or matchmaking change can be guaranteed. If invite and code joins both fail, take note of that exact pattern and report it; do not disable your security software based on a guess.
Before you abandon the run
If you are in the full game and have an available checkpoint, consult the developer-described restore-flow guide. It describes day-start checkpoints and the original host returning with the team; it does not certify that every lobby lock can be recovered. If a new attempt might overwrite a checkpoint, avoid repeated resets until you understand what your installed build is offering.
Frequently asked questions
Is the issue fixed in the launch build? Not independently established by this guide. The forum includes a demo patch, and a full release may differ.
Should we restart the host? It is a possible general troubleshooting action, but the historical reports include an affected person who remained stuck even when hosting. A restart is not a demonstrated universal solution.
Can we use a keyboard instead of a controller? One person reported success changing input in the demo. Your game version and device configuration may behave differently.
Is the bug the same as the purple screen? No. A rendering failure and an input lock are different symptom groups. For graphics evidence, read purple screen.
Sources and next action
Publisher screenshots are not copied into this site because a specific monetized rehosting license was not documented. See the Steam discussion — Unable to Move in Multiplayer, the official Steam discussion index, the local-only session checklist and checkpoint restore. This is an independent fan-made support article.