42fe0a7b6a
These are the per-chassis completeness trackers, and they still described the
pre-install state: header said STAGED, jenner2c listed jenner_2c.* filenames
that no longer exist, and every one carried the "REVIEW MOVEMENT TYPE" item
that has since been decided.
Each file now has three sections. "installed" lists exactly what landed for
that chassis and what is shared with the other five. "applied" records the
data decisions and, for dasher and marauder, records that nothing was changed
and why - a deliberate no-change is a result worth tracking, not an omission.
"still to do" keeps the registration steps, renumbered without the settled
movement-type item, and adds a final step to delete the STATUS file once the
chassis is registered.
Per-chassis notes worth having written down:
- dasher is the only one that added zero textures.hint pages; it reuses the
existing @adas0-5 skins, footsteps and the Dasher_destroyed wreck.
- dasher and marauder keep LeftJumpJetSiteName=';' as decompiled, where our
own five LEGMOVETYPE chassis leave it empty. Inert while CanLoadJumpJets
is No, and recorded as a residual rather than quietly edited.
- jenner2c is the only one of the six with its own animscript; the other
five borrow dragon, hauptmann or loki.
- jenner2c's decision block now records that our copy was deleted rather
than overwritten, and why.
STATUS files are LF-only and stay that way; they are notes, not engine input.
Co-authored-by: Claude Opus 5 (Anthropic) <noreply@anthropic.com>
Co-authored-by: GitHub Copilot <copilot@github.com>
53 lines
3.0 KiB
Plaintext
53 lines
3.0 KiB
Plaintext
INSTALLED - assets are in the repo. NOT yet added to Content/core.build, so
|
|
the chassis is still inert at runtime.
|
|
|
|
have: .erf / .mw4anim / .obb source
|
|
thunderbolt.armature thunderbolt.contents thunderbolt.instance
|
|
thunderbolt.subsystems thunderbolt.data thunderbolt.damage
|
|
thunderbolt.torso thunderbolt.engine
|
|
|
|
All eight decompiled from the V4H package and verified by round-tripping
|
|
the same decompiler over our own 64 chassis:
|
|
.data 8291/8306 keys .damage 6605/6605 keys
|
|
.contents 7480/7480 keys .instance 896/896 keys
|
|
.torso/.engine 1279/1280 keys .armature/.subsystems see sections 5, 8
|
|
Every internal reference here resolves to a file that is present.
|
|
|
|
installed (2026-08-09, commits a67d1c00 + 8e859007): chassis folder, wreck
|
|
folder thunderbolt_destroyed, skins @athu0-5, FootSteps/thunderbolt_*,
|
|
the 9 matching textures.hint pages (6 skin + 3 footstep, copied
|
|
verbatim from the Annihilator template) and portrait
|
|
hsh/Mechs/thunderbolt.bmp.
|
|
Shared by all six chassis: generic damage dolls hsh/hud/generic.bmp
|
|
and hsh/radar/hud/generic.bmp (supplied by V4H), plus cockpit doll
|
|
Content/textures/HUD/generic.tga, target-MFD tile hsh/MFD/generic.bmp
|
|
and the [hud\generic] page (authored here).
|
|
All 1217 file references across the six chassis resolve.
|
|
|
|
applied: MoveTypeFlag LEGMOVETYPE -> LEGJUMPMOVETYPE. CanLoadJumpJets=Yes,
|
|
JumpJetTonnage=4 and both jump-jet site names are real, so the
|
|
LEGMOVETYPE it was decompiled with was the inconsistent value.
|
|
FootStepTexture typo footsteps\thunerbolt_dirt -> thunderbolt_dirt.
|
|
This was the only unresolved reference of the 1217 checked.
|
|
Wreck geometry renamed thunderbolt_destroyed.obb ->
|
|
thunderbolt_destroyed_solid.obb to match the _solid convention the
|
|
other four wrecks use, with the SolidOBB key updated.
|
|
|
|
still to do:
|
|
1. Add $(M_Thunderbolt) to Content/ShellScripts/MechLabHeaders.h and $(IDS_Thunderbolt) to
|
|
Content/Defines/MissionLang.defines. The .data references both. V4H's packages
|
|
store mech ids from an OLDER roster (shifted against ours), so the stored
|
|
integer was deliberately discarded - see DECOMPILING.md section 8c.
|
|
2. Register the chassis through the rest of the chain in ADDING-A-MECH.md.
|
|
The code arrays grow 65 -> 71 and LastMechID 64 -> 70; the shell-script
|
|
arrays are currently sized 65-67.
|
|
3. Add the .build entries to Content/core.build, one chassis at a time. Until
|
|
that happens the chassis is inert - the packer never visits these files.
|
|
4. Delete this STATUS file once the chassis is registered.
|
|
|
|
notes: The .obb and .armature filenames are not stored in the package; the values
|
|
in .data / .contents were matched to the files actually present here.
|
|
Rename the file and the key together if you change either.
|
|
|
|
see: MW4COMPARE/DECOMPILING.md sections 8c-8g and 11
|