All versions
2.0
Release
Release3 months ago 189
Compatibility
Minecraft: Java Edition
1.21.11
Platforms
Bukkit
Paper
Spigot
Changes
AntiSpam
A lightweight, fully configurable chat spam protection plugin for Paper servers — with optional EssentialsX integration for mutes and kicks.
✨ Features
- Message cooldown — Stops players from flooding chat with a configurable delay between messages.
- Escalating punishments — Automatically progresses from warn → mute → kick, each with its own configurable threshold.
- EssentialsX support — Optionally uses EssentialsX's
/muteand/kickcommands to integrate with your existing punishment history and logs. - Built-in fallback — No EssentialsX? No problem. Use the plugin's internal mute and kick system with a single config option.
- Fully configurable — Enable or disable the entire plugin, warnings, mutes, and kicks independently. Only want warnings? Disable mutes and kicks.
- Bypass permission — Exempt staff or trusted players from all spam checks.
- Reload support — Reload the configuration without restarting your server.
⚙️ Configuration
enabled: true
cooldown-seconds: 1.5
warn:
enabled: true
message: "&cYou're sending messages too fast!"
mute:
enabled: true
threshold: 5
use-essentials: true
essentials-duration: "2h"
internal-duration-minutes: 120
reason: "Spamming chat"
message: "&cYou have been muted for spam."
kick:
enabled: false
threshold: 10
use-essentials: true
reason: "Kicked for spam"
message: "&cYou have been kicked for spam."
📜 Commands
| Command | Description | Permission |
|---|---|---|
/antispam reload |
Reload the plugin configuration | antispam.reload |
/antispam unmute <player> |
Remove an internal mute (not needed when using EssentialsX) | antispam.unmute |
🔑 Permissions
| Permission | Description | Default |
|---|---|---|
antispam.reload |
Reload the plugin configuration | op |
antispam.unmute |
Unmute players (internal mutes only) | op |
antispam.bypass |
Bypass all spam checks | false |
📦 Requirements
- Paper 1.21+
- EssentialsX (optional — only required when
use-essentialsis enabled)
Optional dependencies
Any compatible version
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:hPXxIIoi:G8jcsUyP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hPXxIIoi:G8jcsUyP"
}

