Difference between revisions of "Entity Component System"
(Add link to A Handful of Components article) |
(Add link to Entity Systems Project) |
||
| Line 12: | Line 12: | ||
* [http://altdevblogaday.com/2011/10/08/a-handful-of-components/ A Handful of Components], descriptions of some useful components by Michael A. Carr-Robb-John | * [http://altdevblogaday.com/2011/10/08/a-handful-of-components/ A Handful of Components], descriptions of some useful components by Michael A. Carr-Robb-John | ||
* [http://entity-systems.wikidot.com/ Entity Systems Project], an entity component system wiki | |||
Revision as of 08:41, 17 March 2012
An entity component system is a way to implement your game objects so that you can build their functionality through composition instead of object-oriented inheritance. The prevailing wisdom in current game development seems to be that complex games should have one of those instead of an inheritance-based object system that is likely to lead to unmaintainable blobs of a class. A roguelike is probably a complex enough game that you should use an entity component system in one.
The basic idea is that game objects at their core are just unique identifiers (UIDs), plain strings or integers, instead of complex objects. The complex data and functionality is moved into multiple components, which are stored in their own containers and associated with the object UIDs.
This makes it easy to have data-driven object construction and allows very diverse combinations of component loadouts in objects that still coexist in the same game world as the same fundamental type of program object.
The Teratogen roguelike uses a simple component system.
References
- Good overview and links on Stack Overflow: http://stackoverflow.com/questions/1901251/component-based-game-engine-design
- A Handful of Components, descriptions of some useful components by Michael A. Carr-Robb-John
- Entity Systems Project, an entity component system wiki