Shift At Midnight Troubleshooting

Symptom boundary

Symptom	Public evidence	What is not established
Failed to create or join a session	One current community report; a dated official July 22 post	A single current universal fix
Crash after a late-night result	One current community report logged by a developer representative	A confirmed cause or recovery path
Microphone or rejoin issue	The captured report is from the 2025 demo	That the same issue exists in the 2026 release
Lag	No current game-specific official fix in the cited evidence	That every lag report has the same network cause
Save concern	No current game-specific recovery instruction in the cited evidence	A safe file path, deletion step, or guaranteed recovery method

The July 22 branch instruction was explicitly described as temporary. Its current applicability is unverified; it is historical evidence, not a current action on this checklist.

Evidence-safe checklist

1. Record Steam, Xbox, or PC Game Pass as the storefront, not only “PC.”
2. Copy the exact error message and note whether solo play still starts.
3. Confirm every party member belongs to the same storefront pool in the crossplay guide.
4. Confirm every party member is on the same branch and build before retrying; do not use the historical temporary branch as a current default.
5. Compare the group size with the multiplayer limits.
6. Restart the game and platform client, then use Valve’s documented file-integrity check on Steam; neither step is guaranteed to fix the symptom.
7. Include the build date, affected night, and repeatable steps in Steam Support or the feedback and bug-reporting route named in the dated official Discord announcement.

For hardware eligibility, compare the official PC requirements. Do not treat a community report as proof that every installation shares the same cause.

Lobby cannot create or join

Confirm storefront pool, player count, and the exact session error. The current evidence includes individual reports and a temporary July 22 historical workaround, but no universal present-day branch instruction. Use crossplay and multiplayer to eliminate documented mismatches first.

Crash or exit to desktop

Restart, record the night and action immediately before the crash, and verify Steam files using Valve’s instructions. One post-night crash report exists, but it does not establish the cause or guarantee that verification resolves it.

Microphone not working

Check the current game’s input device and voice settings, then record whether the platform can hear the microphone outside the game. The captured microphone report is from the 2025 demo, so it cannot establish a current-release bug or fix.

Lag or delayed co-op actions

Record host storefront, region, player count, and whether the symptom affects every party member. The cited evidence has no current game-specific official lag fix; avoid assigning a network cause without measurements or a repeatable case.

Save or progress concern

Stop before deleting, renaming, or replacing any file. Record the platform, account, last completed night, and displayed state, then use official platform support. The cited evidence provides no verified save path or recovery procedure, so this page does not invent one.