
注意:这是 CraftEnhance 项目的个人分支,原版发布在 Spigot。此版本可以安全地替换 Spigot 上的原版。
展示
该插件允许你通过图形界面在游戏内创建和禁用任何配方。它使用简单直观。以下是一个稍显过时但依然有用的演示视频,展示了核心功能:
演示

配方支持
支持完全自定义的酿造、工作台(包括合成器)、熔炉、烟熏炉和高炉配方。如果启用了“学习配方”选项,玩家加入时也会获得这些配方。
此外,当 Minecraft 版本支持时(如 1.14+ 等现代版本),插件会尝试使用完整的物品元数据(包括材料)直接在服务器上注册配方。在旧版本中,与输出物品相比,对材料元数据的支持可能较为有限。无论版本如何,插件都保证通过自动回退到兼容的普通物品注册方法来确保配方始终按预期工作。
自定义物品
你可以使用附魔、自定义名称、耐久度、药水或游戏中可用的任何物品数据来创建配方。
GUI 支持
通过库存图形界面,可以编辑配方、创建配方、查看配方以及在查看器 GUI 中对配方进行排序。
快速编辑访问
打开配方的编辑器不是通过命令完成的,而是通过在配方查看器中对某个配方点击鼠标中键完成。这需要相应的权限。
设置权限
为了给予服务器管理员完全的控制权,自定义配方存在权限限制。没有特定自定义配方权限的人无法制作或查看该配方。“查看”部分可以进行配置。
隐藏配方
你可以简单地为没有相应“绕过”权限的玩家隐藏配方。如果他们拥有该配方的权限,他们仍然可以制作这些配方。
禁用原版配方
有一个图形界面可供你禁用所有你想要的原版配方。不再有过于强大且廉价的钻石/下界合金盔甲!
在游戏中编辑物品
要制作酷炫的配方,需要一个物品编辑器。这个物品编辑器允许用户设置彩色描述文本、彩色名称、耐久度、附魔、物品标志,甚至是物品的本地化名称。顺便说一句:也支持物品标志(用于隐藏附魔或属性)。
Tab 补全支持
我个人认为自 Minecraft 1.13 更新以来这是一个必备功能。再也不用记住所有命令了,只需输入基础命令的前几个字母即可。
以下是与自定义配方创建和查看相关的命令。
命令
/ceh -> 对此使用 Tab 补全!
/ceh viewer [页码或分类] [编号或名称] -> 打开配方查看器 GUI。你也可以打开特定的页面或配方分类。
/recipes -> 打开配方查看器 GUI。
/ceh createrecipe [密钥] [权限] -> 使用指定的密钥和权限创建一个配方。如果没有提供参数,它将为你生成一个密钥,并让该配方不需要任何权限。
/ceh specs [密钥] -> 显示指定密钥配方的规格。目前规格仅包含权限信息。
/ceh setpermission [密钥] [权限] -> 将指定密钥配方的权限更改为新权限。
/ceh changekey [密钥] [新密钥] -> 此命令允许用户更改指定密钥配方的密钥。
/ceh reload -> 重新加载整个插件!
物品编辑
物品编辑
/edititem -> 这是编辑物品的基本命令。请对此使用 Tab 补全。
/edititem name [名称] -> 编辑你主手中物品的名称。
/edititem durability [1-100] -> 将你主手中物品的耐久度设置为最大耐久度的 [1-100]%。
/edititem enchant [附魔,clear] [等级] [... 等等] -> 将你指定的附魔设置到你手持的物品上。它会移除所有现有的附魔(不会保留旧的附魔),然后添加指定的附魔。如果觉得奇怪需要修改,请告诉我。如果要清除旧附魔,请使用 clear 代替附魔名称。
/edititem itemflag [物品标志] [物品标志] [... 等等] -> 切换你手持物品上指定的物品标志。
/edititem lore [行号] [描述文本] -> 将你手持物品的描述文本指定行设置为指定的文本。如果需要添加空行,文本部分可以留空。

权限是可配置的!
不过,以下是默认权限。你也可以在 config.yml 文件中查找它们。
权限
craftenhance.edit -> 用于 /ceh createrecipe, /ceh cleanitemfile, /ceh reload, /ceh setpermission, /ceh specs, /ceh changekey。这也是点击鼠标中键打开编辑器所需的权限。
craftenhance.view -> 用于 /ceh viewer, /recipes
craftenhance.edititems -> 所有以 /edititem 开头的命令。
craftenhance.edit_categorys -> 给你编辑分类的选项,这样你就可以从此分类中移动配方、删除分类、更改分类名称以及更改显示物品。
除了 config.yml 之外,还会生成四个额外文件:guitemplates.yml, recipes.db, categorys.yml, 和 server-recipes.yml。
GUI 模板
此文件允许你完全自定义插件使用的所有 GUI。预设配置应该相当不言自明,因此这里只涵盖核心概念:
- fill-space:定义可以自动填充物品的槽位索引范围(例如配方查看器中的配方槽)。
- Menus:包含不同的 GUI 菜单。请勿重命名这些键,因为它们在内部是必需的。
- buttons:指定按钮位置,以及每个按钮在菜单中显示的名称和描述文本。
- action_type:定义按钮执行的操作类型。这些操作是硬编码的,无法修改。
Recipes Database
所有配方都存储在此 SQLite 数据库中。虽然可以在这里手动创建或编辑配方,但不建议这样做,因为所有配方都可以通过游戏内的 GUI 进行管理。
config
此文件包含各种设置,包括消息和权限。其中有两个重要选项:一个用于在不影响服务器上已注册配方的情况下禁用自定义合成;另一个用于控制玩家是否可以查看他们没有权限使用的配方。

Note: This is my own fork of the CraftEnhance project, originally released on Spigot. This version can safely replace the Spigot one.
Showcases
The plugin allows you to create and disable any recipe in-game through guis. It’s simple and intuitive to use. Here’s a slightly outdated but still useful video that demonstrates the core features:
Demonstration

Recipe support
Supports fully custom recipes for brewing, crafting tables (including the crafter), furnaces, smokers, and blast furnaces. If “learn recipes” is enabled, recipes will also be granted to players on join.
In addition, the plugin will attempt to register recipes directly on the server using full item metadata, including ingredients, when the Minecraft version supports it (modern versions like 1.14+). In legacy versions, ingredient metadata support may be more limited compared to output items. Regardless of version, the plugin guarantees full functionality by automatically falling back to a compatible plain-item registration method so recipes always work as expected.
Custom Items
You can create recipes using enchantments, custom names, durability, potions, or basically any item data available in the game.
GUI Support
Editing recipes, creating recipes, viewing recipes and ordering the recipes in the viewer GUI are all possible through inventory GUIs.
Quick Edit Access
Opening the editor for a recipe is not done through a command, but done through a simple middlemouseclick on a recipe in the recipe viewer. This does require a permission.
Set permission
To give server owners full control, permissions for the custom recipes exist. People that don't have the permission for a custom recipe, can’t craft or view it. The 'seeing' part can be configured.
Hide recipes
You can simply hide recipes for the players that don't have the 'bypass' permission for it. They'll still be able to craft the recipes if they have permissions for the recipe.
Disable vanilla recipes
There's a gui which you can use to disable all the vanilla recipes you want. No more over-powered, cheap diamond/netherite armor!
Edit items in-game
To make cool recipes an item editor is needed. This item editor allows users to set colored lore, colored names, durability, enchantments, item flags, and even the localized name of items. And for the record: Item flags (used to hide enchantments or attributes) are also supported.
Tab completion support
I personally think this is a must have feature since the 1.13 update of Minecraft. No more remembering all commands, just the first few letters of the basics.
These are the commands related to custom recipe creation and viewing.
Commands
/ceh -> Use tabcompletion on this!
/ceh viewer [page or category] [number or name] -> Open the recipe viewer GUI. You can also open specific page or a recipe category.
/recipes -> Open the recipe viewer GUI.
/ceh createrecipe [key] [perms] -> Create a recipe with the specified key and permission. If no arguments are given it'll generate a key for you and let the recipe require not permission.
/ceh specs [key] -> Show the specs of the recipe with the specified key. The specs only include the permission currently.
/ceh setpermission [key] [perms] -> Change the permission of the recipe with the specified key to new_permission.
/ceh changekey [key] [newKey] -> This command allows users to change the key of the recipe with the specified key.
/ceh reload -> Reloads the whole plugin!
Item editing
Item editing
/edititem -> This is the basic command for editing items. Please use tab completion on this.
/edititem name [name] -> Edit the name of the item in your main hand.
/edititem durability [1-100] -> Set the durability of the item in your main hand to [1-100]% of it's max durability.
/edititem enchant [enchantment,clear] [level] [... etc.] -> Set your specified enchantments to your held item. It removes all enchants (will not remove old enchants, any more) and then adds the specified ones. Please let me know if this is weird and needs modification. For clear old enchants use clear instead of the enchantment name.
/edititem itemflag [itemflag] [itemflag] [... etc.] -> Toggle the specified itemflags on your held item.
/edititem lore [line_number] [lore] -> Set the specified line of the lore of your held item to be the specified text. The text section can be left empty if an empty line needs to be added.

The permissions are configurable!
However, these are the default permissions. You can also look these up in the config.yml file.
Permissions
craftenhance.edit -> for /ceh createrecipe, /ceh cleanitemfile, /ceh reload, /ceh setpermission, /ceh specs, /ceh changekey. This is also the permission required to middleclick recipes to open the editor.
craftenhance.view -> for /ceh viewer, /recipes
craftenhance.edititems -> All commands that start with /edititem.
craftenhance.edit_categorys -> gives you the option to edit categories, so you can move recipes from this category,remove category,change category name and change the display item.
Alongside config.yml, four additional files will be generated: guitemplates.yml, recipes.db, categorys.yml, and server-recipes.yml.
GUI Templates
This file allows you to fully customize all GUIs used by the plugin. The preset configuration should be fairly self-explanatory, so only the core concepts are covered here:
- fill-space: Defines a range of slot indexes where items can be automatically filled (for example, recipe slots in the recipe viewer).
-Menus: Contains the different GUI menus. Do not rename these keys, as they are required internally.
- buttons: Specifies button locations, as well as the name and lore displayed for each button in the menu.
- action_type: Defines what action a button performs. These are hardcoded and cannot be modified.
Recipes Database
All recipes are stored in this SQLite database. While it is possible to manually create or edit recipes here, it is not recommended, since all recipes can be managed through the in-game GUIs.
config
This file contains various settings, including messages and permissions. Two important options are: one that allows you to disable custom crafting without affecting recipes already registered on the server, and another that controls whether players can view recipes they don’t have permission to use.
评论 0
登录后参与评分
还没有评论,来抢沙发吧