Introduction
What ExyliaSurvivalCore is: fifty modules on one plugin, each one switchable, each one registering nothing when it is off.
ExyliaSurvivalCore is the survival server in one jar. Homes, warps, TPA, random teleport, kits, crates,
mines, bounties, rankup, farming milestones and regenerating zones sit next to an economy with its own
currencies, a server shop, a player market with auctions and buy orders, land protections, duel rooms,
missions, seasons and votes. Each of them is a module you switch on or off in config.yml.
A module that is off registers nothing at all: no commands, no listeners, no database tables, no placeholders. Turning one off is not a flag the code checks in a hundred places — it is a feature that never loads.
It is fifty modules, one hundred and eighteen menus, seventy-two database tables and three hundred and thirty-seven menu actions, and almost everything an administrator configures is edited from an in-game screen rather than a file.
What is included
Spawn, homes, warps, TPA, /back, random teleport and /near. Homes, warps and TPA work across the
network.
Kill rewards with streaks, bounties on players' heads, tracked statistics with leaderboards, death handling and graves.
Duel roomsEnclosed PvP rooms that lock when enough players step in.
ProgressionA rank ladder with prestige, playtime rewards, farming milestones and a /reclaim for donors.
Daily and weekly missions, and daily, weekly and monthly rankings paid when they close.
Rewards and votesRewards claimed from a menu, and votes through NuVotifier with daily streaks and a vote party.
Kits and cratesKits with cooldowns and previews, ten crate animations drawn in the world, loot chests and item spawners.
ZonesMines that reset whole or block by block, regenerating zones from schematics, AFK zones, portals, jump pads and power-ups.
RestrictionsEnchantment caps per world or region, and items that cannot be used or crafted where you say.
Quality of life/heal, /fly, /repair, join and leave messages, scheduled commands, and a preferences screen
every player owns.
Stored currencies, /balance, /pay, /baltop and /wallet, a Vault bridge, boosters and sell
wands.
The server shop: categories of products, edited in game.
MarketA player market, an auction house and buy orders, priced in any currency the server runs.
Trade and vaultsTrading face to face, and personal storage.
ProtectionsLand protected with a core block or a selection, with roles, clans and flags — and raids, banks, upkeep and rent on top.
OptimizationStacked items, mobs and spawners, limits per chunk, and outdated items replaced by their fixed version.
CommandsEvery command of every module, with its arguments and its permission.
How a server is set up
Turn off what you do not want
All fifty ship as true. Set the ones you do not need to false in config.yml and restart —
module switches are the one thing a reload does not pick up, and /sc reload names the ones still
waiting for a restart.
Set the spawn
/spawn set. The spawn module can also force players there on first join, on every join and on
respawn.
Build the content from menus
Mines, crates, warps, kits, loot chests, portals, jump pads, power-ups, AFK zones, regen zones, duel rooms, currencies, the shop, menu rewards and item updates are all built from admin screens and stored in the database. There is no list to hand-edit.
Write the ladders in YAML
Ranks, playtime rewards, farming categories, kill rewards, RTP worlds, repair groups, join groups, the stat list, missions, seasons and vote rewards are files, because they are ladders rather than objects.
At a glance
| Version documented | 1.1.2, source of 14 September 2026 |
| Minecraft | 1.21+ |
| Platforms | Spigot, Paper and Folia |
| Required | ExyliaLib, packetevents |
| Optional | FastAsyncWorldEdit (regenerating zones), PlaceholderAPI, WorldGuard, BlueMap, dynmap, Votifier, Apollo, FeatherServerAPI, Vault or PlayerPoints, ExyliaClans or SimpleClans, the Worlds plugin on Folia |
| Database | H2 by default; MySQL, MariaDB, PostgreSQL and MongoDB through ExyliaLib |
Every default, message, node and rule on these pages was read from the plugin's source as of 14 September 2026 — not from the comments in the generated files, several of which are out of date. Where a page says something does not work, that is because the code does not do it.
Something missing on this page? Tell us on Discord