1.4
Compatibility
Changes
NOTE: 1.3.6 worlds are likely no longer compatible with 1.4 due to core changes
Changelog TLDR: Rivers & Lakes, 4x Ocean Archetype islands, more configurations, structure improvements and performance enhancements
Added
- Rivers & Lakes (+Configuration for each independently)
- 4 New Ocean archetypes
- Biome topsoil based on the biome itself (Top blocks are biome-based now)
- Structure category configuration in Advanced menu UI
- Island radius recommendation based on structures loaded
- Added new structure category
EXPERIMENTAL, which lets you enjoy the perks of island aware placement without the criteria of whether something is valid or not in placement (Outside of overlap and biome checks). Primarily for MASSIVE/LARGE structures or structures that have trouble spawning. - Ocean Monument support via Lagoons being able to spawn them.
Changed
- Menu items have been moved to be in better spots
- Structures before used to try find any islands and check for biome compatibility, instead they begin with region-level for biome checks which are cheaper and reduces the exhaustion of probes since they are more guaranteed to hit a correct biome.
- Islands have a more refined shape, with minor height plays (wavey when you look from the side)
Fixed
- Biome blending
- Caves & Caverns under the ocean layer spawn as normal (No more solid mass)
- Smaller UI screens changes on buttons alignment (Not perfect but improvements made)
- The erosion artifacts that caused islands to have a bunch of smaller fractured dots of terrain that did not look great.
- Concurrency issue where more computation was being spent than necessary, resulting in higher chunk generation per second and more concurrent structure placement requests.
And lots more, but these were the more note-worthy changes.
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:sHFNUlBU:XPc17YJD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sHFNUlBU:XPc17YJD"
}

