Tags
Creators
Details
4.16.10
Compatibility
Required content
Changes
Warning
This update requires the latest WolfyUtils beta !
You can download it from Modrinth: https://modrinth.com/plugin/wolfyutils/version/4.17-beta.4
Recipe / Custom Item Loading
This update makes a couple of changes to the whole loading process of custom items and recipes.
If a recipe or custom item depends on another plugin, that isn't available, it will fail instantly and will not to attempt to load it any further (like it previously did). No verification or anything is done.
If a recipe or custom item depends on plugins that are available, then it makes sure the recipe or custom item is loaded once all its dependencies are available. Only then it tries to verify the recipe and checks if it is loaded properly.
Additionally, information about pending, failed or invalid recipes can be viewed in-game via the new /recipes info command.
Without any more arguments, this opens a chat interaction menu, that lists all the recipes.
The /recipes info <recipe> command can be used to get info about a specific recipe.
Note: The chat menu is still in a very early state, so it does not yet provide all possible information For example why a recipe failed to load. This and other info can be found in the logs for now.
Changelog
- #363 - Allow Applying Permisson Condition to Smithing Recipes
- #361 - Update ru_RU.json by @Pavel-Gornov
- #364 - No Longer Display Note About Brewing Stand Recipes
- #373 - Fix Smithing Recipes: Duplication & Empty Ingredient Issue
- #372 - Implement the WolfyUtils Dependency system
- #369 - Update zh_CN.json by @SnowCutieOwO
bca3359e- Adddata.syncoption that loads the data on the main thread- Required for plugins that use sync events for item creation (e.g. MMOItems)
New Contributors
- @Pavel-Gornov made their first contribution in #361
- @SnowCutieOwO made their first contribution in #369
Full Changelog: v4.16.9.1...v4.16.10
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:qmTmOySQ:YiVQ2vdU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qmTmOySQ:YiVQ2vdU"
}

