It seems you're referencing a potential bug or glitch in a game or simulation (possibly ZOEI or a similarly named title), where child objects are not properly handling collisions—possibly due to issues with parenting, collision detection, or physics layering. However, "ZoI" (or "ZOEI") isn't a widely recognized game or engine as of now, so here's a general troubleshooting guide to fix issues with child objects not detecting collisions—a common problem in game engines like Unity, Unreal, or custom physics systems: ✅ Common Causes & Fixes for Child Collision Glitches 1. Physics Layering / Collision Matrix Issue: Child objects may inherit the parent’s collision settings, but if the layer is set to ignore collisions, they won’t detect anything. Fix: In Unity: Check the Physics Layer of the child object and ensure it’s set to collide with the relevant layers. Go to Edit > Project Settings > Physics and verify the collision matrix allows your child’s layer to interact with others. 2. Rigidbody or Collider Missing Issue: The child object may lack a Rigidbody (if it's dynamic) or a Collider. Fix: Ensure the child has: A Collider (e.g., BoxCollider, SphereCollider). A Rigidbody (if it should move or react to physics). If the parent has a Rigidbody, the child may need isKinematic or useGravity set properly. 3. Parent-Child Hierarchy Issues Issue: When a child is attached to a parent with a Rigidbody, it may "follow" the parent’s motion and not react independently to collisions. Fix: Avoid parenting physics objects unless necessary. If the child must be a child: Set isKinematic = false on the child’s Rigidbody. Use Constraints to prevent unwanted rotation or movement. Ensure the parent’s Rigidbody isn’t "pulling" the child into invalid states. 4. Trigger vs. Collision Issue: The child might be set as a trigger, so it doesn’t block or respond to collisions. Fix: Check the isTrigger checkbox on the child’s Collider. If you want it to collide, uncheck isTrigger or use proper OnCollisionEnter logic. 5. Resetting the Physics State Issue: The child’s collider might be disabled or offset after spawning. Fix: In code (e.g., Unity C#), ensure the child’s collider is enabled:childCollider.enabled = true; childRigidbody.isKinematic = false; Reset transform if offset:childTransform.position = originalPosition; 6. Use of Transform.SetParent vs. Manual Positioning Issue: Using SetParent can break physics if not handled carefully. Fix: Use SetParent(parentTransform, false) to keep the child’s world position. Or, avoid parenting and use GameObject.Find or references instead. 🔧 Example Fix (Unity) void FixChildCollision(GameObject child) { var collider = child.GetComponent(); var rb = child.GetComponent(); if (!collider) { collider = child.AddComponent(); } if (!rb) { rb = child.AddComponent(); rb.useGravity = true; rb.mass = 1f; } collider.isTrigger = false; // or set based on need rb.isKinematic = false; // Ensure it's not buried in the hierarchy child.transform.SetParent(null); } 📌 Summary "Child collisions not working" is often due to: Missing Rigidbody or Collider Incorrect layer settings Misconfigured parenting isTrigger accidentally enabled ✅ Action Plan: Verify child has a Collider and Rigidbody. Check Physics Layers and Collision Matrix. Disable isTrigger unless needed. Avoid unnecessary parenting of physics objects. If you’re using a specific engine or mod (e.g., a mod for ZOEI or ZoI by a developer), please share: The engine (Unity, Unreal, Godot, etc.) The exact behavior (e.g., "child object passes through walls") Any error logs or code snippets I’ll help you debug it precisely!

By CharlotteApr 18,2026