Skip to Content
Migration GuideFrom Oraxen to Nexo

From Oraxen to Nexo

Nexo is the successor to Oraxen, created by the same developer. This is the most common migration path, and LK Creator’s Converter handles it well.


Why Migrate?

  • Oraxen has been discontinued in favor of Nexo
  • Nexo supports Minecraft 1.21.1+ components (food, tool, equippable, etc.)
  • Active development and bug fixes are only happening on Nexo

What’s Different Between Oraxen and Nexo?

AspectOraxenNexo
MC Versions1.18 - 1.20.x1.20.5 - 1.21.5+
Components (1.21.1+)Not supportedFull support
RecipesNot supportedSupported
Config formatVery similarVery similar (evolved)
Active developmentNoYes

The config formats are very similar since Nexo is the direct evolution of Oraxen. Most properties convert 1:1.


Step-by-Step Migration

1. Locate Your Oraxen Configs

plugins/Oraxen/ items/ your_items.yml # <-- Upload this pack/ assets/ # Keep these

2. Convert Using LK Creator

  1. Open the Converter 
  2. Upload your Oraxen item config .yml file
  3. Set Source: Oraxen, Target: Nexo
  4. Preview and download

3. Copy Resource Pack Assets

Oraxen and Nexo use the same resource pack structure:

# From: plugins/Oraxen/pack/assets/your_namespace/ # To: plugins/Nexo/pack/assets/your_namespace/

Textures and models are fully compatible — just copy the entire assets directory.

4. Add Modern Components (Optional)

Since you’re now on Nexo, you can enhance items with 1.21.1+ components that weren’t available in Oraxen:

  • Food components — nutrition, saturation, effects
  • Tool components — mining speed, damage per block
  • Equippable — armor model references
  • Attribute modifiers — attack damage, attack speed, armor

See the Cookbook for examples of these components.


What Converts Automatically

  • Item names and display properties
  • Material assignments
  • Pack configuration (model references, textures)
  • Basic mechanics (furniture, blocks)
  • Custom model data values

What May Need Manual Attention

  • Oraxen-specific mechanics that have slightly different syntax in Nexo
  • Custom recipes — Oraxen doesn’t support them, so there’s nothing to convert. You can create them fresh in Nexo using LK Creator’s Recipe Generator
  • HMCCosmetics integration — if you were using Oraxen with HMCCosmetics, LK Creator supports converting to HMCCosmetics format

Conversion Matrix

For detailed information about which properties convert between Oraxen and Nexo, see the Supported Conversions page.