Below, Rusted Gods Patch Notes

This page is the structured home for Below, Rusted Gods patch notes. Before July 29, 2026, there may be little retail changelog to quote—use it as a template and for demo version context.

How we will log patches

Each entry will include:

• Date and Steam build identity when available
• Player-facing summary (stability, progression, terminals, subtitles)
• Links to related wiki pages that need re-reading
• Explicit callouts if endings or controls change

Demo version context

Itch and Steam demo builds iterated through preview versions (community notes reference builds such as demo-1.x lines). Full-game patches will supersede demo numbering. If a soft-lock persists across builds, document steps using the bug report style FromSouthGames requested during playtests: build number, reproduction steps, expected vs actual, specs, and optional video.

Day-one checklist for Operators

When the first retail patch drops:

1. Read the official Steam news post.
2. Skim this page’s summary.
3. Re-verify Controls if input changes.
4. Re-test stuck points via How to Progress.
5. Update personal notes on Terminals & Radio if machines change.
6. Only then chase new Endings routes.

Related living pages

• Launch News
• Release & Demo
• System Requirements
• Operator Checklist

Current entries

Pre-launch placeholder

• No retail patch notes published yet at time of writing.
• Demo players should rely on latest Steam/itch demo builds.
• Wiki content will expand here without inventing fake changelogs.

When the Administration posts a real patch, this section becomes a dated list—not marketing filler.

Stay ready to relearn the desk. Machines change; the hole does not forgive outdated manuals.

Template for future entries

When a real patch arrives, we will add a dated heading, bullet themes (stability, progression, terminals, text), and wiki pages to re-read. We will not invent percentages or fake build numbers. Until then, this honesty section protects trust.

What players should log

Build ID, short repro, expected vs actual, system specs, and optional video. That mirrors the studio’s playtest guidance and helps everyone. Cross-check soft-locks against How to Progress before filing. Confirm inputs on Controls, machines on Terminals & Radio, layout on Operator Station, tapes on Cassettes & Lore.

Pages commonly invalidated by patches

Endings, Demo Walkthrough (if retail diverges hard), System Requirements, and anything linked from Launch News. Keep rituals on the Operator Checklist. Onboarding: Getting Started. Store facts: Release & Demo. Tone: Review. Hubs: Updates, Guides, Systems, Overview, Tools.

Stay ready to relearn the desk. Machines change; the hole does not forgive outdated manuals.

Example entry format (illustrative only)

YYYY-MM-DD — Build label if known

• Stability: crash fix summary
• Progression: soft-lock repair summary
• Terminals: radio/radar/status change summary
• Text: subtitle or localization notes
• Wiki reread: linked pages

When the first real patch matches this shape, replace the illustrative block. Until then, practice reporting with How to Progress evidence standards. Maintain play skill via Getting Started, Terminals & Radio, Controls, Operator Station, Cassettes & Lore, Demo Walkthrough, Operator Checklist. Meta pages: Launch News, Release & Demo, System Requirements, Review, Endings. Hubs: Updates, Guides, Systems, Overview, Tools.

Community mirror policy

If Steam is down, we may temporarily quote developer Discord or site posts with clear attribution of channel—not as inventing notes. We still avoid dumping unrelated patch spam from other games. When in doubt, wait. Keep playing skill sharp with Getting Started, Operator Checklist, Terminals & Radio, Controls, How to Progress, and track calendar context on Launch News plus Release & Demo.

Closing line

No retail patch text yet means we are doing our job: waiting for truth. Keep your station warm with practice pages and return here when Steam speaks.