1.20.1-7.40-fabric+forge+neo
Compatibility
Changes
No code changes, but thought this was the best way to reach everyone.
Windows Defender has had issues this past week with some mods falsely flagging the mod as a "Trojan:Script/Wacatac.B!ml".
This is a false positive. Microsoft has fixed this in their latest Defender update. The solution is to update Windows Defender's definitions.
This can be done via Windows Update, or alternatively via these steps:
1. Open command prompt as administrator.
2. Run the following, without the “-quotes:
“cd C:\Program Files\Windows Defender && MpCmdRun.exe -removedefinitions -dynamicsignatures && MpCmdRun.exe -SignatureUpdate”
That's it! I wish I could do more. I can assure you there is nothing wrong with the mod. Hopefully in a few days Defender be updated automatically for everyone.
The complete changelog with previous versions can be found at:
https://serilum.com/mods?changelog=collective
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:e0M1UDsY:wipAhCa0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:e0M1UDsY:wipAhCa0"
}

