RoodyMines v1.6.2 is outSee what’s new →
🛡️

RoodyKits

RoodyKits creates tier kits whose pieces are generated from the plugin's files: name, lore, enchantments, attributes, leather dye, unbreakable, an off-hand item and the full-set bonus.

Config keys and default messages are in Spanish. Every text can be changed in lore.yml and messages.yml.

Installation

License: after the first start, paste your key (from My account) in plugins/RoodyKits/license.yml and restart. Without a valid key the plugin does not start. Once checked, it keeps working for 14 days offline.

Updates: when a new version is out, the console says so and ops (permission roodykits.update) get a message with the download link when they join. Turn it off with avisar-actualizaciones: false in config.yml.

  1. Put RoodyKits-<version>.jar in plugins/ and restart.
  2. Design your tiers in tiers.yml (or create them in-game with /rk kit create <id>).
  3. Give kits with /rk kit give <tier> <player> from the console, crates, kit plugins or menus.

Requires Paper 1.21.11 or newer (and forks such as Purpur), Java 21. No plugin required.

Files

File Contents
config.yml Settings, tier defaults and the pieces that make up a kit.
tiers.yml The tiers.
lore.yml Name and lore format, and names of enchantments, effects and attributes.
messages.yml Messages.

If config.yml, lore.yml or messages.yml miss a key, the jar's value is used; not in tiers.yml, so whatever you delete stays deleted. If a file has a YAML error, /rk reload changes nothing.

How it works

  • Pieces: the piezas section of config.yml defines what each kit has and which enchantment group each piece uses. {armadura} and {herramientas} are replaced with the tier's materials. Each tier can remove or change pieces.
  • Automatic updates: every piece carries a hidden tag with its tier and a "version" of the config. When you change something that affects it, it is regenerated: on join, on /rk reload, when opening a chest, when picked up and on a timer in inventories. Amount and durability are kept.
  • Attributes: the material's vanilla attributes are kept and the config's are added on top.
  • Off hand: segunda-mano (per tier or in por-defecto) is any item — totem, apples, shield… It goes to the off hand if it is free.
  • Set bonus: wearing every armour piece of a tier applies its effects. They come back instantly after a totem, milk, /heal or /effect clear, a stronger potion is left alone and, if anything fails, they wear off within 30 s.

When a kit is given, armour is equipped directly if the slot is free (ajustes.equipar-armadura). Whatever does not fit is dropped.

Create a kit in-game

Wear and carry what the kit should have and run /rk kit create <id>. The tier is created with your materials, enchantments per group (and per piece where they differ), dye, pieces you are not wearing disabled, your off-hand item and the rest of your inventory as items-extra. It is appended to tiers.yml without touching the rest and reloaded; then give it a name and colour.

Commands

All need roodykits.admin (op). Aliases: /rk, /roodykits.

Command What it does
/rk kit create <id> Create a tier from what you carry.
/rk kit give <tier> [player] Give the kit (no player = yourself).
/rk item <tier> <piece> [player] [amount] A single piece.
/rk preview <tier> [piece] Show name and lore in chat without giving anything.
/rk list List tiers.
/rk update [player] Force pieces to update.
/rk reload Reload the four files.