Lands the art and data for Champion, Dasher, Griffin, Jenner IIC, Marauder
and Thunderbolt. Nothing is registered in core.build, the code arrays or the
shell scripts yet, so this commit is inert at runtime: packing is manifest
driven, the editor never enumerates Content\Mechs, and deploy drops Content\*.
The one exception is textures.hint, which is not inert -- textures.build has
no explicit .tga lines and packs via texturepool=textures\textures.hint, so
these pages will be picked up by the next textures.mw4 repack.
Contents:
- 11 chassis/wreck folders (658 files), 30 skin TGAs, 15 footstep TGAs
- 6 mech portraits (800x250, 24bpp; hsh/Mechs already mixes 8/24bpp)
- generic damage dolls into hsh/hud and hsh/radar/hud
- 45 textures.hint pages, copied verbatim from the Annihilator template
(30 skin mip pages + 15 footstep pages); Dasher needed none, its
@adas* and footstep pages already exist
Our own Jenner IIC was deleted first rather than copied over. Only 2 of its
84 files shared a path with the V4H set, so a copy would have left 78 stale
j2c_* files behind.
Decisions applied:
- jump jets: LEGJUMPMOVETYPE on champion, griffin, jenner2c, thunderbolt.
Dasher and Marauder declare CanLoadJumpJets=No and are left alone.
- Champion gets its own wreck instead of borrowing Loki's.
- Renames to canonical stems: jenner_2c.* -> jenner2c.*,
champion_stroyed.* -> champion_destroyed.*,
thunderbolt_destroyed.obb -> thunderbolt_destroyed_solid.obb.
All internal references updated to match.
- jenner2c.instance page [jenner_iic1] -> [jenner2c]. Every one of the 89
shipped mechs and all five staged siblings name the page after the
chassis; this was the sole outlier.
- thunderbolt.data footstep typo thunerbolt_dirt -> thunderbolt_dirt.
Verified: 1217/1217 file references resolve, 273 text files are pure ASCII
with consistent CRLF (the staged .data files arrived with an LF-only
Shadow={} block), no hint page duplicates a existing name, and all 278
binaries are stored as LFS pointers.
Still to come: Content/textures/HUD/generic.tga and hsh/MFD/generic.bmp must
be authored, then the [hud\generic] page, then the registration phase.
Co-authored-by: Claude Opus 5 (Anthropic) <noreply@anthropic.com>
Co-authored-by: GitHub Copilot <copilot@github.com>
37 lines
2.2 KiB
Plaintext
37 lines
2.2 KiB
Plaintext
STAGED - complete source set, but NOT yet added to Content/core.build.
|
|
|
|
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.
|
|
|
|
before building:
|
|
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.
|
|
3. REVIEW MOVEMENT TYPE. All six V4H chassis carry MoveTypeFlag=LEGMOVETYPE, so
|
|
none of them can jump - yet all six also carry JumpJetTonnage (2-4), four name
|
|
a real LeftJumpJetSiteName, and griffin + jenner2c have a JumpJetSubsystem
|
|
equipped in .subsystems. Our own roster is 84 LEGJUMPMOVETYPE vs 5 LEGMOVETYPE,
|
|
and those 5 have EMPTY jump-jet site names - internally consistent. V4H's are
|
|
not. This is decompiled faithfully; the inconsistency is in their source data.
|
|
Decide per chassis whether to set LEGJUMPMOVETYPE or strip the jump-jet gear.
|
|
dasher and marauder additionally have LeftJumpJetSiteName=';' - garbage.
|
|
4. Only then add the .build entries to Content/core.build, one chassis at a time.
|
|
Until that happens these files are inert - the packer never visits them.
|
|
|
|
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
|