debug-issue

Debug Godot physics collisions by verifying collision layer and mask configurations on interacting nodes. The workflow maps the non-collision symptom to a physics decision tree to pinpoint mismatched properties.

Godot signals not firing are diagnosed by validating signal connections and handler signatures. The workflow inspects scene node connections to identify mismatched arguments or missing handlers causing the signal failure.

Troubleshoot Godot rendering issues like invisible or flickering visuals by inspecting scene nodes and their properties. The decision tree workflow checks visibility flags and rendering configurations to isolate the visual anomaly.

Fix unresponsive Godot input actions by matching input action names against the project settings. The diagnostic workflow validates the input map and action names to correct detection failures in the scene.

Yes, you can diagnose broken Godot navigation pathfinding using a dedicated decision tree. It routes navigation symptoms through ordered domain checks to identify missing navigation meshes or layer configuration errors.

To start the Godot debugging workflow, provide the specific symptom keyword and the relevant scene path. This allows the diagnostic process to map the issue to the correct domain tree and inspect the appropriate nodes.