Skip to content

ShottyEvents

Runs an events server: one event at a time, started from a hub, with waiting rooms, player votes on a walk-in platform, events that run themselves, private lobbies, twists, prizes, win streaks and a monthly champion.

An event is any game you can start with commands. ShottyEvents doesn’t play the games itself: each event in its config is a list of command lines for joining, leaving, starting, stopping and resetting, so it can run ShottyGames, ShottyDeathSwap, ShottyMace or a third-party minigame plugin. The games report their winners back with /event win, and ShottyEvents pays the prizes.

  • Server: Paper 26.3, Java 25.
  • Optional: Multiverse-Core (creates worlds listed under create-worlds), the ShottyCore companion (network parties and prize money through /gamewin).

See Running an events server for a complete set-up with the Shotty games.

  • The hub. Everyone who connects starts at the hub (hub.on-join), and falling off it puts you back on it (hub.void-rescue). A floating “Now playing” sign and a boss bar say what is on.
  • One event at a time, one event per player. /event join takes you into the event that is on; /event leave takes you back to the hub. /event stop stops the game and brings everyone in it back. /setevent <other> stops the old event first, then switches.
  • Waiting rooms. An event with lobby: true gets a glass waiting room, built by the plugin in a row starting at lobbies.x/y/z. Players who join wait there; /event start takes everyone in the room into the game and runs the start lines. Someone who joins after the start goes straight in.
  • Votes. When nothing is on and vote.min-players are online, a vote opens with vote.options events that suit the player count. Everyone is taken to the vote platform: a round spawn with a fan of coloured wedges in front, one per option, with a floating sign and the event’s icon over each. Walking into a wedge is a vote; the last one you walked into counts. When the vote closes the wedges light up in turn and stop on the winner. With the platform off, players vote with chat buttons or /event vote <n>.
  • Automatic events (vote.auto, or /event auto on|off). Nobody has to run anything: the vote’s winner is set, its game starts once enough players are waiting, and a round with a winner closes the event for the next vote. A game that repeats by itself closes after vote.loop-minutes, an empty one after vote.empty-seconds.
  • Private lobbies. Anyone can host one from the hub (the nether star in the hotbar, or /plobby). The host picks the event and starts it, and everyone in the lobby goes in; when it ends they come back to the lobby’s room. Each lobby has its own empty world for its room and its own copy of the vote platform. Who may join is up to the host: party, friends (and party), or public. Lobbies chat among themselves.
  • Twists. When a round starts it may get a twist from its event’s list: Low Gravity, Speed Rush, One Heart, Lucky Drops, Double Drops, No Crafting Table, Linked Hearts, Randomizer or Rising Lava. A harder twist multiplies the prize.
  • Prizes. A winner is paid for each other player in the round who didn’t win with them, rewards.per-opponent each, up to rewards.max. Beat nobody, no prize. A winning team is paid the same way, each for every player on the other side.
  • Stats and bonuses. Wins, streaks and the first win of the day are kept in stats.yml. Each win in a row adds a bonus, the first win of the day adds a bonus, and the player with the most wins this month is champion: beating them multiplies the prize.

/event (alias /events), /setevent, and /plobby (alias /privatelobby).

Command What it does
/event What is on, with a button to join.
/event list Every event.
/event join Join the event that is on.
/event leave Back to the hub.
/event vote [n] Show the vote, or vote for option n.
/event stats [player], /event top Wins, streaks and this month’s leaders.
/event twists The twists and what they do.
Command What it does
/setevent <id> or /event set <id> Set the event (none to clear it).
/event start Take everyone in the waiting room in and start.
/event stop Stop the game and bring everyone back to the hub.
/event reset Run the event’s reset lines (a new world for a survival event).
/event who Who is in the event.
/event vote open|close|cancel Open a vote now, close it and set the winner, or call it off.
/event auto on|off Automatic events on or off (kept across restarts).
/event twist <id|none|random> The next round’s twist.
/event stats reset <player> Clear a player’s stats.
/event platform here|reset Move the vote platform to where you stand (and build it), or back to the config’s place.
/event reload Reload config.yml.
Command What it does
event win <player...> [--players <n>] [--event <id>] A game names its winners. --players is how many played (without it, everyone in the event). Winners named within rewards.collect-ticks are one team.
event round <id> A game that runs its own rounds started a new one; a new twist is rolled.
Command What it does
/plobby Open the menu (the host’s menu when you host one).
/plobby create Host a lobby.
/plobby list, /plobby join <host>, /plobby leave Find, join and leave lobbies.
/plobby event <id>, /plobby vote, /plobby start, /plobby end Host: pick the event, let everyone vote, start it, end it.
/plobby privacy <party|friends|public> Host: who may join.
/plobby kick <player>, /plobby promote <player>, /plobby close Host: manage the lobby.
Node Default Lets you
shottyevents.join everyone Join events.
shottyevents.lobby.create everyone Host a private lobby.
shottyevents.lobby.bypass operators Join any private lobby, and see every lobby’s chat.
shottyevents.admin operators Run events. Includes join and lobby.bypass.

