Create a new arena with a unique, stable ID:

/wm create <arena_id>

Use IDs such as arcade_1 or castle_whack. The ID is reused by join commands, placeholders, setup output, and saved data.

/wm edit <arena_id>

The home page provides access to locations, portal layout editing, point-block settings, music, display toggles, arena records, signs, and final registration.

Open Manage Arena Locations (FILLED_MAP). Both locations are required.

Start Location

• Click: Saves your exact position. In the normal layout mode, you must already be surrounded by end portal frames.
• Shift-click: Centers the saved position on the current block and automatically places end portal frames in the eight surrounding positions.

When the plugin detects the surrounding frame ring, those eight blocks become the arena's portal locations automatically.

End Location

• Click: Saves your exact position.
• Shift-click: Centers the position on the current block.

The end location is used after normal finishes, leaves, kicks, cancellations, and reconnect recovery.

Portal locations are the positions from which point blocks rise. Use the automatic eight-frame ring from the start-location action, or click Manage Portal Layout (ENDER_PEARL) to build a custom layout.

In Portal Editing Mode:

1. Your inventory is saved and replaced with end portal frames plus a barrier.
2. Place frames to add point-block positions.
3. Break frames to remove positions.
4. Use the barrier to leave editing mode, save the new list, and restore your inventory.

Note: Registration requires at least one portal location. In practice, use several well-spaced frames so multiple blocks can be visible and reachable at once.

The Point Block Settings entry unlocks after portal locations exist. It opens a dialog with arena-specific spawning, movement, and appearance controls.

• Minimum active blocks: Default 4, allowed from 1 to the portal count. Lowest target number of simultaneously visible blocks.
• Maximum active blocks: Default 8, allowed from 1 to the portal count. Hard cap on simultaneously visible blocks.
• Vertical movement step: Default 0.05, allowed from 0.01 to 0.20. Distance moved per tick; higher is faster.
• Maximum vertical step: Default 0.64, allowed from 0.01 to 1.00. Safety cap applied to the movement step.
• Peak wait: Default 12 ticks, allowed from 0 to 40. Time the block waits at its highest point.
• Spawn check period: Default 8 ticks, allowed from 1 to 20. Delay between checks that replace missing point blocks.
• Asynchronous movement: Disabled by default. Moves point-block animation outside the main thread; cleanup remains synchronous.

Choose Active Block Limits to edit the minimum and maximum together. Both are capped by the number of portal locations. If the maximum is set below the minimum, Whack Me raises it to match; changing either value individually also keeps the pair valid.

Tip: More simultaneous blocks increase visual load and decision pressure. Start with 4-8, then test the layout from a player's viewing angle.

Customize Block Appearance (Optional)

Use Customize Point Block Looks to assign the green, red, and gray hit-state items. Put an item on your cursor and click the corresponding preview slot. Blocks, player heads, and custom item metadata are supported, and the saved stack amount is normalized to one.

If NoteBlockAPI is installed, Select Arena Music lists every valid .nbs file in /plugins/WhackMe/musics/.

• Left-click: Select the song for this arena.
• Right-click: Preview the song for yourself.
• No Song: Clear the arena's selection.

Whack Me includes five starter songs and repeats the selected song while a player occupies the arena.

The Other Arena Settings page controls two independent per-arena options:

• Arena Scoreboard: Enables the live scoreboard for this arena. The global scoreboard-enabled option must also be enabled.
• Arena Boss Bar: Enables the configured timer-progress boss bar for this arena. bossbar.yml must also have enabled: true.

Changes apply immediately if that arena currently has a running game.

After an arena has a record, Reset Arena Record shows its holder and score. The confirmation page prevents accidental deletion. Confirming resets only that arena's global holder to None and score to 0; it does not erase player statistics or personal records.

Place a sign, look directly at it, and click Create Arena Sign (OAK_SIGN). Whack Me registers, formats, and waxes the sign. Its state updates automatically, and players can right-click it to join.

Breaking a registered sign requires whackme.sign.break.

Click Register the Arena (FIREWORK) when setup is complete. Whack Me verifies these required values in order:

1. Start location
2. End location
3. At least one portal location

If a value is missing, registration stops and names the missing option. On success, the arena becomes ready, starts its waiting runtime, and the success message includes a clickable /wm join <arena> action.

Note: Arena data is saved automatically and during shutdown. If critical saved locations are missing on a later startup, Whack Me automatically marks the arena as not ready instead of starting a broken game.

How to Join:

• Command: /wm join <arena_id>
• Sign: Right-click the registered arena sign.

An arena accepts one player at a time. If occupied, other players must use another arena or wait until the run finishes.

No permissions required by default.

• /wm join <arena> — Join a registered, currently unoccupied arena and immediately start a timed run.
• /wm leave — Leave the current game, restore the saved player state, and return to the arena's end location.
• /wm stats [player] — Open the statistics menu for yourself or another online/cached offline player.

