The resource pack

Minecraft servers can't send a texture to a player on their own. The resource pack is the file that carries your artwork to everyone who joins.

No pack, no custom look. Without it your armour still works — right stats, right name, right recipe — but it looks like plain iron. Everyone who plays on your server needs it.

What's inside it

You never need to open the zip, but here's what the parts are:

Part	What it's for
Worn textures	How the gear looks on a player, wolf, horse or ghast
Inventory icons	How it looks in a slot and in a hand
Tooltip artwork	Custom tooltip backgrounds and frames, if you made any
Item definitions	Tells Minecraft which item shows which model
`pack.mcmeta`	The pack's name, icon and version range

The pack works on Minecraft 1.21.4 through 26.2. One file for every client.

Where your pack is

After a deploy, on your server:

plugins/NxEquipement/output/resourcepack.zip

Or press Java resource pack on the Build & Export screen to download it.

Now pick how players get it

You use no other custom-item plugins

Easiest path: deploy from the editor and click the button in chat, or run /nxe confirm. NxEquipements hands the pack out for you and you're done.

If you'd rather host it yourself, see Host the pack yourself.

You also use Nexo, ItemsAdder, Oraxen or similar

You have a problem to solve, and there's a standard fix. Only one resource pack can be active at a time. If two plugins each send their own, the second replaces the first and one of them stops working.

The fix is to merge them into one. See Merge with other plugins.

You have Bedrock players through Geyser

Bedrock needs its own version of the pack. See Bedrock and Geyser.

Rebuilt your pack? Hand it out again. Every time you press Build pack the file changes. Deploy again, re-merge, or re-upload — whichever route you use. Players keep the old look until they get the new file.