⛏OreFactoryGuideFIELD MANUAL // UNOFFICIAL
← ALL GUIDES

How to Report an Ore Factory Squad Bug with Useful Evidence

Package the version, exact trigger, expected and observed result, role, save context, screenshots, video, and any specifically requested files.

By Ore Factory Guide Team · Updated 2026-09-11

Quick answer

Create a report that another person can reproduce: include the current game version, platform, exact trigger, expected result, observed result, solo/host/guest role, save context, and screenshots or video. Post a new Steam discussion or use the official Discord feedback channel named by the developer. Attach logs only when the current reporting instructions or a developer reply identifies what to collect; the checked official post does not publish a verified log-file path.

Collect the minimum useful evidence

Before repeating the problem, record what is already known:

  1. Current Ore Factory Squad version.
  2. Windows and hardware context relevant to the issue.
  3. Solo, co-op host, or co-op guest role.
  4. Last action that worked and the first action that failed.
  5. Expected result and exact observed result.
  6. Whether the same steps reproduce the problem after a clean restart.
  7. Screenshot or short video of the visible symptom.
  8. Any additional file explicitly requested by the current reporting instructions or a developer reply.

For a launch failure, follow the safe checks in game will not load after an update. For the narrow multiplayer trigger, use disconnect after contract completion. For a wrong save state, protect it with the save backup guide before reproducing anything.

Copy this report template

Game version:
Platform and relevant hardware:
Solo / host / guest:
Save context and last known good session:
Exact steps to reproduce:
Expected result:
Observed result and exact message:
Does it happen again after one clean restart?:
Mods, loaders, or input tools in use:
Screenshots or video attached:
Developer-requested files attached (only when identified):

Keep the steps short and chronological. Do not replace the exact error message with a guessed diagnosis.

Handle developer-requested files safely

Current developer replies sometimes ask for log files because they can help investigate the cause. The checked official post does not give a stable filesystem path. If your report receives such a request, use only the location supplied by the current official instructions or the developer responding to your case; do not copy a path from another game.

Before posting publicly, review filenames, screenshots, and text for account names, local usernames, invite codes, or other private information. Keep a copy of the original evidence and avoid editing the affected save while the report is unresolved.

Where to send the report

The developer's pinned instructions accept a new Steam discussion and recommend the official Discord feedback channel when you want a faster evidence exchange. Use one primary report, then link to it if you provide follow-up material. A complete packet can help investigation, but it does not guarantee a reply, diagnosis, or fix.

Start at Troubleshooting when you have not yet isolated the symptom. Check the updates and roadmap tracker before filing again in case a later patch explicitly addresses it.

Sources