Installation guide

Install CoreExtractionX on a supported Paper server.

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

Requirements

  • Paper 1.21.11 or newer.
  • Java 21 or newer.
  • CoreExtractionX jar installed on a Paper backend.
  • A permission plugin only if you want to manage coreextractionx.use and coreextractionx.reload outside vanilla ops.

Download

The current source build line is 2026.1.0. Use the packaged jar artifact for deployment.

CoreExtractionX-2026.1.0.jar

Installation Flow

  1. Stop the Paper server.
  2. Place the CoreExtractionX jar in the server plugins folder.
  3. Start the server once so defaults are generated.
  4. Confirm the plugin enables without fatal config warnings.
  5. Edit generated files under plugins/CoreExtractionX/.
  6. Run /coreextractionx reload or /cex reload after normal YAML edits.

Generated Files

plugins/CoreExtractionX/
  config.yml
  ores.yml
  messages.yml

plugin.yml is bundled inside the jar and declares commands, aliases, permissions, and plugin identity.

Reload vs Restart

Use /cex reload for normal edits to config.yml, ores.yml, and messages.yml. Commands remain available even if a fatal global enum error puts extraction logic into safe-disabled state.

Restart when replacing the jar, changing Paper/Minecraft version, or validating a clean boot after large operational changes.

First Tests

  1. Mine coal ore with no Silk Touch and confirm it becomes cobblestone.
  2. Mine deepslate diamond ore and confirm it becomes cobbled deepslate.
  3. Mine nether quartz ore and confirm it becomes netherrack.
  4. Test a Silk Touch tool and confirm vanilla behavior by default.
  5. Temporarily set one rule to mode: DROP and test a fixed extra drop.
  6. Run /cex reload and confirm loaded/skipped counts.

Production Validation

  • Confirm console has no CoreExtractionX warnings after reload.
  • Test with a non-op account if permissions are managed.
  • Test a protected region or claim plugin and confirm cancelled breaks are ignored.
  • Verify world filter behavior before enabling on production worlds.
  • Keep a backup of edited YAML before adding large custom rule sets.