← ClaudeAtlas

unity-physics-2dlisted

2D physics bugs: OnCollisionEnter2D never fires, tunnelling, self-hit casts, one-way platforms.
tipoLi5890/unity-dev-skills · ★ 2 · AI & Automation · score 75
Install: claude install-skill tipoLi5890/unity-dev-skills
# unity-physics-2d — Box2D answers in its own vocabulary > **A PhysX rule renamed with a 2D suffix is usually wrong.** A kinematic `Rigidbody2D` moves > under its velocity, a ray that starts inside a collider hits it, sleep is a timer, there are two > collision-detection modes, and Z separates nothing. Almost nothing here throws. Work the > ladder; do not translate what the 3D engine would do. ## Symptom → where to look First match wins. **Stop at the first cause you confirm** and write the diagnosis. | Symptom | Go to | |---|---| | `OnCollisionEnter2D` / `OnTriggerEnter2D` never fires | §1 | | A kinematic sentry walks through walls and reports nothing | §1 — full kinematic contacts | | A bullet or a fast runner passes through a wall | §2 | | A fast body skips a pickup or a hazard trigger | §2 — triggers are not swept | | A ground check reports the caster itself, or a cast misses what is in its path | §3 | | A click through the camera finds no 2D collider | §3 — a 3D ray against 2D shapes | | `OnTriggerStay2D` / `OnCollisionStay2D` ran, then went quiet | §4 — the body fell asleep | | A `Rigidbody2D` jitters; the runner stutters while the camera follows | §4 | | The tilemap falls out of the scene on Play, or when a composite collider is added | [`reference/shapes-platforms-build.md`](reference/shapes-platforms-build.md) §5 — the composite's body | | The runner snags on flat ground, tile edges or seams | [`reference/shapes-platforms-build.md`](reference/shapes-platforms-bui