Tags
Creators
Details
1.1.0_PRE_RELEASE
Compatibility
Required content
Changes
NOTE: I am aware that 1.21.6 is about to release, thus why I am making this a pre-release to fix any issues before I update to 1.21.6.
its been a while hasn't it lol
Resolved issue in #65. The mod now only stores all mod paths at initialization. The mods are only loaded into a small buffer during the mod transfer process from the client to the server.
Implented workaround for #64. The old mod ID system from the alpha versions has been reimplented as a new transfer method. This transfer methods takes the unique mod ID that all fabric mods must have.
Changed dependencies requirement. All Fabric API versions (for the same Minecraft version, of course) are accepted. The mod now only works on the exact Minecraft version it was meant for, whereas it used to be on the exact and future Minecraft versions. The strictness is due to how much the mod breaks inbetween versions due to how much it changes the login protocol.
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:3pWXKIdZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ljWczies:3pWXKIdZ"
}

