VibeCity

Yeah, I was thinking of it more as the backing for the EntitySets themselves… like a classic console ECS where memory streaming was paramount. In that case, there would just be one giant array of component parts. Each ‘row’ would be an entity with all of the component data in it. The ‘Entity’ would be the interface to that. Once the “query” is performed to gather the data it would be flattened. With an EntitySet, it’s relatively rare to look things up by entity ID. Generally we’re looking for adds/removes or iterating over the whole array. I guess currently the add/remove sets are by ID so that would be one ‘that’s a shame’ place. Otherwise, the entity set user would almost never even care about the ID of things. Edit: note that it’s questionable whether or not this is a “good idea” in Java. Just from a “this would be like a ‘real’ ECS” perspective, it’s an interesting though experiement at least.