
AntiAdminAbuse
π‘οΈ AntiAdminAbuse AntiAdminAbuse is a powerful moderation and transparency plugin designed to prevent admin abuse and keep server actions visible and accountable. π Key Features Command Logging Logs all player and console commands to daily log files
1.0.0
Compatibility
Changes
π‘οΈ AntiAdminAbuse
AntiAdminAbuse is a powerful moderation and transparency plugin designed to prevent admin abuse and keep server actions visible and accountable.
π Key Features
Command Logging
Logs all player and console commands to daily log files
Stores per-player command history (up to 100 commands each)
Includes timestamps and IP addresses (where available)
Dangerous Command Confirmation
Commands like /op, /give, /tp, /ban, /stop, and more require double execution within 10 seconds
Prevents accidental or malicious admin actions
Broadcasts warnings when dangerous commands are attempted
Live Command Broadcasting
Broadcast admin/console commands to all players
Multiple display modes:
Chat
Action Bar
Boss Bar
Title
Subtitle
Filtered commands (e.g. /msg, /tell, /whisper) are hidden for privacy
Admin Control Commands
/antiadmin enable β Enable broadcasting & protections
/antiadmin disable β Disable broadcasting
/antiadmin displayType <type> β Change how alerts are shown
/antiadmin history <player> β View a playerβs recent command history
Persistent History
Command history is saved to disk and restored on server restart
π― Why Use AntiAdminAbuse?
Prevents silent abuse by admins or compromised accounts
Adds accountability without removing admin power
Ideal for SMPs, community servers, and semi-public servers
Fully configurable and lightweight
π Permissions
antiadmin.manage β Required to manage the plugin
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:xWxOKbRI:Blt7m081"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xWxOKbRI:Blt7m081"
}
