godot-playthrough-bot

Simulate real player input in headless Godot playthrough tests.

8|3|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/arthur0n/xenodot-forge --skill godot-playthrough-bot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: godot-playthrough-bot
Source: https://github.com/arthur0n/xenodot-forge/tree/main/plugin/skills/godot-playthrough-bot
Command: npx skills add https://github.com/arthur0n/xenodot-forge --skill godot-playthrough-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify that a Godot-family game responds correctly to real player input in headless tests, catching broken wiring that direct method calls can miss.

Core Features & Use Cases

  • Input-driven playthroughs: Drives movement, jump, crouch, aim, fire, and toggle actions through the actual input layer.
  • Headless physics validation: Steps deterministic physics frames and checks position, state, and signal changes after input is applied.
  • Navigability smoke testing: Confirms that a level is not only rendered but also walkable, with floor collisions, movement, and navmesh behavior working as expected.
  • Use case: Validate that a pause menu, weapon fire, or mouse-look control works in play exactly as it does for a player, not just in a method-call smoke test.

Quick Start

Ask the skill to generate a headless Godot playthrough bot test for a player movement and jump flow using real input events.

Frequently Asked Questions about godot-playthrough-bot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I simulate real player input in Godot headless testing?

Simulate real player input in Godot headless testing by driving the actual input layer with action_press or push_input, then stepping deterministic physics frames to assert that movement, toggles, and combat responses occur correctly.

Why do direct method call tests miss broken gameplay wiring in Godot?

Direct method call tests bypass the input layer, missing broken input wiring. Simulating actual player input headlessly catches these seams by verifying that movement, mouse-look, and pause UI respond to action_press and push_input events.

How do I check if a Godot level is navigable and walkable in headless tests?

Check Godot level navigability headlessly by simulating movement input, stepping physics frames, and asserting position changes. This validates floor collisions and navmesh behavior, confirming the level is walkable and not just rendered.

Can I validate mouse-look and pause menu UI seams in Godot headless mode?

Yes, you can validate mouse-look and pause menu UI seams in Godot headless mode by pushing simulated input events and using timeout-bounded signal waits to assert that the expected state toggles and responses occur.

What is the best way to verify Godot combat and movement responses without rendering graphics?

The best way to verify Godot combat and movement responses without graphics is headless playthrough testing, using deterministic physics-frame stepping and input simulation to assert state and position changes after actions are applied.

Do I need deterministic physics frame stepping for Godot input simulation tests?

Yes, deterministic physics frame stepping is required for Godot input simulation tests to reliably assert movement and state changes. It ensures timeout-bounded signal waits and input actions produce consistent, reproducible results.