No production release yet

Minecraft integrity,
clearly scoped.

A portable Windows scanner for staff-assisted reviews. It checks bounded Minecraft evidence with explicit consent—without claiming to inspect or clear an entire PC.

  • No installer
  • No administrator access
  • Consent before collection
3ab3ali scan
SCAN SCOPEMinecraft evidence only
BOUNDED
Mod inventoryResolved game roots
Complete
Game processesSame user · Windows
Coverage shown
Signed rulesLocally verified pack
Verified
Hard scope boundaryNo browser data, credentials, screenshots, personal documents, or raw process memory.
01Portable Windows app
02Explicit consent gate
03Minimized staff report
04Manual review required
Bounded by design

What the scanner actually checks

The scanner gathers a narrow set of Minecraft integrity signals. Every collector reports its own limits instead of turning missing access into a misleading result.

01

Minecraft mod JARs

Names, sizes, archive metadata, and SHA-256 fingerprints beneath resolved Minecraft game roots.

02

Active game context

Same-user Java and Minecraft process identity, plus loader-visible on-disk module identities where Windows permits.

03

Signed rule matching

Locally verified rules compare bounded observations with known indicators. Rules are signed before evaluation.

04

Coverage-aware report

The result records what completed, what was limited, and what failed—so missing visibility is never hidden.

About deleted cheats: this tool does not pretend to reconstruct deletion history. It reports current, bounded observations and honest coverage; absence is not proof that a file never existed.

A visible process

Consent first. Evidence second.

A scan begins with a one-time staff request. The player sees what will be inspected and uploaded before anything runs.

  1. 1
    Staff creates a scan request

    A short-lived ticket binds the player, policy, and signed rule pack.

  2. 2
    Player reads and consents

    The app lists local collection, upload fields, and explicit exclusions.

  3. 3
    Bounded collectors run

    Item, byte, and time budgets keep the scan predictable and scoped.

  4. 4
    Staff receives a minimized summary

    Findings and coverage go to the secured backend for human review.

Results with context

A verdict is not a conviction.

Results describe configured rules and measured coverage. Staff must review them alongside legitimate mod use and scan limitations.

INDICATORS_FOUND

At least one configured rule matched an observed indicator.

Staff actionStaff review the finding and context. It is not automatic proof.

NO_INDICATORS_OBSERVED

No configured rule matched within fully completed expected coverage.

Staff actionThis does not mean the whole PC—or even every possible cheat—is clean.

INCOMPLETE / INCONCLUSIVE

Required visibility was partial, unavailable, or internally inconsistent.

Staff actionStaff treat the result as limited evidence, never as a failed scan by the player.

No verdict should automatically ban, punish, or clear a player.

Privacy boundary

Useful evidence. Less exposure.

Designed to report

  • Opaque scan and client identifiers
  • Collector coverage, counts, bytes, and duration
  • SHA-256 digests and redacted rule findings
  • Rule-pack identity and verification status

× Explicitly excluded

  • Raw files or raw process memory
  • Credentials, browser, or Discord data
  • Screenshots and personal documents
  • Arbitrary filesystem or command-line contents
Development test channel

Test the Windows GUI now

Unsigned · loopback-only · not a production release.This bundle is for the local demo workflow. It cannot connect to the public scanner API or Discord.

The ZIP contains the portable Windows GUI and exact PowerShell test instructions. The EXE needs no installer, administrator access, or runtime dependency. The temporary local demo still requires this repository and Go.

  1. Start the local cmd/devdemo backend.
  2. Launch the GUI with all four arguments printed by that run.
  3. Paste the one-time code—not the Ticket ID or Scan ID—then select Review scan request.
  4. Consent unlocks only after the exact request and disclosure load.
Download development test (.zip)

Windows may warn because this test build is not Authenticode-signed. Do not disable antivirus. Verify the hashes shown here before running it.

Channel
Development test only
Version
2.0.0-dev
Bundle size
4.79 MB
ZIP SHA-256
95befb73b995e4dbfa86dbf2fad0d7470890e78f77956966e75d659035b90bba
EXE SHA-256
b3cd1aa2aed8e7e093b95f0b10b780700f41a11dfa51fce5248c18a13456f5d6
Build state
Built from a modified development worktree
Release integrity

Release verification pending.

Every public executable must have canonical release metadata and an Ed25519 statement verified by a pre-approved key before its download button can activate.

Release validation in progress

Do not download development builds shared through messages or unofficial mirrors.

Platform
Windows 10/11 · 64-bit
Version
Pending signed release
SHA-256
Published when the production binary is signed
Signature
Verification material pending
Signing key
Approved production key pending
Signed at
Canonical UTC timestamp pending