dots-event-driven-ecs

What problem does it solve?

This Skill prevents hard-to-debug ECS gameplay issues caused by treating one-frame events as unmanaged or persistent state, ensuring events are consumed exactly once and cleared reliably.

Core Features & Use Cases

• Explicit one-shot event modeling: Choose the correct event shape (request entity, enableable command component, or event buffer) based on lifetime and broadcast needs.
• Deterministic producer/consumer ownership: Enforce exactly-one consumer semantics (or an explicit broadcast contract) to avoid double-application and missed consumption.
• Burst-safe, replay-safe anti-pattern guidance: Reject managed-world event patterns (C# events, UnityEvent, static buses) and highlight failure modes like wrong ECB phase ordering and un-destroyed request entities.

Quick Start

Ask the agent to refactor your ECS gameplay flow so every one-frame UI/input/network trigger becomes a request entity, an enableable command component, or an event buffer with a clearly defined single consumer and a guaranteed clearing/destroy step.