# Cross-Server Sync

This guide explains how to use ExcellentEconomy across multiple servers connected to a single MySQL database. By adjusting your configuration, you can choose whether players share the same balance across your entire network or maintain separate balances for different game modes.

# ⚙️ Core Requirements

To ensure balances update correctly across your network, you must configure the synchronization interval.

The Sync_Interval setting in engine.yml must be set to 1 or higher on all connected servers. If this is disabled (set to 0), balances will not stay in sync across the network.

# 🛠️ Configuration Settings

Balance behavior is controlled by two key settings within your Currency Files:

Column_Name: This identifies the column in the database where the balance is stored.
Synchronized: This tells the server to actively watch for and pull balance changes from the database.

# 📋 Setup Scenarios

# 🌍 Scenario 1: Global Shared Balance

Use this if you want players to have the same balance no matter which server they join (e.g., a network-wide "Global Money" system).

Server A: Column_Name: money, Synchronized: true
Server B: Column_Name: money, Synchronized: true
Server C: Column_Name: money, Synchronized: true

# 🏝️ Scenario 2: Isolated Server Balances

Use this if you want players to have a unique balance for every server (e.g., Survival money is completely separate from Skyblock money).

Server A (Survival): Column_Name: money_survival, Synchronized: false
Server B (Skyblock): Column_Name: money_skyblock, Synchronized: false
Server C (Another Mode): Column_Name: money_your_mode, Synchronized: false

# 🏗️ Scenario 3: Mixed/Grouped Balances

Use this to create server clusters. In this example, Server A has its own currency, while Servers B and C share a common pool.

Server	Column Name	Synchronized	Result
Server A	`gems_a`	`false`	Unique balance for Server A
Server B	`gems_shared`	`true`	Shared balance with Server C
Server C	`gems_shared`	`true`	Shared balance with Server B