You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For now we only have the underlying octree implementation (which works flawlessly) and the ability to visualize the octree repartition of a single cuboid region. No data is preserved at all and this needs to be sorted out.
Since the idea is for each minecraft region (mcr) to store its own octree, in the case of some claim existing in that area (this library focuses on only storing/loading as much data as it needs to) we need to figure out a way to load and unload an octree state from a sort of storage.
The text was updated successfully, but these errors were encountered:
For now we only have the underlying octree implementation (which works flawlessly) and the ability to visualize the octree repartition of a single cuboid region. No data is preserved at all and this needs to be sorted out.
Since the idea is for each minecraft region (mcr) to store its own octree, in the case of some claim existing in that area (this library focuses on only storing/loading as much data as it needs to) we need to figure out a way to load and unload an octree state from a sort of storage.
The text was updated successfully, but these errors were encountered: