Installation guide

Install CoreToolsX on a supported Paper server.

CoreToolsX is a Paper-only plugin for Java 21 and Paper 1.21.11 or newer. It generates four YAML files on first boot.

Requirements

  • Paper 1.21.11 or newer.
  • Java 21 or newer.
  • CoreToolsX jar installed on a Paper backend.
  • LuckPerms or another permission plugin only if progression locks are enabled.

CoreToolsX does not require Vault, PlaceholderAPI, a database, custom GUI libraries, CoreArmorX, or custom item plugins. The resource-pack addon is optional and only needed for REAL_TIER inventory models.

Download

The current source build line is 2026.1.0. Use the CoreToolsX plugin repository or your packaged jar artifact for deployment.

CoreToolsX-2026.1.0.jar

Installation Flow

  1. Stop the server.
  2. Place the CoreToolsX jar in the Paper server plugins folder.
  3. Start the server once so bundled defaults are generated.
  4. Confirm the plugin enables without startup warnings.
  5. Edit the generated files under plugins/CoreToolsX/.
  6. Run /coretoolsx reload after normal YAML edits.

Generated Files

CoreToolsX creates its runtime folder under:

plugins/CoreToolsX/

Bundled admin config files:

config.yml
tool-upgrades.yml
tool-skins.yml
messages.yml
resource-pack/        # optional addon for REAL_TIER mode

plugin.yml is bundled inside the jar. It documents plugin identity, command aliases, and permission declarations, but is not edited in the server data folder.

Reload vs Restart

Safe with /coretoolsx reload: runtime toggles, upgrade definitions, skin definitions, messages, recipe registration, progression permission nodes in YAML, lore templates, inventory model mode for refreshed items, and skin durability settings for newly refreshed or newly skinned items.

Restart when replacing the jar, changing Paper/Minecraft version, recovering from startup-only classloading errors, or validating a completely clean boot after large config edits.

If you change the optional resource-pack zip, players must reload or reselect the pack client-side. A server restart is not required for the zip itself.

First Tests

  1. Craft one normal upgrade from each configured path.
  2. Craft one netherite visual skin recipe.
  3. Remove one skin with shears and confirm shears lose durability.
  4. Inspect a skinned item with /coretoolsx inspect.
  5. Run /coretoolsx fixitem on a skinned item.
  6. If REAL_TIER is enabled, verify the addon pack renders inventory and hand models correctly.

Production Validation

  • Run /coretoolsx reload and confirm console has no CoreToolsX warnings.
  • Test recipes with separate one-item ingredient slots.
  • Test progression permissions with a non-op account if locks are enabled.
  • Test fire/lava behavior if skin-stripping.enabled changed.
  • Keep compatibility.custom-items.behavior: BLOCK_IF_DETECTED unless you intentionally want to convert foreign custom items.