Claude (auto-RE) 0434afa6a6 re(route-b): the field map comes out of the code, and with it the Ratio family ...

The filler builds each key as addi r4, r30, -N with r30 = 0x82088f94, so every
store's field NAME is a string in the image. Pairing keys with the following stfs
gives the layout outright: Size_X/Y/Z at +48/52/56, HQRatio +88, ShieldRatio +92,
ThrusterRatio +96, resistances +116..132, Radar/FCS/FiringRange +672/676/680,
Attack/Defence points +692/696/700. verify_fieldmap.rs checks it against the live
dump: 62 fields agree with the disc, 0 disagree.

That yields the runtime value of each field for units whose record omits it --
HQRatio 0.2/1, ThrusterRatio 0.2/1, ShieldRatio 1, ResistanceToPlayer 1,
ResistanceToShell 0.1, ResistanceToExplosion 0.5, AttackVesselPoint 0.1,
AttackCraftPoint 0.1/0.5, DefencePoint 0.1/0.25, FiringRange 0, Size_Y = Size_X.
Recorded with the caveat that several show two values across units, so these are
per-unit runtime values rather than one global default.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-12 23:17:05 +00:00

..

data

fix(mesh): distinct anchor assignment -- no two resources may claim one buffer

2026-08-12 03:16:51 +00:00

examples

re(route-b): the field map comes out of the code, and with it the Ratio family

2026-08-12 23:17:05 +00:00

src

perf(mesh): memoise the whole-container decode

2026-08-12 18:57:50 +00:00

tests

re: n206 was fixed after all -- the audit was classifying by geometry, not buffer

2026-08-12 04:10:05 +00:00

Cargo.toml

feat(formats,viewer): movie subtitles, voice decode, and the movie manifest

2026-07-19 20:15:41 +02:00