Tags
Creators
Details
1.0.4
Compatibility
Required content
Changes
Updated to Minecraft 1.21.3.
Implemented fix for #46. The mod's networking has been changed. Now, there are two ways for clients to transfer their modlists to the server:
- "data" transfer method (the existing method) - Gets the client to transfer the entire file of each mod to the server.
- Generally slightly harder for clients to bypass
- "name" transfer method (the added method) - Gets the client to transfer the file name of each mod to the server.
- Alot faster when the expect modlist is large (like in a big modpack)
Each transfer method have their own checking methods (now named validation methods), "individual" and "group". https://iac.diffusehyperion.com has been updated to reflect this change.
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:ljWczies:gdSvdQ3F"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ljWczies:gdSvdQ3F"
}

