[name]

One-paragraph description of what this bundle assembles (what entity hierarchy it represents, what it looks like in-scene) and when to spawn it.

Composition

Briefly describe the entity hierarchy that lives in entity_template:

• Root: what the root represents (e.g. Vehicle root, Tree trunk).
• Children: notable child entities and what they contribute.
• Components: the components attached to the root + meaningful children.
• Sub-assets: meshes / textures / animations / materials carried inside.

Usage

-- Live-linked (preferred — see this type's README for the full
-- comparison of live-linked vs baked spawn paths):
local id = entity.spawn("instance_1").id
entity(id).component.add("Asset", { source = "[name]" })
-- or via the workflow shortcut:
sc.spawnModel("instance_1", "[name]", 0, 0, 0)

Notes

• Anything callers should know about THIS bundle: scale conventions, required runtime services, animations to drive, replication notes.
• Inner-asset references inside data use the __ref shape ({ "__ref": "<guid>", "name": "...", "type": "..." }). The asset registry resolves them at spawn time.
• Bundles are container-category assets — they keep their .bundle suffix in identity and ride the container-category restore plumbing (see crates/zero_vfs/src/metadata.rs).