Below, Rusted Gods Bug Report Guide
File reports like an Operator log—not a rage post.
Launch week generates noise: soft-locks that are missed radio lines, performance issues mistaken for puzzle gates, and real crashes that need developer eyes. FromSouthGames (Ari Galiano and Alexis Salomon) refined playtest reporting during closed Discord tests before the July 29, 2026 Steam unlock. This page translates that culture into a repeatable bug report template for retail Operators. It does not publish Discord invite codes—use official entry paths on Discord & Community. Always self-triage narrative stalls on How to Progress When Stuck before calling a story gate a bug.
Bug versus puzzle gate (report only real bugs)
| Signal | Likely puzzle gate | Likely bug |
|---|---|---|
| Last radio line mentioned look/check/walk | Yes | Rare |
| Instruments idle after full desk loop | Often missed verb | Sometimes desync |
| Issue survives reload + repro steps | Uncommon for gates | More likely bug |
| Crash, black screen, missing UI | No | Yes |
| Wrong language after Steam language change | User fix (restart) | Report if persists |
When unsure, run the recovery flow on How to Progress When Stuck—especially vitals-then-bathroom beats on Life Support & Squad and Facility Exploration. Instrument disagreement may be authored—see Anomalies & Events—unless it repeats identically across saves.
The FromSouthGames playtest report format
Closed playtests asked for Operator-grade reports. Mirror this structure in Steam discussions, official Discord (when linked from primary sources), or email/contact paths listed on the store:
1. Build number / version identity
Steam displays build or update identity in library properties or news posts. Demo and retail numbering differ—state which binary (demo app 3243360 versus full game 2895680). Demo community notes reference demo-1.x style lines; retail will use its own sequence. Patch Notes tracks official build themes after unlock.
2. Platform and specs
- OS (Windows version; Deck mode if handheld)
- CPU / GPU / RAM (summary is enough)
- Display (resolution, ultrawide, scaling)
- Input device (keyboard/mouse, controller model)
- Language setting in Steam and in-game—Supported Languages
Compare against System Requirements and Steam Deck Verified before reporting “won’t run.”
3. Reproduction steps
Numbered, boring, reproducible:
- Fresh load or specific save slot
- Last completed story beat (room, last radio line if remembered)
- Exact actions in order (instruments used, doors taken)
- Where it fails (desk, bathroom, peephole, menu)
Mention headphone use—audio bugs are often environmental (Headphones & Audio).
4. Expected versus actual
One paragraph each:
- Expected: what should happen per cues, checklist, or prior playthrough phase (Demo Walkthrough as analogy only in retail).
- Actual: what happened instead (idle prompt, crash, wrong subtitle, soft-lock).
Avoid sarcasm. Administration fiction is for Steam news, not bug threads.
5. Screenshots or short video
Visual proof helps for UI clipping, missing prompts, and translation errors. Keep videos short and spoiler-marked if showing late-game facility. Do not upload fake edited footage.
6. Save situation (if relevant)
Note whether the issue appears on new game, continued save, or after language toggle restart. Mention if Accessibility & Comfort or Graphics & Settings toggles were changed mid-session.
Where to post (official channels only)
This wiki does not invent invite codes.
| Channel | Best for |
|---|---|
| Steam Discussions (app 2895680) | Launch-week visibility, reproducible threads |
| Developer Discord | When Steam news or belowrustedgods.com links an active invite—Discord & Community |
| Official site contact | Long-form issues, business inquiries |
| Steam news replies | Usually not support; prefer discussions |
Upvote duplicate threads with good repro steps; do not spam the same report across five channels.
Common launch-week report categories
Expect these themes after July 29, 2026 unlock—Patch Notes will summarize official fixes:
- Startup / crash on boot — include specs and GPU driver date
- Progression soft-lock — only after How to Progress exhausted
- Subtitle / localization — dev materials noted translation fixes for full release; still report wrong strings with language set
- Controller / bind failures — cross-check Controls
- Comfort toggles missing — reference playtest asks on Accessibility & Comfort, not invented menu names
- Deck-specific — note Verified status and handheld resolution
What makes a bad report
- “Game broken” without steps
- No build ID
- Demo issue filed against retail expectations without labeling binary
- Spoiler dumps without tags
- Demands for Discord codes from wiki copypasta
- Reporting authored instrument disagreement as desync without repro—Anomalies & Events
Good report example (template)
Build: [Steam build ID or news date]
Platform: Windows 11 / RTX 3060 / 16GB RAM / 1440p
Input: Xbox controller + headphones
Language: EN UI, EN audio
Repro:
1. New game, complete vitals check on medical console
2. Status → radar → radio cycle complete
3. Walk to bathroom corridor as prompted
4. Interact prompt never appears on [object]
Expected: Interact prompt after audio line [paraphrase]
Actual: No prompt; soft-lock after reload
Video: [link, spoiler tagged if needed]
Save: slot 1, ~15 minutesAdapt; do not treat the template as lore.
After you file
- Watch Patch Notes and Launch News for hotfixes.
- Re-test on new build before commenting “still broken.”
- Help others by linking wiki recovery pages as helpers, not as official support.
- Continue playing with Operator Checklist discipline.
Launch eve note (Jul 28, 2026)
Retail unlock is roughly twenty-two hours away. Steam shows no user reviews yet; the first bug threads will appear minutes after unlock. Prepare this template tonight so launch morning stays calm—pair with Day-One Checklist.
Related pages
- Discord & Community — official links, no fake invites
- Patch Notes — verified fix summaries
- How to Progress When Stuck — puzzle gate triage
- Accessibility & Comfort — missing comfort toggles
- Graphics & Settings — visual QoL verification
Good reports get fixes. Bad reports get ignored.
Hubs
Tools, Updates, Guides, Systems, Overview. Store: Release & Demo. Specs: System Requirements. Tone: Review.
Frequently Asked Questions
Quick answers for operators preparing for the descent.
Where is the Discord invite for bug reports?
This wiki does not host codes. Use Steam news links or belowrustedgods.com when invites are public—see [Discord & Community](/tools/discord-and-community/).
Should I report a soft-lock immediately?
Run [How to Progress When Stuck](/guides/how-to-progress/) first. File only if repro steps persist across reload with build ID included.
What build info does Steam show?
Check library properties, news posts, or in-game about screens after unlock. Label demo versus retail app IDs.
Do I need video?
Optional but helpful for UI and progression bugs. Keep clips short and spoiler-tag late-game content.
Will the wiki forward my bug?
No. We document procedure only. Post to official Steam discussions or developer-linked Discord yourself.