Syncmoney
Running a Minecraft network with multiple servers creates a familiar headache: players earn money on your survival world, hop over to the skyblock node, and suddenly their balance is gone. Syncmoney solves that problem. It is an enterprise-grade economy plugin built specifically for safe, consistent cross-server balance synchronization, bridging Vault and VaultUnlocked economies across every node in your network using Redis Pub/Sub and relational database persistence.
If you have ever watched a player duplicate currency by switching servers mid-transaction, this plugin was written for you.
What Makes Syncmoney Different
Most economy plugins treat synchronization as an afterthought. Syncmoney treats it as the entire point. Balances are served from an in-memory cache with O(1) read performance, while persistent writes happen asynchronously off the tick thread. That means your TPS stays clean even during heavy transaction traffic.
The synchronization layer uses Redis Pub/Sub with atomic Lua scripts, monotonic versioning, and echo suppression. In plain terms: race conditions and duplicated payouts are engineered out of the system rather than patched after the fact.
Core Features at a Glance
- Vault and VaultUnlocked support — integrates with Vault 1.7 and the Vault2 API without conflict.
- Four economy modes — standalone SQLite, Redis-only sync, Redis plus SQL persistence, or CMI-authoritative sync.
- Multi-layer circuit breaker — per-transaction limits, anomaly rate detection, and independent per-player guards across L1 to L4 states.
- Comprehensive auditing — a high-throughput async audit pipeline with search, statistics, and automated cleanup.
- Shadow backups — independent background account snapshots for cold-standby recovery.
- Embedded Web Admin — a modern Vue 3 dashboard for health telemetry, audit viewing, and economy monitoring.
Supported Versions and Loaders
Syncmoney targets modern server software. The current acceptance matrix covers Paper 1.20.4, Paper 26.2, Folia 26.2 BETA, and Canvas 26.2, including a two-backend Paper network behind a Velocity proxy. Plain Spigot is not supported.
Java requirements scale with your server build: Java 21 for Paper 1.20.4 through 1.20.6, and Java 25 for Paper 26.1 and newer. Redis 5.0 or higher is required for the sync, local_redis, and cmi modes, while database options include MySQL 8.0+, MariaDB 10.5+, PostgreSQL 13+, and local SQLite.
Because the plugin is region-scheduler safe, Folia and Canvas administrators get the same consistent economy behavior as traditional Paper setups.
How to Install Syncmoney
Getting started is straightforward, but the order matters. Follow these steps carefully.
Step 1: Back Up Everything
Stop your server and take a full backup of your plugin configs, economy databases, and Redis persistence files. Never skip this on a live network.
Step 2: Install the Plugin
Place the Syncmoney JAR and your preferred Vault provider into the server's plugins directory. Remove any older Syncmoney JAR versions to avoid conflicts.
Step 3: Generate and Configure
Start the server once to create default configuration files, then stop it. In plugins/Syncmoney/config.yml, assign a unique server-name such as survival-01 or lobby-01, select your economy.mode, and enter your Redis and SQL credentials if you are using synchronized modes.
Step 4: Verify
Start the server and confirm in the console that Syncmoney and Vault registered successfully. Test basic transactions with /money and /pay before opening the network to players.
If you prefer a faster path, the foxygame.net launcher bundles Syncmoney directly into its add-on catalog, so you can install it with a single click and let the launcher handle version matching for your server build. Administrators who manage several test environments often find that approach saves a surprising amount of setup time.
Choosing the Right Economy Mode
Your mode choice defines how balances travel between nodes.
- local — single-server SQLite. No Redis or external database needed.
- local_redis — Redis-backed network economy without SQL persistence.
- sync — Redis Pub/Sub plus a central SQL database. This is the standard choice for serious multi-server networks.
- cmi — CMI retains primary economy authority while mutations propagate through Redis.
For most networks, sync mode offers the best balance of performance and durability. Note that SQLite is intended for local and shadow storage only, not as the shared database connection.
Administration and Monitoring
Syncmoney ships with a full administrative toolkit. Commands like /syncmoney admin give, /syncmoney breaker status, and /syncmoney audit let staff manage balances and diagnose issues without touching the database directly. Administrative permission tiers range from Observe to Full, each with configurable daily limits, so junior staff cannot accidentally drain your economy.
The embedded Web Admin dashboard runs on Undertow and provides live health telemetry. Bind it to 127.0.0.1, route external traffic through a reverse proxy with HTTPS, and always replace the placeholder API key with a cryptographically secure token.
Developers are covered too. Syncmoney registers as a standard Vault provider, fires PostTransactionEvent for auditing, and offers an official PlaceholderAPI expansion with placeholders for balances, leaderboard ranks, total supply, and more.
Final Thoughts
Cross-server economies fail in predictable ways: race conditions, stale caches, and silent data loss. Syncmoney addresses each of those failure points with atomic Redis operations, in-memory caching, circuit breakers, and shadow backups. If your network has grown past a single server, or you are planning that growth, this plugin gives you the infrastructure to run a trustworthy economy at scale. Validate every upgrade on a staging environment first, and your players will never notice the machinery working underneath.