validate_strategy

Documentation

Overview

cmd/validate_strategy runs the attack Planner against a single battle screenshot without touching ADB, the live bot, or the network. It diff-prints every tap point that lands off the chosen target edge so a user can see "attacks on 2 sides in 1 corner" regressions in seconds.

Usage:

validate_strategy -screen path/to/battle.png \
                  -strategy assets/strategies/auto_edrag_rush.yaml \
                  -precision assets/precision_config.json \
                  -edge BottomLeft \
                  -out debug_attacks/run-42

Artifacts written to -out:

00_pre.png        — red zone (red box), all 4 corner lines from
                    the (overridden) precision config, and the
                    chosen deploy line (green).
phase_<n>_<name>.png — every planned tap on the phase, colored
                    green if it lands on the target edge's side,
                    red otherwise. Yellow corner lines for
                    side reference.
plan.json         — full structured PlanReport dump.
side_classification.ndjson — one line per planned tap, sortable
                    + jq-friendly for downstream analysis.

The command INTENTIONALLY does not seed rand — Duke's planned location is the chosen-edge midpoint (matches HeroManager's current behavior). If you re-introduce a Duke adjacent-corner random pick in hero_manager.go, add a -seed flag and seed rand.Intn with it.