FAQ
Common questions about CoreToolsX.
Short answers for server owners testing tool progression and netherite visual skins.
What server platform does CoreToolsX require?
CoreToolsX requires Paper 1.21.11 or newer and Java 21 or newer.
Does CoreToolsX require Vault, PlaceholderAPI, CoreArmorX, or a database?
No. CoreToolsX does not require Vault, PlaceholderAPI, database storage, custom GUI libraries, CoreArmorX, or custom item plugins. A resource pack is optional and only needed for REAL_TIER inventory models.
What does the default tool progression look like?
The default chain is Wood to Stone, Stone to Copper, Copper to Iron, and Iron to Diamond, with Iron to Gold as an alternate endpoint.
Does CoreToolsX remove vanilla recipes?
No. Protected direct vanilla crafting is blocked at runtime when enabled. Wooden crafting and vanilla diamond to netherite smithing remain untouched.
Do normal upgraded items receive CoreToolsX data?
No. Normal upgraded tools stay clean and use their vanilla Bukkit material as the source of truth. CoreToolsX PDC is used only for skinned tools and internal skin state.
What tool types are supported?
Swords, pickaxes, axes, shovels, hoes, and spears are supported by the default upgrade and skin cost model.
What skins are included by default?
Netherite tools can receive wood, stone, copper, iron, gold, or diamond visual skins.
Can skins have their own durability?
Yes, but skin durability is optional and disabled by default. It can be configured globally, by skin, or by skin and tool type.
How do players remove a skin?
By default, a skinned tool plus shears crafts back into a clean netherite tool. Shears lose one durability instead of being consumed.
How are progression locks stored?
They are not stored by CoreToolsX. Locks are permission-based and can be handled by a permissions plugin such as LuckPerms.
Why does a recipe output appear but not craft?
Check progression permissions, separate one-item ingredient slots, whether the base item is already skinned, and custom item compatibility settings.
What should I run after changing config?
Use /coretoolsx reload for normal YAML changes. Restart when replacing the jar, changing Paper version, or recovering from startup-only errors.