Tags
Creators
Details
0.2.0-Beta
Compatibility
Changes
0.2.0-Beta
New Features & Major Changes
-
Moderation Module: Added a complete ban/kick system with persistent database storage:
/ban <player> [reason]— Permanently ban a player./tempban <player> <duration> [reason]— Temporarily ban a player (e.g.1d,2h30m,7d)./unban <player>— Revoke an active ban./kick <player> [reason]— Kick an online player./banip <ip|player> [reason]— Ban an IP address (raw IP or resolved from a player name)./unbanip <ip>— Revoke an active IP ban./banlist [page]— List all currently active bans and IP bans./baninfo <player>— Show ban status, total ban/kick count and the last ban reason.- Everything is stored by the player's UUID — name changes can never evade a ban.
- Full history is kept forever: total bans, total kicks and the last ban reason stay available even after a ban expires or gets revoked.
- Cross-server ready: defaults to a local SQLite file (zero setup), or point every server in your network at the same MySQL database and they all enforce the exact same ban/IP-ban list instantly.
- IP bans are checked independently of name/UUID bans on every login.
- Works for offline players too (pre-emptive bans) — a warning is shown if the target never joined before.
plainbase.moderation.exemptprotects a player from being banned/kicked by non-admins.- All commands also work from the console, replacing vanilla's
/ban//kick. - Fully configurable ban/kick/IP-ban/broadcast messages (MiniMessage) in
modules/moderation.yml. - Fine-grained permissions under
plainbase.moderation.*.
-
PlaceholderAPI Support:
- Added
%plainbase_moderation_bancount%,%plainbase_moderation_kickcount%and%plainbase_moderation_banned%.
- Added
Config Changes
- config.yml updated to Version 1.6 (Added configuration entry for the
moderationmodule). - moderation.yml added, Version 2.0 (New configuration file to manage the Moderation module: storage backend, messages, broadcasts and commands).
Tested Environments
- Paper 26.2
- Folia 26.2
It should work on Paper, Purpur and Folia Servers for 1.21.6 to 26.1.2! Spigot is not supported.
Optional dependencies
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:yfx0z1Sw:SvpL6eBQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yfx0z1Sw:SvpL6eBQ"
}
