AutoAntiFlood: The Ultimate Shield Against Server Join Floods
Running a public Minecraft server comes with its share of headaches, and one of the most disruptive is the dreaded join flood. You know the scenario: a wave of guest accounts slams your server at irregular intervals, spamming the connection queue and making the game unplayable for legitimate players. That is exactly where AutoAntiFlood steps in — a lightweight yet powerful plugin designed to detect and neutralize these attacks before they ruin the experience.
Whether you are hosting a small survival world or a massive network, keeping your server stable is a top priority. AutoAntiFlood automates the defense process, locking out guests when an attack is detected while still allowing trusted members to slip through. Let’s break down how this plugin works, how to set it up, and why it deserves a spot in your plugins folder.
How AutoAntiFlood Detects and Blocks Join Floods
The plugin monitors the rate at which new players attempt to join. Once the number of connections exceeds a configurable threshold within a defined time window, AutoAntiFlood kicks into action. Instead of crashing your server or bogging down resources, it immediately blocks guest logins and broadcasts a clear message to everyone online. The core logic is simple: if a player has the bypass permission, they can still join even during an active flood. Everyone else sees a custom kick message and is temporarily turned away.
This approach keeps your server responsive and ensures that your regular members — those with the appropriate rank — never get locked out. Meanwhile, the flood of bots or malicious join attempts simply hits a wall. The plugin also reduces a “score” counter over time, automatically deactivating the protection once the join rate drops back to normal, so you do not have to babysit the console.
Commands and How to Use Them
AutoAntiFlood keeps things straightforward with a handful of in-game and console commands. All commands require the aaf.admin permission unless stated otherwise.
- /antiflood – Displays the current version of the plugin.
- /antiflood on – Manually enables the anti-flood protection.
- /antiflood off – Disables the protection, allowing all players to join freely.
- /antiflood status – Shows whether the anti-flood system is currently active or inactive.
- /onlyop on/off – (Version 0.9) When enabled, only operators can join the server, providing an even stricter lockdown during severe attacks.
- /setflood <amount> – Sets the maximum number of joins allowed before the protection triggers.
- /setfloodrate <ticks> – Defines how quickly the internal score decreases, effectively controlling how long the protection stays active after a spike.
These commands give you granular control without needing to dig into configuration files mid-attack. A quick /antiflood status can tell you whether the shield is up, and adjusting the flood limit on the fly is a breeze.
Permissions: Who Gets In and Who Controls the Plugin
Permission nodes are the backbone of any well-managed server, and AutoAntiFlood uses a clean hierarchy:
- aaf.admin – Grants access to all administrative commands:
/antiflood,/setflood, and/setfloodrate. - aaf.bypass – The golden ticket. Players with this permission can join the server even when the anti-flood system is actively blocking guests. Assign this to your trusted member rank so your regulars never get caught in the crossfire.
By separating administration from bypass, you can let moderators tweak settings without giving them the ability to walk through a flood, or vice versa. It is a small detail that makes a big difference in larger server hierarchies.
Installation: Getting AutoAntiFlood Up and Running
Setting up the plugin takes only a few minutes. Follow these steps to integrate it into your server:
- Download the AutoAntiFlood jar file from a trusted source (the file is typically named
AutoAntiFlood.jar). - Place the jar into your server’s
pluginsfolder. - Reload or restart your server so that the plugin generates its default configuration.
- Open the newly created
plugins/AutoAntiFlood/config.ymlfile and adjust the settings to match your server’s needs. - Add the
aaf.bypasspermission to your member group using your permissions plugin (LuckPerms, PermissionsEx, etc.). - Reload the plugin with
/plugman reload AutoAntiFloodor restart the server once more.
If you juggle multiple plugins and mods, keeping everything organized can become a chore. For those who prefer a streamlined approach, the foxygame.net launcher offers a modern and flexible way to manage your Minecraft experience — you can download and install server tools directly from its menu, making plugin deployment almost effortless. While AutoAntiFlood is a server-side addition, having a launcher that centralizes your mod library saves time and reduces the risk of version mismatches.
Fine-Tuning the config.yml
The configuration file is where you mold the plugin’s behavior to your exact needs. Here are the key entries and what they do:
- Active: true – Enables or disables the entire anti-flood system. Set to
falseif you need to temporarily turn it off without removing the plugin. - MaxJoin: 5 – The threshold of guest joins within the scoring window that triggers the lockout. Lower values make the protection more sensitive; higher values tolerate more traffic.
- ReduceRateTicks: 200 – The interval (in ticks, where 20 ticks = 1 second) at which the internal join counter decreases. A value of 200 means the score drops by one every 10 seconds, so the protection will deactivate roughly 50 seconds after the last join spike if MaxJoin is 5.
- KickMsg: "Sorry %player%, only members are able to join cause of floods." – The message shown to players who are kicked during an active flood. The
%player%placeholder is replaced with their username. - ActMsg: "Only members are able to join cause of floods!" – Broadcast to all online players when the anti-flood system activates.
- DeActMsg: "Server is free for all again!" – Broadcast when the protection deactivates and the server returns to normal.
Tweaking MaxJoin and ReduceRateTicks is crucial. If your server regularly sees a lot of legitimate guest traffic, you might raise the limit to 10 or 15. On the other hand, a small private server can safely set it to 3. The rate should be adjusted so that the protection does not stay on for too long after a false alarm, but long enough to deter a persistent attacker.
Why AutoAntiFlood Deserves a Spot on Your Server
Join floods are not just an annoyance; they can degrade performance, fill up logs, and frustrate your community. AutoAntiFlood provides an automated, permission-aware solution that requires minimal configuration. The ability to let trusted members bypass the lockout ensures that your regulars never feel the sting of an attack, while the dynamic score system prevents the protection from overstaying its welcome.
From the clean command set to the intuitive config, every aspect of the plugin is built with server admins in mind. Whether you are dealing with a sudden surge of bot accounts or just want a safety net for peak hours, AutoAntiFlood acts as a silent guardian that kicks in exactly when needed. Install it, set your thresholds, and give your server the resilience it deserves.