Compatibility
Minecraft: Java Edition
Platforms
Tags
Creators
Details
SlaymAC (GrimAC+)
SlaymAC is a powerful and lightweight anticheat plugin built on top of GrimAC. It brings everything you love about GrimAC while being optimized for better performance and a cleaner experience. All the core features of GrimAC are preserved ā movement simulation, lag compensation, full world replication ā but stripped down and fine-tuned to run lighter on your server.
What's different from GrimAC?
Lighter and more optimized build Cleaner configuration Rebranded and maintained independently as SlaymAC Discord integration removed for a leaner setup Focused on stability and simplicity
Features Movement Simulation Engine
1:1 replication of the player's possible movements Covers walking, swimming, knockback, cobwebs, bubble columns and more Supports riding entities from boats to pigs to striders All client/server version combinations from 1.8 to 1.21 are supported Accounts for minor bounding box differences between versions
Fully Asynchronous and Multithreaded Design
All movement checks run on the netty thread Scales to hundreds of players without breaking a sweat Thread safety is carefully designed throughout
Full World Replication
Maintains a replica of the world for each player Created by listening to chunk data packets, block places and block changes Recreated per player to allow accurate lag compensation
Latency Compensation
World changes are queued until they reach the player Breaking blocks under a player does not trigger false positives Flying status, movement speed and more are all latency compensated
Inventory Compensation
Player inventory is tracked to prevent ghost blocks at high latency
Secure by Design, Not Obscurity
All systems are mathematically impossible to bypass The prediction engine knows every possible movement ā it cannot be fooled
Installation
Java 17 is required Paper, Spigot and Folia are supported If you use Geyser, place Floodgate on the backend server so SlaymAC can exempt bedrock players If you use ViaVersion, keep it on the backend server as movement is highly dependent on client version


