Autoplay
Autoplay keeps the bot playing after the last queued track. Instead of going quiet, FlaviBot picks a track that fits what has been playing and queues it.
Turning it on
/autoplay opens a small panel with a green Enable Autoplay button, a mode
dropdown, and the current state. The panel needs a live player: with the bot not
connected it answers that there is no player. As a prefix command it also
answers to autop.
The AutoPlay button on the now playing message and on the controller panel is the same toggle. It lights up when autoplay is on.
Toggling it on while the bot is connected with an empty queue starts a
recommendation right away, so you do not need a /play first.
Autoplay requires the Toggle Autoplay DJ permission when DJ mode is on.
The three modes
| Mode | Picks | Availability |
|---|---|---|
| Mix | a balance of similar tracks and new discoveries | free |
| Similar | stays close to the current vibe | Premium server |
| Discover | pushes towards tracks you do not know yet | Premium server |
Set yours with the panel dropdown, or directly:
/autoplay mode: discover
Unlike the toggle, /autoplay mode: works without an active player.
Personal choice versus server default
The mode is resolved in this order:
- Your own setting, if you have picked one. It follows you across servers.
- The server default, set on the dashboard.
- Mix, if neither is set.
The panel shows which of the three is in play. When you have a personal override, a Reset button appears to drop it and fall back to the server default.
Server owners set the default on the dashboard, under Music settings, in the Autoplay Mode card.
Starting autoplay automatically
The Default Auto Play switch in the Playback Controls card (Premium) turns autoplay on for every new session, so nobody has to remember to press the button.
Teaching it what you like
Two buttons under the now playing message feed the recommendations: Love this and Not for me. Picking Not for me asks you briefly why (the artist, the genre, or just this song) so the engine knows how wide to apply it.
The engine learns most from tracks that were deliberately picked or searched for. Tracks queued in bulk from a playlist, or filler queued by 24/7 mode, count for much less, so a single long playlist will not drown out what your members actually listen to.
The What's next? button shows the candidates the engine is currently lining up, with a short reason for each.
Blocking what it suggests
The Block button on the controller panel (Manage Server only) removes a track from the server and stops it being recommended again. The server song blocklist on the dashboard does the same for whole artists, and autoplay respects it.
Generating a playlist instead
If you want the recommendations saved rather than played once, /playlist autoplay builds a playlist from a seed track. See
playlists.
