0.1.1
Compatibility
Changes
So, yeah we now have a neoforge of our mod, it's still the same as datapack, but it's easier just to add one more mod to your collection that to download one datapack without knowing what to do with a .zip datapack. Unfortunatelly i dont have enought free time to recode everything just to make it available for 1.21.5 as well, so you need to use 1.21.4 instead for neoforge version. ;)
And btw.: you may be aking yourself why there's no version 0.1.0? it's because it contained a very dangerous error that is now fixed, this error basicly could destroy all of your shaders in one world. (if you don't know what shaders are, you need to know that without them you wouldn't see anything or in other words you would just see pitch black screen)
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:BMg2lJYb:ZlbvUDw9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BMg2lJYb:ZlbvUDw9"
}

