Shift At Midnight Bugs: Fixes for Stuck Customers and the Final Entity
Troubleshoot stuck customers, persistent text, doorway jams, and an invulnerable final entity in Shift At Midnight.
Quick answer
- If the final entity takes no damage, try scaring or shooting one remaining customer.
- Avoid carrying extra customers into the final encounter through canceled dialogue.
- Multiple customers can overlap, crowd the doorway, or remain stuck in the store.
- Avoid answering the phone after aggravating the doppelganger and letting it flee.
Shift At Midnight Glitches
This demonstration shows overlapping customers, persistent text, and a final entity that stops taking damage. It also shows the workaround that restored progression in that specific encounter.
Continue reading
These related guides answer the next questions around this topic so you can keep moving.
Known bugs and the fastest fixes
Shift At Midnight bugs can disrupt transactions, crowd the doorway, and stop progress during the final encounter. The most serious case occurs when the final entity becomes invulnerable while customers are still inside. If that happens, try dealing with one remaining customer instead of continuing to attack the entity.
Final entity is not taking damage
The final entity can stop taking damage if its encounter begins while other customers are still in the store. This can make Shift At Midnight seem stuck even though the encounter has started.
Try this recovery sequence:
In the demonstrated case, scaring off one customer caused the shift-completion state to register and allowed progression. Use this workaround when customers remain inside during the invulnerable encounter; it is not a general solution for every Shift At Midnight entity stuck state.
To avoid the conflict, do not use dialogue cancellation to carry extra customers into the final encounter.
Customer glitches: duplicates, overlaps, and doorway jams
Several Shift At Midnight glitches involve customers entering the store together or losing their normal transaction state.
| Problem | What it looks like | What can happen |
|---|---|---|
| Duplicate customers | Two copies of the same customer push into each other | One may lose its items and remain in the store |
| Overlapping characters | A creature stands in front of an active customer | Dialogue, questions, and transactions can overlap |
| Doorway congestion | Multiple customers crowd the exit | They can obstruct movement and interfere with characters leaving |
| Broken transaction state | A fleeing customer completes a transaction | The customer's dialogue and transaction states can become desynchronized |
A dialogue-cancel glitch can place multiple customers in the store at once. If the night ends without dying, respawning, or restarting, those extra customers can remain during the next shift.
Crowded characters may push into each other near the exit. This can obstruct your movement and prevent other characters from leaving cleanly.
Customer is stuck after their items disappear
A duplicate customer can become stuck after the other copy completes a transaction. In one incident, the remaining customer's items disappeared, but the character stayed inside the store.
No recovery method is established for this exact state. Prevention is safer:
- Do not cancel dialogue to place multiple customers in the store.
- Avoid creating more overlapping customer states.
- Keep extra customers out of the store before the final encounter.
Persistent text at the bottom of the screen
Bottom-screen text can remain visible if you aggravate the doppelganger before answering the phone, wait for it to run away, and then answer the call. In the demonstrated sequence, the text remained for the rest of the game.
Avoid that exact event order. Do not let the doppelganger run away before answering the phone if you want to prevent the persistent-text glitch.
When Shift At Midnight is not working during a transaction
A transaction can break if you injure a customer, approach him, let him begin running away, and then complete the transaction while he is fleeing.
This can desynchronize the customer's dialogue and transaction state. Avoid completing a sale while an injured customer is already running away.