The defense phase begins when the investigation has failed and a creature can return. Shift At Midnight’s official Store description names three responses: board up doors, place traps, and hide. That short list is useful because it prevents a common panic error—continuing the normal shop routine after the threat has changed the objective. It is not a complete tactical chart. Door locations, tool availability, enemy behavior, and the value of confrontation require current-build testing.
Recognize the transition
Keep one sentence ready for the team: “The threat got out; switch to defense.” Say what you know and what you do not know. If you saw the customer leave but did not identify the creature, report that uncertainty instead of sending everyone to the same door. In solo play, use the same mental callout and stop the physical task before deciding where to go.
The station is randomly generated across shifts, and the public Store page says no two shifts are the same. Do not memorize a single universal safe corner. Memorize the principles that survive a changed layout: keep an open route, know which doors can be blocked, notice where traps are available, and never let the shortest path take you into a dead end without a second exit.
Barricades are time, not victory
A barricade buys a decision window. Use it to separate the creature from a route or to create time for a teammate to reach a safer position. Do not treat the first door you see as automatically best. Ask what the barricade protects, where the team can stand afterward, and whether a blocked entrance forces everyone into the same corridor.
If you are carrying out a normal store task when the transition occurs, leave it unless the game explicitly requires it for survival. A shelf, box, or cleaning target does not provide the same value as a route that keeps players alive. Track which barricade was placed and what changed; if the creature breaks through, that observation is more valuable than a vague claim that barricades do not work.
Traps need a reason
Place a trap where it changes the enemy’s route or protects a retreat, not merely where there is empty floor. The public description confirms trap placement but not a fixed damage value, trigger rule, cooldown, or best location. Keep those fields marked as needing live or version testing. A trap that slows an approach may be more useful than a trap that looks dramatic but covers no path the creature must use.
In co-op, announce the trap and its intended route. A teammate who does not know where it is can trigger or bypass the setup. Do not place every available tool at once if the current threat can be observed safely; preserve a choice for the next movement change.
Hide or confront
Hiding is explicitly named by the Store page, so it belongs in the default plan rather than being treated as a failure. Choose a hiding route with a clear reason: you are waiting out pressure, regrouping, or avoiding a threat you cannot safely confront with the current tools. Confrontation is a separate decision. Ask whether the enemy is exposed, whether the team has a retreat, and whether a weapon or trap is actually available in this build.
The July 29 official announcement says a second gun can be purchased for regular store hours and that Rakes emerge from the forest in Endless/Post-Story. That is update-specific evidence, not permission to assume every mode has the same weapon or enemy behavior. Write the mode and update date next to any combat observation.
Learn from a failed defense
After a loss, classify the failure as route, timing, information, or resource. A route failure means the team chose a dead end. Timing means the barricade or trap was placed after the threat reached the station. Information means teammates did not know the same enemy location. Resource means a tool or weapon was spent without changing the path. Change one category on the next run so the result teaches you something.
Make the retreat legible
A defense plan works only if the team understands where it leads. Before placing a barricade, name the protected route and the fallback route. Before placing a trap, name the approach it is meant to influence. If the team cannot agree on those two sentences, pause at the safest available distance rather than spending every tool at once. This is especially important in a generated shift, where a familiar-looking corner can hide a different dead end.
The official Store page confirms the broad choices but does not publish a universal barricade durability, trap cooldown, enemy hitbox, or hiding timer. Keep those values out of a permanent checklist until a current build and mode are identified. A reader benefits more from a test method—place one tool, watch the route, record what changed—than from a precise number that may already be stale.
If the team has no confirmed enemy location, do not spend every resource on a guess. Keep the player with the best sightline listening while another player checks the next safe route. If the threat is visible, describe movement rather than shouting only its name. These small information rules are useful in solo play too: pause, identify the route, choose one action, and reassess after it changes the space.
Sources and limits
Recommended guides
Choose the guide that matches what you want to do next.
All Survival guides
1 focused guides with steps, checks, and current caveats.