This can be partially worked around by making If the client is able to obtain the world seed, it is able to know the real location ofĮvery generated ore, completely bypassing Anti-Xray. Seed Reversing: Another attack vector is the deterministic nature of Minecraft's world This can be mitigated by any competent anti-cheat plugin however, this is not It is possible to, on a default server, extend the range of real ores you can see by a not Because of how Anti-Xray is (and has to be) implemented, Server, it is not by any means infallible. Range Extension: While Anti-Xray alone will prevent the majority of users from Xraying on your engine-mode: 3 can reduce network load when joining by a factor of ~2 and helps with chunk packet compression. Hidden-blocks, engine-mode: 2 will effectively hide all ores, even those exposed to air.

With engine-mode: 2, fake ores obstruct the view of real blocks.

Ores exposed to air in caves or water from a lake will not be With engine-mode: 1, only ores that are entirely coveredīy solid blocks will be hidden. The following images 1 show how each mode will look for a player using Xray with the recommendedĬonfiguration in both the overworld and nether.Įspecially on the client side, engine-mode: 1 is much less computationally intensive, whileĮngine-mode: 2 may better prevent Xray. engine-mode: 3 works the similarly to engine-mode: 2, but instead of randomizing every block, it only randomizes blocks per chunk layer. In contrast, engine-mode: 2 will replace both hidden-blocks and replacement-blocks Other 'fake' blocks, stone ( deepslate at y < 0), netherrack, or end_stone based on theĭimension. engine-mode: 1 replaces specified blocks ( hidden-blocks) with For reference documentation,Īnti-Xray has three different modes. This guide is a step-by-step walk-through for configuring Anti-Xray. If you aren't already familiar with per world configuration, please take a moment to familiarize

Base xrays minecraft downloads