Skip to Content
ConverterHow It Works

How the Converter Works

The LK Creator Converter allows you to migrate your existing item configurations between supported plugins without rewriting everything from scratch.

Note: The converter is currently marked as experimental. While it handles most configurations well, some edge cases may require manual adjustments.

Both Free and Pro users can access the converter. Free users have a limit of 12 conversions per day (tracked separately from generations). Pro users have unlimited conversions.

Step-by-Step Process

1. Select Source and Target Plugins

Choose which plugin your existing configuration is from (source) and which plugin you want to convert it to (target). You cannot select the same plugin as both source and target.

Source plugins: ItemsAdder, Oraxen, Nexo, CraftEngine, MythicCrucible

Target plugins: ItemsAdder, Oraxen, Nexo, CraftEngine, MythicCrucible, HMCCosmetics

2. Configure Target Options (if applicable)

Some target plugins have additional conversion options. For example, when converting to HMCCosmetics, you can select a default cosmetic slot and toggle dyeable support.

3. Upload Your YAML File

Drag and drop your .yml or .yaml configuration file into the upload area, or click to browse. The converter validates the file format before proceeding.

Only .yml and .yaml files are accepted. The converter validates the YAML syntax and will show an error if the file is malformed.

4. Preview the Conversion

Before converting, the system shows a conversion preview that includes:

  • Total items detected in your config
  • Unsupported features that have no equivalent in the target plugin
  • Property warnings for properties that may need manual review
  • Error count for items that cannot be converted

This preview lets you review potential issues before committing to the conversion.

Tip: The conversion preview is available without logging in. You can check compatibility before creating an account.

5. Confirm and Convert

After reviewing the preview, confirm to run the full conversion. The result appears in a side-by-side code comparison view showing your original YAML on the left and the converted YAML on the right.

6. Review, Edit and Download

The converted YAML is displayed in an interactive code editor where you can:

  • Toggle editing mode — Switch between edit and view-only mode
  • Expand the editor — Go full-screen for large configurations
  • Change the theme — Switch syntax highlighting themes
  • Copy to clipboard — Copy the converted YAML directly
  • Download as YML — Save the converted file (named originalname_converted.yml)

What Gets Converted

  • Item names and display names (with color code translation between formats)
  • Material mappings
  • CustomModelData values
  • Model and texture file references (with namespace handling)
  • Lore and enchantments
  • Attributes (attack damage, armor values, etc.)
  • Durability settings
  • Block configurations (hardness, tool requirements, light level)
  • Furniture settings (placement, hitbox, seat)
  • Weapon configurations (bow/crossbow pull states, trident models)
  • Food properties (hunger, saturation, effects)
  • Recipes (shaped, shapeless, cooking)
  • Permission nodes
  • Font and emoji definitions

Namespace Handling

The converter automatically detects and preserves your original namespace from the source configuration. This ensures that model paths, texture references, and item identifiers stay consistent after conversion.

After Converting

  • Move your asset files — The converter handles YAML configs only. You still need to copy your PNG textures and JSON model files to the correct directory structure expected by the target plugin.
  • Test in-game — Always verify the conversion on a test server before deploying to production.
  • Check warnings — Review any property warnings or unsupported feature notices and make manual adjustments if needed.

Tip: For large migrations, convert a few items first to verify everything works, then convert the rest.