Celeste

I've heard this so often, and I still don't quite get it. Let's say most of my game objects have a "Position" component, and all the X/Y coordinates are now in one big integer pool. With this setup I can now add 5 to each object's X position really efficiently. But what's the use case for that? Particle systems, and what else? My game objects always look more like Celeste's Twitter-infamous Player class: https://github.com/NoelFB/Celeste/blob/c32f134d210fcf710d750... Say about the length of the file what you want, but isn't it actually better for caching that all of the Player's instance variables are in one object, and not stored in components somewhere else? (Now, maintainability is another issue. But I've always found Ruby-style mixins much easier to reason about than the toy ECS systems I've seen.)

Project is seemingly dead with the latest commit being from 2018. Two major games with code on github I can think of are Amnesia: The Dark Descent (1) and Celeste (2) (1) https://github.com/FrictionalGames/AmnesiaTheDarkDescent (2) https://github.com/NoelFB/Celeste