Clean actor runtime baseline after motion fix
Some checks failed
ci / headless-e2e (push) Has been cancelled
runtime-self-hosted / runtime-ci (push) Has been cancelled

This commit is contained in:
server
2026-04-14 19:22:49 +02:00
parent 15c10c9a6f
commit 65a8e243d3
4 changed files with 32 additions and 21 deletions

View File

@@ -165,17 +165,15 @@ It also now includes an actor/content validator:
- `scripts/validate_actor_scenarios.py`
On the current real client runtime, the full actor validator reports five data
issues that look like pre-existing content inconsistencies rather than `.m2p`
loader regressions:
The current actor validator now resolves real `MotionFileName` targets from
`.msa` files instead of assuming every motion uses a same-name local `.gr2`.
That removed the old false positives from redirected actor motions, and the
remaining `orc_lord` mismatch was fixed in the runtime assets by correcting
`30_1.msa` to point to `30_1.GR2`.
- `Monster/misterious_diseased_host` missing `25.gr2`
- `Monster/skeleton_king` missing `24.gr2`
- `Monster/thief2` missing `03_1.gr2`
- `NPC/christmas_tree` missing `wait.gr2`
- `NPC/guild_war_flag` missing `wait.gr2`
On the current real client runtime, the actor validator now passes cleanly.
The expanded validator did not find additional breakage in:
It still verifies:
- `.msm` base model references
- `.msm` effect script references
@@ -205,11 +203,11 @@ previous cross-pack and wrong-path sound references were cleaned up in the
runtime assets, and the last remaining `combo7.wav` issue was resolved by
aligning `combo_07.mss` with the byte-identical `combo_08` motion variant.
Those current actor and effect findings are also recorded in:
The current effect findings are recorded in:
- `known_issues/runtime_known_issues.json`
The current audio findings are recorded there as well.
Actor and audio are currently clean in that baseline.
That file is now the shared runtime baseline used by the validators and the
aggregated release gate.