In this video I walk you through composition in Godot (Godot 4.6 RC1, but you can follow along in whatever version you’re comfortable with). I start with the “inheritance trap” I see beginners fall into all the time: stuffing movement, jumping, dashing, attacks, and everything else into one massive player.gd until it becomes a 5,000-line monster you’re scared to touch. Then I break down composition as the “has-a” approach (single responsibility principle: one script, one job) and why it’s the industry standard—reusability, encapsulation, and iterative design. After the concepts, I jump into a real Godot project (using the free Synty Polygon Starter Pack) and we build it the Godot way: nodes as components, signals for decoupled communication, and typed exports with class_name so components can plug into each other safely. I show how @export variables beat fragile get_node paths, and how scene unique names make your “backpack” of components easy to find even after you reorganize your scene tree. Finally, I switch into live-building mode with challenges. We set up an InputComponent, wire it through the player “orchestrator,” and start laying the foundation for a MovementComponent with inspector-driven tuning (speed, jump velocity, gravity multiplier). The big takeaway: keep components selfish and context-agnostic—if it works on a literal rock, you’re doing composition right.