Find the next useful check.
Choose what you can observe. The assistant helps narrow a test; it does not promise an automatic fix or access your game.
Every outcome, without the wizard.
The same recommendations are readable below. They combine official feature notes, labeled player reports and suggested diagnostic steps. No undocumented game values are assumed.
Start upstream, not at the last machine.
Test a small transfer into the first affected section. Check collection, accepted material and the route into that section. An empty input is not evidence that the receiving machine is broken. Read the full guide →
Suggested diagnostic check
Check the network’s state before adding equipment.
Inspect power warnings and supply. The V8 announcement documents E at a pole as a network shutdown interaction, so check the live state rather than repeatedly toggling it. Verify current controls in your build. Read the full guide →
Dated V8 note + suggested check
Clear the downstream question first.
Observe the receiving stage, its accepted input and its exit. Record whether the queue is growing. Test one short route before changing the rest of your factory. Read the full guide →
Suggested diagnostic check
Test one connection in isolation.
Inspect direction, endpoints and the receiving machine’s input. Compare the placement guides from a second viewing position. Document the original layout so the test stays reversible. Read the full guide →
Suggested diagnostic check
Trace material through the search stage.
Check the scanner description, accepted material, operating state and any route that bypasses it. We do not supply an undocumented detection range or promise that one layout catches every needle. Read the full guide →
Suggested diagnostic check
Protect your save before investigating.
Close the game, identify the current build’s actual save files and copy them to a separate location. Do not erase AppData or start a new run as a first diagnostic step. The exact save folder is not verified here. Read the full guide →
Backup-first precaution
Record the unresolved state, not a guessed fix.
Capture the hay counter, needle counter, scanner layout and mod status. Compare current developer notes and the linked 5/6 report. Do not assume a universal needle count, a fixed hidden location or guaranteed recovery after reload. Read the full guide →
Player report; cause unresolved
Isolate the graphics change without losing progress.
Preserve save data, record the setting that changed and consult current developer instructions before editing configuration files. No unverified renderer launch flags are recommended here. Read the full guide →
Player report + cautious diagnostic plan
Compare the game and mod versions.
Back up the host’s world. Check the mod author’s current installation and compatibility notes for every player. Do not replace files with an archive from an unrelated mirror. Read the full guide →
Mod author + suggested check
Check the publisher’s hardware baseline.
The reviewed demo requirements call for a dedicated GPU with Vulkan 1.3 support and warn against integrated graphics. Compare your hardware, then preserve saves before verifying files or changing configuration. Read the full guide →
Official demo requirements
Measure completed sales before expanding.
Time a stable interval without purchases or unrelated income. Record cash gained, elapsed time and blocked or idle stages. Repeat after changing just one part of the line. Read the full guide →
Suggested measurement method
Compare incremental income with the upgrade cost.
Enter the cost, previous net income per minute and new net income per minute in the payback calculator. A non-improving route has no finite payback under this model. Read the full guide →
Arithmetic model, not a game benchmark