Easily create custom recipes via an in-game GUI, including Crafting, Cooking, Smithing, etc. Use advanced config features to merge/copy NBT from ingredients to results, and run Extensions on recipe completion.

Below you'll find the basic information about the plugin to get going.
For more detailed information, tutorials, and information about advanced features, visit the wiki on GitHub.
/cc — Opens the GUI of CustomCrafting
Alias: /customcrafting
Permission: customcrafting.cmd.studio
/cc <option>
reload
—
Reloads the plugin data including items, recipes, languages, and GUIs.
Permission: customcrafting.cmd.reload
lockdown
—
Toggles the lockdown mode. When enabled, all custom recipes are locked and disabled.
Permission: customcrafting.cmd.lockdown
give
—
Gives a player the specified custom item
Permission: customcrafting.cmd.give
The Recipe Book is designed to help your players browse the custom recipes.
You can configure categories for your recipes, create filters that filter recipes by type, etc.
and sort recipes.
In the main menu (/cc) you can find the Recipe Editor on the bottom right, that allows you to add new categories/filters, and edit existing ones.
By the time of writing, the GUI is still a work in progress, and some features are only configurable by editing the recipe_book.conf!
GUI Permission: customcrafting.inv.recipe_book.*
/recipes — Opens the Recipe Book
Permission: customcrafting.cmd.recipes
The plugin provides a recipe book item by default, that opens the recipe book on right-click.
Permission: customcrafting.item.recipe_book
There are 3 types of custom crafting recipes.
Vanilla, Advanced and Elite Workbench recipes.
The vanilla recipes can be easily created via the Workbench option on the Main Menu
They are compatible with the Vanilla and Advanced Workbench.
Similar to the Vanilla recipes, but can only be crafted in the advanced crafting table.
The advanced crafting table is provided as a default item by the plugin and has particle effects when placed down. It has a vanilla crafting menu and all vanilla recipes can be crafted inside of it.
They are created via the same menu in the Recipe Creator, and the Advanced Crafting Table condition must be added & enabled.
/cc give <player> customcrafting:advanced_crafting_table
or via the default recipe
[This Feature is still in Beta]
Elite Crafting Tables have a custom inventory GUI with different sized crafting grids (2x2 - 6x6).
The Recipes are created via the Elite Crafting Table menu in the Recipe Creator GUI.
Other than the Advanced Workbench, you need to create your own.
To do that, you need to create an item via the Item-Creator (You can use any Block Item)
There you will find the Elite Workbench option on the second page.
After you saved the item, you can get the item via /cc give and create a recipe for it if you like.
customcrafting.inv.crafting.crafting_grid3
customcrafting.inv.crafting.crafting_grid4
customcrafting.inv.crafting.crafting_grid5
customcrafting.inv.crafting.crafting_grid6
customcrafting.inv.crafting.recipe_book
Unknown
Unknown
Умови використання, зміни та поширення цього товару.
22.06.2026 · Modrinth
v5 is a complete rewrite and redesign of the entire plugin and recipe structure.
It adds features and improvements that were not possible in v4.
In recent times, Minecraft has changed a lot, new modding/plugin platforms have emerged or separated themselves from their original project.
It's now a major task to make plugins/mods work across various platforms, each with their own different API.
With the [removal of...
Скриншоти та зображення з оригінальної сторінки Modrinth.


Опубліковані версії та оригінальні файли Modrinth.
22.06.2026 · 764 завантаження
v5 is a complete rewrite and redesign of the entire plugin and recipe structure.
It adds features and improvements that were not possible in v4.
In recent times, Minecraft has changed a lot, new modding/plugin platforms have emerged or separated themselves from their original project.
It's now a major task to make plugins/mods work across various platforms, each with their own different API.
With the removal of obfuscation, using and building against the Minecraft internals has become way easier.
It is for that reason that with v5 CC focuses on building features on top of the Minecraft internals instead of platform-specific APIs.
To keep compatibility, the goal of v5 is to integrate into each platform as best as possible (like Events, Listeners, Third-party Plugins/Mods), while keeping most of its codebase platform-agnostic.
That is where scafall comes in. Scafall allows for the creation of cross-platform APIs, which other mods and plugins may use, and makes it easier to link platform-specific implementations together.
However, all of this comes with a variety of new challenges, so going forward, CustomCrafting will only support the latest Minecraft version!
With the release of v5 on Modrinth comes a brand-new wiki, available at:
https://wolfyscript.github.io/CustomCrafting/
The new wiki provides many visual improvements and is managed using git now, making it easier to maintain than the old GitHub wiki.
v5 introduces support for Fabric servers. Server-side-only mods allow vanilla clients to connect to the Fabric server, so similar to Spigot, players don't need to install any client mods.
The Fabric implementation provides many benefits compared to the Spigot/Paper implementation.
It integrates custom recipes that have a vanilla counterpart directly into the vanilla recipe mechanism, this means better integration with existing mods and improved recipe book support.
Starting with this update, there is going to be a separate customcrafting and scafall jar file for paper specifically.
If you are using Paper, you should use that to benefit from the improvements and extra features.
Currently, that extra includes only the Stonecutter recipe support, which is missing in the Spigot version.
v5 introduces some major overhauls to the resource loading and recipe structure.
Sources define where resources are loaded from (Local directory, H2, SQLite, MySQL, etc.).
Backup destinations define where backups will get saved when created. (local directory or zip file)
v5 expands the functionality of all recipe types. Especially the ones that had a bit of a lacklustre feature set in v4.
Tip
This version adds some default recipes that showcase some of the new features.
They'll get loaded on startup and can be found here in the v5 branch
@p, @n, @r, @a, @e, @sThis update introduces new Ingredient options that allow configuring how they are matched and/or consumed.
These options are optional and use defaults that make them behave like they do in vanilla.
Options all have their own Registry, so third-party plugins/mods can register their custom behaviour for each option type.
These options specify how the Ingredient choices are matched against the source stack in the inventory.
Specifies how the Ingredient is consuming the source stack when the result is collected or produced.
CustomCrafting uses error tracking to assist in the maintenance of the plugin/mod.
The Error tracking integration makes issues/errors more visible and provides insight on how well the plugin/mod functions in production.
Which in return enables far quicker bug fixes and improvements than previously possible.
More information on the wiki.
22.06.2026 · 3 220 завантаження
v5 is a complete rewrite and redesign of the entire plugin and recipe structure.
It adds features and improvements that were not possible in v4.
In recent times, Minecraft has changed a lot, new modding/plugin platforms have emerged or separated themselves from their original project.
It's now a major task to make plugins/mods work across various platforms, each with their own different API.
With the removal of obfuscation, using and building against the Minecraft internals has become way easier.
It is for that reason that with v5 CC focuses on building features on top of the Minecraft internals instead of platform-specific APIs.
To keep compatibility, the goal of v5 is to integrate into each platform as best as possible (like Events, Listeners, Third-party Plugins/Mods), while keeping most of its codebase platform-agnostic.
That is where scafall comes in. Scafall allows for the creation of cross-platform APIs, which other mods and plugins may use, and makes it easier to link platform-specific implementations together.
However, all of this comes with a variety of new challenges, so going forward, CustomCrafting will only support the latest Minecraft version!
With the release of v5 on Modrinth comes a brand-new wiki, available at:
https://wolfyscript.github.io/CustomCrafting/
The new wiki provides many visual improvements and is managed using git now, making it easier to maintain than the old GitHub wiki.
v5 introduces support for Fabric servers. Server-side-only mods allow vanilla clients to connect to the Fabric server, so similar to Spigot, players don't need to install any client mods.
The Fabric implementation provides many benefits compared to the Spigot/Paper implementation.
It integrates custom recipes that have a vanilla counterpart directly into the vanilla recipe mechanism, this means better integration with existing mods and improved recipe book support.
Starting with this update, there is going to be a separate customcrafting and scafall jar file for paper specifically.
If you are using Paper, you should use that to benefit from the improvements and extra features.
Currently, that extra includes only the Stonecutter recipe support, which is missing in the Spigot version.
v5 introduces some major overhauls to the resource loading and recipe structure.
Sources define where resources are loaded from (Local directory, H2, SQLite, MySQL, etc.).
Backup destinations define where backups will get saved when created. (local directory or zip file)
v5 expands the functionality of all recipe types. Especially the ones that had a bit of a lacklustre feature set in v4.
Tip
This version adds some default recipes that showcase some of the new features.
They'll get loaded on startup and can be found here in the v5 branch
@p, @n, @r, @a, @e, @sThis update introduces new Ingredient options that allow configuring how they are matched and/or consumed.
These options are optional and use defaults that make them behave like they do in vanilla.
Options all have their own Registry, so third-party plugins/mods can register their custom behaviour for each option type.
These options specify how the Ingredient choices are matched against the source stack in the inventory.
Specifies how the Ingredient is consuming the source stack when the result is collected or produced.
CustomCrafting uses error tracking to assist in the maintenance of the plugin/mod.
The Error tracking integration makes issues/errors more visible and provides insight on how well the plugin/mod functions in production.
Which in return enables far quicker bug fixes and improvements than previously possible.
More information on the wiki.
22.06.2026 · 352 завантаження
v5 is a complete rewrite and redesign of the entire plugin and recipe structure.
It adds features and improvements that were not possible in v4.
In recent times, Minecraft has changed a lot, new modding/plugin platforms have emerged or separated themselves from their original project.
It's now a major task to make plugins/mods work across various platforms, each with their own different API.
With the removal of obfuscation, using and building against the Minecraft internals has become way easier.
It is for that reason that with v5 CC focuses on building features on top of the Minecraft internals instead of platform-specific APIs.
To keep compatibility, the goal of v5 is to integrate into each platform as best as possible (like Events, Listeners, Third-party Plugins/Mods), while keeping most of its codebase platform-agnostic.
That is where scafall comes in. Scafall allows for the creation of cross-platform APIs, which other mods and plugins may use, and makes it easier to link platform-specific implementations together.
However, all of this comes with a variety of new challenges, so going forward, CustomCrafting will only support the latest Minecraft version!
With the release of v5 on Modrinth comes a brand-new wiki, available at:
https://wolfyscript.github.io/CustomCrafting/
The new wiki provides many visual improvements and is managed using git now, making it easier to maintain than the old GitHub wiki.
v5 introduces support for Fabric servers. Server-side-only mods allow vanilla clients to connect to the Fabric server, so similar to Spigot, players don't need to install any client mods.
The Fabric implementation provides many benefits compared to the Spigot/Paper implementation.
It integrates custom recipes that have a vanilla counterpart directly into the vanilla recipe mechanism, this means better integration with existing mods and improved recipe book support.
Starting with this update, there is going to be a separate customcrafting and scafall jar file for paper specifically.
If you are using Paper, you should use that to benefit from the improvements and extra features.
Currently, that extra includes only the Stonecutter recipe support, which is missing in the Spigot version.
v5 introduces some major overhauls to the resource loading and recipe structure.
Sources define where resources are loaded from (Local directory, H2, SQLite, MySQL, etc.).
Backup destinations define where backups will get saved when created. (local directory or zip file)
v5 expands the functionality of all recipe types. Especially the ones that had a bit of a lacklustre feature set in v4.
Tip
This version adds some default recipes that showcase some of the new features.
They'll get loaded on startup and can be found here in the v5 branch
@p, @n, @r, @a, @e, @sThis update introduces new Ingredient options that allow configuring how they are matched and/or consumed.
These options are optional and use defaults that make them behave like they do in vanilla.
Options all have their own Registry, so third-party plugins/mods can register their custom behaviour for each option type.
These options specify how the Ingredient choices are matched against the source stack in the inventory.
Specifies how the Ingredient is consuming the source stack when the result is collected or produced.
CustomCrafting uses error tracking to assist in the maintenance of the plugin/mod.
The Error tracking integration makes issues/errors more visible and provides insight on how well the plugin/mod functions in production.
Which in return enables far quicker bug fixes and improvements than previously possible.
More information on the wiki.
21.09.2025 · 42 448 завантаження
details)details)details)details)details)details)04.09.2025 · 2 549 завантаження
24.04.2025 · 10 732 завантаження
15.04.2025 · 1 401 завантаження
26.03.2025 · 9 615 завантаження
From this update onward, WolfyUtils and CustomCrafting will only support the latest Minecraft version, including drops (minor versions)!
This will allow me to keep up with the new Minecraft update schedule, and concentrate on new features/bug fixes instead of compatibility.
LTS versions, with backported bug fixes, for the previous Minecraft version will be available to Premium. More info about it soon.
Full Changelog: https://github.com/WolfyScript/CustomCrafting/compare/v4.17-beta.5...v4.18.5
04.07.2024 · 68 849 завантаження
This backports a fix, from the recent beta version, to fix an invalid file copy action that causes crashes on some systems.
Full Changelog: v4.16.10...v4.16.11
02.07.2024 · 3 457 завантаження
Warning
This update requires the latest WolfyUtils beta !
You can download it from Modrinth: https://modrinth.com/plugin/wolfyutils/version/4.17-beta.4
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.
bca3359e - Add data.sync option that loads the data on the main threadFull Changelog: v4.16.9.1...v4.16.10
17.03.2024 · 33 653 завантаження
#357 — Fix ItemCreator not properly applying changes to CustomItems#358 — Fix Custom Durability in ItemCreator9c372b10 — Update Oraxen and fix durability application7251fda9 — Directly move from the ItemCreator to the Recipe ItemEditor when cancelling1ec37ad8 — Update Recipe ItemEditor GUI when editing/selecting item790dd645 — Opening the ItemCreator from the main menu now clears the previous item9fbf37ea — Reset previous settings when opening the ItemCreator to edit a new item5c73046a — Don't allow items in empty smithing ingredients6eb03614 — Fix Smithing Recipe preserve & onlyChangeMaterial propertiesd5ed0bc8 — Fix ItemEditor 'Edit Item' interaction hinta2a46712 — Fix ingredient choices not applying to RecipeCreator after editing them via the ingredient menuFull Changelog: v4.16.9...v4.16.9.1
03.03.2024 · 5 432 завантаження
By default, CC detects the source of the item, like Oraxen or MMOItem, etc., but if an item was manipulated manually, or contains multiple third-party plugin options, that system falls apart.
This update adds a new identifier selector to the Item Editor, so you can change the source of the detected stack.
In this example the Oraxen Amethyst was renamed outside Oraxen, CC detects that the stack is from Oraxen and links to it.
However, we want to keep the changes, so we shift + right-click on the result, and shift + right-click again to open the Item Editor.
Here we select the Bukkit parser, that keeps the item as is, so it is no longer linked to Oraxen, and manual stack changes are kept.
When using the local storage loader (default) a backup is created before the recipe and item configs are upgrade to the new format.
This applies to both the automatic upgrade and manual upgrade using the /recipes save.
The backups are stored as zip files inside the CustomCrafting/data_backups directory.
By default, each backup is kept for 60 days. The old backups are only deleted after the specified duration and only when a new backup was created.
The backup feature can be toggled and configured in the config.yml under local_storage.backup.
keep_for specifies the duration for which to keep the backups. The unit can be MINUTES, HOURS, DAYS, and even SECONDS etc.
The lockdown command requires a confirmation before actually toggling the mode.
When Lockdown is enabled, then a log message is printed on the first craft attempt after lockdown has been enabled.
Then another message on the first craft attempt every hour.
54d5ad48 — Reindex Recipe Book when recipes are validated after their dependencies5abf142b — Add a lockdown warning602e8dc2 — The lockdown command requires a confirmation nowf3e01ebc — Fix ShapelessRecipe ingredients failing before validation6f07c40d, 5d99bba3 — Use the new Result#item methods & remove CustomItem usagese43a7bf7 — Fix error in NBTMergeAdapter when selected ingredients are empty9056989f — Fix Anvil Recipe Validator not taking repairTask settings into account22f66be6 — Fix recipe book title in de_DE lang21ac468a — Fix old config files not accepted by validator due to missing original stackcfdf5a21 — Update Cauldron Menu Title when collecting result483e27cb — Replace bukkit recipe when registering in case it already existsFull Changelog: v4.16.8.5...v4.16.9
05.12.2023 · 14 443 завантаження
Full Changelog: v4.16.8.3...v4.16.8.5
15.08.2023 · 10 293 завантаження
Full Changelog: v4.16.8.2...v4.16.8.3
16.07.2023 · 3 394 завантаження
The new Armor Trim merge adapter makes it possible to copy armor trim patterns and materials from ingredients to the result stack.
It provides some further options to customize its behaviour.
Copies the pattern and changes the material to amethyst.
{
key = "customcrafting:armor_trim"
copyPattern = true
copyMaterial = false
defaultMaterial = "minecraft:amethyst"
}
Copies the pattern from the ingredient in slot 1 and the material from slot 2.
{
key = "customcrafting:armor_trim"
copyPattern = [ 1 ]
copyMaterial = [ 2 ]
}
Copies both the pattern and material.
{
key = "customcrafting:armor_trim"
copyPattern = true
copyMaterial = true
}
25.06.2023 · 3 968 завантаження
This is the first release on Modrinth.
Below you'll find the changelog of the most recent update. For previous changelogs, please visit GitHub
Smithing Recipes created in previous versions of CC will be loaded and converted.
By default, they will require the Netherite Upgrade Template to work. So similar to Netherite upgrade recipes.
You can edit the recipe using the in-game editor and remove the template, so that the recipe works without any template.
The crafting system got a complete overhaul again.
Crafting Recipes will register two Bukkit recipes now:
* Display recipe, that contains the ingredients with NBT and may be sent to the client's recipe book.
* Placeholder recipe, that contains the ingredients without NBT and is never send to the client.
Due to the placeholder recipes, it may override vanilla recipes, which then no longer work!
In that scenario, you need to create a custom recipe that is the same as the vanilla recipe and has a lower priority as the other custom recipe.
Campfire recipes are now completely based on Spigots API and no longer use any NMS code like in previous CC versions.
There are no breaking changes here, and it may even work more flawlessly than previously.
The item type merge adapter allows recipes to change the type of the result stack depending on an ingredient.
This is useful for repair/transform recipes, and other similar recipes, where the type of the ingredient should determine the result type.
The ID of the merge adapter is customcrafting:item and acts similar to the other merge adapters, with the difference that it only ever uses the first targeted ingredient slot.
For example, you could create a recipe that converts swords into axes:
target {
mergeOptions : [ {
slots : [ 4 ]
adapters : [ {
key : "customcrafting:item"
typeMappings { // Maps the sword types of the ingredient to a type for the result stack
wooden_sword = wooden_axe
stone_sword = stone_axe
iron_sword = iron_axe
golden_sword = golden_axe
diamond_sword = diamond_axe
}
} ]
} ]
}
For the recipe to work, it of course needs to allow all the different variants of items.
You can do that by shift + right-click on ingredient slots!
This is not meant to replace type specific recipes like for boats, doors, etc.
For those it is still required to create separate recipes, because this can only ever target a single ingredient!
When opening the Editor, it copies the current state of the Recipe Book, and you'll edit the copy from there.
(In comparison, prior to this update, you'd edit the original config directly)
When saving it, it creates a recipe_book_backup.conf of the current config.
It then saves the copy to the recipe_book.conf, which overrides the current config.
Each Category/Filter listed has an extra configure button below it that allows you to edit it, or move it to the left/right, to change the order of the categories/filters.
This is plainly a redesign and bug fix update of the editor.
It still does not cover all the settings available in the recipe_book.conf, so editing the file is still the preferred way.
Full Changelog: https://github.com/WolfyScript/CustomCrafting/compare/v4.16.7.2...v4.16.8.0