batch-structural-change-on-query

To perform structural changes on all entities matching an ECS query, apply EntityManager query-overload APIs using a cached EntityQuery instead of iterating entities individually. This enables single-pass operations like destroying matched entities or adding components safely.

Iterating entities individually for structural changes causes errors because per-entity loops risk iterator invalidation during active SystemAPI.Query iteration. Using query-overload APIs avoids this by applying uniform changes in a single operation.

The best way to destroy multiple entities in a single frame is building and caching an EntityQuery during OnCreate, then invoking the single-pass destroy operation with that query to eliminate archetype thrash and runtime exceptions.

Yes, you can add or remove components from multiple entities without a foreach loop by invoking query-level EntityManager APIs on a cached EntityQuery, applying uniform structural changes across all matched entities in one pass.

Triggering structural changes inside an active SystemAPI.Query foreach loop causes iterator invalidation risks and runtime exceptions. You must avoid query-overload structural changes during iteration and apply them as separate single-pass operations.

You need batch structural changes for entity management when performing mass operations like destroying matched enemies or toggling component enabled states across uniformly affected query results, requiring a cached EntityQuery to execute safely and fast.