Your first repairs, orders, and upgrades

The first repair cycle

1. Read the order. Identify the requested outcome before touching the device.
2. Inspect the gadget. Note anything the current UI marks dirty, faulty, missing, or incomplete.
3. Disassemble carefully. Follow the interactions shown in the game; do not import a real-world screw order.
4. Clean the required parts. Watch for the game's state change before moving on.
5. Replace faulty parts. Track the purchase so you know the real cost of the job.
6. Reassemble and confirm. Check the order state before delivery.

Protect your early cash

Treat cash as working capital. Keep enough available for the next required part or fee instead of spending the entire balance on a cosmetic or convenience purchase. There is no verified universal reserve number yet; it depends on the job and the current economy.

Before buying an upgrade, ask whether it helps with a job you already have and whether the purchase leaves enough cash for parts. The money-making guide provides a simple order ledger.

Keep a tiny session log

For each completed job, record the device, request, purchases, payout, tip if shown, and any dialogue choice that felt important. A five-line note is enough to turn a vague memory into evidence for the next run.

Customers and choices

The official store description says customer interactions can affect their lives and the branching storyline. Read the dialogue and capture the exact choice wording before you confirm it. One forum theory or one save file is not proof of a hidden-ending condition. Use the spoiler-controlled endings guide to track confidence.

When a task does not complete

1. Confirm that the game is updated.
2. Re-read the order and identify the exact required state.
3. Inspect the device for an uncleaned or unconfirmed part.
4. Check inventory, mail, and order tabs.
5. Reload only if the action is reversible, and preserve the original save.
6. Record the device, step, system, and version before reporting the issue.

Beginner checklist

• Complete one repair from acceptance to delivery.
• Record the device and parts used.
• Keep a cash buffer after the first payout.
• Compare an online request with an in-person order when both are available.
• Log the first meaningful dialogue choice.
• Check the current patch before repeating a bugged step.

Frequently asked questions

Should I rush the story?

No fixed route is required. Learn the repair loop, read customer dialogue, and keep short notes. That gives you a stronger base for a route-focused playthrough.

Can I keep repairing after the main story?

The official launch FAQ describes replayability through branching choices, customisation, and online requests, but does not state one universal post-story rule.