Report a Breathedge 2 Bug: Steps, Saves and Report Template

How do you send a Breathedge 2 bug report?

The developer’s launch instructions give this route:

1. Open the pause menu with Esc.
2. Select Report Bug.
3. Describe the problem and the steps that caused it.
4. Use the save-attachment option in that window when the current save reproduces the issue.
5. Add contact information if you want the developer to be able to ask follow-up questions, then submit.

Save attachment and contact details are optional. For a story-state problem, a save from before the failing interaction is often more useful than a screenshot of the final symptom.

What should you check before sending the report?

Compare the installed version with the official patch tracker. A useful report says whether the problem remains after the relevant update.

Then separate an unmet objective from a failed objective. Note the exact journal wording and counter. If the issue concerns an ingredient, record the repair panel. If it concerns a controller, include the device and connection type from the input troubleshooting guide.

What can you paste into the description?

Fill only the fields you can actually observe; leave uncertain details labelled unknown.

Game version/build:
Platform and Windows version:
Problem location or exact quest:
Expected result:
Actual result:

Steps to reproduce:
1.
2.
3.

Does it happen every time, sometimes, or once?
Does another save show the same problem?
Last action before the failure:
Controller / keyboard layout (if relevant):
Resolution and hardware (if relevant):
Screenshot or affected save attached:

For example, describe “after attaching this part, the journal still shows this counter” rather than “the quest is broken.” The first form gives the developer a testable transition.

What if the game cannot open the report window?

The developer lists info@breathedge.com in the launch post and asks players with unresolved broken-save cases to contact it in 0.8.7. This is the developer’s address, not a support inbox run by this wiki.

Describe where loading stops and whether the problem affects one save or every save. Keep the affected file available for follow-up. This guide does not prescribe a save-folder path or tell you to replace files manually without a verified recovery procedure.

Which details matter for crashes and performance?

Include CPU, GPU, RAM and the official requirement comparison, plus the location, settings and action associated with the failure. “Stutters whenever this door opens” is more actionable than an overall description of poor performance.

For a public discussion post, share reproduction details while keeping personal contact information and private attachments out of the public text. Use the report tool or published developer contact for follow-up material.

Reviewed September 7, 2026. Reporting routes are official; the template and diagnostic ordering are editorial suggestions.