Original editorial utility · source bounded

Repair log: make a stuck device reproducible

Do not change several parts or actions at once. Capture the current state, test one action, and write down the result so the next attempt starts with evidence.

The direct workflow

1. Take a screenshot before changing the device.
2. Write the visible symptom and current objective exactly as shown.
3. Protect the save if the job or customer state may change.
4. Test one action or component interaction.
5. Record the result, including “no visible change.”

Copy this repair record

Stop conditions

Stop and restore the protected save when the state changes irreversibly, the result cannot be attributed to one action, or the game version differs from the evidence you are following.

Last reviewed August 12, 2026 · This tool records player observations; it does not assert unverified game routes.