Client Detection

When a player joins, the plugin inspects their client brand string and registered plugin channels. Matches against a list of known cheat clients (Wurst, Meteor, LiquidBounce, Sigma, Impact, Aristois, Future, Vape, RusherHack, Inertia, KAMI, SeedcrackerX, Xray and others) trigger the configured action.

Configuration

ClientDetection:
  Enabled: true
  HackDetection:
    Action: "kick"
    BrandPatterns: []
    ChannelPatterns: []

Key	Description
`Action`	`kick` to disconnect the player, `alert` to only notify staff with `muteessentials.clientdetection.hack`.
`BrandPatterns`	Extra regex patterns added to the built-in defaults. Empty list = defaults only.
`ChannelPatterns`	Same as above for plugin channels.

The built-in patterns are conservative: well-known cheat-client brands and channels.

Commands

/check <player> shows detected client and channels

Permissions

Node	Grants
`muteessentials.clientdetection`	See client detection notifications and use `/check`
`muteessentials.clientdetection.hack`	Receive HackDetection alerts when a flagged client joins
`muteessentials.bypass.clientdetection.hack`	Never be flagged or kicked by HackDetection

Notes

Detection runs after the standard client resolution callback, so the brand string is reliable.
If Action: kick, the kick message is configurable in messages-*.yml with %CLIENT% and %DISCORD% placeholders.

Client Detection

Configuration

Commands

Permissions

Notes

On this page