ClientModGate

Your server. Your rules for client-side mods.

Some servers allow minimaps; others don't. ClientModGate lets you set rules for known client mods and review the information your players' clients expose to the server.

It runs on your Paper server. Players don't need to install a companion mod, and ClientModGate 3.0 does not require PacketEvents.

How it works

When a player connects, ClientModGate checks the available client information against your installed rules. A matching rule can be allowed, monitored, or blocked. You can also scan an online player and open their report.

Features

Feature	What you can do
Built-in rules	Start with 38 rules for cheat clients and mods that a server may consider an advantage. Review them and choose what fits your server.
Player inspection	See detected matches, exposed client components, loader information when available, and confidence details.
Rule modes	Set each rule to Allow, Monitor, or Block.
Modular files	Manage individual .cmg rules, each with its own policy.
Add rules	Browse Modrinth or CurseForge, or import a local mod archive to create a compatible rule.
Punishments	Kick blocked matches by default. Configure strikes, temporary bans, or permanent bans if you want them.
Staff alerts	Receive private alerts and open player reports or available replays.
History and logs	Review saved scans, sanctions, rule changes, and other administration activity.
Administration	Use in-game menus, commands, or the console.
Languages	Use English or French and edit the message files.

Your rules, your choice

The catalog includes rules for clients such as Meteor and Wurst, as well as mods like Xaero's Minimap and Litematica. A rule's presence doesn't guarantee a detection: some clients do not expose enough information to match it. You decide which rules are suitable for your server.

• Allow keeps the rule available without blocking the player.
• Monitor records the match and notifies staff without enforcing it.
• Block applies the configured action when the rule's requirements are met.

On a fresh installation, blocked matches result in a kick. If you enable progressive punishments, configure the strike actions you want: the default entries are kicks.

Player reports

Open a player's profile to see the client information ClientModGate has observed, including allowed and monitored matches. Staff can run a new scan, review previous results, and open reports from alerts. The loader shown is a best-effort identification; Fabric or NeoForge alone is not treated as evidence of cheating.

Add more rules

Search Modrinth from the plugin, use CurseForge with your own API key, or place a supported local archive in the import folder. ClientModGate checks the file and creates a rule only when it can extract suitable information; it does not install the client mod on your server.

Anti-cheat and replay

ClientModGate also includes packet and behavior checks and a server replay system. Replays let staff review recorded players and entities, pause, seek, change speed, and follow a player.

Anti-cheat and Replay are experimental and disabled by default. Replays reconstruct movement and entities in the current world; they are not screen recordings or complete recordings of past blocks.

Network information

The optional Network module can show country and provider information and can be configured to kick connections identified as VPNs. It is disabled by default. When enabled, it sends the public IP address to the configured lookup service; review its privacy settings before use.

Before you install

ClientModGate can only check information and behavior visible to the server. It cannot list every installed mod or reliably identify resource packs, and a clean report does not prove a client is unmodified. For example, previous tests did not detect Wurst 7.54 or 7.56.1 with the bundled scan rule.

Verification failures can also lead to a kick with the default configuration. Test your rules and settings with legitimate players before relying on automatic enforcement.

ViaVersion and ViaBackwards are optional; translated connections may have different detection coverage. Bedrock players connecting through Geyser do not receive Java mod scans.

Installation

1. Download the ClientModGate 3.0 JAR matching your Paper server version from Modrinth.
2. Place the JAR in your server's plugins folder and restart the server.
3. Run /cmg and follow the setup. Review the installed rules before opening your server to players.

Separate builds are available for Paper 1.21.9, 1.21.10, 1.21.11, 26.1.2, 26.2, and 26.3. The 1.21.x builds target Java 21; the 26.x builds target Java 25. Choose the build for the server version. If upgrading, back up plugins/ClientModGate/ first.

Useful commands

Command	Action
/cmg	Open the dashboard
/cmg setup	Open the setup wizard
/cmg mods	Manage mod rules
/cmg scan <player>	Scan an online player
/cmg player <player>	Open a player report
/cmg download	Browse rule sources
/cmg audit	Review activity
/cmg unban <player>	Remove a ClientModGate ban
/cmg help	See available commands

Documentation

Want to learn more? Visit the documentation for setup, rules, commands, and configuration.

Some pages describe an earlier release, so check the version requirements on the Modrinth versions page for ClientModGate 3.0.

Found a problem? Report it here.

**Created by pierrecreeper