1.83.6
Compatibility
Changes
๐ข๐ง๐ ๐ญ๐ฆ๐ค๐ซ๐ฎ๐ฆ
-Added 2 ๐๐๐ ๐๐๐๐๐๐๐๐๐๐ / ๐๐๐๐๐๐๐๐๐
-Added new structures to ๐ท๐๐๐, ๐ฟ๐๐๐, ๐ฃ๐ฒ๐ถ๐ฎ, ๐๐พ๐ฒ๐ต๐ญ๐ฒ๐ท๐ฐ, ๐๐๐๐ ๐๐๐ ๐ฑ๐๐๐๐๐.
-Added 1 new แดฑโฟแตโฑแตสธ
-Added new แตแตแตโฑแตโฟแต หขแตแตโฟแตหข to ๐ต๐๐๐๐๐๐๐๐ ๐๐๐
-Added ambience to โฉโชโฒ
-Adjusted Aphotic's and Uncomformity's Exit Stations
-Added more failsave's to existing Exit Stations to prevent fall damage when entering them with TPS lag
-Adjusted ๐ง๐พ๐๐พ'๐ Structure generation Spawn Weight
-Adjusted ๐ฑ๐๐๐'๐ Generation
More I most likely forgot to list.
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:1epVZXf2:A1lEn4Rg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1epVZXf2:A1lEn4Rg"
}