Requires whackme.arena.* for full access.

• /wm create <arena_id> — whackme.arena.create — Create a new, unconfigured arena with the specified unique ID.
• /wm delete <arena_id> [--confirm] [--cancel] — whackme.arena.delete — Permanently unregister an arena through an explicit confirmation flow.
• /wm list — whackme.arena.list — List every arena and show clickable join actions for ready arenas or setup actions for incomplete arenas.
• /wm edit <arena_id> — whackme.arena.edit — Open the interactive setup menu for an existing arena.

Requires whackme.admin or the listed node.

• /wm — whackme.command.help — Display the installed Whack Me version and author.
• /wm help — whackme.command.help — Display player commands and any administrative commands available to the sender.
• /wm reload — whackme.admin.reload — Reload messages, configuration options, menus, command policy, event profiling, signs, boss bars, sounds, and live game presentation.
• /wm stop [arena] — whackme.admin.stop — Force-stop the current or specified game without applying its run statistics. The console must provide an arena ID.
• /wm kick <player> — whackme.admin.kick — Remove an online player from their current game and follow the normal result and cleanup path.
• Break registered arena signs — whackme.sign.break — Allow staff to break signs registered to Whack Me arenas.
• Bypass the replay cooldown — whackme.cooldown.bypass — Allow a player to join another game without waiting for the configured cooldown.
• Bypass in-game command blocking — whackme.commandblock.bypass — Allow staff to use unrestricted commands while inside a Whack Me arena.

Requires whackme.debug or the listed node and debug: true in config.yml.

Note: Debug commands are intended for testing and troubleshooting.

• /wm debug component <message> — whackme.debug.component — Preview MiniMessage formatting, gradients, hex colors, and components directly in-game.
• /wm debug dump — whackme.debug.dump — Generate an event timing report for troubleshooting performance issues. Enable event profiling in config.yml for meaningful data.

%wm_arenas_total%                 - Total number of registered arenas
%wm_arenas_ready%                 - Number of arenas that are ready to play
%wm_online_players%               - Total players currently inside Whack Me arenas

Outside an active run, these temporary values normally return 0.

%wm_local_score%                  - Current score earned during the active run
%wm_local_point_streak%           - Current consecutive correct-hit streak
%wm_local_longest_point_streak%   - Highest streak reached during the current run

%wm_whacked_point_blocks%         - Total number of green point blocks hit
%wm_whacked_minus_point_blocks%   - Total number of red penalty blocks hit
%wm_whacked_block_rate%           - Positive-hit rate as a percentage value
%wm_record_score%                 - Highest personal score ever reached
%wm_perfect_runs%                 - Total number of perfect runs completed
%wm_games_played%                 - Total number of completed games
%wm_tours_played%                 - Alias for total completed games
%wm_longest_point_streak%         - Highest consecutive correct-hit streak

Generic Statistic Lookup

%wm_stat:<statistic_key>%

Examples

%wm_stat:games_played%
%wm_stat:longest_hit_streak%
%wm_stat:local_correct_blocks%
%wm_stat:local_wrong_blocks%

%wm_arena:<arena_id>:<stat>%

Replace <id> with the exact, case-correct arena identifier.

Arena Settings & Records

%wm_arena:<id>:ready%            - Whether the arena is registered and ready
%wm_arena:<id>:record_holder%    - Arena record holder
%wm_arena:<id>:record_score%     - Highest score recorded in the arena

Live Game Data

%wm_arena:<id>:player_name%      - Player currently using the arena
%wm_arena:<id>:point_blocks%     - Number of active point blocks
%wm_arena:<id>:state%            - Current arena state
%wm_arena:<id>:timer%            - Remaining game time in seconds
%wm_arena:<id>:score%            - Current score of the active player

Display your server's top-performing players on scoreboards or holograms.

%wm_leaderboard:<statistic>:<position>:<name|uuid|value>%

1. Parameters

• <statistic>: The persistent statistic to rank.
• <position>: The rank position from 1 through 10.
• <type>: name (username), uuid (unique ID), or value (raw score).

2. Available Statistics

games_played
perfect_runs
record_score
longest_hit_streak
whacked_plus_blocks
whacked_minus_blocks

3. Usage Examples

# Name of the highest-scoring player
%wm_leaderboard:record_score:1:name%

# Score of the highest-scoring player
%wm_leaderboard:record_score:1:value%

# UUID of the player in 3rd place
%wm_leaderboard:record_score:3:uuid%

# Name of the player with the most perfect runs
%wm_leaderboard:perfect_runs:1:name%

# Value of the 5th longest lifetime streak
%wm_leaderboard:longest_hit_streak:5:value%

Leaderboard entries with a value of 0 are excluded. Empty valid positions return No Player for names and 0 for values.