Tags
Creators
Details
3.1.0-1.21.11
Compatibility
Changes
v3.1.0 -- Minecraft 1.21.11
This release combines the port of the 3.0.0 rewrite from Minecraft 1.21.1 to 1.21.11 with the subsequent v3.1.0 changes, including Forge support and the transition from Java-based entry lists to JSONC-based catalogs.
Porting and Platform Support
- Ported the 3.0.0 rewrite from Minecraft 1.21.1 to Minecraft 1.21.11.
- Added support for Forge.
- Improved cross-loader integration and configuration handling.
Added
- Added a configuration screen for Fabric & NeoForge.
- Added automatically generated advancements for all compressed blocks and crates.
- Introduced JSONC-based catalogs for blocks and crates, supporting custom entries and resource-pack-provided assets.
- Added support for defining custom compressed blocks and crates through catalog entries and resource-pack assets.
See the Custom Entries guide for instructions, required resources, and examples.
Improved
- Refactored block, crate, registration, and platform integration code.
- Consolidated data generation for recipes, models, tags, loot tables, translations, and advancements around the compression catalogs.
- Unified configuration handling across supported platforms.
Configuration
- Forge: Uses the JSONC catalogs to define block and crate settings; no separate loader configuration is provided.
- NeoForge and Fabric: Loader configuration values (toml config) take precedence over the defaults defined by the JSONC catalogs. Catalog values serve as defaults when corresponding configuration values have not been set.
Removed
- Replaced manually maintained resources with generated resources, including advancements.
Downloads
Dependencies and integrations
Optional dependencies
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:IQRVlbit:lKPTWqiD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IQRVlbit:lKPTWqiD"
}

