A human says something is missing on the title. Something is: it plays BGM,
and two different cues.
Method with the control built in rather than bolted on. R4 wants a negative
to show the method finding the menu's cue first; this method cannot produce
a false negative for one screen because it does not look at one screen. It
finds every call of the play function in the image and reads the cue each
passes: 34 callers, cue ids 1103 x24, 1102 x3, 1107 x2, 1108, 1106, 1104,
category 4 on every one. 1103 is the cue the corpus already attributes to
the menu, and the method finds it 24 times.
GamePart_Title's neighbourhood is 0x821C4xxx-0x821C7xxx per the registry
page, and seven play sites fall inside it: 1103 at 0x821C52D0, 0x821C5620
(inside the phase handler sub_821C5580), 0x821C6188 and 0x821C6294; 1102 at
0x821C53B0, 0x821C5BA0 and 0x821C6DE0.
So the title plays BGM_103 and BGM_102, and 1103 is the SAME cue as the
menu's -- which is why a port playing nothing on the title sounds like
something is missing rather than merely quieter.
The sting is NOT answered and the page says exactly why: this play function
carries ids in the 1102-1108 BGM range, the UI stings are SE_* cues with
ids 1-322, and not one of the 34 sites passes an id in that range. SE goes
through a different call and this method is blind to it by construction.
That is a bounded negative about the instrument, not the game, and reading
it as "no sting" would be the third time this corpus mistook a blind spot
for a fact.
Reach: exhaustive over every bl to 0x8217ACF8, so complete for that
function. The GamePart attribution is by address neighbourhood and carries
the registry page's own "by position and convention, not proven" caveat.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jc4pciRArGHfxGGhEbwp5t
f3d77d5fbf