7cd1d51e08
Saved mechlab variants reference their chassis by the .instance PAGE name, so
renaming [jenner_iic1] to [jenner2c] orphaned V4H's three Jenner variants
(Jenner2c 1, Jenner2c 4, Jenner2c Pharaoh). Each stores 'jenner_iic1' in its
{Mech} blob and carries a jenner_iic1{Subsystem} entry.
I renamed it in a67d1c00 for consistency, calling it the sole outlier among 89
chassis. It was not an outlier, it was load-bearing, and the earlier V4H notes
compounded the error by recording those three variants as "broken/orphaned --
chassis jenner_iic1 does not exist even in V4H". It does: it is this page.
Evidence the binding is the page name and not the folder or filename:
Content/Mechs/Blackhawk declares [nova] and its nine Black Hawk variants all
reference 'nova'. Matching is case-insensitive -- [Loki] is referenced as
'loki', [Ryoken] as 'ryoken' -- but the name itself must match. Checking every
offset in the 344-byte {Mech} blob found no position holding the positional
MechID for all 59 sampled chassis, so variants store no index at all and the
alphabetical renumbering from adding six chassis cannot disturb them.
The filename renames jenner_2c.* -> jenner2c.* are kept; nothing references
those. The champion_stroyed and thunderbolt_destroyed.obb renames are also
unaffected, being reachable only from their own .data. The other five new
chassis already declare the page names their variants expect.
Co-authored-by: Claude Opus 5 (Anthropic) <noreply@anthropic.com>
Co-authored-by: GitHub Copilot <copilot@github.com>
16 lines
318 B
Plaintext
16 lines
318 B
Plaintext
[jenner_iic1]
|
|
Model=jenner2c.data
|
|
ExecutionState=NeverExecuteState
|
|
Armature=jenner2c.contents
|
|
Subsystems=jenner2c.subsystems
|
|
DamageObjects=jenner2c.damage
|
|
Alignment=Player
|
|
CurrentHeat=0
|
|
CurrentCoolant=75
|
|
MaxCoolant=75
|
|
DoesHaveInstanceName=yes
|
|
PowerRating=30
|
|
ArmorRating=30
|
|
SpeedRating=29
|
|
HeatRating=100
|