Fix Godot gameplay with AI
Follow a gameplay problem from the scene and input that trigger it to an observable check in your Godot project. Keep the project's existing language and engine version.
To fix Godot gameplay with AI, describe the smallest sequence of inputs that exposes the problem. A menu that opens twice after a player leaves and re-enters a room suggests a different investigation from one that opens twice on the first visit. Give the agent that distinction before it changes a scene.
The godot-gamedev skill follows the project’s current engine version, language and conventions. It checks node lifetimes, signals, input handling and shared resources where relevant. A parser check can establish that a script loads, while an actual run can show whether the player now sees the intended result.
What it does
- Check what a controller button should do during play and while a menu has focus.
- Look for duplicate signal handling when a room is visited a second time.
- Test whether two instances accidentally share an inventory or timer.
- Check pause and resume around an action that was already in progress.
- Exercise a multiplayer change on the affected peers before reporting it as verified.
Install and use
- Install the skill and provide the existing Godot project. Use its matching engine build for runtime checks and its .NET toolchain for C#.
- Ask, “Re-enter this room and find why one interaction opens the dialogue twice.”
- Repeat the same input sequence after the change. Record any visual, sound or multiplayer behaviour that still requires a real play session.
FAQ
Source
Made by Egor Maximov (Setcode). Original skill: godot-gamedev, published on GitHub under the MIT licence.
View on GitHub