Music player

Dispatch.IO has two independent players:

• One player at a time per community, in a single voice channel: if a radio is playing, !play is refused, and the other way round. Use !stop to switch from one to the other.
• Free: the music and radio commands work in every community, with no Premium plan. Only the dashboard player is a Premium perk.
• The bot joins your voice channel on the first !play, at 100% volume.
• Achievements: when achievements are on, every track played counts towards the Music category of the member who requested it (First note, Music lover…) and towards the Jukebox community achievement.

What's different from Discord

The player has the same features as on Discord, adapted to what Fluxer lets bots do:

The queue holds the tracks that will play after the current one.

• !play plays the track if nothing is playing, otherwise adds it to the end of the queue. A playlist link adds all its tracks.
• !play-now puts the track at the front of the queue and skips straight to it.
• !next (or the ⏭️ reaction) skips to the next track; !previous (or ⏮️) restarts the current track, or plays the previous one again in the first 10 seconds.
• !loop repeats the current track or the whole queue.
• !queue shows the queue (10 tracks per page, with the total length); !queue shuffle shuffles it, !queue clear clears it and !queue <number> jumps straight to a track.

When the last track ends, the queue is empty: the bot waits for a new !play without leaving the voice channel (see below).

The player message is posted in the channel where the first !play was typed, and stays there for the whole listening session. It is written in the community's language.

1. First track: the bot posts the player message: title (linking to its source) and thumbnail, author, progress, volume, requester, number of waiting tracks and state ("Playing" or "Paused"). Below it, a legend line and five reactions: ⏮️ Previous, ⏸️ Pause, ▶️ Resume, ⏭️ Skip, ⏹️ Stop.
2. During playback: the same message is edited on every new track, pause or resume, volume change and queue change. Progress is the one at the time of the update: it doesn't move in real time.
3. Queue finished: the message stays, with the title "Unknown", without its legend or reactions. The bot stays in the voice channel.
4. Stop (!stop, ⏹️ reaction, empty voice channel, bot disconnected): the player message is deleted.

• Click a reaction to "press" it: the bot removes it right away, so you can click again. Reactions work for as long as the message is the current player's.
• Confirmations ("The music has been paused by…") are public; a refusal shows for 5 seconds in the channel, mentioning the member concerned.
• If the player message is deleted, the bot posts a new one at the next track. That's what happens in a temporary text channel: the player message is erased like any other after the channel's delay. Start the music from a regular channel instead.
• The !play confirmation ("Song added to queue") disappears on its own after 5 seconds, along with your command.

Music commands are open to every member, with no Fluxer permission. To stop members from cutting each other's music, the bot applies three rules:

1. Be in voice: !play, !play-now and !play-radio require being in a voice channel.
2. Be in the bot's channel: to control playback (pause, volume, queue…), you need to be in the same voice channel as the bot.
3. The requester rule: while the person who requested the current track is in the bot's voice channel, only they can pause it, resume it, skip it, go back, repeat it, change the volume, change the queue, stop it or use the player reactions. If they left the channel, any member in the channel can.

A member with the Fluxer Administrator permission is exempt from the requester rule, and can use ⏭️ Skip, ⏹️ Stop, !next, !loop and !stop without being in the voice channel.

Once the queue has finished, there is no requester anymore: anyone in the channel can manage the player (!stop to make the bot leave, !previous to play the last track again). Start a new track with !play, or let the bot leave when the channel empties. The full table and the error messages are on the Music and radio page.

1. A member types !play-radio followed by the station name (or part of it: !radio nova).
2. The bot joins their voice channel and starts the stream.
3. It replies "Playing now: station" with a ⏹️ Stop the radio reaction, usable only by the person who started the radio. Any member in the bot's voice channel can also stop it with !stop.
4. A new !play-radio from the same voice channel switches station.
5. When the radio stops (reaction, !stop, empty voice channel, bot disconnected, stream cut several times in a row), the message says "The radio playback has been stopped." and its reaction goes away.

If the stream drops, the bot restarts it on its own a few times before giving up. !title shows the station's name and !volume sets its volume; the radio has no queue and no pause.

In every stop case, the player message is deleted.

On top of the commands, you can follow and control the music from the website: the Music player page of the dashboard (fluxer.dispatchio.xyz/dashboard/music), available from the sidebar.

• It follows your voice channel: join a voice channel in a community where Dispatch.IO is present, and the page updates on its own. If the bot isn't in your channel yet, play a track: it joins.
• Live: the current track with its cover, its progress and the number of listeners, updated in real time.
• Controls: play, pause, previous, next, repeat, shuffle, volume, stop.
• Shared queue: everyone in the channel sees the same queue. You can search for tracks and play them now, next or at the end of the queue, move a track up or down or remove it, clear the queue or save it as a playlist.
• Radios: the catalog stations, sorted by genre, one click to start.
• Your library: create your playlists (up to 50, with 500 tracks each), like the tracks you love and play them again in any channel.

The website applies the same rules as the commands: you need to be in the bot's voice channel, and the requester rule applies to the controls. YouTube links are refused there too.

The bot also needs its basic permissions, listed on the Permissions and roles page.

The other error messages are explained on the Music and radio page.

• Music and radio: every music command in detail.
• Buttons, forms and replies on Fluxer: how the bot's reactions work.
• Temporary channels: channels where messages delete themselves.
• Achievements: the Music category achievements.
• Premium plans and limits: the plans that include the dashboard player.
• Permissions and roles: the bot's permissions.