A working economy turns a plain survival world into a living server: players earn currency, trade at shops, run businesses, and chase goals beyond diamond armor. The bad news is that vanilla Minecraft has no money system at all — there is no /money, no balance, no currency. The good news is that adding one is one of the most well-trodden paths in server administration, and the standard stack — EssentialsX plus Vault — has barely changed in years. This guide walks through the full setup: installing the right server software, wiring up the economy, giving yourself and your players money with /eco give, setting a starting balance, building shops, and locking everything down with permissions.
Why vanilla can’t do this (and what you actually need)
The vanilla Mojang server.jar can run vanilla commands — /op, /gamerule, /give, /ban, /whitelist and friends — but it cannot load plugins. There is no /money or /balance command anywhere in vanilla Minecraft. To add an economy you first need a plugin-capable server fork: Paper (recommended for performance and the built-in features it brings), or its ancestors Spigot/Bukkit. Purpur and Folia are downstream of Paper and also work. Once you are on Paper or Spigot, you drop two JARs into the plugins/ folder:
- EssentialsX — the workhorse. Its economy module is the actual “bank” that holds every player’s balance and provides the player-facing commands
/money,/balance(/bal) and/pay, plus the admin command/eco. EssentialsX also gives you kits, homes, warps, spawn, and moderation tools like/tempbanand/mute— so it earns its place several times over. - Vault — an API bridge, not an economy itself. Vault holds no money. Its only job is to let other plugins (shops, jobs, auction houses, mob-arena rewards) read and write the EssentialsX balance through one common interface. EssentialsX’s own economy works without Vault; you install Vault so the rest of your ecosystem can talk to it.
| Component | Role | Provides |
|---|---|---|
| Paper / Spigot | Plugin-capable server fork | Ability to load JARs at all |
| EssentialsX | The economy itself (the bank) | /money, /balance, /pay, /eco |
| Vault | API bridge between plugins | Lets shop/jobs/etc. read EssentialsX balances |
| A shop plugin (optional) | Lets players spend money | Buy/sell GUIs or sign shops |
Step 1 — Get onto Paper and install the plugins
If you are still on the vanilla JAR, switch to Paper first — nothing in this guide will work otherwise. On a managed host this is usually a one-click “change server type” option; if you self-host, download the Paper JAR for your Minecraft version and swap it in. Java servers run on TCP port 25565 by default, which is worth confirming is open before you worry about anything else.
Then download the matching builds of EssentialsX and Vault, place both JARs into plugins/, and restart the server (a restart, not just /reload — reload is unreliable for first-time plugin loads). On boot, each plugin generates its own config folder. If you would rather have the platform handle the Paper build, plugin updates, and version matching for you, our managed Minecraft hosting plans ship Paper-ready with one-click plugin installs. For a screenshot-by-screenshot walkthrough of the control panel side, see the Minecraft setup docs.
Step 2 — Confirm the economy is alive
Once the server is back up, every player automatically has an account the first time they join. Test it from in-game (you’ll need to be an operator — see the permissions section below) or from the server console. Running the balance command should return a number rather than an “unknown command” error:
/balance
# or the aliases
/money
/bal
If you get “unknown command,” EssentialsX didn’t load — check the console log on startup for errors and confirm the JAR is in plugins/. If /balance works but Vault-dependent shop plugins complain there’s no economy, make sure Vault is also installed and that EssentialsX loaded before them.
Step 3 — Give and manage money with /eco
The admin-facing economy command is /eco, and it takes four sub-actions: give, take, set, and reset. This is how you seed a player’s wallet, hand out event rewards, or correct mistakes:
# Give a player 500 currency
/eco give Notch 500
# Remove 200 from a player
/eco take Notch 200
# Set a player's balance to an exact value
/eco set Notch 1000
# Reset a player back to the configured starting balance
/eco reset Notch
Players move money between themselves with /pay , which is the foundation of any player-to-player trade or job market. Note that /eco is admin-only and should never be handed to regular players — it can mint unlimited currency and will instantly wreck your economy if abused. Keep it locked to staff (see permissions below).
Step 4 — Set the starting balance and currency name
New players shouldn’t start at zero — that gives them nothing to spend at their first shop visit. EssentialsX’s economy settings live in its main config file (plugins/Essentials/config.yml). The two values you’ll almost always change are the starting balance every new account receives and the currency symbol shown in messages:
# plugins/Essentials/config.yml (excerpt)
# How much money new players join with
starting-balance: 100.0
# The symbol shown before amounts, e.g. $100
currency-symbol: '$'
# Optional: minimum allowed balance (set negative to allow debt)
min-money: 0
Edit the file, then restart the server (or use the EssentialsX reload command) for the changes to take effect. Exact key names can shift slightly between EssentialsX releases, so if a value doesn’t behave as expected, cross-check the current keys on the EssentialsX wiki before assuming the config is broken.
Step 5 — Let players spend it: shops
An economy with nothing to buy is just a number on a screen. You need a way for players to convert currency into goods (a server “admin shop” that creates items from money) and to sell their loot back for currency. This is exactly where Vault earns its keep: shop plugins talk to your EssentialsX balance through Vault rather than implementing their own money system. Two broad styles exist:
- Sign shops — players (or admins) place a sign with item, price, and buy/sell lines on a chest. Lightweight, classic, and great for player-run markets.
- GUI / menu shops — a clickable category menu, ideal for a centralized admin shop at spawn where prices are fixed by staff.
Whichever you choose, the install pattern is the same: drop the shop plugin’s JAR into plugins/ alongside EssentialsX and Vault, restart, and the shop will auto-detect Vault and bind to the EssentialsX economy. If a shop plugin reports “no economy found,” it almost always means Vault is missing or EssentialsX failed to load — fix that first.
Step 6 — Permissions: who can do what
There are two layers of access control to understand, and people constantly confuse them.
Vanilla op levels vs. plugin permission nodes
Vanilla Minecraft uses numeric operator levels 1–4 stored in ops.json. Level 1 bypasses spawn protection; level 2 unlocks cheat commands and command blocks; level 3 adds multiplayer-management commands like /ban and /kick; level 4 is full owner access including /stop. The /op command grants the level set by op-permission-level in server.properties (default 4). The server console always runs at the equivalent of level 4 with no op needed — which is why /eco give works straight from the console. If you want a moderator at a custom level you edit the level field in ops.json directly. For the full process of adding an admin, see our guide on adding an op admin via ops.json.
EssentialsX commands, however, are not gated by op level — they use plugin permission nodes in the essentials. format. Being op typically grants all of them implicitly, but for a real server you want fine-grained control: regular players should have essentials.balance and essentials.pay, while only staff should have essentials.eco. Crucially, EssentialsX nodes are not auto-inclusive — granting a parent node does not automatically grant its children, so list each one (or use the explicit wildcard forms the wiki documents). Because op grants everything, never op a player just to give them basic economy access; use a permissions plugin instead.
| Command | Who should have it | Permission node (format) |
|---|---|---|
/balance, /money | Everyone | essentials.balance |
/pay | Everyone | essentials.pay |
/eco give|take|set|reset | Staff only | essentials.eco |
Always verify exact node strings against the EssentialsX wiki, since they can be split or renamed between versions. The principle holds regardless: economy spending for players, economy creation for staff.
Keeping the economy healthy
The hardest part of running an economy isn’t the install — it’s preventing inflation. Two common mistakes sink most servers. First, money sinks vs. faucets: if currency only ever enters the economy (mob kills, /eco give, sell shops) and never leaves, prices balloon and the currency becomes worthless. Build in sinks — admin-shop purchases, taxes on /pay, warp/teleport fees, or auction-house listing costs — so money is destroyed at a similar rate to how it’s created. Second, guard your duplication vectors: any item players can produce infinitely and sell to an admin shop (renewable crops, mob farms, easily-automated drops) sets a hard floor on how cheap currency becomes. Price those items low or don’t buy them at all.
It also pays to set a sensible starting-balance rather than a huge one, keep /eco set reserved for genuine corrections, and audit balances occasionally. A slow, deflationary economy where players have to work for currency is far healthier than one where everyone is a millionaire by their second login.
Where the economy fits with the rest of your config
Because you’re already on Paper with EssentialsX installed, you’ve unlocked a lot of adjacent server tuning. Several common quality-of-life and protection settings now become trivial: you can disable creeper explosions while keeping TNT functional with WorldGuard region flags (vanilla’s mobGriefing gamerule can’t separate the two), freeze the day/night cycle with /gamerule doDaylightCycle false, or even add fun cosmetic plugin commands like letting players sit in chairs via GSit. All of these layer cleanly on top of the economy stack.
Frequently asked questions
How do I give myself money on a Minecraft server?
Use /eco give — for example /eco give Notch 500. You must be a server operator or run it from the console (the console always has level-4 access). If /eco returns “unknown command,” EssentialsX isn’t installed or didn’t load. You cannot give yourself money on a vanilla server because vanilla has no currency system at all; you need Paper/Spigot plus EssentialsX first.
Do I need Vault if I have EssentialsX?
Not for the core economy. EssentialsX’s economy works standalone — /money, /pay, and /eco all function without Vault. You need Vault only so that other plugins (shops, jobs, auction houses, kit rewards) can read and modify the EssentialsX balance through a shared API. Since almost every server eventually wants shops, the practical answer is: install Vault anyway. It holds no money itself; it’s purely a bridge.
How do I set the starting balance for new players?
Open plugins/Essentials/config.yml and set starting-balance to the amount you want (for example starting-balance: 100.0), then restart the server or reload EssentialsX. Every new player’s first-join account will use that value. To bring an existing player back to it, run /eco reset . If the key name doesn’t seem to work, check the current EssentialsX wiki — config keys occasionally change between major releases.
How do players buy and sell items with money?
You need a separate shop plugin (sign-shop or GUI-menu style) installed alongside EssentialsX and Vault. The shop plugin connects to your EssentialsX economy through Vault, so purchases deduct from and sales add to the same balance shown by /money. Set up an admin shop at spawn for fixed-price buying/selling, and optionally allow player-run sign shops for a free market. Without a shop plugin, players can only transfer money to each other with /pay.
Why does /money or /balance say “unknown command”?
Three likely causes. First, you’re on a vanilla server — vanilla Minecraft has no economy commands; switch to Paper or Spigot. Second, EssentialsX isn’t in your plugins/ folder or failed to load — check the startup console log for errors and confirm you downloaded the build that matches your Minecraft version. Third, you’re missing the permission node (essentials.balance) if you’re a non-op player on a permissions-managed server. A full server restart after dropping in the JAR fixes most first-time issues.
Can I run a Minecraft economy on Bedrock Edition?
Not with EssentialsX/Vault. The Bedrock Dedicated Server (BDS) has no plugin API — it uses behavior packs/add-ons instead, and runs on UDP port 19132 rather than Java’s TCP 25565. There is no equivalent of the EssentialsX economy on stock Bedrock; any “economy” there is custom-built with add-ons or scripting, which is far more involved. If an economy is a priority, run a Java Paper server. (A Java server can be made joinable by Bedrock clients through a proxy like Geyser, but the economy itself still lives in EssentialsX on the Java side.)
Recap
Adding money to a Minecraft server is a four-ingredient recipe: Paper (so plugins load), EssentialsX (the bank and player commands), Vault (the bridge to shops), and a shop plugin (so currency has somewhere to go). Seed wallets with /eco give, set starting-balance for new joiners, gate /eco behind essentials.eco for staff only while everyone gets essentials.balance and essentials.pay, and design deliberate money sinks so the economy stays valuable. Get those right and your server gains an entirely new layer of progression and player-driven interaction.
Ready to play?
Run your own Minecraft server with XGamingServer
Spin up an always-on Minecraft server your friends can join in minutes — no port-forwarding, no tech headaches.






