-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broadcast remaining votes required to start party #8
Comments
Sure, do you think it would be best with a setting for the interval? For example, every 25 votes the message is broadcasted. |
Yea, sounds great! Thanks for the quick reply. Maybe a /dp list command that shows how many votes left. Also, if the server restarts, do the votes save or not? My server restarts at 2AM every night so I don't know if it would ruin everyone's votes or not. |
No, the votes go away on reloads / restarts. However players could just vote for it again after the restart because the only limit on them voting is that they can't have already voted. Not that happy with how votes work currently though... the party basically remembers the name of every player that voted, which means each player can only vote once, even if votifier voting is enabled and they vote from multiple sites. I may split apart the votifier votes from votes given by command and just increase the number of votes directly so that they're not based on the player name given. |
Seems good, maybe you can even add an interval like every 3 minutes no matter how many votes are needed it says the EXACT amount of votes needs until the drop party. So we can have interval "25 more votes" "50 more votes" "100 more votes" and the specific interval ones that say for example, the exact amount of votes "31 more votes until drop party!" |
Yeah that's a good suggestion too, not sure about the best way to approach it though. If every party was broadcasting at the same interval then all of the parties would broadcast their message at the same exact time. If I had it cycle through the parties, broadcasting them in order one at a time, then all of the parties wouldn't be shown as often as you want them to. I'm thinking the best way might be to add a command such as /dp votebroadcast [party] and let the server owners install whatever auto command executing plugin they prefer (such as http://dev.bukkit.org/bukkit-plugins/consolescheduler2/) so they can have more control over it. |
Hmmm, well for me I planned on having only one drop party, named default, modified messages so it just says "Drop party started" instead of "Drop party default started!". So what you said wouldn't be an issue for me :p |
Yeah I figured, just gotta make it work nicely for everyone else too though :) |
Very true :) I appreciate your awsomeness. |
Hey if you could so kindly add a feature that logs all drop parties that happen onto a .log file for server admin to view maybe even log the amount of players online with it. |
Sure, could you make a new issue for it? |
17 days later... |
I'd like to know if it's possible for broadcasted to go off once you've hit x amount of votes. So let's say you put 150 votes as your votifier vote to start, then you should have an enable or disable config option to send broadcasted messages to the entire server "xx votes left until drop party! Type /vote!"
The text was updated successfully, but these errors were encountered: