Integrations
What ExyliaSurvivalCore, PlaceholderAPI, an economy, world managers, combat and protection plugins change inside a mine, plus networks and Folia.
Nothing below is required. Each plugin is detected on its own, and without it the mine works the same, only without what it adds.
ExyliaSurvivalCore
With ExyliaSurvivalCore installed, four of its systems reach into every mine:
| System | What it does in a mine |
|---|---|
| Boosters | The miner's drop and experience boosters multiply vanilla drops, experience and item loot; their money boosters multiply the money loot pays through its economy. Mines count as the mines source. |
| Auto-sell | Every drop and every loot item is offered to the miner's auto-sell first. What it sells is not given as well. |
| Enchantment limits | The limits it sets for the place are applied to the tool before the mine's own Fortune and Silk Touch limits. |
| Blocked items | A player holding an item its rules forbid cannot break the mine's blocks with it. |
These apply after the mine's own boosts, so the two stack.
The survival core is asked on every break rather than once at startup, so it may be enabled after ExyliaMines, or reloaded, without anything going stale.
Releases of ExyliaSurvivalCore from before the move still have a mines module. If it is on, both plugins
would claim every block broken in a mine, so ExyliaMines warns in the console at startup:
"ExyliaSurvivalCore still runs its own mines module." Update the survival core, or turn its mines
module off. Its mines are not imported while that module runs — see Migration.
PlaceholderAPI
Every placeholder is published to PlaceholderAPI under the plugin's name, with nothing to download from
the eCloud: %exyliamines_mine_reset_coal%. See Placeholders.
Money
Money lines in loot tables and lucky rewards are paid through ExyliaLib's economy, which needs an economy plugin behind it — Vault with one installed, or PlayerPoints. Without one, money lines pay nothing and everything else still works. With ExyliaSurvivalCore, money is offered to its economy first, which is what lets its boosters and its own currencies apply.
World managers
Worlds and Multiverse-Core load their worlds after the plugins enable. A mine in such a world is registered the moment the world loads, and the realistic blocks it was regrowing there are picked up again. Nothing to configure.
Combat plugins
/mine and the /mines menu refuse to send a player who is in combat. Combat is read from ExyliaLib's
combat module, which follows DeluxeCombat or PvPManager when one is installed.
Protection plugins and anticheats
No flags, no exceptions to add. A mine performs its own breaks after the anticheats have had their say and never forces a cancelled break through, so WorldGuard regions and nuker checks keep working inside mines. See Area and shapes.
Other plugins' tools
A plugin breaking blocks for a player — a 3x3 pickaxe, a vein miner, an enchantment — should hand each
block to the mine through MinesService.breakBlock, so every one gets the mine's permission, loot and
regeneration. See the API.
Networks
Several servers can share one database. Each mine belongs to the server it was created on, and each server loads and runs only its own:
- Ids are unique across the network. Creating, cloning or importing a mine checks the whole table, so a mine on one server can never overwrite another server's.
- Boosts belong to the server they were started on.
- Statistics are kept per mine id and written as additions, so counts from different servers never overwrite each other.
- Broken blocks of a mine another server owns are left alone.
The server's name is the one ExyliaLib knows it by on the network. A mine row written before servers were recorded — an old import — belongs to whichever server reads it.
Folia
Supported. Every block change runs on the thread that owns the block, every player change on the thread that owns the player, and the events the plugin fires are called on the region thread of the block they are about.
Something missing on this page? Tell us on Discord