direct-entity-manager-structural-changes

What problem does it solve?

It prevents unsafe or expensive Unity DOTS structural changes by guiding when and how to use EntityManager directly for one-shot, batch operations.

Core Features & Use Cases

• Main-thread batch structural changes: Use EntityManager outside active query iteration to initialize or respawn large sets efficiently (e.g., mass Instantiate, Add/Remove components, Destroy by query).
• Safety-first patterns: Avoid structural changes inside SystemAPI.Query foreach and avoid accessing EntityManager from scheduled jobs.
• Performance-oriented approach: Prefer batch overloads and one-shot system disabling to reduce archetype operations and eliminate per-frame duplication.

Quick Start

In a one-shot ISystem OnUpdate, disable the system with state.Enabled = false before work, then use state.EntityManager.Instantiate(prefab, count, Allocator.Temp) and apply component/buffer changes via batch or query-based APIs outside any query foreach loop.