Tags
Creators
Details
1.3.2+26.3-neoforge
Compatibility
Changes
Chronicle 1.3.2
This release reduces duplicate per-patch uploads by publishing one file for each verified compatibility range.
- No reminder features or saved-data formats changed from 1.3.1.
- Fabric was launched successfully on every supported Minecraft version: 24/24.
- Forge and NeoForge ranges only combine builds whose executable class hashes match on every covered version.
- Every final JAR preserves the selected, previously tested 1.3.1 binary byte-for-byte except for loader metadata.
- The artifact count is reduced from 68 to 40.
The embedded Minecraft ranges match the game versions assigned on distribution platforms. SHA-256 checksums and the full compatibility audit are included with the release.
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:G6251W24:RRSbx36f"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:G6251W24:RRSbx36f"
}

