DaisyVotes — Cross-Server (Redis)

New in 2.0 DaisyVotes can run across a network of servers — a lobby, survival, skyblock, etc. — sharing one set of vote data, with optional Redis for live cross-server delivery.

Network mode is configured in network.yml and is off by default (single-server).

How it fits together

There are two layers:

1. Shared database (required for a network). Point every server at the same database — use MySQL/MariaDB in storage.yml instead of SQLite. This alone keeps vote counts, points, streaks, and the queue consistent everywhere.
2. Redis (optional, adds “live”). Redis powers instant cross-server delivery, player presence, and duplicate suppression — e.g. a vote received on the lobby grants its reward on the survival server immediately, rather than when the player next visits.

Set up the shared database first

Enable a shared MySQL/MariaDB database in storage.yml before turning on Redis. Without a shared database, the servers still have separate data and Redis has nothing to keep in sync.

network.yml

network.yml

enabled: false
server-id: "auto"
redis:
  uri: "redis://localhost:6379"
  key-prefix: "daisyvotes"
  heartbeat-seconds: 15
  message-ttl-seconds: 30
live-routing:
  enabled: true
  deliver-online-rewards-across-network: true
  broadcast-vote-party-across-network: true

Key	Default	Description
enabled	false	Turn on Redis network mode.
server-id	"auto"	This server’s id on the network. auto derives a stable id; set a name (e.g. lobby) if you prefer.
redis.uri	redis://localhost:6379	Redis connection URI. Supports auth and TLS, e.g. redis://:pass@host:6379 / rediss://….
redis.key-prefix	daisyvotes	Namespace for all DaisyVotes keys/channels in Redis.
redis.heartbeat-seconds	15	Presence heartbeat interval (min 5).
redis.message-ttl-seconds	30	How long cross-server messages live (min 5).
live-routing.enabled	true	Master switch for live routing over Redis.
live-routing.deliver-online-rewards-across-network	true	Deliver a reward on whichever server the player is currently on.
live-routing.broadcast-vote-party-across-network	true	Trigger vote parties network-wide.

Protect your Redis URI

The redis.uri may contain a password. Don’t paste it into public channels or support tickets — the plugin redacts it in its own status/log output.

Setup

1. Shared database. Configure the same MySQL/MariaDB connection in storage.yml on every server. See Storage & Data.
2. Enable Redis. Set enabled: true and your redis.uri in network.yml on each server. Give each a distinct server-id (or leave auto).
3. Reload / restart, then check /daisyvotes network status — it should report connected.

Without Redis

Redis is optional. With only a shared database and Redis off, everything still works — votes, points, streaks, and rewards are consistent across servers, and any reward earned while a player is offline is delivered through the shared offline queue (/vote claim). Redis simply makes online delivery and parties instant instead of on-next-join.

Command

Command	Permission	Description
/daisyvotes network status	daisyvotes.admin.network	Enabled/connected state, server id, Redis URI (redacted), last error.

Storage & Data Configure a shared MySQL/MariaDB database.