Advanced problems? Use the end-to-end troubleshooting guide for duplicate rewards, SQL errors, proxy forwarding, offline deliveries, identity mismatches, and period resets.
A healthy real or listener-generated test normally produces both:
[VotingPlugin] Received a vote from service site 'SERVICESITEHERE' by player 'BenCodez'!/av vote <player> <site> tests VotingPlugin processing but does not test the public listener port, token/key, or vote-site connection.
Supported listener options include VotifierPlus and NuVotifier. Public tester availability changes over time; a real test from one configured listing is the strongest end-to-end check.
ServiceSiteThe incoming service name must exactly match:
VoteSites.yml -> VoteSites.<site>.ServiceSite
After a test vote, use /av servicesites to view received service names. Do not substitute the display name or vote URL unless the listing actually sends that value.
If no matching site exists and automatic site creation is enabled, VotingPlugin can create a site. Review generated entries before enabling rewards.
Check:
0.0.0.0 is a wildcard bind address, not an address a vote site should connect to. Bind only when the hosting layout requires it, then restrict the listener port to the expected public exposure and keep unrelated management ports private.
In the standard VotingPlugin topology:
BungeeMethod.A deliberately custom topology can place or forward listeners differently, but each vote must enter VotingPlugin only once. Duplicate listener plugins or forwarding paths commonly cause duplicate rewards.
Test proxy communication separately with:
/votingpluginproxy status
/votingpluginproxy vote <player> <site>
Then send a real/listener-generated vote to verify the public listener path.
OnlineMode values consistent with the network's identity mode.BedrockPlayerPrefix to match the actual Floodgate/Geyser prefix.AllowUnJoined with backend AllowUnjoined; capitalization is significant. The standard proxy-managed layout uses proxy false and backend true.BungeeMethod, shared database, server names, and transport connection.Do not publish private keys, tokens, database credentials, broker credentials, or full unredacted configuration files in support reports.