1.0.1
Compatibility
Changes
v1.0.1
In this hotfix, we have focused on fortifying the mod's technical architecture, ensuring that explorers across all realms and setups can safely descend into our abyss without facing initialization or pre-loading crashes.
🐛 Bug Fixes
- NeoForge Loader Version Crash Resolved: Fixed a critical pre-loading error where the mod incorrectly demanded
javafml:21from the system. The mod now properly recognizes and initializes with the native FML language provider version (v4.x) shipped with NeoForge 1.21.1. - Future Java Compatibility: Lifted the rigid runtime restraints from our environment manifest. The mod now graciously embraces players testing their setups with experimental and future Java runtimes (such as Java 25), while perfectly preserving its stable target for native Java 21.
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:5tVh4IT7:ZrgnaX9B"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5tVh4IT7:ZrgnaX9B"
}

