Scenario Runner Capture

Implement deterministic Scenario Runner + capture outputs for agents

majiayu000 c602407 2 files · 1.5 KB Updated 567 repo stars

File contents

Skill: Scenario Runner + Capture

Objective

Allow agents to validate gameplay and visuals without controlling the OS window.

Steps

  1. Implement a Scenario Runner autoload
  • game/autoload/ScenarioRunner.gd
  • Parse CLI args after --:
    • --scenario <id>
    • --capture_dir <dir>
    • --seed <int>
    • --quit_after_frames <int>
  1. Define scenario scripts
  • Store scenarios under tests/scenarios/ (JSON)
  • Actions should include:
    • wait_frames
    • move_to
    • interact_nearest
    • trigger_encounter
    • select_battle_command
  1. Capture outputs
  • Always write a trace.json of executed actions + timings
  • Primary: use deterministic movie capture mode in Godot CLI (Movie Maker)
  • Secondary: checkpoint screenshots if stable
  1. CI scripts
  • Implement tools/ci/run-scenario.sh <scenario_id>

Verification

  • Scenario runs headlessly
  • Artifacts appear in captures/ or specified capture dir
  • Runs are deterministic across repeated runs on the same machine

majiayu000/claude-skill-registry-data/tree/main/testing/scenario-runner-capture commit c6024071d3

Frequently asked questions

npx skillmds add majiayu000/scenario-runner-capture