In this video I break down Godot’s collision system using a super simple platformer project: a player that moves and jumps, enemies that run toward me, coins I can collect, and a few platforms (including moving ones). The goal is to finally make the “which node do I use?” question feel straightforward. I walk through the main CollisionObject2D options in 2D (and the same logic applies in 3D): StaticBody2D, Area2D, CharacterBody2D, plus a quick intro to AnimatableBody2D. The big takeaway is: physics bodies are for real physical interaction (gravity, solid collisions, not passing through the floor), while Area2D is just a region of space for detecting overlaps. That’s why a coin should be an Area2D (I don’t care about physics, I care about detecting collection), while the player and enemies are CharacterBody2D (moved by script and part of the physics engine). I also show how to detect “body entered” events reliably: use Area2D signals, and if you need player-vs-enemy detection, combine nodes by adding an Area2D hitbox to the player and reusing the same CollisionShape2D as a linked resource. Finally, I cover a practical tip: when reloading a scene from a collision callback, use call_deferred to avoid engine warnings and weird issues.