The binaries and packages committed as RC2 in 8bfaf9b9 no longer match the
source tree: MW4.exe, mw4print.exe and three resource packages have all changed
since. RC2's own notes warn about exactly this situation with RC1, so this is a
version bump rather than an edit in place.
Console title -> V5.1.0b3, with a new dated line in the ConLobby.script
changelog block; the existing lines are left alone. That string lives in
props.mw4, so it only appears on a pod after the repack, which is what makes it
a usable "did this machine get the new content" check.
Release notes and checklist renamed RC2 -> RC3. The notes' front matter was
restructured rather than having a third block stacked on it: "Already testing
RC2? Here is what is new in RC3" now leads, followed by "What was new in RC2"
for anyone jumping two versions.
New in the notes, written for pod owners rather than engineers:
* Damage displays corrected on 22 'Mechs, described as the two faults an
operator would actually notice -- the figure was mirrored, and the zones did
not line up with the artwork -- plus the note that Rifleman and Battlemaster
had been using another chassis' layout entirely.
* The target picture on the MFD showed the wrong 'Mech. Includes the
gos-displays.txt line to look for, and what it means if the card refuses the
larger atlas and falls back.
* High Explosive charges now fire, how to use them (weapon group, not eject),
the NARC side effect, and the advice to refit the charge on saved variants.
* Three content faults corrected. Cauldron Born is explicitly flagged as
behaviour-unchanged so nobody hunts for a difference that is not there.
* mw4print -debug.
* A warning that this build changes artwork as well as the executable, and
upgrade step 2 now says to copy the whole folder. An old hsh\ with a new
MW4.exe gives wrong damage displays, which is the trap this build creates.
Checklist gained sections 18-22, 88 -> 133 checkboxes, all marked as never
having been run on hardware:
* 18 names every one of the 22 chassis individually for both displays, and
makes handedness an explicit check, since the mirroring is the fault that
reads as "slightly odd" rather than obviously broken. Calls out that the
Atlas MFD doll was regenerated and so replaces shipped art.
* 19 leads with targeting a Zeus, and requires flying a Behemoth II in the
RELEASE build -- that fault was fatal in Release and masked in Profile by the
placeholder texture, so testing it with MW4pro.exe proves nothing.
* 20 includes the NARC ammo-count regression check.
* 21 frames the content fixes as "confirm nothing moved".
* 22 covers mw4print -debug.
The build-requirements header was materially wrong and has been rewritten. It
named props.mw4 only; core.mw4 and textures.mw4 now change too, each must be
deleted before repacking because the packer carries stale entries forward and
never drops deleted ones, coord.cpp is #included by DXRasterizer.cpp so a
mapping change needs a full exe rebuild, and the 21 changed hsh\ dolls are
loose files that arrive only via deploy-mw4.ps1.
All three documents remain pure ASCII with CRLF endings so they open correctly
in Notepad on a pod; the HTML was checked for balanced tags.
Nothing here covers the six staged V4H chassis. They are not in the source tree.
Co-authored-by: Claude Opus 5 (Anthropic) <noreply@anthropic.com>
Co-authored-by: GitHub Copilot <copilot@github.com>
1684c3fbd2
