Resource packs

Nexo export

The Nexo export is content for a server already running Nexo, not a second resource pack for players to install. It contains item definitions and a normal pack folder. Nexo reads the definitions, builds the item wiring, merges the pack folder, and serves the result to players.

Install it#

1. In Export, choose Plugin Support → Nexo.
2. Unzip the download directly into your server's plugins/ folder. Do not put the zip inside Nexo/items or Nexo/pack — it already contains those folders.
3. Run /nexo reload, then rejoin or send Nexo's regenerated pack to players.

The resulting layout is:

plugins/
  Nexo/
    items/<your-pack>/items.yml
    pack/external_packs/<your-pack>/assets/

Nexo merges folders in external_packs into the resource pack it generates. The separate namespace keeps your models and textures from colliding with other content. To give an exported item, use /nexo give <item-id> [amount] [player]; the exact ids are the keys in items.yml.

What comes across#

Nexo assigns the required item wiring, including CustomModelData on servers that use it. Do not add a value by hand unless you are deliberately managing your entire server's allocation. On 1.21.4+ clients, Nexo can instead use item models when Pack.generation.prefer_item_models is enabled in its settings.

Limits#

Exported 3D models are static items. Their animation keyframes remain in the model JSON, but vanilla item rendering does not play them; use Model Engine or RP Engine where animated playback is required.

Icons, font-based GUI overlays, HUDs and shader canvases are intentionally not included. Nexo's font configuration owns the same provider files as its own glyphs, so merging ours would risk replacing existing emoji or UI. Use the Java export for those assets, or add them to Nexo using its font configuration.