Currently, rendering hatch overlays can be computationally expensive on the client side with a large number of loaded multiblocks, even if they are all spread out over a wide area.

Would it be possible to limit the distance at which the hatch overlays for multiblocks are rendered, in order to reduce the impact of loaded but distant multiblocks on client-side FPS?

The simplest and most performant check would be to verify the distance from the player to each multiblock's controller is less than R blocks before rendering its hatch overlays.

This threshold R could be 64 blocks by default, which should be enough to enable players to see where hatches can go from a distance on multiblocks whose size ranges from a simple EBF to GTNH's DTPF and Eye of Harmony.

Inspired from #983 (comment)