dustcontributor / dustartemis Goto Github PK

Entity objects look less and less useful each time I look at them.

Its one layer of pointer indirection, plus around 20 bytes of overhead per instance, using int arrays erases the whole idea of pooling entity objects (but it introduces the idea of pooling component bit sets).

There should be some mechanism to pool components. End of story.

Silly distinction. They both go through exactly the same things inside World instance. Since EntityObserver doesn't has a World instance, EntitySystem defines it, also Manager defines it.

Other methods like 'initialize' and such could easily be implemented for all EntityObserver, Managers and EntitySystems alike, regardless of their nature.

The only real difference is that EntitySystems inspect which entities they're interested in through Aspects, but they do that on their own, public API is just EntityObserver methods.

They'll get equalized.

Brooooookeeeeen. Gotta fix it.

Yup. Doing this. Someday.

Now with the configuration file, it's possible to add parametrized entity pooling. Working on that.

Well, this should be a good way to try out GitHub's issue system.

Plenty of parameters around should be configurable.

• Bag's default capacity.
• Bag's grow rate theresold.
• Entities alive in the world (as an approximation rather than fixed maximum).
• Component types present in the world (aprox).
• Entities alive per system (aprox).
• Mappers per system (aprox). This one is more of a "just because I can", can shave off a millisecond or two in mapper initialization. Prolly overkill.

Need to review if there is anything else.