On this page
- Choose the plugin before adding sword files
- Set up resource pack hosting first
- Create a sword with ItemsAdder
- Create the configuration and texture files
- Compile the pack and obtain the sword
- Define a sword with Nexo
- Save the definition and reload Nexo
- Use a ready-made pack to skip drawing the swords
- Check missing textures before adding more weapons
Key takeaways
5- Start with a working Nexo or ItemsAdder installation and configure resource pack hosting before adding sword artwork.
- ItemsAdder's modern sword example uses a namespaced YAML file, a PNG texture and /iazip to compile changes.
- Nexo's documented full reload command is /nexo reload; /nexo pack resends the pack.
- Players must accept the resource pack, and modern graphics or ItemModels require compatible client versions.
- Our team's Sword Expansion Pack supplies 18 sword textures and preconfigured files for either plugin.
This guide is for server owners who want custom sword appearances using Nexo or ItemsAdder. You will define a sword, generate its resource pack and check that players receive the artwork, with a ready-made option if you want to skip drawing the textures.
Choose the plugin before adding sword files
Nexo creates custom items through file-based configuration and generates and sends their resource pack. Its documentation covers item names, materials, textures, enchantments and attribute modifiers.
ItemsAdder also generates resource packs and provides a dedicated first-sword tutorial. Its documented sword configuration includes a texture reference and a maximum durability setting.
| Route | Starting point | Pack workflow | Free or paid |
|---|---|---|---|
| Nexo | An item YAML with a material and Pack settings | Generate the pack and select a hosting method | Paid |
| ItemsAdder | A namespaced content folder containing configuration and textures | Compile changes with /iazip after setting up hosting | Paid |
Use one route for this first sword. If you are still choosing a content system, our custom content plugin comparison covers that broader decision.
Begin with a working installation of your chosen plugin. Check its installation requirements and supported versions before adding content, rather than assuming a configuration pack also installs the plugin. If you have not prepared the base server yet, follow our server installation guide first.
Set up resource pack hosting first
Choose how players will receive the generated pack before troubleshooting the sword itself. ItemsAdder's hosting documentationSource site lists Simple Self Host, LobFile and self hosting among its recommended options. Its first-sword tutorial recommends simple self hosting for version 4.0.17 and later.
Nexo chooses hosting through Pack.server.type in settings.yml. Its documented options include POLYMATH, an upload service run by the Nexo team, SELFHOST, LOBFILE and S3. Nexo's self-hosting option needs an open port and a public address.
Use your shell or SFTP client to open the selected plugin's hosting configuration. Follow its hosting guide for the chosen method. If you choose Nexo SELFHOST, arrange the public address and open port that its documentation requires.
Use the File Manager or SFTP to edit the plugin's hosting settings. Before choosing a method that needs an additional port, ask your host whether it can provide one. Choose a documented upload-based method if an additional port is unavailable.
Use Files / FTP to edit the hosting configuration. Ask your host about additional ports before choosing self hosting. If the panel does not expose the necessary network settings, ask the host to configure them or use another documented hosting method.
Do not change several hosting settings while also rewriting the sword configuration. First establish the delivery method, then work through one item.
Create a sword with ItemsAdder
The official first-sword tutorialSource site uses a namespace, an item definition and a PNG texture. The example below follows its modern graphics format, which requires Minecraft 1.21.4 or later clients.
Create the configuration and texture files
The paths below are relative to your ItemsAdder plugin folder.
Using your shell or SFTP client, create contents/my_items/configs/myswords.yml. Upload your sword texture to contents/my_items/textures/item/mysword.png, creating the folders as needed.
In the File Manager, open the ItemsAdder plugin folder. Create contents/my_items/configs/myswords.yml, then upload the PNG to contents/my_items/textures/item/mysword.png. SFTP is another way to create and upload these files.
Open the ItemsAdder plugin folder through Files / FTP. Create contents/my_items/configs/myswords.yml and upload the texture to contents/my_items/textures/item/mysword.png.
Put this definition in myswords.yml. The name is an example; the configuration keys follow the documented sword structure.
info:
namespace: my_items
items:
mysword:
name: Harbor Sword
material: DIAMOND_SWORD
permission_suffix: my_items.mysword
graphics:
texture: item/mysword
durability:
max_durability: 1324The texture reference is relative to the namespace's textures folder and omits .png. Keep item/mysword aligned with the uploaded file rather than entering its full server path.
Compile the pack and obtain the sword
In the server console, run iazip to compile the changes. In game, use an account with the required command access and run /iaget my_items:mysword.
Open Console and run iazip. Once compilation finishes, run /iaget my_items:mysword in game using an account with the required command access.
Use the server console to run iazip. Then run /iaget my_items:mysword in game using an account with the required command access.
For a visual introduction, the following tutorial covers adding custom content with ItemsAdder. Use the current wiki's syntax and hosting instructions when following along.
Define a sword with Nexo
Nexo's item documentationSource site describes itemname, material and a Pack section containing texture and model settings. The following example combines those documented fields into a sword definition.
harbor_sword:
itemname: Harbor Sword
material: WOODEN_SWORD
Pack:
texture: custom/items/harbor_sword
custom_model_data: 452harbor_sword and the texture reference are illustrative names. The value 452 comes from Nexo's documentation example; it is not a required sword identifier. This YAML does not contain the artwork, so supply the corresponding texture through your resource pack and follow the documentation for its asset layout.
Nexo generates its pack in plugins/Nexo/pack. Its resource pack documentation also supports third-party ZIP files or folders in external_packs, where they are merged into the generated pack.
Save the definition and reload Nexo
Use your shell or SFTP client to edit the item YAML in your Nexo configuration and add the matching pack assets according to the resource pack documentation. In the server console, run nexo reload. In game, run /nexo give harbor_sword.
Use the File Manager or SFTP to edit the item YAML and upload the matching pack assets. Open Console and run nexo reload, then run /nexo give harbor_sword in game.
Use Files / FTP to edit the item YAML and upload the matching pack assets. Run nexo reload in the console, then obtain the item in game with /nexo give harbor_sword.
The documented command to reload everything is /nexo reload. It covers items, recipes and the pack; separate reload targets include items and pack. The reload permission is nexo.command.reload, and giving items requires nexo.command.give.
This Nexo overview provides a visual introduction to its custom content workflow.
Use a ready-made pack to skip drawing the swords
Our Sword Expansion Pack, made by our team, is a paid option containing 18 sword textures with a vanilla-like model, editable names and preconfigured files for both ItemsAdder and Nexo. It also includes 18 PNG images and a README with installation instructions for each plugin.
Choose the configuration for the plugin you already run and follow that README. The pack requires either ItemsAdder or Nexo for its supplied configurations; using it as a plain vanilla texture pack requires implementing the swords yourself.
- Choose the manual route if you want to draw and configure your first sword yourself.
- Choose the supplied configurations if you want a set of sword appearances without preparing those definitions from scratch.
- Our team's support covers adding the pack's files to either plugin, rather than general troubleshooting of those plugins.
Check missing textures before adding more weapons
Test one sword through the complete workflow before expanding the collection. Use this order to keep configuration, artwork and pack delivery checks separate.
- Check the item identifier. Use the identifier from your configuration when obtaining the sword, such as
my_items:myswordfor the ItemsAdder example. - Check the artwork reference. For ItemsAdder, confirm that
item/myswordmatches the PNG under the namespace's textures folder. - Check pack generation. Complete the compilation or reload step for your chosen route after changing the assets.
- Check delivery and acceptance. Confirm that hosting is configured and that the player accepted the pack.
- Check client requirements. The ItemsAdder example uses modern graphics syntax; Nexo's ItemModels also require Minecraft 1.21.4 or later clients.
If Nexo's automatic pack sending failed, its documented resend command is /nexo pack <player>, requiring nexo.command.pack.
In the server console, run nexo pack PlayerName, replacing PlayerName with the test player's name.
Open Console and run nexo pack PlayerName for the test player.
Use the server console to run nexo pack PlayerName for the test player.
For ItemsAdder, distinguish configuration reloads from pack generation: its wiki lists /iareload for configuration changes and /iazip for resource pack generation. For texture changes, return to the compilation step above rather than relying on a configuration reload alone.
Frequently asked questions
How do I make a custom sword in ItemsAdder?
Create a namespaced item configuration and upload its matching PNG texture, following the official first-sword tutorial. Run /iazip to compile the changes, then /iaget my_items:mysword for the example item. Configure pack hosting and accept the pack so the artwork displays.
How do I create a custom item in Nexo?
Define the item in YAML using documented fields such as itemname, material and Pack texture settings. Supply the matching resource pack assets, run /nexo reload and obtain it with /nexo give . The YAML definition alone does not include the artwork.
Why are my ItemsAdder sword textures not showing?
Check that the configured texture reference matches the PNG path and omits the .png extension. Compile the changed assets with /iazip, then check hosting and whether the player accepted the pack. The modern graphics example also requires Minecraft 1.21.4 or later clients.
Should I use CustomModelData or ItemModels in Nexo?
Nexo's documentation recommends ItemModels when your supported clients are all on Minecraft 1.21.4 or later. It describes CustomModelData as the option for supporting older clients. Choose according to the clients your server needs to support.
Do ready-made sword configurations replace ItemsAdder or Nexo?
Our Sword Expansion Pack requires either ItemsAdder or Nexo to use its supplied configurations. It includes configurations and a README for both plugins. Implementing the swords in a plain vanilla texture pack requires doing that work yourself.
