Links
Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 3 weeks ago
All versions
2.9.5+26.1-neobric
Release
2.9.5 for 26.13 weeks ago 519
Compatibility
Minecraft: Java Edition
26.1.x
Platforms
Fabric
NeoForge
Supported environments
Client and server
Changes
2.9.5
Critical fix about custom dimension config function. (Thanks to @rpfurlong)
- Fix config cannot back to default when player leave custom dimension.
- That leads default config file will be overwritten or deleted if you 'Save Changes' or 'Delete Current File' in configScreen.
- And other strange issue that I cannot expect...
- Fix logical side mem leaks that causing player cannot receive any SFCR packet after respawn.
- Fix cloud sample seed will re-random when play change dimension or respawn across dimension on Neoforge.
- Fix client did nothing after player change dimension or respawn on NeoForge remote server.
- Cloud sampler keep sampling the old (unloaded) level, breaks biome/rain-based dynamic features.
- And per-dimension config self-load was also skipped when enableServer is disabled.
- Critical fix for 1.21.11-neoforge startup crash causing shader compile error that bundled incorrect shader file.
- Impl Forgix again to mergeJar. Now fabric & neoforge was compressed into single file for 26.x version.
- Optimize code structure to get a high compression level.
- Add a simple screen to notify player install Cloth Config instead of red config button.
- Remove useless MixinTargetNotFound warning log out on game launch.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:Hoop89kN:5R1Ua33j"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Hoop89kN:5R1Ua33j"
}

