Connecting a Traditional OO Inheritance Hierarchy to a Component-Based Entity System

This page summarizes the projects mentioned and recommended in the original post on /r/gamedev

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • Nez

    Nez is a free 2D focused framework that works with MonoGame and FNA

  • I have an entity-based component system based on Nez that implements most of the lower level functionality of my game, such as animation, rendering, physics, and collision initiated interactions. It was originally supposed to be an ECS but now I consider it more of an entity-based component system since the components are more about adding functionality to entities, rather than data and there (currently) are no separate systems. I've implemented a custom messaging system, of which I am quite proud, so that when one component needs to send a message to another component it doesn't have to perform a lookup using reflection nor does it need to always store a reference to that component.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts