TunnelVision

A CoreProtect-based x-ray detection tool for dedicated servers.

TunnelVision analyzes mining behavior recorded by CoreProtect and flags sessions that look like they were guided by information the player shouldn't have — i.e. x-ray. It doesn't try to detect x-ray in real time; instead it reconstructs each mining session after the fact and scores it based on trajectory, yield, and how directly the player moved toward ore.

🌐 tunnelvision.fr — live interactive demo, full documentation, and beta access requests.

⚠️ Status: Beta. Commands, permissions, and configuration are not yet stable and may change between versions. Not recommended for critical/large-scale production use yet — feedback and testing are welcome.

Requirements

• CoreProtect — TunnelVision reads its block-break logs; it does not log anything itself.
• Access to TunnelVision's analysis service. The plugin does no computation itself — every command queries a central API over HTTP. Access is currently a free, limited-spot beta: request access on the website to get your API key.
• Works on any Paper/Spigot 1.21 server. No local Docker or heavy setup required on your end — just drop in the jar and configure your API key.

How it works

1. The Java plugin reads mining data from CoreProtect and sends it to TunnelVision's analysis service over its API, using the key issued when your access was created.
2. The analysis pipeline reconstructs each player's mining sessions from the raw block-break events.
3. For each session, it computes trajectory and yield indicators — direction changes, straight-line "runs," ore yield per block dug, detour factor between veins, and whether turns consistently point toward the next (undiscovered) vein.
4. These indicators feed a 0–100 suspicion score with a verdict (clear / worth watching / strongly suspicious), plus an independent anomaly score (Isolation Forest, unsupervised) that flags sessions statistically unlike the rest of the server's corpus.
5. Results are available as an interactive 3D report: the mined path, ore locations, and the full breakdown of indicators for the selected session, with a per-server session leaderboard sorted by suspicion score. Reports can also be hosted on a shareable link with collaborative annotations, so they stay viewable without server access — see a live example.

What the score is (and isn't)

The 0–100 score is a heuristic, calibrated on known game mechanics (expected yield at a given depth, geometry of a legitimate grid-mining pattern, etc.) — not a trained classifier. It's meant as a triage tool to help admins decide which sessions deserve a manual look, not as automatic proof of cheating. The anomaly score adds a second, independent signal (statistical outlierness vs. the server's own data) precisely because a single heuristic can be wrong — a session flagged by one and not the other is exactly the kind of case that needs a human look before any action is taken.

Recommended use: treat every flagged session as a lead to investigate (e.g. via the visual report, or the /tp shortcut to the mined area), not as a verdict on its own.

Known limitations

• Path-straightness metrics can be distorted by common mining patterns (e.g. a 2-block-tall tunnel alternates a horizontal and a vertical step, which flattens the "straight segment" measurements for everyone).
• Thresholds are calibrated on the developer's own test data and known game knowledge; they haven't yet been validated against a large labeled real-world dataset.
• A player who mixes legitimate mining and x-ray behavior within the same session will have their score diluted.
• A player exploiting cave networks and only digging the last block or two toward a vein can partially evade the "dig yield" signal.

Roadmap

• Stabilize in-game commands and permissions.
• Improve path-simplification to better separate genuine strip-mining grids from erratic x-ray paths.
• Recalibrate score thresholds against real (non-synthetic) labeled data.
• Sliding-window scoring within a session, to catch players who only cheat part of the time.

📚 Full documentation, including every config key: tunnelvision.fr/documentation.html

Feedback, bug reports, and testing on real servers are especially valuable at this stage — this is beta software.