Skip to content

Releases

v1.4.1 - RimWorld 1.7 Waylith save support

Choose a tag to compare

@Booyaka101 Booyaka101 released this 13 Oct 06:39

RimWorld 1.7 (Waylith) save support.

  • 1.7 saves scan natively, pinned by two real fixtures from the 1.7 unstable install (build 1.7.4976): a brand-new colony saved in 1.7, and a real 1.6 save loaded into 1.7 and re-saved there.
  • Measured on those fixtures: 1.7 writes structurally identical save XML to 1.6 at every depth. No format changes to map.
  • Any structural block a future 1.7 build adds outside the vocabulary measured on real saves back to 1.3 is surfaced as "new in 1.7 - not yet mapped" with its element name and byte weight, never silently dropped. Saves from 1.6 and older report byte-for-byte identically to 1.3.0 (verified, not assumed).
  • Install discovery accepts the Waylith exe name (RimWorld.exe), so mod attribution keeps working on 1.7 installs.

The exe below needs nothing else installed. Full changelog: https://github.com/Booyaka101/rimsave-xray/blob/main/CHANGELOG.md

rimsavexray 1.3.0

Choose a tag to compare

@Booyaka101 Booyaka101 released this 11 Oct 23:19

First release.

See inside your RimWorld save: a read-only Windows tool that takes one .rws
or .rws.gz save and reports where every byte went and what is eating your
ticks, per section, per map, per def, per mod and per component Class, with
a ranked fix list.

  • Terminal summary plus a self-contained HTML report (no scripts, no
    external assets) with the Top 25 defs by bytes and the mod that owns
    each, byte bars per section and per map, and the world pawn breakdown
    by faction.
  • Def-to-mod attribution from the save's own load order: installed mods'
    Defs and Patches files are read for the defNames they define, last
    writer in load order wins, official content groups as Vanilla.
  • Component measurement: game, world and map components count by Class
    with exact byte spans, plus a rule that fires when one component holds
    over 3% of the save.
  • Seven rules, every message printing the counted number it fired on:
    world pawns over 800, floor items over 20000, filth over 5000, apparel
    on dead pawns over 2000, a mod over 15% of bytes, a component over 3%,
    file over 150 MB.
  • Read-only proof: SHA-256 of the input printed before and after every
    run into the report.
  • --json emitting the same numbers as the HTML; --out, --game, --list,
    --open; double-click mode that asks which save to scan and waits for
    Enter before closing.
  • A 400 MB synthetic save parses well under a minute at under 50 MB of
    memory; a test proves it, and the full suite runs on Windows and Linux
    in CI.
  • examples/save-drift-check.py compares two saves of one colony (drift
    per section and per mod, biggest movers, a growth budget with exit 2),
    usable as a gate while developing your own mods.

The exe is unsigned: SmartScreen may warn the first time ("More info",
then "Run anyway"). The pip install avoids that.