Tags
Creators
Details
Licensed Apache-2.0
Published 6 months ago
Updated 3 weeks ago
All versions
1.1.1+fabric-1.21.1
Release
1.1.1 · fabric · 1.21.13 weeks ago 51
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
Fixes
- Restored the Crafting Terminal survival recipe on Minecraft 1.21.1 (Fabric, NeoForge) by migrating to the singular
recipe/data directory and the current resultidfield. - Restored the recipe on Minecraft 26.2 (Fabric, NeoForge), including its direct-string ingredient format.
- Restored terminal block drops on 1.21.1 and 26.2 by migrating their block loot tables to the singular
loot_table/data directory. - Fixed 26.2 block/item initialization by assigning their registry IDs before construction, as required by that Minecraft version, and preserved the existing block-item translation key.
- Updated the shared 26.2 resource/data pack metadata to accept the current client and server pack formats.
- Preserved the existing recipe ingredients, layout, output ID and quantity; the 1.20.1 recipe is unchanged.
Regression coverage
- Added native Minecraft recipe discovery, decoding, crafting-grid matching, crafted output and block-loot generation tests for all three supported versions, including rejection of the older broken resources.
- Added a source-backed native 26.2 registry-property construction regression.
- Added source-resource and packaged-loader-jar checks plus a non-publishing CI build/test workflow.
- Native recipe/loot tests use a stand-in item registered under the terminal's exact ID; client JEI display and Sophisticated Storage interactions require separate in-game verification.
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:Ss3e4qjk:cYaNzdLI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ss3e4qjk:cYaNzdLI"
}

