ecs_component_design

Design cache-friendly ECS components by using unmanaged record structs with blittable fields, keeping sizes under 64 bytes, and applying hot/cold splitting to optimize memory layout for Arch ECS codebases.

Tag components in ECS are empty data markers used for efficient entity querying without adding memory overhead. Use them to group entities for fast filtering when no additional component state is required.

You cannot use Godot types or references inside Arch ECS components. Components must remain engine-agnostic and contain only unmanaged fields, with constraint checks preventing any Godot dependencies or logic from entering the data layout.

ECS components need to be unmanaged structs in .NET 8 to ensure cache locality and enable thread-safe processing. Unmanaged record structs prevent garbage collection overhead and keep game logic fast and testable.

The best way to split hot and cold data in game architecture is to separate frequently accessed component fields from rarely used ones into distinct structs. This hot/cold splitting improves cache locality and query performance in ECS systems.

Handle entity ID references in cache-friendly components by storing them as unmanaged blittable fields within the struct. Include validation rules and thread-safety documentation to ensure safe entity references across parallel ECS systems.