Skip to Content
Migration GuideFrom Other Generators

From Other Generators

Migrating to LK Creator from other item generation tools or manual processes.

From MCModels / Model Marketplaces

If you’ve been purchasing or downloading models from MCModels or similar marketplaces:

  1. Your models are compatible — LK Creator works with standard Minecraft JSON models and PNG textures
  2. Upload your purchased models and textures to the LK Creator Generator
  3. Select your target plugin(s) and fill in the configuration
  4. Generate the complete resource pack with proper plugin configs

Tip: Use Batch generation (Pro) to process multiple purchased models at once.

From MCStacker / Command Generators

If you’ve been using command generators to create custom items:

  1. MCStacker generates /give commands — these are not plugin configs
  2. LK Creator generates plugin-specific YAML configs that work with ItemsAdder, Nexo, Oraxen, and CraftEngine
  3. You cannot directly import MCStacker output, but you can recreate items in LK Creator using the same textures and models

From Hand-Built Resource Packs

If you’ve built resource packs manually (editing JSON models and textures directly):

  1. Keep your assets — your textures and models are the most valuable part
  2. Use LK Creator to generate the plugin configuration YAML that references your assets
  3. In Developer Mode, you can fine-tune the exact YAML output
  4. LK Creator handles the boilerplate (namespace paths, model predicates, custom model data) automatically

Manual Resource Pack Structure to LK Creator

What you had:

assets/
  minecraft/
    models/
      item/
        paper.json       # Custom model data overrides
    textures/
      item/
        custom_sword.png

What LK Creator generates:

# Plugin-specific config (e.g., Nexo):
custom_sword:
  itemname: "Custom Sword"
  material: PAPER
  Pack:
    generate_model: true

# Plus the resource pack structure:
pack/
  assets/
    your_namespace/
      models/item/custom_sword.json
      textures/item/custom_sword.png

From Another Server Using Different Plugins

If you’re migrating an entire server from one plugin ecosystem to another:

  1. Export all item configs from your current plugin
  2. Batch convert using the LK Creator Converter — upload one config file at a time
  3. Review each conversion result for warnings and unsupported features
  4. Transfer your resource pack assets (textures, models) to the new plugin’s directory
  5. Test in a staging environment before going live
  6. Gradually roll out to production

Important Considerations

  • Player inventories: Custom items in player inventories may break if the internal IDs change. Plan for this with your server admin tools
  • Economy/shop plugins: Update any shop configurations that reference custom item IDs
  • Permission nodes: Different plugins use different permission systems
  • Recipes: May need to be recreated for the target plugin

Getting Help

Migration can be complex, especially for large servers. Resources:

From Oraxen to NexoMinecraft Version Compatibility