coherence-nested-prefabs

Add Coherence.Toolkit.PrefabSyncGroup to the parent prefab's root and bake so the synced ids field enters the schema. It assigns deterministic ids to nested child CoherenceSyncs, sets them to NoDuplicates uniqueness, and collapses per-client copies onto one host-owned entity.

Scan prefab YAML for PrefabInstance blocks whose m_SourcePrefab guid resolves to another prefab containing a CoherenceSync MonoBehaviour. If the parent root lacks a PrefabSyncGroup, the nesting is unsynchronized.

No. PrefabSyncGroup only covers edit-time nesting inside the prefab asset. Runtime parenting, such as picking up an item or mounting a vehicle, is handled by CoherenceNode and parent-child sync, which is a separate concern.

Each client instantiates its own copy of the nested child as a separate network entity because coherence has no edit-time record tying the copies together. PrefabSyncGroup records the nesting so NoDuplicates uniqueness collapses the copies onto the host's entity.

De-nest when the child's lifetime and authority should be explicit and independent: make it a top-level prefab the host instantiates and reparents at runtime. Also fold the child into the parent's bindings if it only needs a few synced values.

It requires a CoherenceSync component, disallows multiple instances, and must sit on the prefab root or OnValidate errors. Nested children 2 or more levels deep need a CoherenceNode, and scene-placed nested entities should use NoDuplicates uniqueness directly instead.