Duelling

Challenging

/duel <player> opens the challenge screen. It tab-completes every player on this server, and every player on the network when network duels are on.

Before the screen opens, the plugin checks that:

• the player is not challenging themselves;
• the target takes challenges (/duel toggle turns them off);
• neither player is already in a duel, watching one or on their way to one, or held by another plugin (an ExyliaLib session such as a queue or a minigame);
• neither player is combat tagged;
• at least one arena is ready (or, on a network, a kit duel could be fought on the arena server);
• the challenger is not on the challenge cooldown (requests.cooldown, or the rank's exyliaduels.cooldown.<n>, skipped with exyliaduels.bypass.cooldown).

The challenge screen

One screen, one card per term. Every click redraws it in place; ESC closes it and leaves nothing behind.

The screen opens on own inventory when the server allows it and an arena takes it; otherwise on the first enabled kit. A change that the chosen arena no longer takes (a different kit, or own inventory in a kit-bound arena) puts the arena back to Random. A money bet the player cannot afford, or under the minimum, is refused when typed, so the screen never shows a bet that cannot go out.

Each option sits behind a node everybody holds by default (exyliaduels.mode.own, mode.risk, bet.money, bet.items, arena.choose, kit.<id>). A button the player's rank does not include answers "Your rank does not include that option." and changes nothing. See Permissions.

The request

On send, the cooldown starts and the challenged player receives a centred block in chat: who, the mode, the arena, the bet and how long it waits, with clickable [✔ ACCEPT] and [✘ DECLINE] buttons. A kit with hits to win or rounds says so after its name: "(first to 5 hits)", "(best of 3)". A challenge waits requests.expiry (60 seconds by default); when it runs out both are told.

Each player has at most one challenge out: a new one replaces the previous. Leaving the server drops every challenge a player sent or received.

From accept to fight

Accepting checks the terms, both players and both balances again: the server, the arenas or either player may have changed since the challenge was sent. Then:

The fight

• Only the two opponents can hurt each other. This runs last, so a no-PvP region of another plugin does not stop a duel, and nobody outside can join one. Fighters and spectators cannot hurt players outside the duel.
• Nobody leaves the arena. A fighter cannot walk out of the arena's columns, and a teleport away is refused with "You can't leave the arena during a duel." Nobody else walks or teleports into an arena in use, except players with exyliaduels.admin.
• Falling out loses. Dropping more than a block below the arena's floor counts as a death, and so does dropping below the kit's fall depth.
• The kit's rules apply: its arena flags, no damage, hit delay, regeneration, hunger, the ender pearl and golden apple cooldowns and the build height. See Arenas and kits.
• Skill plugins are held back. AuraSkills and mcMMO give fighters no experience, abilities or combat stats until they are home.
• Commands outside allowed-commands are refused.
• Dropping items is refused in kit duels and own-inventory duels without risk: what the snapshot gives back would come back twice. In a risk duel the items are the players' to throw.
• The ender chest cannot be opened from the arena on: it is restored with the player afterwards.
• Dying never really happens: the death is cancelled and nothing drops. During the fight it loses the duel. Graves, death chests and kill rewards never see a duel death.

Rounds

A kit with Rounds set is played as a best of 3, 5 or more. Losing a round (a death, a fall, or the opponent landing the hits to win) scores it for the other player: both see the score in chat and as a ROUND WON or ROUND LOST title for match.end-delay. Then the arena's blocks are put back, what was left lying around is cleared, and both start again from their spawns with the kit and its fight start (a kit from another plugin is put on again by it, with the same roll), frozen through match.countdown with the round number under the title.

• The first to win the kit's rounds wins the duel. Only the duel decides records, bets and stakes.
• match.max-duration covers every round together: running out is a draw, whatever the score, and every stake is refunded.
• Quitting during any round forfeits the whole duel.
• The score is on rounds-scoreboard, and the challenge reads "(best of N)".
• Own inventory duels, kept or at risk, are always a single fight.

How a duel ends

Both see a VICTORY, DEFEAT or DRAW title, and the loser watches the end as a spectator. The result stays on screen for match.end-delay (3 seconds by default). Then spectators are sent back, both players are restored, the stakes are settled, and the arena is freed and regenerated.

Who gets what

A player who quit gets their things back on their next join. Wins, losses and streaks are only recorded when there is a winner; a draw changes no record.

After the duel

Once a duel that reached the fight is decided, both players read a centred block in chat: DUEL OVER with the opponent, the duration ⌚ and, for a kit of rounds or hits, the score. Three buttons work for after-duel.window (5 minutes by default; 0s turns them off):

A button clicked after its window, or by somebody who was not in the duel, answers "That duel can no longer be looked back on." On a network the summary is kept in the shared database until its window closes, so the buttons work from whichever server the players were sent back to.

History

/duel history lists your finished duels, newest first: result, opponent, mode, score, duration ⌚ and date, with your wins, losses and draws among them. /duel history <player> shows anybody's and needs exyliaduels.history.others. Each duel opens a screen with the mode and arena, the score, the money bet, the time, the server that decided it, and Watch replay.

Every duel that reached the fight is stored, draws included; a duel called off before the fight never is. Each player keeps history.keep duels (45 by default) for up to history.max-age (30 days).

Replays

Every duel that reaches the fight is recorded (or only kit duels, with replays.kit-only): both fighters, every arrow, pearl and potion, every block placed, broken or blown up inside the arena, and each round. Watch replay gives the viewer a free copy of the same arena, where they fly around the fight as a camera nobody can touch, driven from a hotbar:

The time, length and speed show above it. /duel leave, quitting or a stop also leave, and the viewer is put back exactly as they were. The hotbar is drawn for the viewer only: what they really hold stays untouched.

• Your own duels need exyliaduels.replay; anybody's, exyliaduels.replay.others.
• The replay is watched in its own arena: a server without that arena refuses it with "That duel's arena is not on this server.", and when every copy is in use, "No copy of that arena is free right now."
• One replay is stored for both players and deleted with the last history row that lists it, or after replays.max-age (14 days).

Spectators

/duel spectate <player> watches a duel being fought on this server, from inside the arena, in spectator mode. It tab-completes the players fighting here. The spectator is saved and taken between the two spawns, a little above them; both fighters are told who is watching.

A spectator cannot leave the arena's box and can only use the commands in allowed-commands. /duel leave sends them back exactly as they came, and so does the end of the duel. Switched off with spectators.enabled: false.

Records

Every player has a record: wins, losses, current win streak, best streak and money won. /duel stats shows your own, /duel stats <player> anybody's the server knows.

Money won only counts payouts in the configured currency (bets.money.currency, or the server's default): amounts in different currencies do not add up.

Win rate, games played, leaderboards of wins and streaks, and the last duel's opponent and result are placeholders: see Placeholders.

/duel toggle stops or resumes receiving challenges; it is stored with the record, so it follows the player across servers sharing the database.