game-collisionlisted

# Game Collision — if it looks solid, it IS solid This is the skill that exists because AI games are full of ghosts: a rock is drawn, but there's no rock — just pixels. You asked for a wall and got wallpaper. **Drawing a thing is not making a thing.** Every object that should block, hit, or carry the player must own a collision body that the movement code actually checks — and you must have *seen* that body with your own eyes in the debug overlay. ## The Prime Directive **A visual is not a collider. A collider is not a visual. Every solid object needs BOTH, explicitly wired together — and verified in the debug overlay before you trust it.** If you can't point to the line that registered the rock's body, and see its box drawn on screen, the rock does not exist as far as the player is concerned. No exceptions. ## BANNED (every one of these is a walk-through-the-rock bug waiting to happen) - **Drawing a sprite and calling it solid.** `drawImage(rock, x, y)` with no body created, no collider added. This is *the* bug. The asset exists; the obstacle doesn't. - **Whole-sprite hitboxes in top-down.** Making the entire tree/house image collidable → an invisible wall around the canopy, and the player can't walk behind it. Collision is the **footprint** (trunk base), not the picture. - **Collision you've never rendered.** Shipping hitboxes you can't see. If the debug overlay isn't wired first, you're guessing. - **Moving both axes then testing once.** Resolving X and Y together make