Links
Tags
Creators
Details
All versions
v1.1.0
Release
Contents Director v1.1.0last month 35
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
1.7.10
Platform
Forge
Supported environments
Client and server
Changes
Added
- Manual CurseForge download fallback with browser/copy/select and Downloads-directory detection.
- Japanese and Simplified Chinese UI translations.
- Localization documentation and regression coverage for complete key sets, placeholders, external overrides, and fallback behavior.
- Linux and Windows CI coverage with a Java 8 test runtime.
- Regression tests for installer staging/commit behavior, network redirects/errors, partial downloads, provider response validation, side metadata, remote configuration safety, and offline startup paths.
Changed
- Installation now separates pre-install resolution, staging, hash validation, commit, and deferred cleanup responsibilities.
- Provider configuration can use explicit filenames to avoid unnecessary metadata queries when resolving already-installed files.
- Jackson dependencies are aligned through a common BOM.
- Java compilation explicitly uses UTF-8 for cross-platform source consistency.
- macOS interactive Swing UI is isolated in an external helper JVM.
Fixed
- Existing live files are preserved when staging or hash validation fails.
- Hash validation checks all supported configured digests and accepts case-insensitive hexadecimal input.
- Archive extraction and modify operations reject paths that escape their allowed roots or traverse symbolic links.
- URL extraction rejects unsupported/malformed non-ZIP archives instead of silently treating them as empty ZIP content.
- Cross-task supersede cleanup no longer removes files published by another install task.
- Omitted metadata
sideis treated as unrestricted. - Remote configuration files are parsed in memory, use URL basenames only for type dispatch, reject recursion cycles/depth overflow, and validate bundle modify paths before mutations.
- External localization overrides now resolve through absolute filesystem paths consistently across Windows, Linux, and macOS.
- Partial translations fall back to canonical English instead of an unrelated JVM system-locale bundle.
Known limitations
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:2JWWdEgd:BpJI4xMV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2JWWdEgd:BpJI4xMV"
}

