Skip to content

battle_test: recorded walk by default, slow menu walk off unless asked for - #74

Merged
schindlershadow merged 1 commit into
mainfrom
fast-harness-default
Nov 16, 2026
Merged

schindlershadow merged 1 commit into
mainfrom
fast-harness-default

Conversation

@schindlershadow

Copy link
Copy Markdown
Owner

battle_test.py run, compare, actions and scan now reach the fight with the recorded pad walk (--direct, ~30 s) by default. The picture-by-picture menu walk (~100 s) raises unless --menu-walk / BT_MENU_WALK=1 is given (recording a walk for another character or stage, a runtime without direct_battle.cpp, tools with no --direct yet). Also fixes run --shots with no --script: the test driver only runs with a script, so the fight's start was never seen; such runs now get an idle script.

Tested on the desktop: a plain battle_test.py run --shots 2 reaches the fight in 29 s and saves its screenshot.

Release notes

  • none

🤖 Generated with Claude Code

…d for

run, compare, actions and scan now replay the recorded walk (--direct,
tests/replays/quick_battle_walk.txt, ~30 s to the fight) unless --menu-walk
is given. walk_menus (~100 s, picture by picture) raises unless
BT_MENU_WALK=1, so deck_battle.py, combo_timing.py and android_battle.py
without --direct say why instead of taking the slow path. A --stage other
than 12 with the default walk prints a note.

Also: a run with --shots and no --script never saw the fight start (the
runtime's test driver only runs with PSPRECOMP_TEST_SCRIPT set, so
"[TEST] battle started" was never logged); it now gets an empty script.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@schindlershadow
schindlershadow merged commit 1372b44 into main Nov 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant