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
Awesome work. One thing: Could you seperate the worlds in the weather vote? That would be awesome.
Just uploaded V1.4.5_01. I added VoteNotFound to the config.yml due to it being a hardcoded value. It will automatically update your config file.
Vote V1.4.2_03 works fine with Bukkit V1.4.5-R0.2. No need to update the plugin.
@XicoBooM
V1.4.2_03 has a reload option available to ops by default.
Just added a new custom command, called FINDPLAYER, and it takes one argument and attempts to resolve a partial name. Check out the kick and ban votes in the config.yml after updating to see how it works.
@XicoBooM
Do you know of any open source apps that enable their own reload? I spent about an hour looking up on how to do it, but I didn't find anything.
Will you ever add an option for OPs/admin node that lets you reload the vote plugin alone without having to reload the whole server? something such as /vote reload I would love to have it since my server usually has about 15 or so people and I would love to have it because i use LockIP as to prevent account hijacks.
@SBlack08
Yes, it's used to mimic a superadmin to execute commands when the command can't be executed via the console. The account Notch is owned by Markus Persson, founder of Mojang, and creator of Minecraft.
The chance of him joining your server is incredibly small, and the chance of him abusing his super admin powers if he joined your server is non-existent.
this plugin op notch?!
@briankdk
You won't notice anything different with Vault installed. Just like Bukkit is an API for Minecraft, Vault is an API for all the permissions plugins out there. If you want my plugin to work with PEX, you'll need to have Vault installed. If you don't, my plugin will default to the Bukkit permissions.
hi
what does Vault do for my server ? (i dont have it, do i need it?) I would like to use your plugin, what will i gain by using vault ?
I have PEX for permissions....
V1.4.2-R0.2 broke V1.4.2_01. V1.4.2_02 has been uploaded and is compatible with V1.4.2-R0.2.
An update for V1.4.2-R0.1 (V1.4.2_01) has been uploaded, and should be approved sometime tomorrow afternoon.
Vote 1.3.2_08 works fine with 1.3.2-R1.0, 1.3.2-R2.0, and 1.3.2-R3.0 as well.
I'll have a beta for 1.4.2 out as soon as bukkit has a beta build available.
@chopstick121
Remove the permissions vote.startvote.kick, vote.startvote.ban, and vote.startvote.restart
Or simply delete them from the config.yml if you don't feel like messing with the permissions.
how to i disbale /vote restart or ban or kick!
@Flaronix
Yup. It'd be something like:
tp [%0] [%1]
[%0] would be the target player to teleport to. [%1] would be the player who started the vote. The last parameter is always the player who started the vote.
@RabidCrab
Ok I see. But how would I select players based off what they voted? so a command would execute something like "/tp <Players who voted yes> <Player who started vote>"?
@Flaronix
Yup, the customized votes are designed for things like that. If the commands are supposed to make a player do something, like teleport, jump, etc, make sure that IsConsoleCommand is set to false.
It's possible that the teleporting plugin won't let my plugin execute the teleport command, but it's unlikely.
Is it possible to select the players that vote yes or the players that vote no when entering the commands? for example: a vote that would ask something like "Teleport to [Player]?" (Player being who started the vote) or something like that. Then everybody who voted yes will be teleported to that player. Similarly you could have 2 outputs, so you could have a vote that would say "Want to play in Creative mode?". Players who vote yes get creative and players who vote no get survival. Is this already implemented or possible to add?