Unity-osztagok és tömegek

NPC Squads and Crowd Coordination

Inspect existing navigation/movement authority, encounter rules, actor counts and the per-frame AI budget. Separate group decisions from each member's perception, action execution and locomotion.

• Give the coordinator explicit membership and lifetime. Register/unregister on spawn, death, disable and pooling; invalidate reused actor identities so old reservations cannot affect a new lifetime.
• Assign roles or tactical slots to valid members. Project candidate positions onto reachable navigation and check cover/line-of-fire rules rather than sending every actor to the target's exact point.
• Make reservations owned, expiring and cancellable. Release them when a path fails, an action is interrupted, the target changes or a member disappears. Define a fallback if every useful slot is occupied.
• Share alerts as bounded knowledge: source, observation time, last-known position and confidence. A shared Transform reference must not silently update an unseen target's location forever.
• Coordinate spacing/steering with the existing motor and NavMesh avoidance. Local separation cannot solve disconnected paths or a blocked chokepoint; diagnose global routing separately.
• Bound neighbor searches with suitable spatial filtering and stagger expensive path/role updates. Compare crowd density and worst-frame CPU at intended encounter size before adding Jobs/Burst or a new framework.

Verify member loss and replacement, blocked slots, stale alerts, target loss, dense doors, regrouping and simultaneous replans. Trace role/slot owner, alert age, path status and retry count; report measured load and remaining playtest judgments.

Reference: installed AI Navigation documentation. The upstream coordinator scaffold is a design reference, not an installed dependency.