Events are under events: in config.yml, keyed by an id:

events:
sumo:
name: "<red><bold>Sumo</bold></red>"
description: "Knock everyone off the platform"
icon: SLIME_BALL
min-players: 2
twists: [low-gravity, speed]
worlds: [sumo]
instances: true # each private lobby plays its own copy
join:
commands: ["player: games join sumo {instance}"]
leave: ["player: games leave"]
start: []
stop: ["console: games stop sumo {instance}"]
reset: []
Key What it does
name, description, icon How the event is shown (MiniMessage; icon is a material).
min-players The vote only offers it with this many online; automatic events start it once this many wait.
worlds The worlds it is played in. Anyone standing in one counts as in the event. A trailing * matches every world starting with that name.
lobby: true A waiting room; /event start takes everyone in.
join.teleport Where joining takes a player: world (its spawn) or world;x;y;z;yaw;pitch.
join.commands, leave, start, stop, reset Command lines run at each moment (see below).
elimination: true Dying makes you a spectator; the last player left wins and the event stops itself.
rejoin: true A player who disconnects mid-game is still in the event when they come back.
win How the winner is found: last-alive, dragon (the players picked at the start win when the Ender Dragon dies; the others once every picked player has died), best-score, or not set (the game reports its winners with event win).
twists The twists this event can roll. None listed, no twists.
variant A Manhunt variant: infection or assassin (see variants:).
loops The game starts its own rounds over and over while the event is on (default: true for events with no start lines).
instances: true A private lobby plays its own copy; {instance} is that copy’s name (p1, p2 …, empty in the main lobby).
private: false Keep this event for the main lobby only.
parties: together A player picked at random brings their party, so a party is never split between sides.
party-teams Team names given to parties by party-teams: lines.
via-permission The permission a via-player: line lends for that one command.

Each line starts with words that say who runs it and for whom, each followed by a colon:

Prefix Runs
console: From the console (also when nothing is said).
sender: As the staff member who typed /event start, stop or reset.
player: As the player joining or leaving.
via-player: For a plugin that ignores the console: typed by a player on the server’s behalf, who holds via-permission for that one command only.
each: Once for every player in the event ({player}).
random: For one player picked at random ({random} in later lines).
pick: Picks the same way, but runs the line once with all the picked names.
others: For everyone except the ones picked.
party-teams: For every party of two or more in the event, with a team name ({team}), once per member.
if-picked:, if-not-picked: Only when the player concerned is, or isn’t, one of those picked.
tell: Not a command: the text (MiniMessage) is shown to everyone in the event.

They combine: others: player: compass makes everyone but the picked player type /compass. A line that names {random} is skipped while nobody has been picked.

Placeholders: {player}, {sender}, {host} (who set the event), {random}, {spawn_x} {spawn_y} {spawn_z}, {instance}, and {s} (“s” when more than one was picked).

For a minigame plugin that has its own join and start commands and a way to run a command when someone wins:

events:
tntrun:
name: "<red>TNT Run</red>"
min-players: 2
worlds: [tntrun_arena]
lobby: true
join:
commands: ["player: tntrun join arena1"]
leave: ["player: tntrun leave"]
start: ["console: tntrun start arena1"]
stop: ["console: tntrun stop arena1"]
reset: []

Then, in that plugin’s “on win” hook, run event win %player% --players %players% --event tntrun.

Section What it sets
prefix The start of every message from ShottyEvents.
hub The hub world and spot, the “Now playing” sign, on-join, void-rescue, and locator-bar (off in every world).
create-worlds Worlds Multiverse should create if missing (name: normal | nether | the_end).
lobbies Where the waiting rooms are built and how far apart; the delay before a started game begins.
rewards Money per player beaten, the most one win pays, the currency, whether only the set event pays, the command that pays ({event} {player} {uuid} {amount} {beaten} {label}), and paid-to, a line telling the winner where the money is.
stats The time zone for days and months, and the leaderboard size.
streaks, daily, bounty The win-streak bonus, the first win of the day, and the champion’s multiplier.
twists How often a round gets one, and the list: name, description, prize multiplier, weight, and each twist’s own settings.
vote Automatic events and their timings, the vote pool, and the platform (place, size, pad colours and blocks, the reveal).
private-lobbies How many at once, size, default privacy, voting on their own platform, own chat, hide-others, the hotbar slot, and the world prefix.
variants Infection and Assassin Manhunt settings.
bossbar, announce The “Now playing” bar, and telling the server when staff change the event.
events The events.

The default rewards.command is gamewin {event} {player} {amount} {label}, which the ShottyCore companion turns into a network announcement and money on your economy server. Without ShottyCore, point it at your own economy:

rewards:
command: "eco give {player} {amount}"

mvn -B package gives target/ShottyEvents-<version>.jar (JDK 25, Paper API 26.3).