Vanilla crafting, controlled progression

Tool progression for Paper servers.

CoreToolsX adds a server-owned path from wood to diamond or gold, protects direct crafting where needed, and gives netherite tools configurable visual skins without databases, GUIs, economy hooks, or a mandatory resource pack.

Get Started Explore Features
  • Paper 1.21.11+
  • Java 21+
  • YAML driven
  • Optional pack
Tool Progression Preview
upgrade path Wood to Diamond
Craft

Players upgrade tools through configured recipes instead of skipping protected tiers.

Skin

Netherite tools can take visual wood, stone, copper, iron, gold, or diamond skins.

Fix

Admins can inspect or refresh skinned tools when config, lore, or model settings change.

Upgrades vanilla+ progression
Skins netherite visuals
PDC safe skinned identity
Wood
Iron
Diamond
Netherite Skins visual material, netherite profile
6 supported tool types
6 default netherite skins
PDC skinned tool identity
YAML all recipes and messages

Core feature set

Tool progression with clean vanilla behavior.

CoreToolsX keeps normal upgraded tools clean, stores plugin identity only where it is needed, and uses runtime recipe validation to make crafting predictable for real servers.

Controlled Tool Progression

Default recipes move tools through Wood, Stone, Copper, Iron, and Diamond, with Gold as an optional endpoint branch from Iron.

Runtime-Safe Recipes

YAML recipes support ingredient groups, one-item-slot matching, recipe book discovery, and safe reloads without duplicated CoreToolsX recipes.

Netherite Visual Skins

Netherite tools can look like wood, stone, copper, iron, gold, or diamond while keeping netherite-equivalent tool behavior.

Metadata Preservation

Names, original lore, enchants, damage, trims, flags, unbreakable state, compatible custom data, and non-CoreToolsX PDC are preserved.

Why CoreToolsX

Progression control without turning tools into a database system.

The plugin is designed for owners who want a stronger crafting path and cosmetic netherite skins, but still want vanilla items, vanilla crafting, and simple YAML operations.

01

Normal Upgrades Stay Clean

Upgraded tools use Bukkit material as the source of truth and do not receive CoreToolsX PDC.

02

Skins Carry Explicit Identity

Only skinned tools store clean material, skin identity, lore snapshot, model mode, and optional durability state.

03

No Heavy Integrations Required

Vault, PlaceholderAPI, databases, custom GUIs, CoreArmorX, custom item plugins, and mandatory resource packs are not required.

Setup and compatibility

Built for modern Paper servers.

Install the jar on Paper, let the default YAML files generate, then tune recipes, skins, progression locks, and lore in the plugin data folder.

Runtime

Paper 1.21.11+

CoreToolsX is Paper-only and targets Java 21+. It does not ship proxy, web, or database modules.

  • Paper server plugin
  • Java 21+
  • Vanilla crafting table flow
Files

Four YAML surfaces

Global behavior, upgrade paths, skins, and messages are split into focused files under plugins/CoreToolsX/.

  • config.yml
  • tool-upgrades.yml
  • tool-skins.yml
  • messages.yml
Paper only Java 21+ Optional resource pack addon

Resources

Docs for setup, configuration, and production checks.

Hub

Documentation Hub

Entry point for setup, feature overview, configuration reference, FAQ, and operational checks.

 Product

Product Overview

Detailed view of upgrade recipes, netherite skins, metadata handling, permissions, and scope.

 Setup

Installation Guide

Requirements, generated files, reload boundaries, first tests, and validation sequence.

 Config

Configuration Reference

YAML file map, runtime model, permissions, troubleshooting, and production checklist.

 FAQ

Complete FAQ

Short answers for requirements, skins, PDC, permissions, lore, fire/lava behavior, and custom items.

 Ops

Troubleshooting

Recipe discovery, permissions, stale lore, skin durability, usage locks, and reload checks.

FAQ preview

Answers before opening the config files.

These are short operational answers. Use the configuration reference when you need exact keys and reload rules.

Does CoreToolsX require a resource pack?

No. The default VISUAL_SKIN mode uses vanilla tool materials and vanilla crafting behavior. The pack is only for REAL_TIER inventory models.

Does it store player unlock data?

No. Progression locks are permission-based. Use a permission plugin such as LuckPerms when locks are enabled.

Do normal upgraded items get CoreToolsX PDC?

No. Normal upgraded tools stay clean; CoreToolsX PDC is used for skinned tools and internal skin state.

Can skinned tools be returned to netherite?

Yes. The default removal recipe uses a skinned tool plus shears to restore a clean netherite tool.

Also try

More CoreX plugins for the same server stack.

Each project stays focused, so you can add only the systems your Paper server actually needs.

Armor

CoreArmorX

Vanilla+ armor upgrade paths, netherite skins, metadata-safe conversions, and YAML control.

Open site
Cases

CoreCaseX

Structured player reports, staff triage, evidence, replies, notes, and resolution workflows.

Open site
Chat

CoreChatX

Channels, private messages, pings, ChatItems, moderation, bridges, locales, and Velocity support.

Open site
Extraction

CoreExtractionX

YAML-driven block extraction, block replacement, natural drops, and configurable extra item drops.

Open site

Ready to test the progression path?

Install CoreToolsX, generate defaults, and craft through the chain.

Start with the setup guide, then tune recipes, skins, lore, and permission locks from YAML.

Open Installation Guide Open Configuration Reference