ExecutableItems vs Nexo: Which Plugin Do You Need?
ExecutableItems and Nexo solve different problems and are built to work together, not against each other. Nexo generates and hosts the resource pack that gives your items, blocks, and furniture custom 3D textures; ExecutableItems attaches event-driven abilities, cooldowns, and conditions to items and can read Nexo's textures directly. If your item just needs to look different, Nexo alone is enough; if it needs to do something, you need ExecutableItems, with or without a resource pack underneath it.
This guide breaks down what each plugin actually does, how Nexo relates to Oraxen, and when to run one, the other, or both.
What Nexo Actually Does
Nexo is a resource-pack-first plugin: you define custom items, blocks, armor, and furniture in file-based configuration, and Nexo generates the resource pack and dispatches it to every player automatically. Per its own documentation, "Nexo automatically handles Resource Pack generation" and "dispatches the pack to all players on the server."
Nexo is listed on the official NexoMC store at €19.99 for a one-time purchase, requiring Paper 1.21.4+ or Folia 1.21.4+. There is no meaningful free tier: the core plugin is paid-only. Nexo also sells companion products (Carpentry for stairs/slabs/doors, Scaffolding for Bedrock support via Geyser) as separate add-ons.
What Nexo does not do: it has no event-driven ability system. It gives an item a look, a model, and a place in the world. Making that item do something on right-click, track a cooldown, or check a WorldGuard region is outside its scope.
Is Oraxen Still Maintained? Nexo vs Oraxen
Nexo is positioned as the modern successor to Oraxen, covering the same category: custom items, blocks, and resource-pack management. Oraxen's GitHub repository was still receiving commits as recently as July 2026, so it has not been archived or abandoned outright. But Nexo's documentation ships an official, dedicated migration tool at docs.nexomc.com/migrate/oraxen-nexo, described as "mostly automatic": you install the Nexo jar, copy your existing plugins/Oraxen folder into plugins/Nexo/converter/Oraxen, back up your server, remove the old Oraxen jar, and restart. The docs themselves warn that "there might be small oversights leading to minor loss of furniture/custom blocks" during conversion, so a tested backup is not optional.
Practically: if you're starting a new server today, there's little reason to pick Oraxen over Nexo given how actively Nexo is being promoted and developed. If you already run Oraxen and it works, the existence of an official migration tool means switching is a deliberate, tested decision rather than an emergency.
What ExecutableItems Actually Does
ExecutableItems is an ability plugin, not a texture plugin. Items are YAML files that attach event-driven activators (100+ of them, covering clicks, block breaks, entity hits, and dozens of other triggers) with conditions, cooldowns, delays, and chance rolls. A gun with a 3-round burst and a crouch requirement, or a totem that fires before the killing blow lands, is a single config file, no code required.
Crucially, ExecutableItems does not require a resource pack. Items work with vanilla materials and vanilla or custom textures out of the box. From 1.20.5+, EI can optionally generate and host its own resource pack via a config URL, and Premium ships 60+ included 3D weapon textures for 1.21.4+, but neither is mandatory to use the plugin's ability system.
Free vs Premium
| Tier | Cost | Limits |
|---|---|---|
| Free | €0 | 500 items, 1 activator per item, roughly 14 activators available, watermark in item lore |
| Premium | €19.99 one-time | Unlimited items and activators, all 100+ activators, no watermark, lifetime updates |
Source: ExecutableItems Free vs Premium FAQ.
Can You Use ExecutableItems With Nexo?
Yes, and this is the combination most servers running both plugins actually use. Per the ExecutableItems compatibility documentation, "you can use the textures from Nexo inside your ExecutableItem just by using the Custom model data value or the item_model." In practice: build your item's look in Nexo (model, texture, furniture placement if relevant), then reference that same Custom Model Data or item_model value inside an ExecutableItems config to attach abilities, cooldowns, and conditions to it. Neither plugin needs to know the other exists beyond that shared reference; there's no plugin dependency, soft or hard, between them.
Head-to-Head
| ExecutableItems | Nexo | |
|---|---|---|
| Core job | Item abilities & triggers | Resource-pack items, blocks, armor, furniture |
| Resource pack required | No (optional) | Yes, generated automatically |
| Event-driven activators | 100+ | None |
| Custom blocks / furniture | Via companion plugin ExecutableBlocks | Built in |
| Free tier | Yes (500 items, 1 activator/item) | No |
| Premium price | €19.99 one-time | €19.99 one-time |
| Minimum version | Works well below 1.21 | Paper/Folia 1.21.4+ |
| Reads the other plugin's items | Yes (Custom Model Data / item_model) | Not applicable |
What ExecutableItems Doesn't Do
To be direct about the limits: ExecutableItems does not generate or host a resource pack the way Nexo does out of the box (only an optional auto-host feature from 1.20.5+, not a full asset pipeline), and it does not manage custom blocks or furniture placement itself, that's the job of its companion plugin ExecutableBlocks. If your server's priority is a large catalog of custom-textured cosmetics, blocks, and furniture with minimal ability logic, Nexo alone may be all you need.
When to Choose Which
- Pick Nexo alone if your server's goal is visual: custom furniture, custom blocks, custom armor models, and you don't need items with triggered behavior.
- Pick ExecutableItems alone if you want abilities, cooldowns, and conditions on items and don't care about custom 3D textures, vanilla materials are fine.
- Run both if you want Nexo-textured items that also do something on right-click, kill, or block break, this is the most common real-world setup and the two plugins are designed to interoperate through Custom Model Data.
Get Started
- ExecutableItems documentation
- Best Minecraft Custom Items Plugin 2026: full comparison
- Custom Item Textures in Minecraft: the server owner's guide
- Getting Started with ExecutableItems
Sources
- ExecutableItems: Information, official plugin documentation
- ExecutableItems: Free vs Premium FAQ, free tier limits and premium pricing
- ExecutableItems: Compatible Plugins, Nexo texture compatibility (Custom Model Data / item_model)
- Nexo Documentation: Overview, resource pack generation and hosting
- Nexo Documentation: Migrate from Oraxen, official migration steps and caveats
- NexoMC official store, current pricing and version requirements, as of September 2026