class Entity
{
BehaviourObj behavObj;
DrawObj drawObj;
etc.
}
class Player(or Enemy, or Bullet, or whatever): public Entity
{
}
class Player(etc.)
{
Entity * entity;
}
GoEntity | |- contains - RenderModel |- contains - RigidBody |- contains - SoundSourceQuote:Original post by Ariste
I've adopted an outboard component system and it's worked pretty well so far. In a nutshell, it works like this:
An entity is created and a message is sent out to interested listeners. Listeners inspect the entity and, if they're interested, create internal 'subsystem-level' component representations. A graphics subsystem, for example, might create a Renderable for each visual entity. From then on each subsystem does its own thing, querying the entity for any information it doesn't store internally.
It's pretty simple to set up once you get your head around it, and I haven't run into any complications yet. Let me know if you have any questions [smile]
entity.addComponent(Movement, MovementType.WALKING);switch(entity.MovementType) case MovementType.FLYING: entity.y--;entity.x++; case MovementType.WALKING: entity.x++ case MovementType.CIRCLING: entity.x = sin(entity.x++)... etc?!Quote:(Does anyone know of a simple (perhaps the most simple!) implementation of say, a pong game or even just a demo?)Simple, or even complex-ish games, don't NEED an entity/component system. Applying one just makes things more confusing, without clearly showing the benefits or even the purpose of such systems.
Quote:I'm not sure what you're describing here. If you had different types of movement, you'd probably have different subclasses of MovementComponent, each one with a different type of movement, and you'd put the correct one into each entity. That's just one approach, though.
The part I am stuck on at the moment is: does each component have to know how to deal with every single "type" of entity? For example, if you have MovementComponent which updates each entity... how do assign the algorithm for the different types movement? When set the component up for an entity do you give it a type... for example
entity.addComponent(Movement, MovementType.WALKING);
and do something like this for each entity inside it's update method?
