ItemsAdderAdditions

ItemsAdderAdditions is an add-on plugin for ItemsAdder that extends it with extra actions, behaviours, recipe types, and other advanced features, all configured directly inside your existing ItemsAdder YML files.

Table of Contents

• Features
• Requirements
• Installation
• Usage
• Documentation
• Creative Inventory Integration
• Custom Paintings
• Contributing
• Support
• License
• Credits

Features

Please see the documentation for the full feature list, configuration details, and examples.

Extra Behaviours

ItemsAdderAdditions adds new behaviours that can be attached to your custom items, blocks, and furniture.

Examples include:

• Connectable
• Contact Damage
• Storage
• And more...

Extra Actions

ItemsAdderAdditions adds new actions that can be triggered by configured events.

Examples include:

• Actionbar
• Ignite
• Mythic Mobs Skill
• And more...

New Recipe Types

ItemsAdderAdditions adds additional recipe types that are not available by default in ItemsAdder.

Currently includes:

• Campfire recipes
• Stonecutter recipes
• And more...

Creative Inventory Integration

Note

This feature is only available on Minecraft 1.21.5 and newer. It also requires Operator permissions and the Operator Items Tab to be enabled.

Any custom item you add through ItemsAdder can be integrated into the Operator Items Tab, making it much easier to access your custom content in creative mode.

This allows operators to:

• browse custom items directly in creative mode
• search for them in the creative search tab
• quickly access custom content without using commands

How it works

Minecraft 1.21.5 introduced data-driven paintings, allowing resource packs and data packs to define custom painting variants.

Each painting variant appears as its own item inside the Operator Items Tab.

ItemsAdderAdditions uses this system by generating painting variants for custom items. These generated entries use the custom item's icon or model so they visually appear like proper creative inventory entries.

When a player takes one of these generated painting items from the creative inventory, or drops it into their inventory, ItemsAdderAdditions detects it and replaces it with the actual associated ItemsAdder item.

This makes the integration feel native while working within vanilla Minecraft's creative inventory systems.

Custom Paintings

Note

This feature is only available on Minecraft 1.21.5 and newer.

Custom paintings can be defined directly in ItemsAdder content YML files using a top-level paintings section. Each entry registers a real Minecraft painting variant and can optionally link an ItemsAdder item that places it in-game.

info:
  namespace: mynamespace

paintings:
  sunset:
    enabled: true
    width: 2
    height: 1
    asset: mynamespace:sunset
    title: "<yellow>Sunset"
    author: "Toutou"
    item: mynamespace:sunset_painting
    include_in_random: true

The asset value points to the painting texture asset. For example, mynamespace:sunset uses:

contents/mynamespace/textures/painting/sunset.png

No datapack files are required for this feature. The plugin injects the painting variants and updates the vanilla minecraft:placeable painting tag at runtime.

The linked item must be an existing ItemsAdder item. When right-clicked on a valid wall face, it places the configured custom painting and follows normal interaction cancellation/protection checks as closely as possible.

Set include_in_random: true to let vanilla painting items randomly choose this custom painting when it fits the wall. Leave it false or omit it to make the custom painting placeable only through its linked ItemsAdder item.

Runtime Configuration

The plugin-level config.yml keeps feature gates separate from ItemsAdder content files:

features:
  creative_inventory_integration: true
  custom_paintings: true

behaviours:
  bed: true
  connectable: true
  contact_effect: true
  stackable: true
  storage: true
  text_display: true

actions:
  actionbar: true
  clear_item: true
  ignite: true
  message: true
  mythic_mobs_skill: true
  open_inventory: true
  play_animation: true
  play_emote: true
  replace_biome: true
  replace_item: true
  shoot_fireball: true
  swing_hand: true
  teleport: true
  title: true
  toast: true
  veinminer: true

update-checker:
  enabled: true
  on-join: true

Reloading ItemsAdderAdditions uses one shared reload pipeline whether it is triggered by ItemsAdder finishing its data load or by /itemsadderadditions reload. The command reloads config.yml, reapplies enabled/disabled actions and behaviours, rescans ItemsAdder content files, and refreshes runtime systems in a consistent order. Existing config keys remain compatible.

For maintainers, the reload pipeline is implemented as small ReloadableContentSystem steps instead of one large manager method. Actions, behaviours, paintings, creative registry data, recipes, and worldgen each reload through their own focused system while sharing one ItemsAdder item list and one parsed content-file registry.

The Java source tree is organized by runtime responsibility and feature module. Entrypoints live under plugin, long-lived runtime ownership under runtime, reload contracts under runtime.reload, user-facing settings under settings, feature systems under feature.*, optional integrations under integration.*, bytecode patches under patch, and shared helpers under common.*. See docs/PACKAGE_LAYOUT.md for the full maintainer map.

Requirements

• Paper server
• A compatible Java version for your server version
• ItemsAdder installed and working correctly
• ItemsAdderAdditions jar placed in the plugins/ folder

Some features may depend on specific Minecraft versions. For exact compatibility and per-feature requirements, please check the documentation.

Installation

1. Install ItemsAdder on your server if you have not already.
2. Download the latest version of ItemsAdderAdditions from one of the available platforms:
   • Modrinth
   • Hangar
   • Spigot
3. Place the ItemsAdderAdditions jar into your server's plugins directory.
4. Start or restart the server.
5. Configure features directly inside your existing ItemsAdder configuration files as described in the documentation.

Usage

ItemsAdderAdditions is configured through your existing ItemsAdder YML files.

The plugin is designed to integrate with the ItemsAdder content pipeline, so you generally do not need to maintain separate configuration files for the features it adds. Instead, you define additional behaviours, actions, or recipe-related options where appropriate in your ItemsAdder content setup.

Because the available options vary depending on the feature, please refer to the documentation for exact configuration formats and examples.

Documentation

Full documentation is available here:

• ItemsAdderAdditions Documentation

The documentation contains:

• Full feature list
• Configuration examples
• Setup instructions
• Version-specific notes
• Behaviour and action references

Contributing

Contributions are welcome !

If you would like to improve the project, feel free to:

• Submit a pull request
• Suggest documentation improvements
• Share feedback and ideas in the Discord server

Support

If you need help, want to report a bug, or have a feature suggestion, please use the Discord server.

Useful channels include:

• #support-chat for help and setup questions
• #bug-report for reporting bugs
• #suggestions for feature requests and ideas
• #showcase if you want to share what you made with the plugin

You can also check the documentation for setup guides and feature references.

License

This project is licensed under the GNU General Public License v3.0. See the LICENSE file for details.

Some parts of this project may include code licensed under additional third-party licenses. See THIRD_PARTY_LICENSES for details.

Credits

Special thanks to:

• twinkycome for being the co-maintainer, creating the logo and showcases, and making the models and textures for the default optional pack
• LoneDev for creating ItemsAdder, which is why ItemsAdderAdditions exists
• misieur for creating the original creative menu integration code that inspired and helped shape this implementation
• Andre601 for helping create this README