1.0.16h2
Compatibility
Required content
Changes
Apologies for not uploading this sooner, I was working on moving computers since this one was getting repaired.
quarter-baked
OH also, there is a Well rework planned, but it relies on another feature that will take a while to implement. For now, I'm pushing this out to fix a bug that was killing servers.
Changes
-
Fixed a critical bug where Wells making sounds would crash servers.
- I mean they can warp reality so it makes sense
-
There's a bit of Patchouli stuff in here that is coming out in the next update, for now it's heavily unfinished.
- Consider this a sneak peek. Pretty much all of the text will change though so
Config Changes
- Literally nothing
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:JeRs1qZv:Qri54cGT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JeRs1qZv:Qri54cGT"
}

