1.0.9
Compatibility
Changes
π Version 1.0.8 (Alpha) - Balancing & Void Protection
This update focuses on stabilizing the endgame combat loop, refining project files for optimal performance under NeoForge, and introducing custom enchanting protections against the forces of the Void.
π§ What's New & Fixed:
- βοΈ NeoForge Refactoring: Optimized data-maps (
monster_room_mobs.json) and mod architecture tags to prevent cross-mod compatibility lag during dimension chunk generation. - πͺ΅ Recipe Polish: Unified tags for all Cosmic Wood variants (doors, trapdoors, and fences), making them fully compatible with Π²Π°Π½ΠΈΠ»Π»Π° item-repair tags and external technical mods.
- π Bug Fixes: Fixed a rare issue where the Cult Leader True Form would lose its targeting AI after switching phases.
Thank you for playing Celestial Adventure! Feel free to leave your feedback and report any bugs in the comments.
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:8TVKynTx:TfKruUhI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8TVKynTx:TfKruUhI"
}

