Links
Tags
Creators
Details
1.0.0
Compatibility
Required content
Changes
Minecraft 1.21 - 1.21.11, 26.1 - 26.3 Fabric and NeoForge
Restrict by output item
A new permission axis restricts an item rather than one path to it:
restricted-crafting.item.<item_id>blocks every crafting recipe that makes the item, for a player.restricted-crafting.crafter.item.<item_id>does the same for the auto-crafter, read from thedefaultgroup.
Special recipes (firework rocket, map cloning, armor dyeing, ...) build their result at craft time and declare no output item, so restrict those by recipe id.
Everything else
- NeoForge support added
- Only crafting recipes now get permission nodes - smelting/stonecutting/smithing/etc. are no longer suggested, since the mod can only check crafting
- Permission nodes are re-registered on datapack
/reload, so recipes added by datapacks become restrictable without a restart - New command
/restrictedcrafting dumpwrites every managed permission node and its default-group state torestricted-crafting/permissions.txt(op level 4) - Permission checks go straight through the LuckPerms API on both loaders (the
fabric-permissions-apidependency is gone) - New permission axis by output item:
restricted-crafting.item.<item_id>andrestricted-crafting.crafter.item.<item_id>restrict every recipe that makes an item, including recipes added later by a datapack /restrictedcrafting dumpnow also lists every crafting recipe under the item it outputs- Hardening: dump writes a fixed path, denied recipes are evicted from the book on
/reload, book-hiding no longer fails the boot on new versions
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:Tf9ijCH5:2fKlaNdH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Tf9ijCH5:2fKlaNdH"
}

