All versions
1.0.0
Release
Yapi: Paleofusion 1.0.02 months ago 44
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client-side
Server-side
Client and server
Changes
Yapi: Paleofusion 1.0.0
- Officially released as version 1.0.0.
- Updated compatibility for the latest Shineal's Prehistoric Expansion.
- Added full support for the new SPE creatures:
- Diplocaulus
- Triceratops
- Hippocampus
- Pteranodon
- Harpy
- Updated SPE biome blocking so newly added SPE biomes are also covered.
- Updated SPE spawn blocking so newly added SPE mobs are also prevented from naturally spawning when compatibility is active.
- Removed the old Dodo Egg tweak so it no longer conflicts with the new native SPE baby dodo behavior.
- Fixed several Unearthed Journey egg entity links so affected eggs hatch into the correct creatures.
- Improved Titanoboa compatibility and stability.
- Fixed a major issue that could cause world creation or world entry freezes.
- Added support data for more recent SPE incubation and hatching content.
- Added unique textures for embryo items instead of relying on shared placeholders.
- Redrew, cleaned up, and improved a large number of compatibility textures.
- Added many new visual assets for eggs, roe, embryos, and other compatibility items.
- Fixed the Hippocampus roe visual mismatch.
- Added compatibility item tags for prehistoric eggs and embryo-based food handling.
- Expanded cross-mod egg compatibility so more prehistoric egg items are recognized consistently between supported mods.
- Expanded and reorganized built-in integration pack content across supported mods.
- Removed the experimental oyster fishing integration.
- Moved oysters to Prehistoric Fauna geologist trades instead.
- Added and cleaned up a large amount of missing compatibility data, models, textures, and localization.
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:Awfe3MVr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1bX8jlrZ:Awfe3MVr"
}

