Question

For a 2D game I’m making (for Android) I’m using a component-based system where a GameObject holds several GameComponent objects. GameComponents can be things such as input components, rendering components, bullet emitting components, and so on. Currently, GameComponents have a reference to the object that owns them and can modify it, but the GameObject itself just has a list of components and it doesn’t care what the components are as long as they can be updated when the object is updated.

Sometimes a component has some information which the GameObject needs to know. For example, for collision detection a GameObject registers itself with the collision detection subsystem to be notified when it collides with another object. The collision detection subsystem needs to know the object’s bounding box. I store x and y in the object directly (because it is used by several components), but width and height are only known to the rendering component which holds the object’s bitmap. I would like to have a method getBoundingBox or getWidth in the GameObject that gets that information. Or in general, I want to send some information from a component to the object. However, in my current design the GameObject doesn’t know what specific components it has in the list.

I can think of several ways to solve this problem:

1. Instead of having a completely generic list of components, I can let the GameObject have specific field for some of the important components. For example, it can have a member variable called renderingComponent; whenever I need to get the width of the object I just use renderingComponent.getWidth(). This solution still allows for generic list of components but it treats some of them differently, and I’m afraid I’ll end up having several exceptional fields as more components need to be queried. Some objects don’t even have rendering components.

2. Have the required information as members of the GameObject but allow the components to update it. So an object has a width and a height which are 0 or -1 by default, but a rendering component can set them to the correct values in its update loop. This feels like a hack and I might end up pushing many things to the GameObject class for convenience even if not all objects need them.

3. Have components implement an interface that indicates what type of information they can be queried for. For example, a rendering component would implement the HasSize interface which includes methods such as getWidth and getHeight. When the GameObject needs the width, it loops over its components checking if they implement the HasSize interface (using the instanceof keyword in Java, or is in C#). This seems like a more generic solution, one disadvantage is that searching for the component might take some time (but then, most objects have 3 or 4 components only).

This question isn’t about a specific problem. It comes up often in my design and I was wondering what’s the best way to handle it. Performance is somewhat important since this is a game, but the number of components per object is generally small (the maximum is 8).

The short version

In a component based system for a game, what is the best way to pass information from the components to the object while keeping the design generic?

Answer 1

We get variations on this question three or four times a week on GameDev.net (where the gameobject is typically called an ‘entity’) and so far there’s no consensus on the best approach. Several different approaches have been shown to be workable however so I wouldn’t worry about it too much.

However, usually the problems regard communicating between components. Rarely do people worry about getting information from a component to the entity – if an entity knows what information it needs, then presumably it knows exactly what type of component it needs to access and which property or method it needs to call on that component to get the data. if you need to be reactive rather than active, then register callbacks or have an observer pattern set up with the components to let the entity know when something in the component has changed, and read the value at that point.

Completely generic components are largely useless: they need to provide some sort of known interface otherwise there’s little point them existing. Otherwise you may as well just have a large associative array of untyped values and be done with it. In Java, Python, C#, and other slightly-higher-level languages than C++ you can use reflection to give you a more generic way of using specific subclasses without having to encode type and interface information into the components themselves.

As for communication:

Some people are making assumptions that an entity will always contain a known set of component types (where each instance is one of several possible subclasses) and therefore can just grab a direct reference to the other component and read/write via its public interface.

Some people are using publish/subscribe, signals/slots, etc., to create arbitrary connections between components. This seems a bit more flexible but ultimately you still need something with knowledge of these implicit dependencies. (And if this is known at compile time, why not just use the previous approach?)

Or, you can put all shared data in the entity itself and use that as a shared communication area (tenuously related to the blackboard system in AI) that each of the components can read and write to. This usually requires some robustness in the face of certain properties not existing when you expected them to. It also doesn’t lend itself to parallelism, although I doubt that’s a massive concern on a small embedded system…?

Finally, some people have systems where the entity doesn’t exist at all. The components live within their subsystems and the only notion of an entity is an ID value in certain components – if a Rendering component (within the Rendering system) and a Player component (within the Players system) have the same ID, then you can assume the former handles the drawing of the latter. But there isn’t any single object that aggregates either of those components.