Creators
Details
0.1.12-alpha
Compatibility
Changes
This patch release changes the client ResourcePack distribution boundary while preserving TreasureRun's existing runtime localisation features and the v0.1.11-alpha server-safety baseline.
Changes
- Minecraft language payload JSON files and the shared generated ResourcePack ZIP are no longer bundled in the repository or server JAR.
- Server operators can generate client packs locally from their own Minecraft Java Edition 1.20.1 installation.
- Generated packs are marked
LOCAL_ONLY_DO_NOT_PUBLISHand recorded inlocal-pack-manifest.tsv. - Locally generated client packs are operator-local outputs and are not public release assets.
- Automatic public ResourcePack delivery remains disabled by default.
- 17 mappings are validated; six uncertain mappings remain explicitly on hold.
- There is no silent English fallback and no guessed
lzh -> lzhmapping.
Preserved
- 23 plugin-owned language YAML files
- Player language selection and persistence
- ProtocolLib packet localisation as an optional external dependency
- The pure-Java i18n core and Fabric Java runtime
- Database and ranking behavior
- The v0.1.11-alpha server-safety baseline
- Third-party license and notice packaging
Verification
./gradlew clean test shadowJar --no-daemon- Two independent disposable-clone builds produced a byte-identical candidate JAR.
- The published GitHub Release JAR was re-downloaded and checked by SHA-256.
- The final server JAR contains 0 Minecraft language payload JSON files, 23 plugin-owned language YAML files, 0 shared ResourcePack ZIP files, and 0 bundled ProtocolLib classes.
SHA-256:
5b98c2b3244f0dd6202a41c7801914c4d4a5e9df0fc529697d3615057b515df1
Operator note
No client ResourcePack ZIP is included as a public release asset. Generate it locally from your own Minecraft Java Edition 1.20.1 installation when needed.
This release does not add /treasurerun create or /treasurerun join; those remain planned for the separate v0.2.0-alpha milestone.
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:druDRDrE:JmLdDk6x"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:druDRDrE:JmLdDk6x"
}

