baking-type-component

To prevent intermediate baking data from leaking into the runtime ECS world, apply the `[BakingType]` attribute to your temporary `IComponentData` or `IBufferElementData`. Baking systems can safely read this staged data before it is automatically stripped from the final runtime output.

The best way to pass staging data between Bakers and baking systems in Unity DOTS is using `[BakingType]`-annotated components. This creates a typed message channel for multi-stage baking pipelines, allowing baking systems to consume temporary transformation data without polluting runtime archetypes.

You need baking-only components in Unity DOTS when your baking pipeline requires cross-entity aggregation, blob asset staging, or multi-stage transformations. These temporary typed message channels let baking systems read intermediate data that cannot be expressed directly in the final runtime component.

Yes, Unity automatically strips `[BakingType]` components from the runtime ECS world after baking systems complete. This prevents archetype pollution and runtime misfires by ensuring intermediate Baker-to-baking-system data remains isolated from the final destination world.