Mark ISSUES #159 done (2de5a011) and record the key finding for #170: the
CombatAnimationPlanner numbering fix is latent (the planner isn't wired into
the live dispatch) and the Mite Scamp's 0x62-0x64 attacks were always in the
correct block — so #170's visible symptom is sub-bug 2 (the pending_motions
MOTIONDONE loop), not command misclassification. Roadmap L.1b note updated.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
2de5a011b4
commit
5eb902ffe7
2 changed files with 14 additions and 5 deletions
|
|
@ -616,7 +616,9 @@ change must keep both phase plans in sync.
|
|||
`AceModernCommandCatalog` runtime default + full-extraction
|
||||
`Retail2013CommandCatalog` conformance; deleted the blind 0x016E–0x0197
|
||||
override; exposed + filed the `CombatAnimationPlanner` 2013-numbering bug
|
||||
as ISSUES #159. Spec: `docs/superpowers/specs/2026-06-30-movement-wire-parity-design.md`.)*
|
||||
as ISSUES #159 — **fixed 2026-07-04 `2de5a011`**, the constants now derive
|
||||
directly from `DatReaderWriter.Enums.MotionCommand` by name.
|
||||
Spec: `docs/superpowers/specs/2026-06-30-movement-wire-parity-design.md`.)*
|
||||
*(D6.2a, shipped 2026-07-01:* ported `CMotionInterp::adjust_motion` /
|
||||
`apply_run_to_command` / `apply_raw_movement` into `MotionInterpreter` and
|
||||
unified the local velocity + keyboard turn + jump onto one input-built
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue