4.1.0
Compatibility
Changes
This is the only text I have typed fresh in these logs. I have no idea what happened here, the version seems to have jumped all the way to v6.. but then back to v4?? No idea. These are new versions with new fixes and features, and for newer versions of Minecraft. Treat these v4 versions as if they are v6 versions, or maybe v7.. because.. well.. they should have been.
-Replaced all/most of the entity textures, they all broke with the update. Some of them still are and I don't know why.
-All of the item textures are broken. No idea why, that'll be fixed in the release, but I have no idea how, so that'll take a while. -Fixed (hopefully) the item textures.
-Relinked the sound files.
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:nVWmFwF8:DkZjGN48"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nVWmFwF8:DkZjGN48"
}

