Tags
Creators
Details
1.19.4-2.3.5
Compatibility
Changes
Natural Progression Changelog (1.19.4)
2.3.5
Initial Port to 1.19.4
Woof, that was a pain in the butt. Nothing major, just lots of internal changes I had to make because of changes Mojang and/or Forge made to:
- Damage Sources (used for splintering & crushing damage when punching w/o the right tool)
- Requires a freaking access transformer to use. Come on Mojang, this is unacceptable.
- Creative Tabs
- Not only was it pain to a custom tab at all, but now I'm required to sort things manually rather than sorting by order it was added in code, which sucks. I hope you at least like the current creative tab sorting I implemented 🤞
- World Gen
- I had done a lot of stuff with
DeferredRegistry<?>which I could no longer use and had to manually port as a datapack
- I had done a lot of stuff with
Overall, 0/10 would not recommend. I hope you enjoy though, and give me shout on the bug tracker if you see anything not behaving!
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:VkVpYDxO:7XbDKyYQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VkVpYDxO:7XbDKyYQ"
}

