Files
Neutron/docs/gameplay/baseball-targets.md

100 lines
5.8 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# VR07 moving targets and Baseball contacts
2026-11-02. Static recovery and source projections; original whole-game execution
has not been observed. Original EXE SHA256 is
`f5281076e1a2492f2d61f87aae3f4544b6d0f535ebe33f9fbb6f78710fe1aea8`.
`tools/binary/baseball_targets.py` guards the reviewed spans, virtual bindings,
factory and false registration filter. It reports PE-mapped offsets. All code
addresses below have file offset VA−400000 in this executable.
## Evidence and identity
The generated EXE copy was inspected with local REA/Ghidra12.1.4, profile digest
`e1ad533d4cc0333c2136fe0894217de2d61feea098240326e78633f9e4ddcbf9`.
Complete Evidence and a closed snapshot are retained in
`artifacts/baseball-targets/rea-local-ipc/`:
| Procedure | Evidence |
| --- | --- |
|430220 moving-target construction|ev_3e420d49b2d4d524b6a80f3aebddef7d54863186d417cfc3b48d0f2a20b0fa29|
|430570 Baseball contact|ev_3a2778c478e072e201b1e3baaf87434837fd570a00b5ee84022491175c00c7c4|
|441AC0 sprite PostLoad|ev_236e87925819c8924f5becb9a72da56152655b79d0527a2d81bdef32c912917f|
|4573F0 VR07 construction|ev_11fddbe40ea4b959e27cba000aa4557cb04b2d4d104b11f155feedf88a97f04c|
4306B0 and475CD0 were not recognized procedures and the provider's numeric
fallback interpreted them as unmapped file offsets. Their behavior is supported
by guarded disassembly, not attributed to pseudocode. The initial restricted
attempt failed at the Ghidra local socket; its owned batch was interrupted and
has no close/snapshot artifact. The later successful session explicitly closed
and exported its snapshot. Permitted local IPC resolved that host restriction. No client configuration
or original bytes changed. REA inspection is static, not target execution.
3TAR's actual factory45CA06 constructs430220, complete table4A8E74, game interface
complete+C8/table4A8A10. Do not confuse it with Jimmy's C3DTarget aim helper or the
different4453B0 class also registering3TAR. Actual runtime type is C3DMOVINGTARGET.
VR07 constructor4573F0 binds complete game4CFAE0; slot134→475CD0 returns false
(`32c0c21800`), permitting the previously recovered NC/checkpoint registration
filters. VR07 has134 serialized triangles and no special Jimmy wall materials.
Textureless triangles remain collision candidates even though rendering skips them.
## State and interaction
| Complete field | Meaning / writer |
| --- | --- |
|57C/580/584|Sprite size/index/database; defaults100/98/sprites.omt; GAM overrides150/135/sprites.omt|
|5EC..5F8|Start XYZ/W, W initialized1|
|5FC..608|Destination XYZ/W, W initialized1|
|60C|Speed, default100|
|610|Respawn timer, initialized0|
|614|ActivateObject name|
|678/67C/680|HitsRequired(default5), NumPoints(default10), RespawnTime(default15)|
Source radius75 is set at430485. World response and support are disabled by
430478/430480; integration is enabled430495. Frame game3C4→4306B0 first invokes
463090, then updates orientation, respawn and velocity. Positive respawn subtracts
dt with a float store; <=0 clamps0 and unhides. Hidden targets keep moving.
The vector to Destination is quick-normalized and multiplied by Speed. Ordinary
sqrt distance<100 then teleports to Start through314. Endpoints are not swapped;
the just-published velocity survives the teleport into the next integration phase.
Zero-length normalization is explicitly bounded to zero in the modern port.
Contact game40→430570 first calls470A90, then accepts C3DBASEBALL only while
timer<=0. It hides the target, copies RespawnTime, and awards NumPoints through
42ADC0. It does not hide/destroy the ball. Lookup of ActivateObject returns the
first matching tagged actor. Missing parent requests SFX198. A C3DTROPHY or
C3DPICKUPITEM parent has its respective hit counter incremented; activation
occurs only when count **> HitsRequired**, then resets counter and requests199.
This strict comparison requires four qualifying contacts for VR07's value3.
Trophy interface4BE404 slot428→40E1F0 takes activation1, conditionally enables
collision via3AC when interface584 is nonzero, then unhides. It does not execute
the script trigger interpreter or restart integration. Activation0 disables
collision via3A4 and hides. The port preserves that limited visibility/contact
operation; its existing actor flags remain a narrower adapter than all source flags.
## Actual tutorial and implementation boundary
VR07 GAM SHA256 is
`1260b75d82ec794f9375ada30e186424746bc1dd4e4b0540c9b69bb7ad12d0b1`.
Six3TAR records at file offsets885,AD6,D27,F78,11C9,141C all use the same tag
C3DMOVINGTARGET. They must be stored by source instance/offset, never collapsed
by a tag dictionary. Each has speed100, score10, respawn15 and HitsRequired3.
Only record11C9 names parent `trophy`; the others name `none` and produce198.
The original visible target is the explicitly serialized sprites.omt Canv135
star,150×150.441AC0 proves that binding; RetainedSprites Canv8 `target` is separate.
SceneBaseballs separates body integration before controller from target frame
updates after controller. Pair discovery currently checks current sphere overlap
at radii15+75 and Jimmy recovery15+player radius. This is a declared modern adapter,
not recovered47A580 registry ordering, swept dynamic contacts or full enemy combat.
Static ball response uses the source body/grid/support with ball callbacks; its
angular reflection tail and full logical/render Euler lifecycle remain open.
VR07's hidden trophy has contact disabled until its source activation so the
existing pickup adapter cannot collect it while invisible.
Four Python groups cover identity/spans, duplicate source identities, hit gate,
stored respawn subtraction and strict parent threshold. Modern managed/native
results are recorded separately in baseball-implementation.md. Retained helpers
across level loads, moving target generic flags/rotation, full original cadence,
original runtime and native Windows comparison remain unresolved.