Contents
What are the characteristics of an entity component system?
ECS (“Entity Component System”) describes a design approach which promotes code reusability by separating data from behavior. Data is often stored in cache-friendly ways which benefits performance. An ECS has the following characteristics:
Where are the components of an entity stored?
Common ECS approaches are highly compatible, and are often combined with data-oriented design techniques. Although an entity is associated with its components, those components are typically not necessarily stored in proximity to each other in physical memory.
Who is the founder of Entity component system?
In particular, Martin’s work popularized the ideas of “systems” as a first-class element, “entities as IDs”, “components as raw data”, and “code stored in systems, not in components or entities”. In 2015, Apple Inc. introduced GameplayKit, an API framework for iOS, macOS and tvOS game development that includes an implementation of ECS.
How to track which components an entity has?
Since an entity is simply an ID, we need a way to track which components an entity “has”, and we also need a way to track which components a system cares about. I chose the very simple approach of using a std::bitset (modern C++ equivalent of a bitfield), called a Signature.
How are entities matched with systems in ECS?
Archetypes (aka “Dense ECS” or “Table based ECS”) Sparse set ECS (aka “Sparse ECS”) Bitset based ECS Reactive ECS How are components modified? How are entities matched with systems? How-to How to create a hierarchy in ECS?
How are objects and components organized in ECS?
Instead, objects (entities) are composed out of a set of simple datatypes (components). A component in ECS is data only and may not contain any behavior. Instead, behavior in ECS is organized in functions (systems) that are dynamically matched against matching entities, based on their set of components.