Skip to main content
NMEntities 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 a single option in config.yml:
Leave it on and NMEntities detects whichever of the two you have installed and merges into it. Turn it off if you’d rather serve the NMEntities pack yourself.

​
Nexo

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

​
ItemsAdder

Almost automatic, with one manual step because of how ItemsAdder works. ItemsAdder has no pre-build hook, so instead NMEntities writes its assets into the folder ItemsAdder already merges from:
This happens every time the NMEntities pack is generated: on startup and on /nme reload. Because the files land in ItemsAdder’s own contents folder, run /iareload (or /iazip) once afterwards so ItemsAdder rebuilds its pack and picks them up. The console confirms the write, for example Merged 5883 file(s) into ItemsAdder (nmentities).

​
Good to know

  • The nmentities sub-folder inside ItemsAdder’s contents is fully managed by NMEntities. It’s rewritten on every reload, and stale models from an earlier build are cleared for you, so don’t hand-edit it.
  • Skins on player-type NPCs have nothing to do with this. They come straight from Mojang and work with or without Nexo or ItemsAdder.

​
Keeping the packs separate

Set merge-with-external-resources: false and NMEntities stops merging. You then serve its generated pack yourself, the same as on a server with no other resource-pack plugin.