Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 5 days ago
All versions
1.8.1-neoforge-21.1
Release
v1.8.1 ~ Neoforge 21.15 days ago 63.2K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
- Introduced a system for alternate targeting in worldgen modifiers.
- Instead of a target being a "single_id", ["id","list"], or a "tag", there is an object format with a custom targeting type. The targeting types are:
lithostitched:any-> Matches all entries in the registrylithostitched:regex-> Matches all entries in the registry whose ids match the given regex patternlithostitched:biome/climate-> Matches all biomes within given climate rangeslithostitched:biome/has_feature-> Matches all biomes that have a given placed feature
- Instead of a target being a "single_id", ["id","list"], or a "tag", there is an object format with a custom targeting type. The targeting types are:
- Fixed various places where processor list injections didn't apply.
- Any template pool element nested inside a
list_pool_element(primarily impacts Pillager Outpost towers) - Planks, logs, and chains in mineshafts
- Leaves, vines, and surrounding netherrack in ruined portals
- Sand and suspicious sand in desert temples
- Dried ghasts in nether fossils
- Spawners in strongholds and nether fortresses
- Cobblestone extensions in woodland mansions
- Chests in various structures
- Any template pool element nested inside a
- Added two new block tags in tandem with the previous changes to allow smoother palette swapping of vanilla structures.
#lithostitched:supports_mineshaft_extension-> Blocks in this tag can have log and chain extensions built off of them.#lithostitched:supports_ruined_portal_leaves-> Blocks in this tag can have leaves from overgrown ruined portals spawn on them.
- Fixed a freeze that would infrequently occur from the
lithostitched:matching_biomesprocessor condition.
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:cZu4cHY3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XaDC71GB:cZu4cHY3"
}

