Welcome to the Game III First Night Guide

Your first job is not to optimize the entire night. It is to learn enough of the motel, establish one income loop, and reach the next Normal checkpoint with a setup you understand.

Patch and verification scope: Community route compiled July 20, 2026. The detailed player sources predate Patch 1.0.3. Official patch changes are included where documented, but this site has not independently replay-tested the route on 1.0.3.

Mode: Normal is the recommended learning mode because official launch information documents a checkpoint at each full in-game hour. Spoilers: light mechanic and early-threat preparation; no ending details.

First-night checklist

Do not chase all seven tasks at once. Complete the motel setup, then work down the list.

Step 1: learn the physical route

Before a long computer session:

1. Walk from the desk to the rear access.
2. Find the electrical area and the outside network repair point.
3. Identify at least one hiding route.
4. Practice returning to the desk and locating the panic button quickly.
5. Lock doors behind you when the current interaction allows it.

Several threats are reported through quiet audio or a visual approach. Knowing where to go removes a second decision when a cue interrupts browsing.

Step 2: make a small inventory plan

Players repeatedly associate Cletus with requesting one meth item. During the opening motel check, look for one. If you find several, carry one and remember where the others are instead of loading the inventory with all of them.

This is community advice, not a guaranteed spawn rule. If you find none, do not waste the whole opening phase repeating the same rooms. Continue the setup and use the failure table below if the encounter occurs.

Step 3: start income without getting trapped in it

Official material confirms the central VirtMesh choice: mount a compromised machine for access or convert it into a DOS Coin miner. For the first loop:

1. inspect the rates and access options shown in your current interface;
2. choose a useful available machine rather than memorizing an old ranking;
3. watch for the risk of staying on one machine too long;
4. rotate when the interface indicates that access is becoming unsafe;
5. preserve a DOS Coin reserve for the defense branch you choose next.

The goal is repeatable income, not the most expensive grid upgrade before you know whether the motel can be defended.

Step 4: choose a defense branch

Use the problem your run actually has.

Sensor-first

Choose this when you miss approach cues or become overloaded at the computer. Use the dedicated DOS Coin route to compare its reported sensor branch with the economy branch. Before buying full coverage, test whether the first warning layer actually answers the approach question that is ending your runs.

Patch 1.0.3 increased non-jumpscare threat audio by 20 percent. Older advice that treats heavy audio assistance as mandatory may therefore be stale, but the patch does not make every cue obvious or identify the threat for you.

Economy-first

Choose this only when you can already handle early warning checks. Community evidence supports establishing the core access apps and a warning reserve, then evaluating VM expansion, mining, and Key Cue one decision at a time. If the next purchase prevents you from funding the warning tool needed before the next checkpoint, stop.

The DOS Coin route compares both branches and keeps its counterexample and source limits on that strategy page.

Step 5: use the browser systematically

The official description says keys can be hidden across websites and page source. On every promising site:

1. read visible text;
2. test hover and click targets;
3. inspect images;
4. inspect page source.

If you find a key, record its number and complete hash together. If you find a URL or Fetch value needed by a request, save it with the site name. Good notes turn a death into a short checkpoint recovery instead of another full search.

Step 6: treat interruptions as task switches

When a threat cue, hack, power loss, or network loss interrupts the computer:

1. stop the current input;
2. identify whether the problem is physical, digital, power, or network;
3. perform the shortest known response;
4. wait for an observable all-clear rather than resuming on a guessed timer;
5. record what happened after the run is safe.

For exact community-reported cue/action routines, keep the threat guide open. For the five hacking interfaces, use the controls guide rather than guessing under a deadline.

Step 7: review at the checkpoint

At the next full in-game hour, Normal should create the documented checkpoint. Use it as a learning boundary:

• Which door or path did you forget?
• Did an alert identify a useful direction?
• Did a purchase produce value before the checkpoint?
• Which links, requests, and full hashes are already preserved?
• What single failure is most likely to end the next hour?

Change that one failure first. A checkpoint is most useful when each retry tests a revised decision instead of repeating the same plan.

Failure and recovery

Handoff to the full route

You are ready for the Normal walkthrough when you can:

• navigate the motel without searching for doors;
• start a DOS Coin loop and leave it before access becomes unsafe;
• name the defense branch you chose and the problem it solves;
• preserve a complete key hash or useful request link;
• reach a full-hour checkpoint and identify one adjustment.

The Normal walkthrough continues from that state through A.C.R.S. contacts, later Wiki access, systematic key search, decryption, merge, and the recorded completion signal.

Source note

Rechecked July 21, 2026 against official product, launch, VirtMesh, and Patch 1.0.3 information plus a live community threat discussion, third-party editorial guides, and public playthrough evidence. The ordered routine is original synthesis; no source prose, screenshot, thumbnail, or video frame is reproduced.