fix(reverse): trace active injected ball states
The tracer could only rediscover the game object while all original position copies agreed, which is normally true at the waiting launcher but not during an active controlled probe. Accept the injector-reported object base explicitly so one process can be sampled through an entire sequence of collision tests. Test Plan: - `ruff check original/tools/trace_original_state.py original/tools/inject_original_state.py` -- passed - active live trace with `--object-base 0xadc2b0` -- passed - `git diff --cached --check` -- passed
This commit is contained in:
@@ -104,7 +104,8 @@ original/tools/inject_original_state.py --x 289 --y 94 --vx 0 --vy 0
|
||||
The executable image remains unchanged; only the current disposable Wine
|
||||
process is modified. Run the injector while the ball is waiting in the launcher
|
||||
so it can identify the live game object, or supply the previously reported
|
||||
`--object-base` during a sequence of probes.
|
||||
`--object-base` to both the injector and tracer during a sequence of active
|
||||
probes.
|
||||
|
||||
A probe at `(289,94)` captured the original terminal-18 path. The collision
|
||||
suspended the ball while frames advanced from 10 through 18 at the configured
|
||||
|
||||
Reference in New Issue
Block a user