Creators
Details
2.0.6.3
Compatibility
Changes
This update includes an exploit fix in the recipe booklet. I highly advise updating.
CHANGE LOG:
ADDED
➔ Support for MC 1.21.11.
➔ Smithing recipes (still in beta; includes exploit fix).
➔ Serialization/deserialization of recipes from the creation GUI to config files (supports potions, spawners, colored armor, heads, lore, etc.). Old format still works, but will be converted over soon.
➔ Custom NBT components now save from the creation GUI, enabling support for custom items from other plugins or data packs.
➔ 'Ignore-Lore' option for recipe ingredients.
➔ Converted from NBTEditor to NBTAPI.
➔ 'Uses-ID' button for using direct results or saving NBT data for MMOItems, Nexo, Oraxen, etc.
➔ Support for blacklisting recipes on MC < 1.16.
FIXED
➔ Exploit in the recipe booklet (/cr book). PM for more details.
➔ Booklet pagination issue after customizing menu labels.
➔ Furnace experience not saving properly.
➔ Argument issue with /cr give causing errors.
➔ Recipe builder now correctly saves recipe permissions during command creation.
➔ Disabled recipes now correctly hidden in the GUI book for players.
➔ Recipe builder now matches ID with name during command creation.
➔ Recipe builder opening the wrong recipe when multiple recipes have matching results.
➔ Recipe builder enable toggle button.
➔ Recipe builder grindstone button.
➔ Default files now correctly don't regenerate after first load.
➔ Suppressed MythicMobs errors on 1.12 (unsupported until 1.16).
➔ Fixed occasional block place errors.
➔ Fixed no-perm-message reading from config instead of blacklisted.yml.
The wiki has been updated with important information.
For questions about these changes, check the wiki or reach out for support.
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:HpZj2RIt:XBM9grSd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HpZj2RIt:XBM9grSd"
}

