Links
Tags
Creators
Details
3.0.8-VIGIL
Compatibility
Changes
DeMalware-RETRO v3.0.8-VIGIL Correlative Threat Heuristics & Live Audit Release
Installation Requirement: Prepend the JVM agent argument pointing to your plugins directory on server startup: java -javaagent:plugins/DeMalware-RETRO.jar -jar server.jar
Fixes & Improvements:
- Correlative Threat Scoring Engine: Replaced package whitelists with a dynamic multi-indicator threat scoring algorithm. Standard non-malicious plugins (EssentialsX, Skript, ViaVersion, Geyser, Protobuf, JNA) are bypass-checked as safe warnings while true malware (l/M/x trojans) is accurately blocked.
- Active AI Audit Telemetry: Enabled real-time interactive audits querying Spigot nodes via WebSocket to collect active loaded plugin lists alongside network interception logs.
- Node Identifier Mapping: Enforced server node badges across network telemetry and threat violation tables on the dashboard panel.
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:xISZZmmm:Lp0Fgsj9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xISZZmmm:Lp0Fgsj9"
}
