This is the most specific fault in the game’s launch week, and it is documented well enough to answer properly. It is also a useful case study in why “the game is broken” needs a week number attached.
What went wrong
In Week 10, the portal event could leave the player unable to keep operating the inn. Because the week’s objectives could no longer be completed, the run stalled there rather than crashing.
That distinction matters for troubleshooting. There was no error dialog and no failure state to report; the game simply stopped offering the actions the week required.
The two fixes, in order
| Version | Date | What it changed |
|---|---|---|
| 1.0.0.261023.1 | 23 October 2026 | Fixed the issue where, after the portal was repaired, it still denied adventurers access |
| 1.0.0.261024.1 | 24 October 2026 | Fixed the portal repair event triggering again while a repair was already in progress |
The first fix restores the portal; the second stops the repair sequence from restarting itself. A run that hit both faults needed both patches.
Resuming a run that was already stuck
The launch-week note gave a specific instruction for players who were mid-Week 10 when the update arrived: to avoid problems, load Day 2 when resuming the game and start again from there.
Two things that instruction implies. The fix applies forward from a loaded day rather than to a corrupted file, and Day 1 of that week is effectively forfeit. The note also says that players starting Week 10 for the first time after the fix should not encounter the issue at all.
About the test branch
Before the public fix, the developers opened a beta branch called dibugtest so affected players could help confirm the fix and report error messages. The first note is explicit that the bug was confirmed fixed on that branch.
If you find a guide telling you to switch to dibugtest, you are reading launch-week material. The public build has the fix, and switching branches now would only move you off the stable version.
If Week 10 still stalls today
- Confirm the version is at least 1.0.0.261024.1.
- Load Day 2 of Week 10 rather than the affected day.
- If it still blocks, back up the save folder before anything else, then report the version and the exact point where the week stops.
The crash and loading page covers the other launch-week freezes, several of which share the same “interface stops responding” shape without being the portal fault.