FAQ
Common questions about CoreExtractionX.
Short answers for server owners testing YAML-driven extraction rules.
What server platform does CoreExtractionX require?
CoreExtractionX requires Paper 1.21.11 or newer and Java 21 or newer.
Does it require Vault, PlaceholderAPI, WorldGuard, or a database?
No. It does not require Vault, PlaceholderAPI, database storage, GUI libraries, economy plugins, or protection-plugin hard dependencies.
What blocks are configured by default?
The default ores.yml includes vanilla overworld ores, deepslate ores, nether ores, and Ancient Debris.
Can I add custom source blocks?
Yes. Add any valid block material under blocks: in ores.yml, then configure the mode and replacement material.
What is REPLACEMENT mode?
The mined source block is replaced in the world, vanilla drops are disabled, and CoreExtractionX manually spawns the original block's natural drops and XP.
What is DROP mode?
The block breaks normally and CoreExtractionX adds a configured extra item after generated drops exist.
Does Fortune work?
Yes. In REPLACEMENT mode natural drops are calculated through Paper using the player's current tool and player entity. In DROP mode vanilla handles the original block drops normally.
What happens with Silk Touch?
The default VANILLA behavior makes CoreExtractionX do nothing, so vanilla handles the Silk Touch break. DENY cancels the break.
What happens when a player lacks permission?
VANILLA lets the block break normally. DENY cancels the break and sends the configured message.
Can rules be reloaded?
Yes. Use /coreextractionx reload or /cex reload. Fatal global config errors safe-disable extraction logic until fixed and reloaded.
How does protection compatibility work?
CoreExtractionX ignores already-cancelled block break events. If a claim or protection plugin cancels the break first, CoreExtractionX does nothing.
Does it implement vein mining or auto mining?
No. CoreExtractionX intentionally stays focused on single-block configured extraction rules.