Links
Tags
Creators
Details
All versions
3.0.4-VIGIL
Release
DeMalware-RETRO v3.0.4-VIGIL3 months ago 1
Compatibility
Minecraft: Java Edition
1.21–1.21.4
1.20
1.19
1.18
1.17
1.16
1.15
1.14
1.13
1.12
1.11
1.10
1.9
1.8
Platforms
Folia
Paper
Spigot
Changes
DeMalware-RETRO v3.0.4-VIGIL Threat Telemetry & Bug Fix Release
Fixes & Improvements:
- Direct Threat Telemetry: Fixed threat violation reporting so offline & runtime scans immediately post threat logs to the web dashboard.
- Dashboard Logs Filtering: Resolved UI table filtering in the web panel for connected server nodes.
- Config & Endpoint Hardening: Hardcoded the licensing verification server endpoint directly in bytecode and removed user-configurable
license-serverparameter to prevent spoofing. - Directory Consolidation: Removed legacy fallback directory checks (
plugins/DeMalware/) to ensure clean single-folder configuration underplugins/DeMalware-RETRO/. - Java 25 Profiler Safeguard: Disabled native JNI profiler crashes on Java 25.
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:Ad2ewXqX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xISZZmmm:Ad2ewXqX"
}
