Installation guide

Install CoreArmorX on a supported Paper server.

CoreArmorX 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.
  • CoreArmorX jar installed on a Paper backend.
  • LuckPerms or another permission plugin only if progression locks are enabled.

CoreArmorX does not require Vault, PlaceholderAPI, a database, custom GUI libraries, a resource pack, CoreToolsX, or custom item plugins.

Download

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

CoreArmorX-2026.1.0.jar

Installation Flow

  1. Stop the server.
  2. Place the CoreArmorX 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/CoreArmorX/.
  6. Run /corearmorx reload after normal YAML edits.

Generated Files

CoreArmorX creates its runtime folder under:

plugins/CoreArmorX/

Bundled admin config files:

config.yml
armor-upgrades.yml
armor-skins.yml
messages.yml

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 /corearmorx reload: runtime toggles, upgrade definitions, skin definitions, messages, recipe registration, progression permission nodes in YAML, lore templates, 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.

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 /corearmorx inspect.
  5. Run /corearmorx fixitem on a skinned item.

Production Validation

  • Run /corearmorx reload and confirm console has no CoreArmorX 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.