ArenaLaster

@ArenaLasterJoined 2026
0
Score
1
Public projects
0
Views

Badges2/14

II
Going Public
common
I
First Build
common

Top projects1

RedVsBlue

+0

# Minecraft Plugin Development Request: Red vs Blue (RvsB) Create a fully functional Minecraft Java plugin called **RedVsBlue (RvsB)**. I want a professional Red vs Blue PvP minigame with a polished GUI system, automatic team assignment, customizable kits, kill tracking, player glow effects, and countdowns. **IMPORTANT:** Do not make this plugin overly complicated to operate. I want simple commands, clickable inventory menus, and an easy setup process. Everything should work in-game without needing to edit configuration files manually. ## 1. Main Commands Create the following commands: - `/rvsb set redteam` – Set the location where Red Team players will be positioned before the battle. - `/rvsb set blueteam` – Set the location where Blue Team players will be positioned before the battle. - `/rvsb set spawn` – Set the RvsB spawn location. Players who die during a match will be teleported here. - `/rvsb player kit` – Open the player kit management GUI. - `/rvsb force battle` – Force-start a Red vs Blue match. - `/playerkitstart` – Open the kit selection menu for the upcoming battle. All administrative commands must require OP or the appropriate permission. ## 2. Starting a Battle When an administrator executes: `/rvsb force battle` The following should happen: 1. Automatically collect all eligible online players. 2. Randomly divide players into Red Team and Blue Team. 3. Players CANNOT choose their own teams. 4. Automatically balance the teams as evenly as possible. 5. Teleport Red Team players to the Red Team location. 6. Teleport Blue Team players to the Blue Team location. 7. Open a clickable kit selection menu for the administrator. The administrator should then be able to choose the kit for the entire upcoming match. ## 3. Kit Selection GUI Create a professional inventory GUI titled: **RED VS BLUE - SELECT BATTLE KIT** Show these clickable kit options: - UHC Kit - Sword Kit - Mace Kit - Axe Kit - Custom Kit Each option should have its own Minecraft item icon. When the administrator clicks a kit, it should select that kit for BOTH teams unless a different team-specific configuration has been selected. After selecting a kit, automatically open the 20-second countdown. ### Important kit functionality I want to completely customize kits using an in-game GUI. Create a kit editor where I can: - Choose every armor piece. - Choose the helmet, chestplate, leggings, and boots. - Choose the offhand item. - Choose all 9 hotbar slots. - Choose the entire player inventory. - Choose item quantities. - Choose enchantments and enchantment levels. - Choose shields, weapons, food, blocks, potions, and other items. - Save the kit. - Edit an existing kit. - Reset a kit to its default settings. I want to be able to create separate kits for Red Team and Blue Team. For example: - Red Team can have a diamond sword kit. - Blue Team can have an axe kit. The GUI must allow me to move items around just like a normal Minecraft inventory. **VERY IMPORTANT:** Save all kit configurations permanently so they remain after server restarts. ## 4. Custom Kit Editor The `/rvsb player kit` command should open a GUI where I can manage all kits. Include: - Create Kit - Edit Kit - Delete Kit - Save Kit - Red Team Kits - Blue Team Kits - Preview Kit When editing a kit, allow me to configure the exact armor, hotbar, inventory, offhand, and enchantments. I should not need to use complicated commands to configure individual items. ## 5. Countdown System After the administrator selects a kit: - Start a visible 20-second countdown. - Display the countdown in the middle of every player's screen using a title and subtitle. - Display the countdown in chat or action bar. - Play a sound effect every second. - Use a different, louder sound for the final 3 seconds. - Display a special battle-start sound at 0. During the countdown: - Players cannot move. - Players cannot attack. - Players cannot damage teammates or opponents. - Players cannot leave their assigned team area. When the countdown reaches zero: - Unlock player movement. - Enable PvP. - Start the battle. - Announce that the match has started. ## 6. Team Protection Implement proper team-based PvP. RED TEAM: - Players have a red team identifier. - Red players cannot damage other Red players. BLUE TEAM: - Players have a blue team identifier. - Blue players cannot damage other Blue players. Players can ONLY damage members of the opposing team. Prevent friendly fire through every damage method, including melee attacks, projectiles, and other relevant PvP damage sources. Show colored team tags next to player names: - [RED] in red. - [BLUE] in blue. ## 7. Player Glow Effects I want a special glow effect system. - Red Team players should have a red glow. - Blue Team players should have a blue glow. - Use Minecraft's scoreboard team color system where appropriate. - Ensure teammates and opponents can identify players easily. Additionally, select ONE special player in each team. These two players should: - Have a stronger visual identification using the glow effect. - Display their current kill count above their heads. - Be identifiable as the special Red and Blue players. Make the special players change automatically if necessary, such as when they leave the match. ## 8. Kill Tracking and Leaderboard Track every player's kills during the match. Create a live leaderboard showing: RED VS BLUE 🔴 RED TEAM - Team kills - Top player - Top player's individual kills 🔵 BLUE TEAM - Team kills - Top player - Top player's individual kills Display this information using a scoreboard on the side of the screen. Update it automatically whenever someone gets a kill. Also: - Display individual kill counts above the two special players' heads. - Announce kill milestones. - Announce when a player becomes the kill leader. - Show the winning team when the match ends. ## 9. Death and Respawning When a player dies: 1. Count the death. 2. Keep their team assignment. 3. Prevent them from changing teams. 4. Teleport them to the location configured with `/rvsb set spawn`. 5. Apply their team's configured kit again if they are allowed to continue fighting. I want respawning to be automatic and reliable. Do not allow dead players to exploit respawning to duplicate items or reset their kill count. ## 10. Match Management Implement the following: - Automatically detect when a team has no active players. - Announce the winning team. - Stop the battle properly. - Disable PvP after the match. - Remove temporary effects. - Clear temporary match data. - Restore players to their normal state. - Prevent players from joining an ongoing match unless the administrator allows it. If players disconnect during a battle, handle them properly without breaking the match. ## 11. Visual Design Make every GUI look professional. Use: - Red and blue color themes. - Clearly labeled inventory menus. - Attractive item icons. - Glass pane borders where appropriate. - Simple navigation buttons. - Back buttons. - Confirmation menus before deleting kits. - Clear messages when settings are saved. Use Minecraft inventory GUIs rather than chat-based menus wherever possible. ## 12. Technical Requirements - Target my server's Minecraft Java version: **26.3**. - Check the actual server API and version compatibility before choosing dependencies. - Make the plugin compatible with my server software. - Use persistent configuration storage. - Make sure the plugin works after restarting the server. - Avoid unnecessary dependencies. - Include proper permission checks. - Prevent command conflicts. - Handle errors properly. - Make the plugin efficient and avoid unnecessary repeating tasks. ## 13. Final Requirements I want this to be a COMPLETE working plugin, not just a demonstration. Before finishing: 1. Verify that every command works. 2. Test the GUI interactions. 3. Test kit saving and loading. 4. Test random team assignment. 5. Test the countdown and sounds. 6. Test friendly-fire protection. 7. Test kill tracking. 8. Test death and respawning. 9. Test match endings. 10. Test persistence after restarting the server. Provide: - The complete plugin source code. - A compiled `.jar` file. - A configuration file with sensible defaults. - Installation instructions. - A simple in-game setup guide explaining each command in order. **MOST IMPORTANT:** Make the plugin easy to use. I want to control practically everything through clickable GUIs instead of having to remember dozens of commands. Do not leave unfinished features, placeholders, or fake GUI buttons. Every clickable button must perform its actual function.

minecraftspigot-java0 views

Want your name on a profile like this?