0.1.0-beta-1.12.2
Compatibility
Changes
SimpLimeDefender - Changelog
v0.1.0-beta - Initial Public Beta This is the first public beta release of SimpLimeDefender, a lightweight security plugin focused on providing essential protection against common server attacks.
đ Features
Command Spam Protection:
Introduced a robust defense mechanism against command spam from compromised operator accounts. The system triggers an emergency server shutdown if a privileged user exceeds a configurable command execution threshold (e.g., 2 commands per second), providing a powerful failsafe against griefing attempts.
Operator Impersonation Shield:
Implemented a security check to prevent players from logging in with the same nickname as an already online operator. A detected impersonation attempt can be configured to immediately shut down the server to mitigate security risks.
Modrinth Update Checker:
Added an automatic update checker that queries the Modrinth API on server startup. Operators with the simplimedefender.notify permission are notified in-game upon joining if a new version is available.
Admin-Focused Notifications:
Enhanced server monitoring by broadcasting operator login events to other online administrators.
Critical security events (impersonation attempts, spam triggers) are now logged to the console with a SEVERE level for high visibility in server logs.
đ§ Improvements Configuration Overhaul:
The ConfigLimeDef.yml has been completely restructured with logical sections and detailed comments for improved clarity and ease of management.
Command Aliases:
Added convenient command aliases /sld and /defender for faster access to plugin commands.
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:uRJ5g9k2:gU0aHqW5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uRJ5g9k2:gU0aHqW5"
}

