CustomiZer — Pack Conversion Guide

Contents

1. Overview

CustomiZer ships three built-in converters. Each one reads the native export format of the source plugin and produces a standard CustomiZer pack in plugins/CustomiZer/packs/<packName>/.

2. ItemsAdder Conversion

What to put in the input folder

Drop one content folder from ItemsAdder's contents/ directory. It must contain exactly these two sub-folders:

• configs/ — YAML item definitions (with info.namespace and items.* entries)
• resourcepack/ — namespaced resource pack assets already organized under assets/

Expected layout inside the input folder:

plugins/CustomiZer/converters/itemsadder/input/<packName>/
  ├── configs/
  │   └── <namespace>/
  │       └── items.yml          ← item definitions
  └── resourcepack/
      └── assets/
          └── <namespace>/
              ├── models/
              │   └── item/
              │       └── my_item.json
              └── textures/
                  └── item/
                      └── my_item.png

Command

/zpack convert itemsadder <packName>

What the converter does automatically

• Reads every YAML file under configs/ and extracts item definitions
• Copies models and textures from resourcepack/assets/ into the CustomiZer pack structure
• Generates a gui.yml so items appear in /z gui
• Auto-classifies items by name / material: hats, wings, swords, staves, cosmetics, etc.
• Creates functional YML files for swords, staves, and cosmetics so they appear in /zitems

3. Nexo Conversion

What to put in the input folder

Drop your exported Nexo pack folder inside the input directory. It must contain two sub-folders:

• items/ — YAML item definition files
• pack/ — resource pack assets (models, textures…)

Expected layout:

plugins/CustomiZer/converters/nexo/input/<packName>/
  ├── items/
  │   └── my_item.yml            ← item definitions
  └── pack/
      └── assets/
          └── <namespace>/
              ├── models/
              │   └── item/
              │       └── my_item.json
              └── textures/
                  └── item/
                      └── my_item.png

Command

/zpack convert nexo <packName>

4. Oraxen Conversion

What to put in the input folder

The Oraxen converter uses the same structure as Nexo — two sub-folders, items/ and pack/:

plugins/CustomiZer/converters/oraxen/input/<packName>/
  ├── items/
  │   └── my_item.yml            ← item definitions
  └── pack/
      └── assets/
          └── <namespace>/
              ├── models/
              │   └── item/
              │       └── my_item.json
              └── textures/
                  └── item/
                      └── my_item.png

Command

/zpack convert oraxen <packName>

5. After conversion

The converted pack is automatically placed in packs/<packName>/. Then reload and rebuild the resource pack:

1. 1Run the conversion command (see above).
2. 2Reload packs so CustomiZer picks up the new pack:
   /zpack reloadpacks
3. 3Rebuild the resource pack ZIP and push it to players:
   /zpack zip

6. List available packs before converting

Run the command without a pack name to see every folder that is ready to convert in the corresponding input directory:

/zpack convert nexo
/zpack convert oraxen
/zpack convert itemsadder

CustomiZer will list every valid pack found in the input folder so you can pick the right <packName>.

# 1. Drop the pack into:
#    plugins/CustomiZer/converters/nexo/input/my_pack/
#    (must contain items/ and pack/)

# 2. Convert
/zpack convert nexo my_pack

# 3. Reload and rebuild
/zpack reloadpacks
/zpack zip