ecs-component-mutators

You can avoid duplicating component update logic by centralizing it in mutator classes. This approach encapsulates common update patterns into dedicated mutator instances, keeping components as pure state containers and improving system clarity.

A mutator class in ECS architecture is a dedicated structure that encapsulates reusable component update behavior. It separates behavior from data by keeping components as pure state containers while managing state updates through bound instances.

Keep TypeScript ECS components allocation-light by encapsulating behavior in mutator classes rather than components. This reduces object creation within performance-critical game loops by ensuring components remain pure state containers managed by reusable mutators.

Yes, the mutator pattern supports declarative, allocation-light ECS systems. By keeping components as pure state containers and encapsulating behavior in bound mutator instances, it maintains the declarative structure while managing state updates efficiently.

Use mutator classes when you have repetitive component update patterns across multiple systems, such as game ability cooldown timers. Mutators ensure consistent behavior, reduce code duplication, and improve overall system clarity.