is presently its sole maintainer,
You can support him:
Scaling low-frequency entity updates
Revising the tile map
Thinking about changing tile map to store entities instead of tiles
Options for how to reference entities in memory
Storing entities in tile entity blocks
Thinking of a technique to improve low entity access
Going in the other direction
Removing invalid code
Thinking about the size of the tile_map TileChunkHash
Renaming tile_map to world
Do you still expect the gameplay to be broadly grid-based even without tiles?
Could you use reflection to help handle the entities and world chunks?
Will everything in the game be an entity even if it does not need collision detection or movement?
Don't you think most of the storage concerns stem from having just high and low entities and would be solved by having more granularity there so you have more and smaller arrays of entities with some particular aspect?
You mentioned considering having the world chunks store a fixed entity count and then add multiple chunks to the hash table if necessary to store more entities. If you were to go that route, how would you compare one chunk to another? Multiple chunks would have the same X,Y,Z.
In terms of handling entity compression and decompression, where would you grab/store the state of objects that are coming in and out of the update scope?
Why do you call C compiled with a C++ compiler “C++”?
Why can't world_position just have a pointer to a world_chunk instead of all those AbsTiles? Then Offset_ is relative to the world_chunk.
I didn't get to watch the entire stream so I don't know if you considered it, but why don't you have a flag for “about to be deleted” that every entity checks against and nulls pointers. Have it visible for all entities for one frame.
Do you think the todo puzzler will be handled tomorrow, and do you often sleep on decisions like that?
(follow-up) What I was getting to is that we seem to be working towards what's called the Entity Component system where what we call now “high” and “low” are just components alongside anything else we want to add to entities later.
Seeing that the computer handles 1 million entities without lagging, do we really need to worry about the performance hit coming from one extra pointer dereference?
Will entities be able to transfer from one chunk to another?
Will we start using the entity system for something other than players/walls soon or will the renderer come first?