baking-type-cleanup-component

Track destroyed entities in Unity DOTS incremental baking by attaching a [BakingType] cleanup component that survives entity destruction, allowing you to detect missing baked components and trigger recomputation for dependent parent-level data.

Recalculate compound bounds in Unity ECS by storing the previous Parent reference in a cleanup component, comparing it to the current hierarchy during baking, and triggering parent-level recomputation when discrepancies are detected.

Cleanup components accumulate stale data across baking passes when they are not removed after processing. You must explicitly remove the cleanup component after recomputation to prevent old records from persisting and causing incorrect outputs.

Yes, applying the [BakingType] attribute prevents cleanup components from entering the runtime world in Unity DOTS by stripping them from the final runtime world, while still allowing the cleanup component to survive entity destruction within the baking world for lifecycle tracking.

The best way to handle entity lifecycle events in Unity ECS hierarchy baking is using an ICleanupComponentData cleanup pattern to track creation, re-parenting, and destruction across incremental baking passes, ensuring parent-derived data remains accurate.