1.2.4+mod
Compatibility
Changes
After doing some testing with "coding master" IcyG, the crashing should be fixed.
BIG THANK YOU to two kind souls, IcyG and Cass, for reaching out and sending over the files they fixed after ATi's professional capital letter coding incident, and to IcyG for going out of his way to help me fix the issue during a Discord call. ✨
(Apologies for this issue taking its sweet time to get addressed.) -Hardwater
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:t0YT91nL:xR2jWhmr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:t0YT91nL:xR2jWhmr"
}

