One mod · Repeatable production

Build it.
Prove it in game.

Each update follows the same small, reviewable loop. An attractive render is a starting point—not a substitute for a working asset.

  1. Choose a bounded change

    Start with player feedback or one equipment/material family. Identify what it replaces, which game behaviour must remain and what the test must prove.

  2. Approve the visual direction

    Compare concepts with the BTCMedical and copper-machinery design language. Preserve original artwork and transparency. Keep alternate treatments separate from the approved standard look.

  3. Build the game-ready asset

    Prepare sprites, atlases, models or interface layers. Check scale, pivots, layering and configuration. Preserve native identifiers and mechanics where appropriate; use unique identifiers for genuinely new items.

  4. Test in a disposable setup

    Check loading, appearance, interaction, collisions, animation, player and bot access, and save/reload. Code and file validation do not count as gameplay approval.

  5. Package and review the beta

    Declare dependencies and supported modes, inspect logs, preserve the last good package, and verify the archive. Remove private paths and unnecessary metadata from publication copies. Publish only the approved selection.

  6. Listen and repeat

    Use bug reports and requests to choose the next small update. Reproduce failures, fix regressions and defer content that has not passed its checks.

The next acceptance gates.

Current private trial

Wall cladding

Editor loading and appearance have been seen. Still check mounting, wrench removal, carrying, hatch and ladder clearance, store availability and save/reload. Cosmetic cladding must not replace pressure hulls.

Keep the beta stable

BTCMedical & UI

Retest patient switching, injury colours, tooltips and native treatment access across supported contexts. Check close/reopen, display scaling and dependency setup.

Optional branches stay optional.

Water Reaver art is part of this same project’s wider direction, not a required second pack for the current beta. Live NPC conversations remain at the very back of the schedule and require a separate trial for usefulness, reliability, privacy and cost.

Read the gameplay checklist → · See the beta schedule