Content generated with AI — it may contain mistakes.

ExyliaEmotes/GuidesUpdated in v1.4.1

Play a duet

Let two players do one emote together: send the invitation, accept it, and see how the two bodies meet in the middle.

Page 5 of 214 min read

You end up with two players performing one emote at the same moment, facing each other. A duet is an emote with kind: duet in emotes.yml. Two ship, both in the Social tab: highfive (HIGH FIVE) and handshake (HANDSHAKE).

Before you start#

Both players need to own the emote, see Permissions. They must stand within duet.max-distance blocks of each other (three by default), in the same world. A duet cannot be started from the menu, because a menu row has nobody to name.

Steps#

Invite

The first player runs /emote play handshake <player>, naming the other.

Answer

The invited player clicks Accept in the chat message, or runs /emote accept (alias yes), or right-clicks whoever invited them. To refuse, they click Decline or run /emote deny (aliases decline, no).

Watch it start

Both bodies start on the same tick, both players are told the emote is playing, and the cooldown starts for both.

Check that it works#

With two players close together, the first runs /emote play handshake <the other player>. The other sees a message with Accept and Decline. After accepting, both vanish into their own cameras and the two bodies meet in the middle. If the invitation is refused, see the reasons below.

Going further#

Invitations last 20 seconds#

Each player holds one invitation at a time, the one they were sent last. A second invitation replaces the first, and whoever sent the first is not told. An invitation lasts duet.invite, 20 seconds by default and never less than one.

Where the bodies stand#

Not where the players do. Both bodies are placed on the line between the two players, gap blocks apart and turned towards each other, so the choreography meets in the middle whether they stood shoulder to shoulder or three blocks apart. Each body keeps its own player's height. The players are never teleported: their hidden hitboxes stay where they were. The shipped handshake uses a gap of 1.51, the high five 1.13.

Ending a duet#

The two halves are one emote: anything that ends it for one ends it for both, including a punch at either body.

Duets never appear in a showcase

A showcase plays one body at one spot, and half a handshake is a body reaching out at nothing. Duets are left out of every showcase whatever showcase.emotes lists. See Showcases.

Why an invitation is refused, and the message keys

Naming a player for a solo emote is ignored and the emote simply plays. Leaving the player out of a duet is refused with needs-partner, which tells the player to use /emote play %id% <player>. Servers that ran 1.3 or older had it naming /emote %id% <player>, which only opens the menu; updating rewrites that part of the line and keeps the rest.

The invitation is refused on the spot when:

RefusalMessage key
You named yourselfinvite-self
They are performing an emotepartner-busy
They are further than duet.max-distance, or in another worldpartner-too-far

Otherwise the inviter gets invite-sent, the invited player invite-received with the buttons, and feedback.on-invite is played to them. An invitation is sent even if a player does not own the emote, is on cooldown, in combat or in a world where emotes are off: those are checked when it is accepted.

Right-clicking the inviter runs /emote accept <name> as the player, as if they had typed it, so whatever stops them typing it (a missing permission, a combat plugin blocking commands) stops the right-click too. The name after accept or deny is ignored: there is only ever one invitation to answer.

AnswerMessage key
Nothing to accept or declineinvite-none
It ran out, or the inviter leftinvite-expired
The emote was removed by a reload in betweenunknown-emote
The invited player declinedinvite-declined (told to the inviter)

On accept, these are checked in order:

  1. The inviter owns the emote, is not already performing, is in an allowed world, out of combat and off cooldown. The first failure is told to both.
  2. The partner is still online and not performing anything, or partner-busy.
  3. The partner passes the same checks as the inviter, or partner-cannot.
  4. They are still within duet.max-distance in the same world, or partner-too-far.

Something missing on this page? Tell us on Discord