Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 3 days ago
All versions
1.8.0-neoforge-21.1
Release
v1.8.0 ~ Neoforge 21.1last week 42.5K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
Lithostitched 1.8.0 is largely focused on backend changes, with the codebase split up based on version again. Various other changes and fixes have made it in, though.
Additions
add_spawn_costsmodifier (adds spawn costs for mobs in given biome(s))set_tree_decoratorsmodifier (adds/overrides tree decorators on given tree feature(s))branched_mega_junglefoliage placer (for wider mega jungle trees)branched_mega_pinefoliage placer (for wider pine jungle trees)large_mangroveroot placer (for root placements with 2x2 trees)cellulardensity function type (in-house 2d cellular noise with more consistency/features than fast noise)- Introduced an optimization to density function caching. This will be most noticeable when playing with heavy worldgen packs like Tectonic or Lithosphere.
- A special thank you to Unnecessarymb and Evanbones for finding and implementing this optimization, respectively.
Fixes
- Fixed a critical issue that caused worlds with surface rule injections to corrupt under certain conditions, such as when having a world with both RU 0.6 and Terrablender installed.
- Fixed the fields on the
offsetplacement modifier being non-optional. - Fixed the
dungeonfeature type not working. - Fixed annoying but harmless log errors when World Weaver is installed.
- Fix the assumed minimum value in various places (e.g.
sample_densityplacement condition) being 0, not roughly -1.8E308.
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:XaDC71GB:sPmtDq1X"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XaDC71GB:sPmtDq1X"
}

