Currently, RayWorldCollider in Etcetera has a number of optimizations that are specifically tuned for the "close enough" approach required by Glitter. However, these optimizations make it almost unusable for other purposes. We need to move the current "close enough" implementation into Glitter and replace the version in Etcetera with a more precise version.
One decision that needs to be made before implementing the precise version is how much caching should be done. Out of anything, the VoxelShape -> List<AxisAlignedBB> cache is the most likely to stay, though I'll have to check whether things like EnderIO pipes are using "mutable" VoxelShapes (in that the returned AABBs can vary).
Currently,
RayWorldColliderin Etcetera has a number of optimizations that are specifically tuned for the "close enough" approach required by Glitter. However, these optimizations make it almost unusable for other purposes. We need to move the current "close enough" implementation into Glitter and replace the version in Etcetera with a more precise version.One decision that needs to be made before implementing the precise version is how much caching should be done. Out of anything, the
VoxelShape->List<AxisAlignedBB>cache is the most likely to stay, though I'll have to check whether things like EnderIO pipes are using "mutable"VoxelShapes(in that the returned AABBs can vary).