moecs - easy to use entity component system crafted with odin

modev

I am writing this project in my spare time, just like all my other hobby gamedev. If you want the highest performance, it's best not to use any ECS. I love ECS because it allows you to systematize and separate/parallelize logic/data, move each part of the game into its own system, customize its operation, and generalize logic for entities with different components. moecs only has the basics and doesn't yet have some of the features found in others (hierarchy, relationships, prefabs, etc.) and perhaps will never have because of performance overhead. But if you really need some feature you can open an issue. As for speed, it will vary on different computers. You can play around with main.odin, and see the benchmarks (I use this code for testing). I'd be interested in seeing your results.

My tests show this:

With 7 components, 3 systems, 1 million entities, 6 archetypes, world progress 100 times takes 56 milliseconds (at each iteration: 1 system adding component to 100 entities and despawning one entity and 2 others getting 6 components for each entity)

Complete description with examples you can find in readme on github: helioscout/moecs

I also built simple space game as a demo.
helioscout/mouniverse

Peter

Nice. I read the Wikipedia article but still don't fully understand what an ECS is.
https://en.wikipedia.org/wiki/Entity_component_system
As far as I understand it, it helps to "manage" 3D objects and complex data.

This ECS is usable only with the Odin programming language?

modev

Yes, this one only with Odin.
Very popular one is flecs - https://flecs.dev.
It have bindings to other languages.
ECS helps write game logic in data oriented style.
You create entity, it can be a spaceship, then you add Position, Sprite, Rotation components.

You have a systems - functions that select entities/components by some configuration (set of them) and you can iterate through entities and make some actions, draw them for example, or update their components values based on physics changes in other system.
Systems executes one by one, so you craft your game logic this way.

If you have collision from physics library you can add Collision component (data struct instance) to collided entities and in some other system you select such entities and make some actions, draw spark or smth.

ECS is just a tool, many devs do not like them.
I like for the reason I wrote in first message of this post.

Peter

modev Ah, I understand now. Thanks for the explanation.

For small games an ECS is overkill I think. But I can see its use cases now. :) Edit: For example quests in an RPG I think. But many other stuff, too.