A useful Low-Budget Repairs report identifies the installed build, mission, exact objective, last successful action and first failing action. Separate what you observed from what you think caused it, and preserve the failing save rather than erasing the evidence.
Choose the failure boundary
For a save/load problem, compare the same target immediately before saving and after loading. For a travel problem, record departure and destination. For a tool problem, note the preceding tape-measure or leveler interaction if there was one. These boundaries match different official issue records and prevent a report about one symptom being mistaken for another.
Copy this report outline
Record: installed build; selected language; mission name exactly as displayed; objective text; save type and timing; numbered reproduction actions; expected result; actual result; whether the issue repeats. Include relevant screenshots of the target and Work Plans. Do not fill unknown fields with guesses.
Attach evidence safely
Use the game's Steam discussion area or another support channel explicitly linked by the developer. Remove personal desktop content from screenshots. Do not post Steam credentials, account tokens or a whole unrelated documents folder. Keep the original save unchanged; provide a copy only through an appropriate channel.
Retesting an announced fix
The latest reviewed announcement is Update 6. Check your installed update before claiming a regression. Describe whether the issue survives in the same old save, a known-good earlier state or a new attempt; these are different results. No reply time or successful recovery is promised.
Your checklist
0 / 5Saved on this browser only. No Steam connection.
Sources & build scope
Full release · official patch notes; not a local gameplay retest. Source review is separate from a gameplay test.
- Gray2RGB: official announcements ↗Tier A · Launch through Update 6