Vendors

Guide for vendors and others wanting to make Third-Party packs for Nexo

Below is the recommended way to add content to Nexo in a "drag & drop" format For these examples I will make it as a store named "NexoMC"

ResourcePack

For including a ResourcePack, the ideal way is to use an "External Pack" Nexo allows for merging multiple full resourcepacks, so to avoid conflicts, it is the best approach Using proper namespaces is also ideal, not stuffing everything into the default minecraft-namespace Nexo/pack/external_packs/NexoMC/assets/nexomc/models/item/some_model.json This allows you to minimize possible conflicts with other packs and items others might have made

📁Nexo
└── 📁pack
    └── 📁external_packs
        ├── 📁RequiredPack.zip         #Nexo Default
        ├── 📁DefaultPack.zip          #Nexo Default
        └── 📁NexoMC
            └── 📁assets
                └── 📁nexomc
                    ├── 📁models
                    |   └── ...
                    └── 📁textures
                        └── ...

Items

Nexo also improves the structuring of items abit by allowing subfolders inside Nexo/items This means the recommended way to add premade itemconfigs is the following Nexo/items/NexoMC/nexo_christmas_furniture.yml

📁Nexo
└── 📁items
    └── 📁NexoMC
        ├── 📄 christmas_furniture.yml
        └── 📄 easter_armor.yml

Glyphs

There are no big changes to glyphs, but it allows for multiple namespaces now Same as with resourcepacks, you should use a separate namespace where you can

santa_claus:
  texture: nexomc:santa_claus
  font: nexomc:christmas_glyphs
  ...

PreviousEcoItems NextAPI

Last updated 3 months ago

📁Nexo └── 📁pack └── 📁external_packs ├── 📁RequiredPack.zip #Nexo Default ├── 📁DefaultPack.zip #Nexo Default └── 📁NexoMC └── 📁assets └── 📁nexomc ├── 📁models | └── ... └── 📁textures └── ...