toentityarray-snapshot-pattern

Iterator invalidation occurs because structural changes alter archetypes while you are still iterating. You must snapshot entity IDs and component data into NativeArrays before performing structural changes to avoid this exception.

To safely iterate and perform structural changes, build an EntityQuery, copy matching entities and component data into NativeArrays using an appropriate allocator, execute structural changes on the query, then iterate the snapshot arrays afterward.

Use ToEntityArray and ToComponentDataArray when per-entity conditional logic differs and query-level batch overloads cannot express entity-specific changes. Snapshotting allows safe computation and initialization for each individual entity.

No, modifying archetype state during an active query iteration causes safety exceptions. You must first snapshot the required entity IDs and component data into NativeArrays, stop iterating, perform the structural changes, then iterate the arrays.

You must use an appropriate allocator to copy ToEntityArray and ToComponentDataArray data into NativeArrays. This snapshot persists safely outside the query iteration scope, allowing structural changes and subsequent per-entity data initialization.