ExecutableItems vs ItemsAdder: Which Fits Your Server?
Short answer: ExecutableItems and ItemsAdder solve different problems and are not really substitutes for each other. ExecutableItems gives any item YAML-configured abilities (triggers, cooldowns, conditions) without requiring a resource pack, while ItemsAdder is a resource pack manager built to add custom textures, blocks, mobs, furniture, and HUD elements. Many servers run both together, since ExecutableItems can read ItemsAdder textures directly.
This guide breaks down exactly where the two overlap, where they complement each other, and which one (or both) belongs on your server.
What Does Each Plugin Actually Do?
ExecutableItems: items that do things
ExecutableItems is a YAML-based plugin that attaches event-driven abilities to any Minecraft item. Every ability starts with an activator, an in-game event such as a right click, a block break, or taking damage, and the plugin ships with 100+ activators covering nearly every player action. Each activator supports conditions, cooldowns, delays, and chance rolls, so a grappling hook, a burst-fire gun, or a totem that triggers before death is a single YAML file, no coding involved.
Custom textures are optional. ExecutableItems works on vanilla item models out of the box; a resource pack is only needed if you want the included 3D weapon models, and the docs explain how to host it.
ItemsAdder: assets, blocks, and the resource pack pipeline
ItemsAdder is a resource pack manager and content framework first. Its job is handling the full pipeline from a custom 3D model to an in-game item, block, mob, furniture piece, or sound, served to players automatically through a resource pack. It also covers custom HUDs, GUI elements, emojis and font-based graphics, and custom paintings.
Because it is asset-first, a resource pack is not optional for ItemsAdder: textures and models depend on client-side assets the player has to download and accept when joining.
Where They Overlap
Both plugins let you create "custom items" in the loose sense, and both support CustomModelData and item textures. If your only goal is renaming an item and giving it a new texture, either plugin can technically do it. That overlap is where a lot of the "which one do I need" confusion comes from, but it stops there: ExecutableItems does not manage resource pack assets as its core job, and ItemsAdder's ability/trigger system is far more limited than ExecutableItems' activator list by default.
Where They Complement Each Other
This is the part worth knowing before picking one over the other: ExecutableItems and ItemsAdder are built to be compatible, not exclusive. According to SPlugins' own compatible plugins documentation:
- An ExecutableItems item can use an ItemsAdder texture directly, either through the
customModelDatafield or theitem_modeloption. - An ItemsAdder item file can link to an ExecutableItems ability by adding an
executableitemid block to it, meaning the visual comes from ItemsAdder while the behavior comes from ExecutableItems. - ExecutableBlocks (a companion SPlugins tool) can reuse an ItemsAdder block's texture as its visual model.
- ExecutableItems activators can target ItemsAdder blocks specifically through the
detailedBlocksoption.
In practice, a common setup is: ItemsAdder handles the resource pack, custom textures, and cosmetic assets; ExecutableItems handles what those items do when a player interacts with them.
Feature Comparison
| Category | ExecutableItems | ItemsAdder |
|---|---|---|
| Primary purpose | Item abilities and triggers | Resource pack / asset manager |
| Resource pack required | No (optional) | Yes |
| Ability/trigger system | 100+ activators, conditions, cooldowns | Limited, scripting-dependent |
| Custom 3D textures | Optional, 60+ included (1.21.4+) | Core feature |
| Custom blocks / furniture | No (use ExecutableBlocks) | Yes |
| Custom mobs, HUD, emojis | No | Yes |
| Config format | YAML + in-game GUI | YAML + resource pack assets |
| Free tier | Yes, 500 items, ~14 activators, watermark on free items | No, paid only (19.99 EUR on SpigotMC, September 2026) |
| Premium price | €19.99 one-time | Check the current price on the store page |
| Server dependency | Requires the free SCore library | Standalone |
| Track record | 5+ years, 4,000+ servers, 280+ five-star reviews | Established, large creator community for packs |
Pricing and Licensing
ExecutableItems is €19.99 one-time for the premium tier, with lifetime updates, sold through Modrinth, Spigot, Polymart, and BuiltByBit. The free tier caps out at 500 items, one activator per item, roughly 14 available activators, and a watermark in the item lore, according to SPlugins' free vs premium comparison.
ItemsAdder is distributed through the same kind of official stores (SpigotMC, Polymart, BuiltByBit) and is paid only: the SpigotMC listing shows 19.99 EUR as of September 2026, with no free tier. Prices on these marketplaces change over time and are not reliably quoted second-hand, so check the current price on the store page before budgeting for it.
Supported Versions
ExecutableItems supports Minecraft 1.8 up to the latest release (1.8 to 26.1 on the product page as of September 2026), with full support from 1.14+ and 3D weapon textures available from 1.21.4+. It runs on Spigot and Paper (Java Edition) and requires the free SCore library alongside it.
ItemsAdder's documentation references features tied to recent versions (1.21.3+, 1.21.5+), and its wiki covers both modern and older-version setups in its FAQ, but does not publish a single comprehensive version range on its overview page. If your server runs an older Minecraft version, verify support against the current ItemsAdder wiki before committing.
Learning Curve
ExecutableItems items live as individual YAML files, and there is a full in-game GUI (/ei gui) for admins who prefer clicking over editing config. A basic right-click ability item is around 10 lines of YAML, and changes reload without restarting the server. The tradeoff is that the wiki is large simply because the feature set is large: new users can feel overwhelmed scrolling through 100+ activators before they find the one they need.
ItemsAdder's learning curve is shaped differently: you are managing YAML configs and resource pack assets (models, textures, sounds) at the same time, which means understanding a resource pack pipeline in addition to plugin configuration. For a server owner who has never built or hosted a resource pack, that is the steeper of the two curves.
Performance Considerations
ExecutableItems items run through SCore, the shared library used across SPlugins' tools, and abilities that are not resource-pack-dependent add no client-side asset weight. ItemsAdder's performance profile includes an additional variable ExecutableItems does not have: resource pack size and hosting. A large custom asset pack means a bigger download for players on join and a hosting method to maintain (self-hosted, or a hosting service). Neither plugin publishes independent benchmark numbers, so treat server-specific performance as something to test on your own hardware and player base rather than take on faith from either vendor.
What ExecutableItems Does Not Do
To be direct about the limits: ExecutableItems is not a resource pack manager. It does not create custom blocks, furniture, custom mobs, or HUD elements, those are the job of ItemsAdder, Nexo, or companion SPlugins tools like ExecutableBlocks. If your project is primarily a cosmetic shop with custom hats, pets, and furniture, ExecutableItems alone will not cover that scope, ItemsAdder (or ItemsAdder plus ExecutableItems for the ability layer) is the better fit.
When to Choose Which
Choose ExecutableItems if: you want items with real behavior, abilities, cooldowns, conditions, region checks, and you do not want to force every player to download a resource pack to use them.
Choose ItemsAdder if: your priority is visual, custom textures, blocks, furniture, mobs, and HUD elements, and your player base accepts resource packs on join.
Choose both if: you want ItemsAdder's textured assets and ExecutableItems' ability system on the same items. This is a supported, documented setup, not a workaround, see the compatible plugins doc for the exact configuration.
For a wider comparison that also covers Nexo and MMOItems, see the best Minecraft custom items plugin guide. For the texture and resource pack side specifically, see custom item textures in Minecraft. If you are new to ExecutableItems itself, start with getting started with ExecutableItems or the official documentation.
Sources
- Information EI, SPlugins documentation, ExecutableItems overview, activator count, version and SCore requirements
- Free vs premium, SPlugins documentation, free tier limits and premium pricing
- Compatible Plugins, SPlugins documentation, ItemsAdder to ExecutableItems and ExecutableBlocks integration details
- ExecutableItems product page, SPlugins, current price and supported version range
- ItemsAdder Wiki, plugin overview, feature list, and resource pack requirement
- ItemsAdder on SpigotMC (price and listing)