Karaoke

Minecraft 版本： 1.21 1.21.1 1.21.2 1.21.3 1.21.4 1.21.5 1.21.6 1.21.7 1.21.8 1.21.9 1.21.10 1.21.11 26.1 26.1.1 26.1.2

平台： bukkit paper spigot

? KaraokePlugin

A full-featured karaoke event management plugin for PaperMC servers.

KaraokePlugin lets you run live karaoke nights directly on your Minecraft server. Assign singers, manage a judge panel with live scoring displays, drop the stage floor for dramatic effect, teleport the crowd, handle a singer queue — all from a clean in-game GUI without touching a single command by hand.

✨ Features

• GUI Control Panel — open with /karaoke or /k; every action has a dedicated button
• LuckPerms Integration — singer, judge, and listener roles are applied and removed automatically via fully configurable console commands
• Live Scoring — judges and audience vote yes/no; scores are tracked separately and displayed on the leaderboard
• Judge Display Blocks — concrete blocks in the world flip from yellow → green or red as judges vote
• Judge Suffixes — judges automatically receive a coloured [J1] [J2] etc. suffix via LP meta
• Singer Queue — add multiple players to a waiting list; advance through them one-by-one
• Round Timer — optional per-singer time limit with title countdowns; auto-advance queue when it expires
• Stage Drop — removes the floor under the singer's feet; restores it automatically after a configurable delay; teleports the singer back to stage on respawn if they die
• Execution Chamber — teleport the singer to a separate chamber via a redstone trigger
• Top-3 Winner Announcement — broadcasts a formatted results banner with judge and audience score breakdown
• Spawn Return — sends every player to a configured spawn point when the event ends
• Event Commands — run any commands on behalf of every player (with * permissions) when the event starts or ends
• PlaceholderAPI Support — 9 placeholders for scoreboards and displays
• Fully Configurable — all LuckPerms commands, messages, scoring weights, timers, and locations are set in config.yml
• Persistent Setup — captured locations and scores are saved to data.yml and survive restarts

? Installation

1. Drop KaraokePlugin.jar into your server's plugins/ folder.
2. Start the server once to generate plugins/KaraokePlugin/config.yml.
3. Set your LuckPerms group names under roles: if they differ from the defaults (singer, judge, listener).
4. Optionally edit luckperms-commands: to customise exactly what LP commands are run.
5. In-game, run /karaoke setup to capture all required locations (stage, judge bench, listener deck, spawn, trapdoor region, execution chamber).
6. Done — run /karaoke start to begin your first event.

Requirements

?️ Commands

All management commands require karaoke.host. Aliases: /k

? Permissions

? PlaceholderAPI Placeholders

Requires PlaceholderAPI to be installed.

⚙️ Configuration Overview

config.yml is read-only at runtime. data.yml is written by the plugin and holds all captured locations and runtime state.

luckperms-commands:

The exact console commands dispatched for every role action. Supports {player}, {group}, and {ordinal} placeholders. Set any entry to "" to skip it entirely.

luckperms-commands:
  singer-add:       "lp user {player} parent add {group}"
  singer-remove:    "lp user {player} parent remove {group}"
  listener-add:     "lp group default parent add {group}"
  listener-remove:  "lp group default parent remove {group}"
  judge-add:        "lp user {player} parent add {group}"
  judge-remove:     "lp user {player} parent remove {group}"
  judge-suffix-set:   'lp user {player} meta addsuffix 1000 " &6[&eJ{ordinal}&6]&r"'
  judge-suffix-clear: "lp user {player} meta removesuffix 1000"

event-commands:

Commands run for every online player on event start/stop. Each player executes them with temporary * permissions, so warps and other permission-gated commands work for everyone.

event-commands:
  on-start:
    - "warp karaoke"
  on-stop:
    - "warp spawn"

Other notable settings

?️ Setup Guide

Open /karaoke setup and click each button while standing at (or looking at) the relevant position:

All captures are saved to data.yml and persist through restarts.