nexo itemsadder oraxen

Nexo, ItemsAdder & Oraxen Integration

The page below will explain about Nexo specifically, you can do the same steps for ItemsAdder and Oraxen.

Overview

This guide explains what each integration does in RareSpawns and shows the config-level steps and examples you can use as a server operator. You will not need to touch or build plugin code — just install the Nexo plugin and edit RareSpawns' config/entity/item files as described below.

Summary

• RareSpawns has optional support for the Nexo plugin.
• If Nexo is installed, RareSpawns can:
  • Use Nexo items as drops and equipment for rares.
  • Place Nexo blocks through the PowerItems feature.
  • Use Nexo-provided block data and sounds for effects.
• If Nexo is not installed, RareSpawns keeps working — Nexo-specific features are skipped.

Enable Integration

1. Download and install Nexo:
   • Put the Nexo plugin JAR in your server's plugins/ directory.
2. Restart the server so both plugins load.
3. Confirm installation:
   • Run /plugins or check the server console — Nexo should be listed.
   • RareSpawns logs whether it detected Nexo at startup (look for a message like "Nexo integrated!" in the RareSpawns startup log).

How you will use these in RareSpawns

• Drops (entity drop-tables)

  • You can add Nexo items to a rare's drop-table in the same place you currently add other drops.
  • RareSpawns supports a few drop syntaxes (see your entity template files). A common pattern for referencing external/custom items is the "custom" form (examples and syntax comments are present in RareSpawns' item/drop templates).
  • Example (add to an entity's drop-table items list — replace my_nexo_item_id with the actual Nexo item id):
    • /entities/.yml (inside drop-table -> items):

      items:
        main-hand: template # <-- RareSpawns item 'template'
        helmet: nexo:awesome_helmet # <-- Nexo item 'awesome_helmet'
      
      drop-table:
        real: true
        items:
          # material:amount
          # material:amount:chance
          # material:min-max:chance
          - nexo:my_nexo_item_id:1

    • Meaning: attempt to fetch the Nexo item with id my_nexo_item_id and drop 1 of it. If Nexo is not present or the ID is invalid, the drop will not produce that Nexo item (RareSpawns will not crash).

• Shared or group drops

  • You can include Nexo items in global shared-drops, or in spawn-groups' shared-drops using the same "custom" syntax:

    shared-drops:
      - nexo:my_nexo_item_id:1

  • This makes that Nexo item available on the shared drop table for all rares covered by the config.

• Power-items and Nexo "papers" (placing custom Nexo blocks)

  • RareSpawns supports a power-item that places a block chosen from your hotbar. If a PAPER in the hotbar carries a Nexo block id tag (Nexo note-block paper), RareSpawns will place a NOTE_BLOCK with Nexo block data and play the Nexo place sound.
  • What that means for you (no coding):
    • Give players the Nexo paper item (created by Nexo or via in-game Nexo commands). The paper must include the Nexo block id as NBT (Nexo produces these items).
    • When the player uses RareSpawns' place-power-item, RareSpawns recognizes the paper, reads its Nexo id, and places the right Nexo-backed block.
  • You do not need to configure anything in RareSpawns to enable this — it works automatically if Nexo is installed and the paper item carries the required Nexo id tag.

Practical examples — copy/paste snippets

• Entity drop example (template-style entity file):

  drop-table:
    real: true
    items:
      - DIAMOND:1:20
      - nexo:my_nexo_sword:1

  • DIAMOND is a normal Minecraft material drop. nexo:my_nexo_sword:1 is a Nexo item id example.

• Shared-drops example (config.yml or group shared-drops):

  shared-drops:
    - template:1
    - nexo:thunderforged_ring:1

Testing and verification

• After installing Nexo and editing configs:
  1. Restart your server.
  2. Check the console for RareSpawns startup logs (it will print whether Nexo was detected).
  3. On a test world:
     • Spawn or wait for a rare that has a Nexo item in its drop table.
     • Kill the rare and check the drops; if Nexo is installed and the item id is valid, the player should receive the Nexo item.
  4. For paper -> block placement power-items:
     • Give the test player a Nexo block (created by Nexo).
     • Use the RareSpawns power-item action and verify the NOTE_BLOCK placed uses the Nexo block behavior/sound.

Troubleshooting (simple checks)

• RareSpawns didn't detect Nexo:
  • Ensure the Nexo JAR is in plugins/ and appears in /plugins output.
  • Restart the server; check console for RareSpawns messages — it logs detection status at startup.
• Nexo item didn't drop:
  • Confirm the Nexo item id is correct (check Nexo docs or the Nexo plugin's item list).
  • Confirm Nexo is installed and compatible with your server version.
  • Check server console for warnings or messages from RareSpawns about missing assets.
• Block placements don't work:
  • Be sure the block item created by Nexo uses PAPER as material (it must carry the Nexo id tag). If you created a paper manually, it will not work unless it has the proper NBT tag.

Notes & best practices

• Nexo is optional. If you rely on Nexo items in your config, keep a note of which rare definitions require Nexo so you know to install it on servers that need those features.
• Always test changes on a staging server before applying to production.
• Keep backups of your RareSpawns entity/item configuration files before editing.

If you're unsure about the correct Nexo item id to use, check the Nexo plugin's documentation or its in-game item creation commands — the id you use in RareSpawns configs must match the one Nexo uses.