MLSAC

MLSAC is a neural-network anti-cheat plugin for Minecraft servers. It analyzes combat camera movement and surrounding data packets for patterns associated with KillAura, TriggerBot, AimAssist, Reach and hits through walls. The plugin sends combat camera and body movement, hit details, and player name and UUID to MLSAC's cloud for scoring; it does not send chat or inventory data. Its maker says detection runs remotely and does not use the Minecraft server's CPU or TPS. Setup uses the server plugin, a licence key and a website-configured preset; no client mod is needed, and PacketEvents is included in the plugin jar. Server owners can configure alerts, damage reduction, kicks and bans. A dashboard provides licences, keys, presets, statistics and player dossiers. The free Beginner plan includes the Mini model. Pro and Pulse require paid plans, Pulse also requires project verification, and Ultra is early access for plugin 2.0 and cannot run alongside other models. Checks pause when the daily request limit is reached.

MLSAC offers server-side installation with remote combat analysis and configurable enforcement. Before choosing it, consider the cloud data sent, daily request limits and model requirements.

MLSAC suits Minecraft server owners seeking cloud-scored combat checks and configurable responses. It is available for Paper, Spigot, Folia, kSpigot and Purpur servers.

Overview

MLSAC is a cloud-scored anti-cheat plugin for Minecraft server operators who want neural-network checks focused on combat cheats. It is best suited to owners who value remote analysis and configurable punishments, and are comfortable sending combat data to MLS’s cloud. The free Beginner plan offers an entry point, but its daily request cap and the paid-model requirements matter for sustained use.

Key features

The plugin analyzes camera movement and surrounding packets for KillAura, TriggerBot, AimAssist, Reach and hits through walls. Neural-network scoring runs on remote MLS servers; the maker says detection does not use the Minecraft server’s CPU or TPS. That separation may appeal to operators guarding server performance, but it makes cloud data transfer central to how MLSAC works.

Setup involves installing the plugin, applying a licence key and configuring a preset on the site. PacketEvents is bundled in the plugin jar, and players need no client mod. The dashboard manages licences, keys and presets, and provides statistics and player dossiers. Owners can configure enforcement ranging from alerts and damage reduction to kicks and bans; replay analysis is also supported.

The plugin sends combat camera and body movement, hits, player names and UUIDs for cloud analysis, but not chat or inventories. MLSAC’s privacy policy says it may also collect account identifiers, technical information and interaction history, and does not require passport data or photos. It describes reasonable security measures while warning that internet-transmitted information cannot be guaranteed absolutely secure. Operators should weigh that data flow against the benefit of off-server analysis.

Pricing

The Beginner plan costs nothing and includes the Mini model. It gives small or trial-stage servers a way to use MLSAC without a subscription charge, but checks pause until the next day when the plan’s daily request limit is reached. That makes the free tier a less dependable fit for servers that need continuous coverage through busy periods.

Pro and Pulse are reserved for paid plans, but no plan prices or quotas are provided here; treat them as custom pricing. Pulse additionally requires project verification, so paying alone does not ensure access. Ultra is early access for plugin 2.0 and cannot run alongside the other models, limiting its usefulness for operators who need to combine models. After payment confirmation, a purchased subscription or licence is assigned to the dashboard, usually instantly or within 1 to 5 minutes.

Platforms

MLSAC is a web-managed plugin for Minecraft servers running Paper, Spigot, Folia, kSpigot or Purpur. Its listed platforms are web and Windows. Setup help is offered through support tickets, Telegram and Discord.

Who it's for

MLSAC suits Minecraft server owners seeking remote neural-network analysis of combat behavior, configurable enforcement and a free Mini-model starting point. It is a weaker fit for operators who do not want player combat data and identifiers sent to a cloud service, or whose daily check demand could exceed the plan’s quota.

Pros and cons

• Pros: Remote scoring keeps detection off the game server’s CPU and TPS, according to the maker, which may suit performance-conscious operators.
• Pros: No client mod is required, and PacketEvents is built into the plugin jar, reducing player-side requirements.
• Pros: Configurable alerts, damage reduction, kicks and bans let owners choose how detections affect players.
• Cons: Combat movement, hits and player identifiers go to MLSAC’s cloud, a material consideration for privacy-conscious communities.
• Cons: The free plan’s daily request limit pauses checks until the next day, so it may not cover sustained high activity.
• Cons: Pulse requires project verification, while Ultra is early access and cannot be combined with other models.

Alternatives

For a broader comparison, browse Minecraft Anti-Cheat Plugins. Choose Intave if its free plan’s movement and combat detection is enough and you do not need combat automation or build automation detection; priority support is also excluded from that tier. Consider Shard if inspecting, self-hosting or contributing to fully open-source checks matters more than MLSAC’s cloud-scored model. AntiGuard is a free MIT-licensed option for Paper or Purpur 1.20.x on Java 17. CheckHacks is another always-free option, with donations optional. Choose ExploitShield if its stated Minecraft 1.17.x–1.21.x support and Paper, Spigot or Folia compatibility fit your server, and you can meet its Java and dependency requirements. GK AntiCheat, Grace Anticheat and GuardAC are other free-plan options to compare.

Verdict

Choose MLSAC if you run a compatible Minecraft server and want remote neural-network combat scoring, configurable punishments and no required client mod. Its strongest case is moving detection off the server’s CPU and TPS; its clearest trade-off is sending combat data and player identifiers to the cloud, with a daily cap on the free tier. Look elsewhere if local control of that data or uninterrupted checks without quota pauses are priorities.