How do I report a bug to the developers?
The studio names one reporting route in its own patch notes, and repeats one request about it: fill in the email field.
Quick Answer
Send the report through the F8 feedback form and fill out the email field. The developer names that form in both 1.0 hotfix announcements and, in both, asks players to supply an email address so the studio can get back to them. Problems that already have a documented answer are covered by the developer's own Troubleshooting Guide in the game's Steam discussions.
Steps
- Check your version first. Versions 1.0.0a and 1.0.0b each closed release-week issues, so an unpatched build may be reporting an already-fixed bug.
- Note what you were doing when the problem happened, and whether it repeats.
- Open the feedback form the developer refers to as the F8 feedback form.
- Fill out the email field. The developer states this is what lets the studio reply.
- Describe the issue and send the form.
Requirements / Limits
- F8 is the developer's own naming for the form. The studio names the key in its patch notes; it does not publish a separate controls entry for it.
- The developer describes it as a feedback form. No source describes a ticket number, a public queue or a response time.
- The Official Troubleshooting Guide, written by the developer in the game's Steam discussions, is the documented route for problems that already have an answer.
- No source states what the form collects besides the email field.
Common Mistakes
- Sending the form with the email field blank. The developer asks for it twice, in two consecutive hotfix announcements, precisely because reports arrive without it.
- Reporting a bug that the next hotfix already fixed. The decontamination-zone lock and the 'SELECT AREA' interface lock were both closed in 1.0.0a.
- Using the form for a question the Troubleshooting Guide already answers.
- Reporting through a third-party site and assuming the developer reads it.
Sources Checked
- Developer changelog · accessed 23 August 2026Yet Another Update 1.0.0b (Hotfix)
Developer hotfix, 21 August 2026, the latest public patch, re-read in full on 23 August 2026 for the Display-tab cursor toggle, the interface framerate limit and the mission objective tuning.
- Developer changelog · accessed 23 August 2026Yet Another Update 1.0.0a (Hotfix)
Developer hotfix, 20 August 2026, read in full on 23 August 2026 for the decontamination-zone lock fix and the F8 feedback-form request.
- Developer guide · accessed 23 August 2026Official Troubleshooting Guide
Developer-authored guide in the game's own Steam discussions, rechecked on 23 August 2026. Used here as the documented self-service route that sits alongside the feedback form.