physics-review

To review Godot 4.x physics code, scan CollisionObject2D setups and collision_layer/collision_mask configurations against known gotcha rules. This maps offending code to specific gotcha IDs and recommends concrete fixes for body_entered and area_entered callbacks.

Godot physics callbacks like body_entered fail when collision_layer or collision_mask configurations are mismatched after code changes. Reviewing your implementation against gotcha rules flags these specific configuration and callback pitfalls, then provides targeted code fixes.

The best way to debug Godot 4.x collision detection is applying a gotcha-driven review checklist. It checks CollisionObject2D nodes, physics-loop velocity, and damping logic, then optionally runs static checks and runtime penetration tests for deeper validation.

Yes, this physics review works with Godot 4.x area_entered, body_exited, and area_exited callbacks. It reviews all physics callbacks tied to CollisionObject2D nodes and matches your implementation against gotcha rules to prevent subtle callback failures.

You should run a physics code review immediately after making physics-related code changes in your Godot project. Scanning post-implementation code prevents subtle, hard-to-debug physics behaviors by catching known collision and callback pitfalls early.

When configuring Godot collision masks and layers, look for known gotchas tied to CollisionObject2D usage and physics-loop velocity logic. The review matches your code against specific gotcha IDs G1 through G6, citing offending lines and recommending fixes.