Shift At Midnight’s public Store page describes a Story Mode built from 13 randomly generated shifts, plus an Endless Mode labeled BETA. The page also says a free major update is planned for Q4 2026. Those labels matter: released Story content and a beta mode should not be described as if they have identical objectives, enemy pools, or progression. Recheck mode details after each official patch.
Story Mode is the starting route
Story Mode combines the gas-station job with the detective loop. Players stock shelves, take deliveries, clean, serve customers, examine IDs, cross-check a computer, and observe behavior. The official page presents those duties as the core premise. Build your first run around learning the sequence rather than rushing to a single ending or copying a route from an unrelated game.
The page says there are 13 randomly generated shifts. Random generation means the same checklist can survive while the station arrangement, customer timing, or route changes. Keep a mental model of evidence and exits, not a claim that one shelf or room always contains the needed interaction.
Random shifts change the plan
Before a shift, decide who handles the current customer and who watches the station. During the shift, note the location of the computer, likely retreat routes, and any tool that is actually present. After the shift, record what changed. This produces useful knowledge without pretending that one successful run proves a global spawn rule.
Randomness also affects how you write a guide. Mark confirmed facts from the Store page separately from observations made in a specific shift. A reader should be able to tell whether “13 shifts” is official product information or whether a suggested route is only a current-build example.
Endless Mode boundaries
Endless Mode is labeled BETA on the official Store page. The July 29 announcement says that Rakes emerge from the forest in Endless/Post-Story and that patience was removed in Endless/Post-Story. Those are useful dated notes, but they are not a promise that Endless has the same customer sequence as Story or that future builds will preserve the exact balance.
Do not present a planned feature as already available. The Store page says a free major update is planned for Q4 2026; that schedule can move, and it does not define the update’s final contents. Put planned items in an Updates timeline with a date and a status label.
Mode-aware threat notes
When recording a creature or defense result, write the mode first. A Rake observation from Endless/Post-Story should not become a Story-mode rule. Likewise, a second-gun note from the July 29 announcement is described for regular store hours and may not map to every stage. Mode labels protect the guide from overgeneralization.
Track progress without a false checklist
Numbering a shift is useful for personal progress, but do not infer that “shift seven” always contains a particular customer, creature, or room. The official wording is randomly generated shifts, so a page should tell readers what to verify rather than promise a sequence. Keep a personal log with the shift number, mode, objective, evidence, and outcome; use the log to improve a method, not to manufacture a fixed walkthrough.
Solo and co-op choices
The Store page lists both single-player and online co-op. Solo players must perform the evidence and route jobs themselves, so a short callout to self—ID, computer, behavior, exit—helps preserve the order. Co-op teams can split those jobs, but should use proximity chat and agree on a final decision maker when several players are nearby.
Returning after a patch
After an update, replay one familiar investigation and one unfamiliar shift. Compare the customer-check loop, the available shop tools, and the defense transition. If the change is only described in an announcement, label it as a patch note; if it is planned, keep it out of released-mode instructions. This gives returning players a fast way to identify what needs a fresh test.
Write the mode name and date on every observation. This is especially important for the July 29 Rakes and patience notes, which are explicitly tied to Endless/Post-Story. A mode label stops a useful discovery from becoming a misleading universal Story rule. Keep planned Q4 2026 content separate until an official announcement confirms that it is live.
Write a mode label on every observation
The simplest version-control habit is to begin a note with Story, Endless, or Post-Story, followed by the date and the Steam branch if one was used. Then record what the customer did, what tool was available, and what changed after the decision. This is particularly important because the July 29 announcement ties Rakes and the patience change to Endless/Post-Story. A mode label stops a useful observation from becoming a misleading universal claim.
Keep planned work separate
The official Store page’s Q4 2026 major-update statement belongs in a planned section until an announcement confirms that the content is live. Do not build a route around a future system, and do not give a planned feature a release date that the source does not guarantee. When the update arrives, replace the plan with the official note and a current-build check. This preserves trust for readers who use the guide between patches.
Sources and limits
Recommended guides
Choose the guide that matches what you want to do next.
All Modes guides
1 focused guides with steps, checks, and current caveats.