F
Federal SMP
Minecraft Moderation

Recognizing Bypass Attempts

Chapter 4 — How to recognize the signs that a player is trying to hide cheat clients before or during a screenshare.

Some players try to hide cheat clients rather than remove them before a screenshare. This chapter teaches you to recognize the signs of these attempts so you know when to slow down, ask more questions, and involve a second staff member — it is not a technical manual for performing these techniques yourself, and staff should never attempt to reproduce or "test" any of them.

Self-Destructing / Self-Deleting Clients

Some modified clients are built to erase themselves — deleting their own files, or reverting a folder to a clean state the moment they detect the game closing, a screenshare tool opening, or certain processes starting. The tell is usually behavioral rather than visual: a player stalls before starting the game, closes Minecraft unusually fast right before or during a screenshare request, or a folder that should logically contain client files appears freshly emptied with recent deletion timestamps and nothing to show for it.

Renamed or Disguised Files

A cheat client's files can be renamed to look like ordinary system or game files. The sign to watch for is not any single filename, but a mismatch: a file claiming to be an innocuous system component sitting somewhere it has no reason to be (inside the Minecraft or mods directory, for instance), or a file whose properties, size, or modification date do not match what a genuine file of that name should look like.

Hidden Data Streams & Unusual Storage Locations

On some systems, data can be tucked away in locations that do not show up in a normal folder listing. If a player's visible files all look clean but their behavior or a flag still strongly suggests cheating, that is a signal to loop in a more experienced Admin rather than clearing the player — this kind of concealment is beyond what a standard screenshare checklist alone can rule out.

Process Concealment

Some tools attempt to hide their own process from Task Manager, or run disguised as part of a legitimate program. Warning signs include a player's system resource usage (CPU/RAM/GPU) not matching what should be running based on the visible process list, or a player who is unusually eager to close Task Manager quickly or redirect your attention elsewhere during the check.

Virtual Machines

A player may claim their "real" computer is clean while actually playing from within a virtual machine that contains the cheat client, keeping their host system apparently clear. Signs include unusual display resolution or window behavior consistent with a VM, a "too clean" or freshly-installed-looking operating system with no personal files or history, or noticeably degraded performance inconsistent with their stated hardware.

WHAT TO DO WHEN YOU NOTICE THESE SIGNS

Do not accuse. Stay calm and professional, note exactly what you observed, and bring in a second Moderator or an Admin before drawing any conclusion. Evasion behavior itself is a strong signal, but the final decision should always involve more than one set of eyes given how serious the outcome can be.


Quick Review — Q&A

Q: What is the key sign of a self-deleting client, since the files themselves may already be gone?

A: Behavioral: unusual stalling or rushing right before/during a screenshare, and folders showing recent deletion activity with nothing left to inspect.

Q: How do you spot a disguised/renamed cheat file?

A: Look for a mismatch — a file that claims to be something ordinary but is sitting somewhere it shouldn't be, or whose size/date doesn't match a genuine file of that name.

Q: If a player's visible files look completely clean but everything else points to cheating, what should you do?

A: Do not clear them on file-check alone — escalate to a more experienced Admin, since some concealment goes beyond what a standard check can rule out.

Q: What is a warning sign that a player may be running the game from a hidden virtual machine?

A: A 'too clean' OS with no personal history, unusual display/window behavior, or performance that doesn't match their claimed hardware.

Q: What is the one rule that applies to every sign in this chapter?

A: Never accuse based on a single observation — document what you saw and bring a second staff member before making a decision.

On this page