> ## Documentation Index
> Fetch the complete documentation index at: https://entities.lodemc.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Nexo & ItemsAdder

> Merge LodeEntities' generated model assets into Nexo or ItemsAdder so players load one pack, and use their items on mobs.

LodeEntities generates a resource pack for your models, and it can hand those assets to another plugin that's already managing a pack, so your players only ever load one. Two integrations are supported: **Nexo** and **ItemsAdder**.

Both are controlled by one option in `config.yml`:

```yaml theme={null}
merge-with-external-resources: true   # on by default
```

Leave it on and LodeEntities detects whichever of the two you have installed and merges into it. Turn it off if you'd rather serve the LodeEntities pack yourself.

## Nexo

Fully automatic. Nexo offers a hook before it builds its pack, so LodeEntities hands its assets over and Nexo bundles them into its own build. Nothing else to do.

Nexo items also work on mobs: put `nexo:<id>` in a mob's [equipment](https://entities.lodemc.net/mob-equipment.md) or an item [mechanic](https://entities.lodemc.net/mechanics-items.md), and a Nexo item can run [`/le spawn`, `spawnlook` or `spawnat`](spawnlook) to summon a mob.

## ItemsAdder

Almost automatic, with one manual step because of how ItemsAdder works.

ItemsAdder has no pre-build hook, so LodeEntities writes its assets into the folder ItemsAdder already merges from:

```text theme={null}
plugins/ItemsAdder/contents/lodeentities/resourcepack/assets/
```

This happens every time the LodeEntities pack is generated: on startup and on `/le reload`. Because the files land in ItemsAdder's own contents folder, **run `/iareload` (or `/iazip`) afterwards** so ItemsAdder rebuilds its pack and picks them up. The console confirms the write, for example `Merged 5883 file(s) into ItemsAdder (lodeentities). Run /iareload to rebuild its pack.`

The `lodeentities` folder inside ItemsAdder's contents is **managed by LodeEntities**. It's rewritten on every reload and stale models from an earlier build are cleared for you, so don't hand-edit it.

## Keeping the packs separate

Set `merge-with-external-resources: false` and LodeEntities stops merging. You then serve its generated pack (`plugins/LodeEntities/build.zip`) yourself, the same as on a server with no other resource-pack plugin.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.