Links
Tags
Creators
Details
1.1.1
Compatibility
Changes
Hotfix
- Fixed a Windows/NTFS startup failure introduced in 1.1.0 where normal local configuration paths could be incorrectly rejected as unsafe, including fresh installs with no legacy configuration.
- Added Windows-specific path identity validation for safe configuration migration while preserving fail-closed protection against junctions/reparse points, path replacement, migration conflicts, and partial writes.
- No gameplay, registry ID, save-data, public API, configuration-format, or supported Minecraft/NeoForge range changes.
Compatibility
- Minecraft 26.2
- NeoForge 26.2.0.12-beta through the 26.2.0.x line
- Java 25
- Client and server both require the mod
- Recommended for all 1.1.0 users, especially Windows/NTFS users
Back up worlds and configuration files before updating. Automated Windows/NTFS migration coverage has passed; please report any remaining Windows client startup error with a screenshot or latest.log.
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:uTrWOEHF:os96U4ok"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uTrWOEHF:os96U4ok"
}

