-
-
Notifications
You must be signed in to change notification settings - Fork 70
Bungeecord Setups
Ben edited this page Dec 26, 2023
·
12 revisions
- This is the best and easiest method currently
- Proxy server has votifier only
- Global/per server reward
- Pretty easy to setup
- Almost drop and go, minor setup (Click above for details)
- Similar to PLUGINMESSAGING
- Minor configuration
- Global/per server rewards
- Proxy server has votifier only
- Hardest method (Would try PLUGINMESSAGING first)
- Global/per server reward
- No votifier forwarding required
- Last resort method generally
- Running on bungeecoord not required, but recommended to avoid reward delays (2-3 minutes at most)
- Uses MYSQL database to transfer votes between servers (With votingplugin on bungee telling other servers to check for votes, rather than waiting for background task)
- Can also broadcast cross server
- Only 1 reward per network only
- Pretty easy to setup
- Votifier going to one spigot server only
- Use PLUGINMESSAGING or REDIS with multiple proxies
- Experimental but working
- Each server runs independently from each other, as a standalone server
- Uses votifier forwarding method
Velocity requires a mysql driver to be installed, one available here (install as a plugin in plugin folder) will allow VotingPlugin to run on velocity with no compatibility layer. Works the exact same as bungeecord.
Setup/Configuration:
BungeeCord/Velocity Setups:
-
Proxy Setups
- PLUGINMESSAGING (Best method)
- REDIS (Second best)
- SOCKETS
- MYSQL
- Global Data Handling
- Multi-Proxy Setups
Knowledge base:
- Commands & Permissions
- Special Rewards
- File Layout
- API
- Converting data storage
- Vote Reminding
- Time Changes
- Minecraft Server Lists
- Performance Settings
- Bedrock Player Support
- Debug
- Minecraft Server Lists
- PlaceHolderAPI Expansion
- Signs
- Online/Offline Mode
- WIP MonthDateTotals
Troubleshooting
Rewards:
More setups: