@series-inc/rundot-3d-engine 0.6.14 → 0.6.16

package/SKILL.md

@@ -172,6 +172,51 @@ renderer.setMaterial(customMaterial)
 
 **Static meshes** (`isStatic: true`) skip per-frame matrix updates — use for non-moving objects.
 
+#### Sub-Meshes & Named Children
+
+Meshes with named child groups (from the editor's hierarchy) are automatically promoted to GameObjects.
+You can access them by name to add components, move them, etc.
+
+```typescript
+const renderer = new MeshRenderer("vehicle_mesh")
+const meshObj = new GameObject("VehicleMesh")
+meshObj.addComponent(renderer)
+parent.add(meshObj)
+
+// Wait for mesh to load, then access named children
+renderer.onLoaded(() => {
+    // Get a single child by name
+    const wheel = renderer.getMeshChild("Wheel_FL")
+    if (wheel) {
+        wheel.addComponent(new WheelSpinner())
+        wheel.position.y -= 0.1  // offset the wheel
+    }
+
+    // Get all named children
+    const children = renderer.getMeshChildren()
+    if (children) {
+        for (const [name, childGO] of children) {
+            console.log(`Child: ${name}`, childGO.position)
+        }
+    }
+})
+```
+
+**Sub-mesh mode** (from prefab): When a `stow_mesh` component has a `subMesh` field, MeshRenderer
+loads only that named group's geometry instead of the full mesh. This is how the editor's expanded
+sub-mesh hierarchy works at runtime — each child node gets its own MeshRenderer rendering only its part.
+
+```json
+{
+    "type": "stow_mesh",
+    "mesh": { "pack": "main", "assetId": "vehicle" },
+    "subMesh": "Wheel_FL"
+}
+```
+
+Each sub-mesh node is a real GameObject in the prefab tree, so you can attach any component
+(physics, scripts, etc.) to individual parts of a mesh.
+
 ### SkeletalRenderer — Animated Characters
 
 ```typescript