Proxy Setups

⚙️ Running on Velocity

Velocity requires a MySQL driver to be installed.
You can download a prebuilt plugin here if needed:
🔗 MySQLDriver (Jenkins)

💾 Database Requirement

All proxy methods require MySQL, with every server — including the proxy — pointing to the same database.
The proxy manages vote forwarding, user vote totals, and synchronization between servers.
Backend servers handle all rewards, milestones, and streaks locally.

📨 Votifier Configuration

Votifier (or VotifierPlus/NuVotifier) only needs to run on the proxy.
VotingPlugin automatically handles forwarding votes to backend servers.

---

Proxy Methods

VotingPlugin supports multiple communication methods between your proxy (BungeeCord/Velocity) and backend servers.
Each method provides the same core functionality — sending votes from the proxy to backend servers — but differs in setup and infrastructure requirements.

Method	Description
PLUGINMESSAGING	Easiest option — drop and play. No extra setup needed beyond placing the plugin on all servers.
REDIS	Uses a Redis server for fast, reliable network-wide message passing.
MQTT	Relies on an MQTT broker for cross-server vote forwarding (ideal for distributed environments).
SOCKETS	Uses direct TCP socket connections (requires open ports between servers).
MYSQL	Shares vote data directly through the common MySQL database.

---

How It Works

This diagram shows the typical single-proxy network layout. Multi-proxy setups and custom Votifier routing may use a different topology.

When a player votes:

1. The proxy receives the vote from Votifier.
2. VotingPlugin (Proxy) records the vote in the database and updates totals (if enabled).
3. The proxy then forwards the vote to backend servers using the configured method.
4. Each backend’s VotingPlugin instance handles rewards, milestones, and streaks locally.

The proxy acts as the central controller for vote tracking and forwarding.
Backend servers focus on reward delivery and gameplay logic.

---

Abilities

VotingPlugin’s proxy integration provides full network-wide support for:

• 🌍 Global or per-server rewards
• 🎉 Proxy-wide or individual server vote parties
• ⏰ Global time synchronization (via the GlobalData setting)
• 🧱 Server blocklist/whitelist controls
• 🔁 Multi-proxy synchronization
• 📊 Centralized vote totals and logging handled by the proxy
• ⚙️ Local reward and streak logic handled by backend servers

---

Multi-Proxy Support

For networks with multiple proxies, MultiProxyMethod supports SOCKETS or REDIS synchronization between proxies. This is separate from the backend BungeeMethod selected for communication between a proxy and its backend servers.

⚠️ Note: Multi-proxy setups are experimental but functional in current releases.
See the full guide here:
🔗 Multi-Proxy Setup

---

More Technical Details (Summary)

The proxy receives and manages votes from Votifier before forwarding them to backend servers.

Proxy Responsibilities

• 📨 Receives votes from Votifier on the proxy.
• 🕓 Handles time-change conditions when GlobalData is enabled (queues votes safely).
• 🧩 Resolves UUIDs and supports Bedrock players (prefix detection).
• 💾 Manages totals when BungeeManageTotals: true — updates MySQL totals (daily, weekly, monthly, all-time, and points).
• 🎉 Updates vote party progress and broadcasts VoteUpdate / VoteBroadcast.
• 🔁 Forwards or caches votes for backend servers depending on player presence and configuration.
• 🌐 Supports multi-proxy setups, syncing votes across proxies and preventing duplicate rewards.

Backend Responsibilities

• Executes rewards, milestones, and streak tracking.
• Handles all in-game logic and GUI-related features.

---

Common Config Keys

Key	File/location	Description
BungeeManageTotals	Proxy bungeeconfig.yml	Enables proxy-managed totals.
SendVotesToAllServers	Proxy bungeeconfig.yml	Sends votes to all servers or only the player’s current server.
AllowUnJoined	Proxy bungeeconfig.yml	When false, the proxy validates that the player has joined before accepting the vote.
AllowUnjoined	Backend Config.yml	When true, a backend accepts forwarded votes without repeating the proxy’s joined-player check.
WaitForUserOnline	Proxy bungeeconfig.yml	Queues votes until the player logs in.
GlobalData	Proxy bungeeconfig.yml and backend BungeeSettings.yml	Enables global data/time synchronization and vote queueing; enable and align it on the proxy and applicable backends.
MultiProxySupport	Proxy bungeeconfig.yml	Allows votes to synchronize between multiple proxies.
PrimaryServer	Proxy bungeeconfig.yml	Marks the primary proxy for supported multi-proxy responsibilities.

---

Simple flow reference

This compact version preserves the older proxy-flow overview. The detailed architecture near the top of this page is the authoritative reference for communication methods and shared storage.

---

For a deeper technical breakdown, see the implementation in
VotingPluginProxy.java.