Skip to content
David Saltares edited this page Aug 3, 2014 · 6 revisions

Ashley offers a very simple and easy to understand API. Here is an UML class diagram that will help you understand Ashley's architecture.

  • Entity: simple containers of components.
  • Component: base class for your game components, they are supposed to be bags of data with no logic whatsoever.
  • ComponentMapper: provides super fast component retrieval of entities.
  • Family: used to represent a set of entities with a specific collection of components.
  • Engine: mains class of the framework, manages all entities, systems and listeners.
  • EntitySystem: allows you to implement game logic that may operate on entities of a given family.
  • EntityListener: can be used to be notified of entity related events.