[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMKZ230HFDBBYY61TY415Y":3,"skill-same:01M7CMKZ230HFDBBYY61TY415Y":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CMKZ230HFDBBYY61TY415Y","unity-physics-3d",null,"3D PhysX bugs: OnTriggerEnter never fires, tunnelling, raycast misses, exploding ragdolls.","tipoLi5890\u002Funity-dev-skills","tipoLi5890","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F177803612?v=4","01M7CMD7DHGZ09CB53CRFHAA34","Li, ching yu","01M7CMD7E70K5RAHWWZVYX9YMG",2,"MIT","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-physics-3d\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: unity-physics-3d\ndescription: >-\n  3D PhysX bugs: OnTriggerEnter never fires, tunnelling, raycast misses, exploding ragdolls.\n---\n\n# unity-physics-3d — a triage ladder, not a list of things to try\n\n> **Your prior knowledge about PhysX callbacks is unreliable, and the errors are silent.**\n> Almost nothing in this domain throws. A collider that will never collide looks identical in the\n> inspector to one that will. Work the ladder; do not reason from what \"should\" happen.\n\n## Symptom → where to look\n\nFirst match wins. **Stop at the first cause you confirm** and write the diagnosis; the rest of the\nladder is for when that check comes back clean.\n\n| Symptom | Go to |\n|---|---|\n| `OnCollisionEnter` \u002F `OnTriggerEnter` never fires | §1 |\n| Objects pass through each other at speed; a fast object passes through a wall | §2 |\n| A hit is reported before the two objects visibly touch | §2 — speculative contacts |\n| `Physics.Raycast` misses something clearly in front of it | §3 |\n| A click finds no UI, or a world ray keeps hitting the HUD | §3 — two raycasters, two worlds |\n| `AddForce` seems to stop working once the object settles | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §4 — and it is **not** the sleep state |\n| `OnTriggerStay` \u002F `OnCollisionStay` ran for a while, then went quiet | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §4 — the body fell asleep |\n| Everything frozen but raycasts still hit | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §4 |\n| Ragdoll explodes on the first frame | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §5 |\n| Collider is the wrong shape after import \u002F imported geometry does not collide | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §5 |\n| Objects come to rest with a visible gap between them | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §5 — contact offset |\n| Things pass out through a concave mesh they should sit inside | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §5 — inverted normals |\n| It collides in the editor and not in the build | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §6 |\n| Collisions stopped after a respawn or a return to the pool | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §6 — per-instance ignore pairs |\n| A sports ball must curve, bounce with spin, replay and be predicted exactly | [`reference\u002Fown-ball-physics.md`](reference\u002Fown-ball-physics.md): no PhysX for the ball |\n\n## 0. Before diagnosing\n\nConnect to the Editor rather than reading files — `unity-debug` → `reference\u002Feditor-control.md`.\nThree rules specific to physics, then two about how the turn ends:\n\n- **Never verify with `Physics.Simulate()` outside play mode.** Editor-mode simulation does not\n  dispatch MonoBehaviour callbacks, so a working setup reports as broken. It is a guaranteed false\n  negative and it will send you down the wrong branch.\n- **Geometry queries DO work outside play mode — but only after a sync.** `Physics.autoSyncTransforms`\n  is **`false`** by default, so a collider you just created or moved is not where PhysX thinks it\n  is, and every raycast against it returns false. Call `Physics.SyncTransforms()` once before\n  querying, or you will diagnose a perfectly good collider as broken — the call, and where it\n  goes: [`reference\u002Fqueries.md`](reference\u002Fqueries.md).\n- **Record the original value of any Project Setting you change** (Queries Hit Triggers, the\n  Layer Collision Matrix, Contact Offset) and restore it. A diagnosis that leaves the project\n  altered is not a diagnosis.\n- **Answer with what the ladder confirmed.** When the checks you can reach are exhausted without a\n  confirmed cause, write the most likely diagnosis off the ladder, labelled unconfirmed, with the\n  one check that would settle it.\n- **End with the fix or the diagnosis.** Make the change yourself where you can reach it — a\n  script, or the live scene over an Editor connection — otherwise hand over an explanation complete\n  enough to apply without you. Ask only for information you cannot get yourself, and name it.\n\n## 1. No callback fires\n\nWork down. First match wins.\n\n1. **At least one of the pair needs a `Rigidbody`.** Two static colliders never generate contacts.\n2. **An unticked `Collider` and an inactive GameObject are both completely silent.** No warning,\n   no error: the object is simply not in the physics scene, and the inspector looks correct\n   because the checkbox is the only difference. Check `Collider.enabled` *and*\n   `gameObject.activeInHierarchy` — `Collider` declares its own `enabled` rather than inheriting\n   one from `Behaviour`, and `activeInHierarchy` is read-only, so a parent\n   switched off two levels up reads as the child's own fault.\n3. **Layer Collision Matrix** — `Project Settings → Physics`. An unchecked pair is silent.\n4. **Trigger vs collision.** If either collider `isTrigger`, you get `OnTrigger*` and **never**\n   `OnCollision*`.\n5. **`OnCollision*` and `OnTrigger*` must be on a GameObject that has a collider** — not on a\n   parent that merely contains one.\n6. **`CharacterController` never raises `OnCollisionEnter`** → `OnControllerColliderHit`. Do not\n   add a `Rigidbody` to \"fix\" it; the two movement models are mutually exclusive.\n7. **A 3D scene with `OnCollisionEnter2D`** in it. `resources\u002FCollisionDebugger.cs` catches this\n   specifically.\n\n> **Two kinematic triggers DO fire `OnTriggerEnter`.** The Trigger matrix is not the Collision\n> matrix. Kinematic × kinematic produces no `OnCollisionEnter`, which is where the belief comes\n> from — but kinematic-trigger × kinematic-trigger produces `OnTriggerEnter` normally.\n\n> **A kinematic body must be moved with `MovePosition()` or by writing `transform.position`.**\n> Assigning velocity is ignored without warning, the body does not move, and the broadphase\n> never updates — which then reads as \"collisions stopped working\".\n\n> **In Unity 6 the property is `Rigidbody.linearVelocity`.** `velocity` still exists and old code\n> compiles; mixing the two in one file reads as a bug that is not there.\n\n## 2. Tunnelling\n\n| `collisionDetectionMode` | Sweeps against |\n|---|---|\n| `Discrete` | Nothing — default; fast objects pass through |\n| `Continuous` | **Static colliders only** — silently falls back to Discrete against dynamic bodies |\n| `Continuous Dynamic` | Static + other Continuous Dynamic bodies (expensive) |\n| `Continuous Speculative` | Everything, cheaper than CCD, occasional ghost contact |\n\nChoose by what the fast thing hits, not by how fast it is.\n\n- **Against static geometry** — thin floors, walls, terrain — `Continuous Speculative` is the\n  one to reach for. `Continuous` is also correct there, but it degrades to `Discrete` the moment\n  the counterpart is a dynamic body, and it does that without saying so.\n- **Against another moving body**, accuracy belongs to `Continuous Dynamic`. Speculative contacts\n  are *predictions*: the solver widens the contact distance and resolves against where the body\n  is about to be, and a prediction that does not come true surfaces as a **ghost contact** — a\n  callback with the objects visibly apart, a bullet scoring early, a shivering stack. When \"it\n  hits before it touches\" meets `Continuous Speculative`, the mode *is* the finding; do not hunt\n  for an oversized collider.\n\nWrite the mode out in full (`ContinuousDynamic`, `ContinuousSpeculative`): the bare word\n\"continuous\" in a bug report has meant each of three modes.\n\n> **For a bullet or any projectile, raise `Physics.SphereCast` as well** — sweeping rather than\n> stepping removes tunnelling entirely, independently of the physics step:\n> [`reference\u002Fqueries.md`](reference\u002Fqueries.md).\n> A ball the rules own, swept in substeps by your own code: [`reference\u002Fown-ball-physics.md`](reference\u002Fown-ball-physics.md).\n\n## 3. Raycast misses\n\n- **An origin inside the target collider returns false** — backface culling; Queries Hit Backfaces\n  rescues only a `MeshCollider`.\n- **Triggers are hit by default.** `Physics.queriesHitTriggers` is `true` and `UseGlobal` defers\n  to it — pass `Ignore` or `Collide` explicitly, never rely on a default.\n- **Check the mask you passed is the mask you meant** — A\u002FB it against\n  `Physics.DefaultRaycastLayers`, which excludes `Ignore Raycast`; `Physics.AllLayers` does not.\n- **A disabled `Collider` or an inactive GameObject is invisible to queries too.**\n  `Physics.OverlapSphere` asks what PhysX actually has at a position.\n- **`GraphicRaycaster` finds UI, `Physics.Raycast` finds colliders**, never each other's\n  (`unity-ui-ugui`).\n- **After writing `transform.position`, queries see the old position** until\n  `Physics.SyncTransforms()` — once, never every frame.\n\nEach rule in full — the primitive-versus-mesh split, the three trigger results, the A\u002FB probe, the\nscreen-point call and the `MovePosition` alternative:\n[`reference\u002Fqueries.md`](reference\u002Fqueries.md).\n\n## 4–6. Sleep, shapes, editor versus build → `reference\u002Fsleep-shapes-build.md`\n\n§4 a body that moved then stopped (sleep, `AddForce` that wakes it, `timeScale`); §5 colliders\nthat are not the shape they look — imported geometry, non-uniform scale, ragdoll overlap, contact\noffset, inverted normals, compound bodies; §6 what differs in a build. Same numbering there.\n\n## The probe\n\n`resources\u002FCollisionDebugger.cs` — attach to **both** suspected objects, read the console, remove\nit when done.\n\n| Console | Diagnosis |\n|---|---|\n| Neither object logs `[Setup]` | The script is not on the objects you think it is |\n| `[Setup]` from both, no `[Collision]` \u002F `[Trigger]` | §1 steps 1, 3, 4 |\n| `[Setup]` reports `collider none` or `enabled False` | §1 step 2 — the collider is not in the scene |\n| Only one side logs anything | The other object is not the one colliding |\n| `[2D Collision]` appears | 2D components in a 3D scene |\n\n## Scope — what this skill does NOT do\n\nPathfinding, NavMesh baking and agent steering are `unity-navigation` — a collider that was\nabsent at bake time still collides here and is still not pathed around there. Canvas hit-testing\nand the EventSystem are `unity-ui-ugui`. Stripping and `link.xml` are\n`unity-android-release`. A `CharacterController` motor — ground, slopes, steps — is\n`unity-3d-controller`. Hit and hurt layers and damage events are `unity-combat`. A ball the game\nintegrates itself (drag, spin, swept contact, a shot solver) is\n[`reference\u002Fown-ball-physics.md`](reference\u002Fown-ball-physics.md).\n\n2D physics — `Rigidbody2D`, `Collider2D`, `Physics2D` — is `unity-physics-2d`. DOTS \u002F the Unity\nPhysics package (`com.unity.physics`) is **not** this skill's subject either: it gets a\nbest-effort answer in its own vocabulary — never a PhysX rule from this page under a DOTS name,\nnever \"move the project onto PhysX\":\n[`reference\u002Fneighbour-stacks.md`](reference\u002Fneighbour-stacks.md).\n","# unity-physics-3d — a triage ladder, not a list of things to try\n\n> **Your prior knowledge about PhysX callbacks is unreliable, and the errors are silent.**\n> Almost nothing in this domain throws. A collider that will never collide looks identical in the\n> inspector to one that will. Work the ladder; do not reason from what \"should\" happen.\n\n## Symptom → where to look\n\nFirst match wins. **Stop at the first cause you confirm** and write the diagnosis; the rest of the\nladder is for when that check comes back clean.\n\n| Symptom | Go to |\n|---|---|\n| `OnCollisionEnter` \u002F `OnTriggerEnter` never fires | §1 |\n| Objects pass through each other at speed; a fast object passes through a wall | §2 |\n| A hit is reported before the two objects visibly touch | §2 — speculative contacts |\n| `Physics.Raycast` misses something clearly in front of it | §3 |\n| A click finds no UI, or a world ray keeps hitting the HUD | §3 — two raycasters, two worlds |\n| `AddForce` seems to stop working once the object settles | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §4 — and it is **not** the sleep state |\n| `OnTriggerStay` \u002F `OnCollisionStay` ran for a while, then went quiet | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §4 — the body fell asleep |\n| Everything frozen but raycasts still hit | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §4 |\n| Ragdoll explodes on the first frame | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §5 |\n| Collider is the wrong shape after import \u002F imported geometry does not collide | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §5 |\n| Objects come to rest with a visible gap between them | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §5 — contact offset |\n| Things pass out through a concave mesh they should sit inside | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §5 — inverted normals |\n| It collides in the editor and not in the build | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §6 |\n| Collisions stopped after a respawn or a return to the pool | [`reference\u002Fsleep-shapes-build.md`](reference\u002Fsleep-shapes-build.md) §6 — per-instance ignore pairs |\n| A sports ball must curve, bounce with spin, replay and be predicted exactly | [`reference\u002Fown-ball-physics.md`](reference\u002Fown-ball-physics.md): no PhysX for the ball |\n\n## 0. Before diagnosing\n\nConnect to the Editor rather than reading files — `unity-debug` → `reference\u002Feditor-control.md`.\nThree rules specific to physics, then two about how the turn ends:\n\n- **Never verify with `Physics.Simulate()` outside play mode.** Editor-mode simulation does not\n  dispatch MonoBehaviour callbacks, so a working setup reports as broken. It is a guaranteed false\n  negative and it will send you down the wrong branch.\n- **Geometry queries DO work outside play mode — but only after a sync.** `Physics.autoSyncTransforms`\n  is **`false`** by default, so a collider you just created or moved is not where PhysX thinks it\n  is, and every raycast against it returns false. Call `Physics.SyncTransforms()` once before\n  querying, or you will diagnose a perfectly good collider as broken — the call, and where it\n  goes: [`reference\u002Fqueries.md`](reference\u002Fqueries.md).\n- **Record the original value of any Project Setting you change** (Queries Hit Triggers, the\n  Layer Collision Matrix, Contact Offset) and restore it. A diagnosis that leaves the project\n  altered is not a diagnosis.\n- **Answer with what the ladder confirmed.** When the checks you can reach are exhausted without a\n  confirmed cause, write the most likely diagnosis off the ladder, labelled unconfirmed, with the\n  one check that would settle it.\n- **End with the fix or the diagnosis.** Make the change yourself where you can reach it — a\n  script, or the live scene over an Editor connection — otherwise hand over an explanation complete\n  enough to apply without you. Ask only for information you cannot get yourself, and name it.\n\n## 1. No callback fires\n\nWork down. First match wins.\n\n1. **At least one of the pair needs a `Rigidbody`.** Two static colliders never generate contacts.\n2. **An unticked `Collider` and an inactive GameObject are both completely silent.** No warning,\n   no error: the object is simply not in the physics scene, and the inspector looks correct\n   because the checkbox is the only difference. Check `Collider.enabled` *and*\n   `gameObject.activeInHierarchy` — `Collider` declares its own `enabled` rather than inheriting\n   one from `Behaviour`, and `activeInHierarchy` is read-only, so a parent\n   switched off two levels up reads as the child's own fault.\n3. **Layer Collision Matrix** — `Project Settings → Physics`. An unchecked pair is silent.\n4. **Trigger vs collision.** If either collider `isTrigger`, you get `OnTrigger*` and **never**\n   `OnCollision*`.\n5. **`OnCollision*` and `OnTrigger*` must be on a GameObject that has a collider** — not on a\n   parent that merely contains one.\n6. **`CharacterController` never raises `OnCollisionEnter`** → `OnControllerColliderHit`. Do not\n   add a `Rigidbody` to \"fix\" it; the two movement models are mutually exclusive.\n7. **A 3D scene with `OnCollisionEnter2D`** in it. `resources\u002FCollisionDebugger.cs` catches this\n   specifically.\n\n> **Two kinematic triggers DO fire `OnTriggerEnter`.** The Trigger matrix is not the Collision\n> matrix. Kinematic × kinematic produces no `OnCollisionEnter`, which is where the belief comes\n> from — but kinematic-trigger × kinematic-trigger produces `OnTriggerEnter` normally.\n\n> **A kinematic body must be moved with `MovePosition()` or by writing `transform.position`.**\n> Assigning velocity is ignored without warning, the body does not move, and the broadphase\n> never updates — which then reads as \"collisions stopped working\".\n\n> **In Unity 6 the property is `Rigidbody.linearVelocity`.** `velocity` still exists and old code\n> compiles; mixing the two in one file reads as a bug that is not there.\n\n## 2. Tunnelling\n\n| `collisionDetectionMode` | Sweeps against |\n|---|---|\n| `Discrete` | Nothing — default; fast objects pass through |\n| `Continuous` | **Static colliders only** — silently falls back to Discrete against dynamic bodies |\n| `Continuous Dynamic` | Static + other Continuous Dynamic bodies (expensive) |\n| `Continuous Speculative` | Everything, cheaper than CCD, occasional ghost contact |\n\nChoose by what the fast thing hits, not by how fast it is.\n\n- **Against static geometry** — thin floors, walls, terrain — `Continuous Speculative` is the\n  one to reach for. `Continuous` is also correct there, but it degrades to `Discrete` the moment\n  the counterpart is a dynamic body, and it does that without saying so.\n- **Against another moving body**, accuracy belongs to `Continuous Dynamic`. Speculative contacts\n  are *predictions*: the solver widens the contact distance and resolves against where the body\n  is about to be, and a prediction that does not come true surfaces as a **ghost contact** — a\n  callback with the objects visibly apart, a bullet scoring early, a shivering stack. When \"it\n  hits before it touches\" meets `Continuous Speculative`, the mode *is* the finding; do not hunt\n  for an oversized collider.\n\nWrite the mode out in full (`ContinuousDynamic`, `ContinuousSpeculative`): the bare word\n\"continuous\" in a bug report has meant each of three modes.\n\n> **For a bullet or any projectile, raise `Physics.SphereCast` as well** — sweeping rather than\n> stepping removes tunnelling entirely, independently of the physics step:\n> [`reference\u002Fqueries.md`](reference\u002Fqueries.md).\n> A ball the rules own, swept in substeps by your own code: [`reference\u002Fown-ball-physics.md`](reference\u002Fown-ball-physics.md).\n\n## 3. Raycast misses\n\n- **An origin inside the target collider returns false** — backface culling; Queries Hit Backfaces\n  rescues only a `MeshCollider`.\n- **Triggers are hit by default.** `Physics.queriesHitTriggers` is `true` and `UseGlobal` defers\n  to it — pass `Ignore` or `Collide` explicitly, never rely on a default.\n- **Check the mask you passed is the mask you meant** — A\u002FB it against\n  `Physics.DefaultRaycastLayers`, which excludes `Ignore Raycast`; `Physics.AllLayers` does not.\n- **A disabled `Collider` or an inactive GameObject is invisible to queries too.**\n  `Physics.OverlapSphere` asks what PhysX actually has at a position.\n- **`GraphicRaycaster` finds UI, `Physics.Raycast` finds colliders**, never each other's\n  (`unity-ui-ugui`).\n- **After writing `transform.position`, queries see the old position** until\n  `Physics.SyncTransforms()` — once, never every frame.\n\nEach rule in full — the primitive-versus-mesh split, the three trigger results, the A\u002FB probe, the\nscreen-point call and the `MovePosition` alternative:\n[`reference\u002Fqueries.md`](reference\u002Fqueries.md).\n\n## 4–6. Sleep, shapes, editor versus build → `reference\u002Fsleep-shapes-build.md`\n\n§4 a body that moved then stopped (sleep, `AddForce` that wakes it, `timeScale`); §5 colliders\nthat are not the shape they look — imported geometry, non-uniform scale, ragdoll overlap, contact\noffset, inverted normals, compound bodies; §6 what differs in a build. Same numbering there.\n\n## The probe\n\n`resources\u002FCollisionDebugger.cs` — attach to **both** suspected objects, read the console, remove\nit when done.\n\n| Console | Diagnosis |\n|---|---|\n| Neither object logs `[Setup]` | The script is not on the objects you think it is |\n| `[Setup]` from both, no `[Collision]` \u002F `[Trigger]` | §1 steps 1, 3, 4 |\n| `[Setup]` reports `collider none` or `enabled False` | §1 step 2 — the collider is not in the scene |\n| Only one side logs anything | The other object is not the one colliding |\n| `[2D Collision]` appears | 2D components in a 3D scene |\n\n## Scope — what this skill does NOT do\n\nPathfinding, NavMesh baking and agent steering are `unity-navigation` — a collider that was\nabsent at bake time still collides here and is still not pathed around there. Canvas hit-testing\nand the EventSystem are `unity-ui-ugui`. Stripping and `link.xml` are\n`unity-android-release`. A `CharacterController` motor — ground, slopes, steps — is\n`unity-3d-controller`. Hit and hurt layers and damage events are `unity-combat`. A ball the game\nintegrates itself (drag, spin, swept contact, a shot solver) is\n[`reference\u002Fown-ball-physics.md`](reference\u002Fown-ball-physics.md).\n\n2D physics — `Rigidbody2D`, `Collider2D`, `Physics2D` — is `unity-physics-2d`. DOTS \u002F the Unity\nPhysics package (`com.unity.physics`) is **not** this skill's subject either: it gets a\nbest-effort answer in its own vocabulary — never a PhysX rule from this page under a DOTS name,\nnever \"move the project onto PhysX\":\n[`reference\u002Fneighbour-stacks.md`](reference\u002Fneighbour-stacks.md).\n",{"name":5,"description":7},"main","b7459aa49fb881c5abb764223674ec8f397a02b1","skills\u002Funity-physics-3d",0,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills","https:\u002F\u002Fgithub.com\u002FtipoLi5890","https:\u002F\u002Ftipoli5890.github.io\u002F","2026-11-10 09:16:41",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add tipoLi5890\u002Funity-dev-skills --skill unity-physics-3d",{"tool":38,"command":39},"bunx","bunx skills add tipoLi5890\u002Funity-dev-skills --skill unity-physics-3d",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tipoLi5890\u002Funity-dev-skills --skill unity-physics-3d","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-physics-3d\u002FSKILL.md",true,[46,52,56,60,64,68,74],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference\u002Feditor-vs-build.md","REFERENCE","参考文档",2987,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-physics-3d\u002Freference\u002Feditor-vs-build.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"reference\u002Fneighbour-stacks.md",1550,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-physics-3d\u002Freference\u002Fneighbour-stacks.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"reference\u002Fown-ball-physics.md",9763,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-physics-3d\u002Freference\u002Fown-ball-physics.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"reference\u002Fqueries.md",4521,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-physics-3d\u002Freference\u002Fqueries.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"reference\u002Fsleep-shapes-build.md",4872,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-physics-3d\u002Freference\u002Fsleep-shapes-build.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"resources\u002FBallFlight.cs","OTHER","其他",13123,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-physics-3d\u002Fresources\u002FBallFlight.cs",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"resources\u002FCollisionDebugger.cs",1826,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-physics-3d\u002Fresources\u002FCollisionDebugger.cs",[79,86,93,100,107,114],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CMNYXQNW14ST64EYEEZ5V5","unity-web-release","Ship a WebGL\u002FWebGPU build: shrink the download, Brotli server headers, Safari and iPhone memory.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-web-release\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CMNTHD1EA70CCJ2F9FN3HT","unity-vivox","Vivox voice and text chat: channels, positional voice, mute and push-to-talk, mic permission.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-vivox\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7CMNPHPRQZ7K1FES2953DRQ","unity-urp-migration","Migrate a Built-in project to URP, or fix a half-moved one: pink materials, PPv2, old shaders.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-urp-migration\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7CMNJ756DK4V0D50HMAZYQW","unity-ui-ugui","Canvas UI (uGUI): CanvasScaler, RectTransform anchors, Layout Groups, ScrollView, UI built from C#.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ui-ugui\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7CMNDESZN79EK5FRDXCA2WA","unity-ui-toolkit","UI Toolkit (UXML, USS, UIDocument): flex layout, binding, custom elements, editor windows.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ui-toolkit\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7CMN8GBV07K0YCY07BJ6A1W","unity-ugs","Unity Gaming Services API: which package, init and sign-in order, Cloud Save, Cloud Code, Remote Config.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ugs\u002FSKILL.md",[],[]]