Progression

Scrap & Progression:
What Carries Between Runs

Separate temporary raid power from permanent RIG progress, and use Scrap without confusing run upgrades with long-term customization.

Steam release · coverage checked on the demo v81 release-parity buildOfficial + release-parity demoUpdated September 15, 2026
DIRECT ANSWERThink in two layers: raid power helps the current run, while permanent parts and garage progression shape future RIGs. Scrap belongs to the long-term side of that loop. Before spending, decide whether the purchase improves a build you can field now or merely chases a stat you do not yet understand.

Two economies are happening at once

RIG Riot mixes a temporary roguelike run with permanent garage growth. During a raid, you build immediate power through weapons, augments and Volatile Mods. Between raids, permanent parts and meta progression change what you can bring next time.

THIS RUN

Temporary power

Weapon upgrades, augments, Volatile Mods and situational run choices.

FUTURE RUNS

Permanent power

RIG parts, garage configuration and progression purchases that shape later loadouts.

What Scrap is for

Current tutorial footage identifies Scrap as a main progression currency and shows it tied to settlement/garage upgrades and part-mod capacity. The September 8 official patch also changed scrapping parts to reward Scrap instead of SCM, a useful reminder that old videos can use outdated currency behavior.

A safer spending order

  1. Fix access first. Unlock or improve systems that expand the builds you can actually field.
  2. Fund a real archetype. Spend around a RIG you already understand rather than an imagined endgame build.
  3. Protect flexibility. Load, energy and weapon capacity often matter because they let several future parts remain usable.
  4. Delay luxury optimization. Do not sink permanent resources into a narrow interaction until the live version proves you want it.

Version warning for old guides

The demo moved to release-build parity on September 8, 2026, and the developer explicitly noted that years of intervening changes were pulled forward at once. If a guide treats SCM, objective counts or old menu behavior as current without a date, verify it in the current build.