билд батл майнкрафт плагин
BuildBattle | EASY SETUP | TONS OF FEATURES | AUTOMATIC PLOT CLEARING | 100% CUSTOMIZABLE! 1.3.1
Guaranteed the best Build Battle plugin you have come across!
Welcome to BuildBattle. The exact original plugin I made for BuildersRefuge now on spigot! 
This plugin was originally designed and made for mc.buildersrefuge.com by me. With permission, I am now releasing the plugin on here as a free resource.
You must have ActionBarAPI in order to use this plugin!
Want to support my plugins? Donate to the PayPal.me above.
I guarantee you this is the best Build Battle plugin you have seen here on SpigotMC.org. Why? Let me tell you!
Fireworks being launched at the corners of the winner’s arena or plot (better seen in-game rather than photos).
Wondering why this plugin is so great and how it works? Well let me explain by simply showing you how to setup the plugin. As you can see from below, it is real easy. I also have some images above of the plugin!
The process is real simple. Just make sure the hub world for the joining the mini game (so like a hub) and the mini game world, which will hold all the arenas, are on the same server. Once this is done, everything else should be real simple.
Make sure to set the world name for the hub world and the buildbattle world in the config. The default hub world name is world and the default buildbattle world name is buildbattle.
Once this has been done, go to the buildbattle world and set the lobby. To do this, do /buildbattle setlobby. Just make sure you have world guard to protect your spawn of course.
To set the arenas, this is just as easy. So in the config, the total amount of players that can join are 8. Only 2 are needed though for the game to start. You can of course edit these values in the config as literally everything is customizable. So since there can only be 8 players in a game by default, you need 8 arenas. Now if only 3 players join a game, only three of those arenas will be used but you need 8 total in this scenario just in case all 8 play.
Alright so how do you set them? Simple! In the config, the defined length and width, by default, of the arenas is 27 x 27. Therefore, you need an arena that is 27 x 27. Again you can change this. So stand in the center of your arena and do /buildbattle setarena 1. Then do the same for all the other arenas, except it would be /buildbattle setarena 2, then 3, and so on. The default height clearance in the config is 27 also. So players should only build up to 27 blocks high. Why? Well this is because of what I am about to tell you below.
When setting the arenas and lobby, the data is stored in the data.yml file in the plugin folder. This file is created upon first making the lobby spawn.
When the games are completely over, the plots are cleared automatically. No need to get another plugin for this! So that height that you defined in the config? Well that is how many blocks above the floor to the height defined are cleared. So the default height is 27, therefore, 27 blocks above the ground of the arena’s floor are cleared.
FYI: To protect the arenas from being griefed, make sure you use worldguard and protect the floor and the surrounding area of the arena. But make it so players can build above the floor of the arena. Also since by default the height in the config is 27, you will need to protect the blocks above this number in the arena. This way players can only build in the arena and not grief it. If you’re confused by this, simply PM me on Spigot and I will help you. This is super easy to do and takes less than a minute. It is just hard to explain.
On the hub world, the plugin automatically places players into creative mode. To change this, you will need to set the default gamemode of that world (using a plugin like multiverse). If so, DO NOT change the default gamemode of the buildbattle world. Honestly this shouldn’t be necessary to change the hub world’s default gamemode, but keep this in mind.
Once the lobby and the arenas have been setup, when players enter the mini game world the lobby timer should start ticking. Once it hits 5 seconds, it will start counting down in the chat. If there are enough players, the game will begin. If not, the lobby timer will restart. The timer(s) are completely configurable in the config.
If enough players were in the lobby once hitting 0 on the lobby timer, the game should begin and players should be sent to their defined arenas spawns. Players will spawn in the center of each arena.
A random theme is chosen and players can then begin building what the theme is. You may add as many themes as you like in the themelist.yml. Just make sure you follow the format.
FYI: Just about everything in the config.yml is configurable!
By default, players have 5 minutes to build. You may change this in the config if desired. When 10 seconds are left, the timer will start dinging to alert players that the voting session is about to begin.
If you’re in a game and there is only you and 1 other person, then they leave, the game will officially end. However, if more than 2 players are in the game, and someone leaves, they may come back at any time as long as the game is still going on. If they join back during voting, they will be in spectator mode and their build will NOT be voted for.
Once the time limit has ended, players are then teleported to a player’s build in their specific arena, and they may now vote, using blocks in their inventories, on how they thought of the player’s build. The blocks are wool by default. The block type can be changed in the config. The names of the voting blocks may be changed too.
By default, players cannot vote for themselves but this may be changed in the config.
When voting, you simply right click the voting blocks. Doing so will make a sound effect depending on the vote you chose. You can edit the sound effects in the config. I personally really like this feature, as everyone in the game hears the sounds. So yes you can hear what players are saying about your build.
Players, by default, have 10 seconds to vote for each build. Once the time is up, players are teleported to the next player’s build. Once all players have been voted for, players are then teleported to the winner’s build and fireworks will shoot out of each corner of the arena to celebrate the winner! The statistics of the votes resulting in who won are displayed in the chat. Players are then teleported back to the hub after a few seconds of the game being officially over.
When 3 seconds are left to vote for the current player, the timer will start dinging to alert players the voting session for the current player is about to end.
If you have a plugin, such as multiverse, that automatically updates the world’s gamemode, disable this for the hub world and buildbattle world as this will interfere with the game. Also if you use force-gamemode in the server.properties, then disable this.
BuildBattle shouldn’t but might interfere with some plugins that alter the games teleportation system. This is highly unlikely but just throwing that out there.
This plugin 100% works with bungeecord servers and is encouraged to be used on a bungeecord server.
This plugin is designed for 1.13. It has not been tested on any other version and most likely would not function properly on 1.12 anymore (yet to have been tested though. If using 1.12, I advise downloading an older version for it here). If you use viaversion on your server, keep in mind that the scoreboard may not appear properly due to a bug with viaversion.
Make sure to disable enderpearls and chorus fruit when in the mini game arena, or players will be able to travel out of the arenas. This is common sense, but just saying.
It is best to not put this mini game on a server with a crap ton of plugins and to keep things minuscule. Most issues, if any, that you will have with my plugin is interference with other plugins. As more issues are found, I will list common fixes in this section here. As for now, this is all I can tell you. This is why you will probably want to run this plugin on a bungeecord server.
So if you have any issues, please don’t hesitate to private message me on Spigot. I will be more than glad to help you and even get on your server for you to test what’s up. The best way to make this plugin functioning well is you people telling me your problems!
Other than that, the plugin should be working just fine!
A user by the name of Roissica had requested on the plugin discussion page to add a join command and a sign feature. To his request, they have now been added!
Now the sign feature! I spent a good amount of time implementing this is in. There is a lot of features to it, from it catching errors to etc. However, you will figure a lot of those out as you mess around with the signs. For now, let me tell you the basics.
To begin, make sure the player has the permission buildbattle.signplace or they will NOT be able to place a sign. How do you place a sign? Simple! In order to place a BuildBattle sign, type [BuildBattle] on the first line of sign (case sensitive!). If you want the sign title to be, for example, [BuildCraft], you can then edit this in the config!
Once you have created a BuildBattle sign, the sign will have the following lines:
Players: 1/8
———————
JOIN LOBBY
If you edit the sign any time in the config (like the color), simply do /buildbattle reload in-game and the sign will automatically update for you.
If you try placing a BuildBattle sign before setting the lobby and/or arenas, an error message will be displayed.
If you remove the Lobby spawn information and/or arena locations in the data.yml, the sign’s text will change to «ERROR» in red letting you know that there is an issue. The error message will be printed in the console telling you how to fix the issue.
Basically if you do something wrong in the data.yml file, the plugin will notify you by printing a specific error message in the console to let you know how to fix the problem.
Only ONE sign can be placed. If the player tries placing more than one sign on one server, the player will be notified that they can’t. This is because only one instance of the BuildBattle game can run per server. So more than one sign would be unnecessary. You also of course can’t place a BuildBattle sign in the BuildBattle world. You can only place it in the hub world defined in the config.yml.
When players right click the sign, they will join the BuildBattle game. If the lobby and/or arenas haven’t been setup, then the player will be teleported no where. The player will also be notified. In order to use the sign join feature, the player needs the permission node buildbattle.signjoin. If they do not have this permission, then they will NOT be able to right click the sign and it will say they have no permission.
To remove a BuildBattle sign, you can change the «signPlaced» from «true» to «false» in the data.yml file and the sign will be deleted. Then a message, saying the sign has been removed via the data.yml file, will be printed in the console. To remove the sign in-game, make sure to give the player buildbattle.signremove and when ever a player punches the sign, it will be removed. Otherwise, it will tell them they have no permission to remove the sign.
1. /buildbattle | buildbattle.buildbattle
Aliases: /bb
When a player types in this command, it will list the plugins following commands. It only will show commands the player has access to.
2. /buildbattle setlobby | buildbattle.setlobby
Aliases: /bb setlobby
Sets the lobby spawn location for the BuildBattle lobby.
3. /buildbattle setarena [arena_number] | buildbattle.setarena
Aliases: /bb setarena [arena_number]
Sets the arena spawn locations for the BuildBattle arenas.
4. /buildbattle join | buildbattle.join
Aliases: /bb join
Join the lobby if the game has been fully setup.
5. /buildbattle reload | buildbattle.reload
Aliases: /bb reload
Reloads the entire config.yml file.
6. /buildbattle about
Aliases: /bb about
Gives information about the plugin (you can disable this command in the config.yml).
BuildBattle Sign Permissions:
1. %prefix%
The plugin’s prefix for in chat messages.
2. %start_timer%
Displays the amount of time remaining until the game will start (if enough players are in the lobby that are required to start).
3. %players_needed%
The amount of players needed for the game to start.
4. %arena_number%
The arena (1, 2, 3, etc).
5. %time_remaining%
The amount of time remaining until players will vote.
6. %current_theme%
Displays the current theme players are focusing on building.
7. %players_playing%
Displays the number of users playing in the game.
8. %players_allowed%
The total amount of players that can join the game.
9. %num_arenas%
Total number of arenas.
10. (SIGN ONLY) %sign_join_text%
The first line of the sign. This line displays the «signJoinText» from the config.yml.
12. %build_num%
The current build number players are voting for.
13. %player_name%
The player name of who players are voting for. Also used to display players joining the game.
14. (MESSAGE AND SIGN) %status%
Defines whether a player joined the lobby or game. Also used for the signs. i.e JOIN GAME OR JOIN/SPECTATE.
15. %first_place%
The player who won the game. They were first! :O
16. %second_place%
The player who is second place after the game is over.
17. %third_place%
The player who is third place after the game is over.
18. %fourth_place%
The player who is fourth place after the game is over.
19. %fifth_place%
The player who is fifth place after the game is over.
# HAVE ISSUES? PLEASE SEND ME A PRIVATE MESSAGE ON SPIGOTMC.ORG AND I WILL HELP YOU ASAP! 🙂
# PLACEHOLDERS: (MSG) %prefix%, (MSG) %start_timer%, (MSG) %players_needed%, (MSG) %arena_number%, (MSG) %time_remaining%, (MSG) %current_theme%, (MSG AND SIGN) %players_playing%,
# (MSG) %players_allowed%, (MSG) %num_arenas%, (SIGN) %sign_join_text%, (MSG) %world_name%, (MSG) %build_num%, (MSG) %player_name%, (MSG AND SIGN) %status%, (MSG) %vote_block_name%, (MSG) %first_place%,
# (MSG) %second_place%, (MSG) %third_place%, (MSG) %fourth_place%, (MSG) %fifth_place%
# NOTE: To reload the config, do «/buildbattle reload» in-game.
# Customize the message displayed when typing «/buildbattle».
# If a player types in a command regarding BuildBattle, but it is not registered.
unknownCommand : ‘ %prefix%Unknown Command. Type &7/&bbuildbattle &3for a list of commands.’
# When a player types «/buildbattle about», it will display information about the plugin.
displayPluginInformation : true
# If a player doesn’t have access to a certain command, then this is the message that will appear prior than.
noPermissionMessage : ‘ %prefix%&cYou do not have permission!’
# When reloading the plugin, this is the message that will be displayed.
reloadMessage : ‘ %prefix%&aConfiguration successfully reloaded! Due to variables not resetting at certain points, you may need to wait for the current game to end before changes take effect or let the lobby reload. If not, restart the server.’
buildBattle :
# The name of the world where the mini game is ran on. IT IS IMPORTANT THAT THIS IS RIGHT OR THE PLUGIN WILL NOT FUNCTION PROPERLY!
worldName : ‘buildbattle’
# The name of the world where the hub is located for the mini game server (where players can choose another game to play). IT IS IMPORTANT THAT THIS IS RIGHT OR THE PLUGIN WILL NOT FUNCTION PROPERLY!
hubWorldName : ‘world’
# How big the radius is of where players can build in the arenas (i.e 27×27 build area).
arenaRadius : 27
# How many blocks that are cleared from the floor to the sky.
arenaRadiusHeight : 27
# When enabled, some messages will be displayed on the player’s action bar rather than in their chat.
actionBarMessages : true
# Message sent to all players before returning to Lobby (currently only being used if ActionBar messages are enabled to avoid spam)
timeLeftTillReturningToLobby : ‘ %prefix%&3Returning to Lobby in &b%time_remaining%&3!’
# This message is repeatedly sent to all players in the Build Battle lobby, letting them know when the game is about to start.
# %start_timer% is the time remaining until the game will start, as long as there is at least 2 players.
gameStartingWarningText : ‘ %prefix%&3Game starting in &b%start_timer% seconds&3!’
# This message is repeatedly sent to all players who are playing when the Build Battle starts.
gameStarted : ‘ %prefix%Let the build battle begin! If you leave when the game is going on, you will have a certain amount of time until you can join back in! If not, you will only be able to spectate.’
# This message is sent to players when trying to join the lobby when the lobby is full.
tooManyPlayersWarning : ‘ %prefix%Sorry, but the current game is full! Please wait for another game or wait until someone leaves. If the game has already started, then you can join back to spectate. Only &b%players_allowed% players &3can be in a game at once.’
# This message is sent to players when the lobby timer ends and there wasn’t enough players to start the game.
notEnoughPlayersWarning : ‘ %prefix%Not enough players! Restarting lobby timer. At least &b%players_needed% players &3are needed for the game to start.’
# This message is sent to players when a player quits the game and there aren’t enough players to continue.
notEnoughPlayersWarning2 : ‘ %prefix%The game has ended due to not having enough players to continue the game. At least &b%players_needed% players &3are needed for the game to proceed.’
# The sound played when the current time remaining is announced in the lobby. For a full list of sound enums, go here: https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/Sound.html
gameLobbyTimerSound : ‘ENTITY_EXPERIENCE_ORB_PICKUP’
# When a player joins the lobby, this is the text that is displayed.
joinLobbyText : ‘ %prefix%&b%player_name% &3joined the %status%!’
# When a player leaves the lobby, this is the text that is displayed.
leftLobbyText : ‘ %prefix%&b%player_name% &3left the %status%!’
# Whether players can spectate or not (IF HAVING ISSUES WITH SPECTATING, DISABLE IT HERE).
spectatingDisabled : true
# If spectating is disabled (set above), then this is the text that will be displayed when a player tries joining an on-going match to spectate.
joinSpectatingFailedText : ‘ %prefix%&cFailed to join due to a game already in progress!’
# When a player begins spectating the match, this is the text that is displayed (ONLY IF SPECTATING IS ENABLED).
joinSpectatingText : ‘ %prefix%&b%player_name% &3is now spectating.’
# When a player stops spectating the match, this is the text that is displayed (ONLY IF SPECTATING IS ENABLED).
leftSpectatingText : ‘ %prefix%&b%player_name% &3is no longer spectating.’
# Toggle off the sound effect feature here, if you rather not use it.
# TRUE = enabled. FALSE = disabled.
gameSoundEffects : true
# This is the total amount of players that can play in the game. Keep in mind that if you change this, then you need to add more arenas (i.e /buildbattle setarena 5,6, etc)
totalPlayers : 8
# This is the total amount of players that are at least needed for the game to start.
totalPlayersNeededToStart : 2
# This timer here is the amount of time until the game will start in the lobby. The game needs at least 2 players to start. If not, then the timer restarts.
# NOTE: Calculated in seconds. Default for this is 60 seconds.
gameStartTimer : 60
# This timer here is the amount of time a game will last.
# NOTE: Calculated in seconds. Default for this is 300 seconds (5 minutes).
timeRemainingTimer : 300
# The amount of time a player has once they leave the game before they can return in the arena.
timeTillRejoinTimer : 60
# The amount of time a player has to vote for the current player’s build until they must vote for the next player’s build.
# NOTE: Calculated in seconds. Default for this is 10 seconds.
timeTillNextVote : 10
# This is the text that is displayed when successfully setting lobby.
lobbySetSuccess : ‘ %prefix%Lobby set successfully! Players will spawn where you executed the command.’
# This is the text that is displayed when successfully setting an arena.
# %arena_number% is the arena number that was set.
arenaSetSuccess : ‘ %prefix%Arena &b%arena_number% &3set successfully!’
# This is the text that is displayed when trying to set an arena and it fails, because you had done something wrong.
# %arena_number% is the arena number that was set.
arenaSetFailure : ‘ %prefix%&cFailed to set arena! Make sure to use numbers and not words! The number represents what arena you are setting. There also can only be %num_arenas% arenas!’
# This error happens when the player tries setting an arena before the others were set.
# i.e: You try setting arena 4 when arena 3 hasn’t been set yet.
arenaSetFailure2 : ‘ %prefix%&cPlease set arena %arena_to_set% before trying to set arena %arena_number%.’
# This error happens when the player tries setting an arena before the lobby was even set.
arenaSetFailure3 : ‘ %prefix%&cPlease set the lobby before setting the arenas!’
# The message displayed when trying to join the lobby, but no lobby has been set yet. Set the lobby doing /buildbattle setlobby.
cannotStartGameError1 : ‘ %prefix%&cFailed to join lobby because the lobby and arenas haven»t been set up yet!’
# The message displayed when trying to join the lobby, but no arenas have been set yet. Set the arenas doing /buildbattle setarena [arena number].
cannotStartGameError2 : ‘ %prefix%&cFailed to join lobby because the arenas haven»t been set up yet!’
# The message displayed when trying to join the lobby, but you’re already in the lobby.
alreadyHere : ‘ %prefix%&cFailed to join lobby because you»re already here!’
# The message displayed when trying to join the lobby, but the world defined in the config.yml does not exist.
doesNotExist : ‘ %prefix%&cFailed to join lobby because the world defined in the config.yml does not exist!’
# The message displayed when trying to execute commands regarding the creation of BuildBattle in the wrong world.
wrongWorld : ‘ %prefix%&cPlease be in the «%world_name%» world when executing this command!’
# Players can join BuildBattle using a sign. To do this, simply place a sign in-game titled what the «signJoinText» is below!
# To place a sign, name it [signJoinText_HERE]. EXAMPLE: [BuildBattle]
# Only ONE BuildBattle sign can exist at a time per server.
# If the data.yml is altered incorrectly, the current BuildBattle sign will display «ERROR» noting that the data.yml file has been deleted or data is missing. Until the data is back in that file, it will display «ERROR».
# To change how the sign looks, simply edit that below then do /buildbattle reload in-game to update the sign.
signJoining :
# The sign’s join title text. When making a BuildBattle sign, make sure to name it this (CASE SENSITIVE)!
signJoinText : ‘BuildBattle’
# The message displayed when successfully placing a BuildBattle sign.
PlaceSignSuccessful : ‘ %prefix%&bBuildBattle sign &3placed successfully!’
# The message displayed when successfully removing a BuildBattle sign.
SignRemovedSuccessful : ‘ %prefix%&bBuildBattle sign &3removed successfully!’
# The message displayed when trying to place a BuildBattle sign but it fails due to not having a Lobby setup yet. Set the lobby doing /buildbattle setlobby.
cannotPlaceSignError1 : ‘ %prefix%&cFailed to place sign because the lobby and arenas haven»t been set up yet!’
# The message displayed when trying to place a BuildBattle sign but it fails due to not having the arenas setup yet. Set the arenas doing /buildbattle setarena [arena number].
cannotPlaceSignError2 : ‘ %prefix%&cFailed to place sign because the arenas haven»t been set up yet!’
# The message displayed when trying to place a BuildBattle sign but it fails due to an already existing sign.
cannotPlaceSignError3 : ‘ %prefix%&cFailed to place sign because a BuildBattle sign has already been placed!’
# The message displayed when trying to place a sign not in the BuildBattle world.
cannotPlaceSignError4 : ‘ %prefix%&cFailed to place sign because you can only place the sign in the BuildBattle hub!’
# The first line of the sign. This line displays the «signJoinText» from above.
line1 : ‘&8 [ &b %sign_join_text%&8]’
# The second line of the sign. This line represents how many players are in the game out of how many total.
line2 : ‘&bPlayers : &3%players_playing%’
# The fourth and final line of the sign. This line displays the status of the game (JOIN LOBBY OR SPECTATE GAME).
line4 : ‘&0 %status%’
scoreBoard :
# The title of the scoreboard displayed when a game is running.
title : ‘&b&lBUILDBATTLE’
# Change how the time remaining text is displayed on the scoreboard. The time remaining represents how much time is left until the game will end and players will vote.
timeRemainingText : ‘&3Time : &b%time_remaining%’
# Change how the voting time remaining text is displayed on the scoreboard. The time remaining represents how much time is left until the players will have to vote for the next player.
voteTimeRemainingText : ‘&3Vote : &b%time_remaining%’
# Change how the theme text is displayed on the scoreboard.
themeText : ‘&3Theme:’
# Change how the theme name is displayed on the scoreboard. Obviously by its name, this here displays the current theme the players must build beneath the «themeText».
themeNameText : ‘&b %current_theme%’
# Change how the player count text is displayed on the scoreboard. Basically this displays the amount of players currently playing build battle. It does NOT include those spectating.
playersText : ‘&3Players : &b%players_playing%’
# Other is the text displayed on the scoreboard at the very bottom. For this, I just have the website. Add what ever you want here.
other : ‘&btwitter.com/gonfonix’
# When voting, players will receive blocks (wool blocks by default) they can use to vote for the build. They can only vote ONCE for each build, so they cannot change their vote.
# Votes are NOT displayed publicly in chat (for obvious reasons).
# Use this link for setting the voting blocks (and colors if using a block such as wool): https://hub.spigotmc.org/javadocs/spigot/org/bukkit/Material.html
votingSystem :
# When voting, it will say who owns what build in the chat. Edit that text here.
buildByText : ‘ %prefix%Build %build_num% by: &b%player_name%&3.’
# When voting, it TPs to players in order of who joined first. So if one of them left, it will take everyone to the next player still on and it will also warn everyone.
playerLeftText : ‘ %prefix%&cThe next player in line had left, so going to the next build. ‘
# When a player votes, it will send an verification message to the player letting them know the vote had succeeded.
votePlaced : ‘ %prefix%Vote %vote_block_name% &3placed on &b%player_name%»s build&3!’
# If this is TRUE, then players cannot change their votes!
voteOnce : false
# If the above is TRUE, then this message will be displayed when a player tries changing their vote.
# If a player had already voted and tried changing their vote, this message will appear.
voteFailed : ‘ %prefix%&cVote failed! You already voted!’
# If this is FALSE, then players cannot vote for themselves!
selfVote : false
# If the above is FALSE, then when a player tries voting for their self, this message will appear.
selfVoteMessage : ‘ %prefix%&cYou can»t vote for yourself silly!’
# When the game ends (after all players have voted for all builds), the results are displayed.
# %check% checks whether or not there was a first, second, third place, etc.
# Change the name for the «AMAZING» block. This is the highest vote a player can receive.
amazingBlock : ‘&a&lAMAZING!’
# Change the block for the «AMAZING» block.
color1 : LIME_WOOL
# The sound played when a player places an «AMAZING vote». For a full list of sound enums, go here: https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/Sound.html
amazingVoteSound : ‘ENTITY_WOLF_AMBIENT’
# Change the name for the «GREAT» block. This is the second highest vote a player can receive.
greatBlock : ‘&b&lGreat!’
# Change the block for the «GREAT» block.
color2 : CYAN_WOOL
# The sound played when a player places an «GREAT vote». For a full list of sound enums, go here: https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/Sound.html
greatVoteSound : ‘ENTITY_PARROT_AMBIENT’
# Change the block for the «GOOD» block.
color3 : BLUE_WOOL
# The sound played when a player places an «GOOD vote». For a full list of sound enums, go here: https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/Sound.html
goodVoteSound : ‘ENTITY_CAT_AMBIENT’
# Change the name for the «BAD» block. This is the fourth highest vote a player can receive, and it is NOT considered good.
badBlock : ‘&c&lNot Good’
# Change the block for the «BAD» block.
color4 : ORANGE_WOOL
# The sound played when a player places an «BAD vote». For a full list of sound enums, go here: https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/Sound.html
badVoteSound : ‘ENTITY_CAT_DEATH’
# Change the name for the «TERRIBLE» block. This is the fifth highest vote a player can receive, and it is DEFINITELY NOT considered good.
terribleBlock : ‘&4&lTERRIBLE!’
# Change the block for the «TERRIBLE» block.
color5 : RED_WOOL
# The sound played when a player places an «TERRIBLE vote». For a full list of sound enums, go here: https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/Sound.html
terribleVoteSound : ‘ENTITY_HORSE_DEATH’
KNOWN BUGS (Spectating):
— Lets say a player is playing in a match then leaves the server and the game eventually ends. When that player joins back after the previous game has ended, they may be put into spectator mode in the lobby. Simply have them go back to the hub then join back to play again.
— If a player is spectating then the game ends, they may not be teleported back to the hub. Simply have them go back to the hub then join back to play again.
— For some reason that I cannot figure out: If a player joins to spectate after someone had left the game then joins back, they might cause the game to completely break on the server.
—> Due to the spectating issues listed above, it is advised for now to disable spectating in the config.yml until fixed!
REVIEWS:
If you decide on making a review, then that is much appreciated. However, do not state current bugs you are having with the plugin in your review. Please private message me on Spigot beforehand so I can see what the problem is you’re having. Thanks!
Terms and conditions
My plugin is under the all rights reserved license.
You are not allowed to redistribute this plugin on any website.
You are not allowed to modify or decompile this plugin.