Enchantment Workshop
Version 1.0.0. Create native Minecraft enchantments through configuration files, an in-game GUI editor, and /ew commands. Supports 26.2 and 26.3 on Paper.
Create Enchantments from Scratch
Open /ew editor, select "Create New", and follow the prompts to enter an ID and display name. Text input is handled by clicking the chat prompt and entering /ew input <content>. The input session remains valid for two minutes; use /ew cancel to cancel.
The editor allows you to configure:
- Display name, description, maximum level, enchantment cost, and acquisition methods.
- Applicable item tags or individual items: Select from paginated lists of items and item tags registered on the current server, including content from other mods.
- Equipment slots and incompatible enchantments: Multi-select menus with conflict lists containing existing vanilla enchantments and custom enchantments defined in the current configuration.
- One to sixteen effects, each independently configured with a trigger, target, conditions, and actions.
- No conditions, all conditions required, or any condition required; supports conditions based on status, location, weather, time, and more.
- Preview, confirm and save, duplicate, create, and delete. Deleting an enchantment also removes references to it from other custom enchantments' conflict lists.
The GUI editor uses a "Trigger → Condition → Action" combination system, allowing enchantments to be created without starting from a template. It is an in-game menu editor, not an external desktop application or a node-based canvas with draggable connections. Existing triggers, conditions, and actions can be freely combined.
Ten enchantments are provided by default: Lifesteal, Frost, Critical Strike, Auto Smelt, Magnetism, Wisdom, Night Vision, Haste, Swiftness, and Guardian.
Programmable PROGRAM rules support:
| Component | Available Options |
|---|---|
| Triggers | Attack Hit, Damage Taken, Block Break, Entity Kill, Right-Click Interaction, Start Sneaking, Every-Second Check |
| Targets | Self; Attack Target or Damage Source (attack/damage triggers only) |
| Conditions | Sneaking, Sprinting, Swimming, On Ground, Burning, Health, Hunger, Dimension, Biome, Weather, Time, Height, Coordinate Region, Permission, Target Entity Type, Game Mode |
| Actions | Potion Effect, Explosion, Flight, Healing, Ignition, Upward Launch |
Auto Smelt supports Raw Iron, Raw Gold, Raw Copper, and Ancient Debris while preserving the original drop quantities. Silk Touch takes priority. Magnetism preserves any remaining drops when the player's inventory is full. Available potion types, entity types, dimensions, and biomes are retrieved from the server registries.
Flight Rules: Once activated, flight has no fixed duration. Flight permission remains active as long as the enchanted equipment stays in the designated slot, has durability greater than zero, and continues to satisfy the configured conditions. flight-durability-cost is consumed only when the player actually transitions from non-flight to flight. Hovering, normal movement, and landing do not consume durability. If the equipment breaks or is unequipped, the mod revokes the flight permission it granted and briefly applies Slow Falling. Any enchanted item with a flight action and durability greater than zero equipped in a valid slot provides immunity to fall damage, even before the player starts flying. Flight permissions granted by Creative Mode or other sources are not managed by this mod.
Saving and Reloading
Changes to effect values, actions, conditions, descriptions, global effect switches, and similar settings can be applied using /ew reload. Saving these changes through the editor or commands automatically triggers a reload.
Changes to registry-related information, including creating, deleting, or renaming enchantments, applicable items, equipment slots, conflicts, levels, acquisition methods, and enchantment costs, require a full server restart. In singleplayer, exit the world and re-enter it. The save screen indicates whether a restart is required, and /ew status can be used to check the current status. Do not use vanilla /reload as a substitute for a full restart when updating dynamic registries.
Configurations are validated before saving, and a backup is retained as enchantments.json.bak. If another administrator has modified the file, an outdated editor session cannot overwrite the newer changes. When editing JSON manually, ensure UTF-8 encoding and valid JSON syntax. See the Configuration Guide for detailed field descriptions.
Deleting an enchantment removes its definition. After restarting, Minecraft will no longer register that ID. However, deletion does not scan all containers and player data to perform bulk item migration. Existing items containing the deleted enchantment may lose it when their data is reloaded by vanilla Minecraft. If you only want to temporarily disable an effect, consider using globally disabled dimensions or removing the enchantment from specific equipment. Back up your configuration and world data before deleting enchantments.
Commands
Both command prefixes are equivalent: /ew and /enchantmentworkshop. The help, list, and info commands are publicly accessible. Editing, granting items, reloading, and other administrative operations require vanilla operator permissions (typically OP level 2 or higher). The server console can execute operations that do not require a player interface.
| Command | Description |
|---|---|
/ew editor [ID] |
Open the in-game Chinese GUI editor |
/ew list / /ew info <ID> |
View currently active enchantments |
/ew give <online_player> <ID> [level] [amount] |
Give native enchanted books |
/ew enchant <ID> [level] |
Enchant the item in the main hand, checking item compatibility and conflicts |
/ew remove <ID> |
Remove the specified enchantment from the main-hand item or enchanted book |
/ew create <new_ID> <name> |
Create a new enchantment definition that can be edited further |
/ew copy <source_ID> <new_ID> |
Duplicate an enchantment definition |
/ew set <ID> <field> <JSON_value> |
Modify an enchantment field, including nested fields using dot notation |
/ew effect <ID> add <type> |
Add an effect |
/ew effect <ID> set <index> <field> <JSON_value> |
Modify an effect; indices start at 1 |
/ew effect <ID> remove <index> |
Remove an effect; each enchantment must retain at least one effect |
/ew delete <ID> |
Preview deletion; repeat the command with confirm within two minutes to confirm |
/ew validate / /ew status |
Validate the configuration on disk and check restart requirements |
/ew reload |
Reload configuration changes that do not affect registry information |