All versions
1.0.2
Release
Yapi: Paleofusion 1.0.2last month 144
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client-side
Server-side
Client and server
Changes
YapiPaleofusion 1.0.2
This update focuses on partial-mod safety, world creation stability, and deeper cross-mod behavior compatibility.
Stability and compatibility
- Reworked compatibility data so optional mod content no longer breaks partial installations
- Fixed additional advancement, tag, and recipe issues that could appear when only some supported mods are installed
- Split and cleaned compatibility overrides to make mixed mod setups more reliable
- Overrode the broken
trike_shield_smithingrecipe from Unusual Prehistory with a safe replacement
Titanoboa and incubator fixes
- Reworked Unearthed Journey Titanoboa compatibility
- Removed the old global Titanoboa spawn hook that could interfere with new world creation
- Added a targeted Unusual Prehistory incubator fix so incubated Titanoboa spawns correctly without breaking world generation
Cross-mod mob behavior tags
- Added broad The Dawn Era entity tag compatibility for integrated creatures from supported mods
- Added size-class tags for external creatures:
small_animalmedium_animalbig_animalgiant_animal
- Added danger/safe classification tags for external creatures
- Added curated
living_fossilcompatibility tags - Added curated
bleeding_immunityandfracture_immunitycompatibility tags
Release cleanup
- Improved release readiness for varied supported mod combinations
- General compatibility cleanup across supported integrations
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:1bX8jlrZ:W9LU3axf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1bX8jlrZ:W9LU3axf"
}

