Vote
[1.12.2][Spigot][Bukkit] Kick, ban, restart, rain, sun, day, night, and custom votes. A simple to use and lightweight voting system with a little more functionality than the others. You can create votes that run commands on other plugins, as well as customize each vote to your hearts desire.
seewind has made a tutorial video for all the German fans of the plugin!
seewind has made a tutorial video for all the German fans of the plugin!
Features
- Allows you to create your own votes
- You can specify what command(s) to execute and in what order for both a successful and failed vote
- Fully implements Permissions using Vault, but can also default to regular Bukkit permissions
- You can choose what percentage it takes for a vote to succeed, and the minimum number of players it takes to succeed for each type of vote
- Fully customizable notifications
- Messages can be fully colorized to your hearts desire. Every single message/notification is located and editable in the config.yml
- You can pass any number of parameters you want
- Default votes are: Day, night, sun, rain, kick, and ban
- Source is available here
Configuration
Place the Vote.jar in the plugins folder. The configuration file will be created when the server is started. Make sure to have someone, doesn't matter who, as an op or it will shut down on load. The general overview of the config.yml custom commands is located here. You can read about how arguments work in Vote here. You can read about commands specific to Vote here. You can also watch the tutorial on how to create your own votes.Commands
All commands start with /vote- /vote yes/y - Votes yes on the active vote
- /vote no/n - Votes no on the active vote
- /vote [votename] - "/vote restart" will start a vote to restart the server. /vote kick rabidcrab will start a vote to kick rabidcrab
- /vote veto - Immediately cancels a vote.
- /vote reload - Reload the plugin, cancelling any outstanding vote commands, cancelling any active vote, and reloading the config file.
Permissions
If permissions are not enabled, everyone has the ability to start votes and vote.- vote.voteyes.[votename] - Allows the user or group to vote yes on [votename]. I.E vote.voteyes.restart will allow the player to vote for a restart
- vote.voteyes.* allows a player to vote yes for all votes
- vote.voteno.[votename] - Same as vote.voteyes.[votename], except for voting no
- vote.startvote.[votename] - vote.startvote.* for all, or vote.startvote.restart for restart, etc.
- vote.setvalue - The plugin runs it's own commands when voting for rain or sun. You need this permission on all admins for sun and rain votes to work correctly.
- vote.unkickable - Makes the player un-kickable
- vote.unbannable - Makes the player un-bannable
- vote.veto- Allows the player to cancel votes
- vote.reload- Reloads the plugin
I just installed this plugin, and the /vote command doesnt do anything... Help!
@RabidCrab
Thank you very much!
@RabidCrab
Just installed the latest update, the /vote command doesn't appear to actually do anything.
EDIT: Never mind, no ops.
@ryvix
Just updated it with the latest update.
@gdude2002
I found the issue and I believe I solved it. It'll be in the V1.7.9_01 update that I uploaded a few minutes ago. It'll take a few hours at least to be approved though.
Doesn't appear to work for votekicks.
EDIT: My kicks are handled by BanManager, but yeah, players definitely should not be getting kicked asynchronously.
Will you please update your source code on github? Thanks =)
You're French, you're interested in translation
Tu es français, tu es intéressé par une traduction
Click here
Cliquez ici
Good game
Bon jeu ;)
@Blittzer
Hmm, I'll look into it and see what's going on and throw out an update in a bit.
Doesn't seem to work with the 1.7.8 name re-do.
And yes, I had both myself and Notch in the ops.txt file before it got converted to ops.json with the new UUID thing.
Hey, I set up the permissions, everything works great, set up a custom command, works great. Around half of the people can see the message prompting that a vote was started. This appears to be random. They can vote, but they only see vote succeeded. Can you help me with this?
@RabidCrab
No just started the server up, so no one has op. Let me test that. :P
EDIT:
it worked, but now i got this error:
EDIT2:
Nvm i got it fixed.
@Arton123
Do you have a name in the ops.txt file? It needs an op to run correctly. Beyond that, it should power through any other problems it comes across, IE / command conflicts, missing config, etc.
Check the server statup sequence for any information/errors my plugin comes across. It'll notify you of anything that caused it to fail.
@RabidCrab
For some reason my vote light up red in the /pl command, i tried degrading to 1.6.4 didn't change anything. :(
@Arton123
It probably won't. 1.7.2_01 will work with any version of 1.7.2 though.
Should 1.7.2 work with 1.6.4?
No worries, problem solved. Edited the plugin.yml to make the permissions work properly for me.
@Tr33x0rs
Sorry about the colossal delay in response, I accidentally disabled auto-notifications on messages.
By default players can start votes and vote yes/no. The system is designed to allow for the general populace to request automated admin intervention, such as setting the time of day and kicking/banning players until admins can review the evidence to confirm/withdraw the kick/ban.
You can easily override the default permissions through the config file, through bukkit itself, or by using a custom permissions handler.
I just installed your plugin to test on 1.7.2. I have given my players no permissions for this plugin, although anyone can start a vote.
@RabidCrab
Thanks!