particles-review

To review Godot particle code for collision and trail gotchas, run a post-implementation static check against known engine pitfalls. This process maps each detected issue to a specific gotcha ID, shows the offending code, and provides a concrete correction to prevent silent visual failures.

Godot particle collisions and runtime emission changes break silently due to known engine gotchas related to particle materials, collision nodes, and dynamic `.amount`/`.emitting` modifications. A dedicated particle code review identifies these specific pitfalls before they ship.

Yes, you can run static checks on Godot CPUParticles3D and GPUParticles3D implementations. A particle reviewer applies a checklist to map known gotchas to static checks and can optionally run a headless compilation validation to ensure collision and trail behavior works.

Yes, Godot particle code review works with runtime property changes like `.emitting` and `.amount`. The review specifically focuses on detecting known engine gotchas that cause silent failures when particle properties are modified dynamically during gameplay.

The best way to catch Godot particle pitfalls before shipping is to run a post-implementation review that checks GPUParticles2D/3D, CPUParticles2D/3D, particle materials, trails, sub-emitters, and collision nodes against a gotchas checklist to prevent silent visual failures.