Known Limitations
While the converter handles most configurations, there are some limitations to be aware of.
General Limitations
- Custom code/scripts — Plugin-specific scripting (e.g., ItemsAdder actions, MythicMobs skill triggers) cannot be automatically converted
- Plugin-exclusive features — Some features exist in one plugin but not another. These properties will generate warnings and may be dropped during conversion
- Resource pack files — The converter handles YAML configuration files only. Texture files (PNG) and model files (JSON) must be manually moved to the target plugin’s expected directory structure
- Color code formats — The converter translates between MiniMessage and legacy color codes automatically, but complex gradients or advanced formatting may need manual review
- Events and mechanics — Custom event handlers and plugin-specific mechanics are generally not convertible as they depend on each plugin’s unique API
Plugin-Specific Notes
ItemsAdder
- Custom blocks using real blocks (mushroom stem, noteblock) may need manual adjustment after conversion
- Emote configurations are not converted
- ItemsAdder uses a
namespacein itsinfosection — the converter extracts this automatically
Oraxen
- Glyphs and custom fonts may need manual review after conversion
- Mechanics-specific configurations may be partially converted
- Oraxen does not support custom tridents — these will generate an error during conversion
Nexo
- Being a newer plugin, some legacy features from older plugins may not have a direct equivalent
- Nexo components are supported for versions 1.21.1 to 1.21.5
- Nexo natively supports tridents with
display_transformproperties
CraftEngine
- CraftEngine uses a different item structure with
behaviorblocks instead ofMechanics - Block configurations have a unique
block_modelandstatesystem - Components are available for versions 1.20.5 to 1.21.11
- Namespace format uses
namespace:item_idsyntax in item keys
MythicCrucible
- MythicMobs skill integration (
Skills,Triggers) is plugin-specific and cannot be mapped to other plugins - Attribute modifiers use MythicCrucible’s own format which differs from other plugins
- Enchantment categories include weapon, ranged, armor, tool, universal, curse, and trident types
- Only supports NOTEBLOCK-type blocks — other block mechanics (TRIPWIRE, MUSHROOM) are not available
- Does not support food, crop, or font item types
- Uses PascalCase for YAML keys (e.g.,
Material,Display,Generation) unlike other plugins
HMCCosmetics
- Available only as a conversion target — you cannot convert FROM HMCCosmetics to other plugins
- The converter maps items to cosmetic slots (Helmet, Backpack, Chestplate, Leggings, Boots, Offhand, Balloon)
- Not all item types have a meaningful mapping to cosmetic slots — review the assigned slot after conversion
- Dyeable support is optional and can be toggled during conversion
Understanding Conversion Output
After a conversion, you may see three types of notices:
Property Warnings
Specific properties that were translated but may need review. Each warning includes the item ID, property name, and a description of the issue. Warnings have severity levels:
- Info — Informational note, no action required
- Warning — May need manual review
- Error — The property could not be converted
Unsupported Features
Features detected in the source config that have no equivalent in the target plugin. These show the item ID, feature name, and an explanation.
General Errors
Critical issues that prevented parts of the conversion from completing.
Reporting Issues
If you encounter a conversion that doesn’t work correctly, please report it on our Discord server with:
- The source configuration (original YAML)
- The source and target plugins selected
- The warnings or errors shown
- What went wrong or what differs from expected