Detecting X-Ray on Minecraft Servers: Signs and Checks

X-ray lets a player see ores, caves and chests through solid blocks, which wrecks survival economies and fair play. It is quiet by nature: nobody gets hit and nobody sees a flying player, so it often goes unnoticed for weeks. This article covers the signs staff can spot and the difference between the two common forms.

Two very different kinds of X-ray

Not every X-ray is a hacked client, and the distinction changes how you investigate.

Texture-pack X-ray: A resource pack makes most blocks transparent so ores stand out. It runs entirely in the player's game folder and sends nothing special to the server. It is simple, common and sometimes allowed or blocked by server rules.
Client-based X-ray: A modified or injected client alters rendering, or reads block data, to reveal ores. It can be more flexible than a pack and is usually treated as a full cheat under your rules.

Server-side tools can often hide ores from clients that should not see them, which helps against both. But you still need to know who is cheating, which is where behaviour comes in.

Mining patterns that raise suspicion

Honest miners explore. X-ray users head straight for the valuable blocks. Look for:

Straight tunnels that bend exactly to ore. The path avoids stone and turns sharply toward diamonds or ancient debris that were never visible.
Very little wasted digging. A high share of mined blocks are ores, with almost no random branches.
Ignoring obvious caves. A player skips open cave ore that is easy to see and tunnels to buried ore instead.
Fast results on new accounts. A fresh player arrives with a stack of diamonds after a short session.
Digging toward hidden chests or spawners. They go directly to structures with no surface clue.

Use numbers, but carefully

Most anticheat and logging plugins can show how many ores a player mined compared with stone over a session. Ore ratios are a useful starting signal, but they are noisy. A lucky player, a world with generous ore generation, or someone following a known ore-rich spot can all produce odd numbers. Compare against other players on the same world, over a long enough time window, and treat a single session with caution.

A more reliable approach is to combine ratio data with what you can observe. The overview in how to detect cheaters on a Minecraft server explains how to weigh several weak signals into one confident decision.

How staff verify a suspicion

Review mining logs. Check block break history for the suspect's path, using coordinates and timestamps rather than impressions.
Spectate or inspect their tunnels. A tunnel that clearly bends toward ore through solid stone is easier to explain than a statistic.
Ask for a client check. A texture-pack X-ray is a file in the resource packs folder, while a client X-ray lives in the game or launcher. A manual look is covered in the screenshare guide for staff, and the difference between cheat types is in common Minecraft cheats explained.
Decide against your rules. If your server bans resource-pack X-ray, say so clearly in advance so the verdict is not a surprise.

What a scan can add

Ore statistics tell you a player mines suspiciously. They do not tell you which tool is responsible. With Kara Detector, staff enters the player's name, Kara creates a single-use code, and the player accepts in the app and types it. The scan runs and a report usually arrives in the staff panel in under a minute, verdict first, with details underneath.

Remember that it is a decision aid. False positives are possible, and your staff makes the final call, ideally alongside the mining logs you already have.

Prevention helps too

Detection is only half the answer. Many servers also enable ore obfuscation, which sends fake block data for hidden ores so that X-ray shows nothing useful. It does not remove the need for staff review, but it reduces how much damage a cheater can do while you investigate. Keep your rules explicit about texture packs, publish them, and apply them evenly.

Next step

If mining logs raise a flag but you cannot tell what is installed, a client check closes the gap. See the Kara Detector plans and how a Kara check works.