Start with the fix that matches your version and symptom
Dungeonbound's demo updates document several different co-op problems, including stuck lobbies, failed rejoining, blocked gates, disconnects, and doubled screens. The useful first step is to compare your build and exact symptom with those fixes. A patch note about one of them is more specific than a claim that every connection problem has the same cause.
The latest of the three relevant announcements, v0.1.51, explicitly lists fixes for co-op disconnects and doubled screens. If you are running an older build and seeing that matching problem, check for the available update containing the fix.
The official v0.1.51 announcement is the source for that documented change. It does not provide a universal repair sequence for every current lobby error.
Which co-op problems the updates addressed
The obtained developer notes separate the fixes across three versions:
| Update | Documented co-op fixes |
|---|---|
| v0.1.46 Halloween update | Several hangs and stuck lobbies. |
| v0.1.50 | Rejoining, guest Mana and damage totals, and teams stuck at gates. |
| v0.1.51 | Disconnects and doubled screens. |
These are developer-reported fixes for the development builds. They support checking whether a relevant update is installed, but they do not prove that every later symptom with a similar name is the identical bug.
Keep a joining problem separate from a gate problem, for example. Being unable to enter a lobby and being inside a climb with the team unable to move past a gate describe different stages of play, even if both feel like a stalled session.
Check the documented lobby and team-run features
Some lobby behavior also changed alongside the fixes. The Halloween update added Open lobbies, Find Lobby, Show Chat, and the host's ability to remove players. Version 0.1.51 added QUICK JOIN and a ping display.
Use those labels to describe where a problem occurs. A report that says Find Lobby shows a room but joining fails is clearer than simply saying that co-op is broken. The ping display is another available observation, not a documented one-button cure.
Version 0.1.50 also added a saved climb for each team and allowed a player who quits to be replaced by a bot. Those features establish team-run saving and a replacement option; the notes do not spell out a guaranteed sequence for restoring every disconnected player to the same live lobby.
What to record if the problem remains
If the relevant available update is already installed and the issue continues, keep the report focused on the actual failure:
- The game version and distribution you are using.
- Whether you are hosting, browsing a lobby, joining, rejoining, or already inside a climb.
- The visible symptom, such as a stuck gate, disconnection, or doubled screen.
- Any displayed message and whether the problem repeats at the same point.
These details help distinguish a documented old bug from a different current issue. The collected official notes do not establish a single cause or a verified general network workaround for all of them.
FAQ
Which update fixed co-op disconnects?
The v0.1.51 notes list fixes for co-op disconnects and doubled screens.
Were rejoining and stuck gates also addressed?
Yes. The v0.1.50 notes list co-op rejoining and teams stuck at gates among the fixes.
Does a saved team climb guarantee instant reconnection?
No such guarantee is stated in the obtained notes. They document a saved climb for each team and a bot replacement option for a player who quits.
What should I do with a problem that persists after updating?
Record the current build, your role in the session, where the failure occurs, and its exact visible symptoms. The documented fixes are a useful comparison, but a continuing issue should not be assigned an unverified universal cause.