Octree Implementation

[Gregorius (Gregorius Techneticies)]

@CanisArtorus

The trouble is when removing the block, one will have to check all siblings to see if the material was inherited only from the single point that was just removed. Yes, still not up to Root in general, but a much larger computational overhead.

The worst case would be if you removed the only piece of Cobblestone that existed on the entire Planet, which considering how I plan on spontaneously generating “Block States”, might be a very common case actually. However I dont think that will matter a lot, because if you have looked at how Minecraft handles the setBlock Function, yeah that one is inefficient as fuck and will likely be much more laggy than my Octree thing.

@CanisArtorus

Caching up to the eight corners of AABB for the entity collision, versus caching a single point location, to avoid traversing from Root to find world blocks at the entity’s coordinates makes a lot of sense for large worlds. Bit of memory vs search balance there, and relies on how easily siblings are linked for the search.

After thinking about it, it could just be always 8 Nodes too, if that makes iteration for collision and storing the Nodes easier, since even if you happen to be in 1 Node, that Node could still be split in 8.