Tags
Creators
Details
1.2.0
Compatibility
Changes
ReversSecurity v1.0.0 is now available. This project was born with the goal of protecting our servers against the most common vulnerabilities. After several development stages and internal testing at Revers Studio, we are ready to officially launch it as a robust and stable solution. This version marks the beginning of our commitment to the community's security.
⚙️ What's new in this update? Strengthened Security Core: We have rewritten and improved the filtering layers to detect and prevent malicious behavior in real time without affecting server performance.
Enhanced Log Management: The plugin now offers a more detailed logging system. This allows you to quickly identify any intrusion attempts or abuse.
Production Stability: After fixing the bugs found during the development stages, version 1.0.0 is ready for use in high-traffic environments. It delivers an experience free of critical errors.
Intuitive Configuration: We have simplified the configuration files so that even less experienced administrators can adjust their protection levels in seconds.
🚀 Your security, our priority We understand that a secure server is the foundation of a healthy community. That is why we have worked hard to make ReversSecurity lightweight yet effective against exploits.
By downloading this version, you help us continue to improve. If you find any strange edge cases or have an idea for a new protection measure, we invite you to open an Issue in the repository. Your feedback is what keeps this plugin updated against new threats.
Thank you for trusting the work of Revers Studio. Let's keep those servers protected!
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:UGukb0PK:oixLLIOX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UGukb0PK:oixLLIOX"
}

