SurvivalCore
AvailableAn economy, spawn, homes, warps, teleports, chat, kits, ranks and rewards in one jar — so a world and this plugin is a server, not a shopping list. It also supplies the Vault economy the rest of the catalogue was waiting for: install it and MarketPulse, ShopSigns, MarketStalls, ChatGames, PetCompanions and ClaimGuard’s claim costs all start working, with nothing to configure and no EssentialsX.
- Player Utilities
- Economy & Shops
- Gameplay & Progression
- essentials
- economy
- spawn
- homes
- warps
- ranks
- vault
- luckperms
What it does
/setspawn keeps the direction you were looking
Stand where you want players to arrive, look at the build you want them to see, run /setspawn — and everybody arrives facing it. Most plugins lose the angle somewhere between capturing the spot and using it, because the vanilla world spawn is a block position with a facing bolted on that several paths quietly ignore. SurvivalCore stores five numbers rather than three, and sends every arrival to all five. Homes and warps keep their facing from the same code, and the first-join spawn is a separate place, because a welcome area and the point /spawn returns you to are different questions.
The economy the rest of the catalogue was waiting for
Six OrePlugins products ask Vault for an economy on enable and disable themselves when there is none — which, until this jar existed, meant installing EssentialsX for its money and nothing else. SurvivalCore registers one, and they find it with no changes to any of them. If you already run an economy plugin it does not register, says so, and leaves yours alone: two economies on one server means money that only half your plugins can see.
Every other plugin plugs in, and none of them had to be rebuilt
SurvivalCore does not contain the name of another OrePlugins plugin. Guide pages, menu tiles, rank requirements and rewards all arrive through a registry, so a rank can require twenty-five crates opened and a daily reward can hand over a key without the core knowing crates exist. The whole shipped catalogue integrates on first start through YAML manifests — no rebuilds, no updates, nothing to configure — and future plugins get a compile-time API instead. Plugin number forty costs this one nothing.
It stands down instead of fighting your existing plugins
Bukkit hands a command name to whichever plugin registered it first and tells nobody, so two plugins both wanting /home means one silently loses and its players conclude it is broken. Every overlapping module here switches itself off when it sees EssentialsX or CMI, and says why. /orecore modules prints the state and the reason for all thirteen; /orecore commands prints exactly which names SurvivalCore actually won. Force one on if you want ours — but you will know which you got.
Money follows players between your servers
One file is the default and right for a single server. Behind a Velocity or BungeeCord proxy it is not: a player who earns money on one backend and finds themselves broke on the next does not read that as a storage setting, they read it as stolen money — and the same goes for homes, playtime and rank progress. MySQL is one line, from version one rather than a later feature, and every backend pointed at the same database shares everything. Balances are whole cents in an integer column, never a floating point number.
A ladder that measures things other plugins know
A rank is a LuckPerms group, not a second record that drifts from one. Requirements can be playtime — counted here, and it stops while AFK, because a rank you can earn by leaving the game running is not a rank — or money, or blocks mined, or anything another plugin has registered. A requirement nothing can measure is skipped with a warning rather than failed: uninstall a plugin and the ranks that used it get slightly easier, instead of becoming permanently unreachable with no message saying why.
Compatibility
- Modules
- 13, each on/off/auto — auto defers to EssentialsX or CMI
- Commands
- 37, every one droppable in config.yml
- Storage
- SQLite by default, MySQL for a proxied network
- Money
- Whole cents, and registered with Vault for every other plugin
- Ranks
- LuckPerms groups. No second copy of who is what
- Integration
- A published API, plus YAML manifests for plugins that never call it
- Bedrock
- Native forms through Floodgate; chest menus without it
Commands
Permissions default to true for player commands and op for admin ones.
| Command | What it does | Permission |
|---|---|---|
/setspawn [-snap] · /setfirstspawn | Spawn where you stand, facing where you look. -snap rounds to a compass point; first-join spawn is a separate place. | survivalcore.setspawn |
/spawn · /home [name] · /sethome [name] · /warp [name] | The everyday set. All of them keep the facing they were saved with. | everyone by default |
/tpa · /tpahere · /tpaccept · /back · /rtp | Teleports, with one shared warmup, cooldown and cancel-on-move so no command can dodge the rules. | everyone by default |
/balance · /pay · /baltop · /eco give|take|set|reset | Money. The same money every Vault-aware plugin on the server sees. | survivalcore.eco for the admin half |
/rankup · /ranks · /rank check|set | The ladder, what is still missing for the next rung, and the admin override. | survivalcore.rank.admin for /rank |
/daily · /kit [name] | Rewards and kits. Nothing is marked claimed until something has actually been given. | everyone by default |
/guide [topic] · /menu | The in-game guide and the hub — both grow a page and a tile per installed plugin, on their own. | everyone by default |
/orecore modules|commands|integrations|placeholders|reload|wipe | What is on and why, which command names you actually own, and what every other plugin has registered. | survivalcore.admin |
Before you buy
Do I still need EssentialsX?
No, and that is the point. SurvivalCore covers spawn, homes, warps, teleports, kits, chat, private messages, AFK and playtime, and it supplies the economy the rest of this catalogue needs. If you want to keep EssentialsX, keep it: the overlapping modules detect it and switch themselves off rather than fighting for the command names, and /orecore modules tells you which did. You can force any of them back on.
Why do my players all face the wrong way after /setspawn on other plugins?
Because the vanilla world spawn is fundamentally a block position, and the yaw and pitch bolted onto it are dropped by several of the paths that use it — including some respawn and first-join placement. A plugin that reads the world spawn back therefore gets whatever angle happened to be stored. SurvivalCore keeps its own spawn with the facing intact and teleports to that, while still writing the vanilla one so a compass agrees about the block.
Does it need LuckPerms?
Only for ranks. Everything else works without it, and the ranks module disables itself with an explanation at startup rather than half-running. Ranks are LuckPerms groups deliberately — two systems that both believe they own a player’s rank disagree the first time somebody uses the other one, and the one an admin reaches for is always LuckPerms.
I run a proxy with several servers. What do I change?
storage.type to mysql, and point every backend at the same database. That is the setting that makes money, homes, playtime and rank progress follow a player between backends; leave it on sqlite and each server has its own. Both dialects have been there since 1.0.0 rather than one being added later, because an economy that does not follow players is not a missing feature to a player, it is missing money.
How do my other OrePlugins plugins get into the guide and the menu?
They already are. SurvivalCore ships a small YAML manifest for every product in the catalogue, and each one registers that plugin’s guide page and menu tile on first start if the plugin is installed — with nothing rebuilt and no version of anything bumped. The manifests are written into your plugin folder and never overwritten by an update, so you can reword them and keep your wording. Plugins written later use a compile-time API instead, which can also expose live numbers for rank requirements.
Can a player use colour codes in chat?
Only if you grant survivalcore.chat.colour, and you should think about who gets it. What a player types is inserted as plain text and never parsed, deliberately: a chat plugin that runs the format and the message through one parser lets somebody type a click-to-run tag and make everyone who clicks it pay them. The permission turns parsing on for that player, so it belongs to staff and trusted ranks rather than to everyone.
What happens to my config when SurvivalCore updates?
New options are merged in and named in the server log, so a feature you did not know about does not silently switch on with no visible switch. Lists are the exception — an existing list is never added to, so a future version shipping a longer default kit will not change yours. Your integration manifests and guide pages are never overwritten.