24/7 mode

Normally FlaviBot leaves a voice channel once the music stops and the channel empties. 24/7 mode pins it to one channel instead: it stays connected, and it reconnects on its own after a restart or a disconnect.

24/7 mode requires FlaviBot Premium on the server. Voting does not unlock it.

Turning it on

/24-7 enable
/24-7 disable
/24-7 connect

As prefix commands, /24-7 also answers to 247 and 24/7. All three subcommands need Manage Server.

enable uses the voice channel you are currently in, so join it first. The bot connects immediately and stays.

connect sends the bot back to the configured channel without changing any setting. Use it if it is not where it should be.

disable turns the mode off and disconnects the bot.

From the dashboard

Music settings has a 24/7 Mode card: a switch and a voice channel picker. Saving connects the bot right away. The card warns you if you enable the mode without choosing a channel, since 24/7 stays inactive until one is set.

Staying connected

FlaviBot re-checks its 24/7 servers every 30 minutes and reconnects any bot that is no longer in a voice channel. Once a day it goes further and re-applies the whole setting to the bots that are connected, so one that drifted into the wrong channel is put back.

If it cannot get in, the dashboard card shows why, in plain terms:

the configured voice channel no longer exists
the bot cannot view, join or speak in that channel

What can switch 24/7 off, and what only warns

Exactly one failure switches the mode off on its own: the configured voice channel no longer exists. That one is terminal, since the setting points at a channel that cannot come back, and it has to keep happening for 7 days with no successful connection in between. The card then says 24/7 was turned off automatically. Nothing else is cleared, so getting back is two steps: point the card at a voice channel that exists, and switch the mode on again.

Missing permissions never switch it off. If the bot cannot view, join or speak in the channel, the card warns you and keeps warning you, for as long as it takes. That is deliberate: a permission is one click away from being fixed, and cutting the feature off would be the wrong answer.

Everything that is not about your configuration counts for nothing either way. A FlaviBot restart, a moment where the bot cannot be reached, or a server whose Premium has lapsed neither builds the 7 day streak nor clears it. Only a real configuration failure builds it, and only a real connection clears it.

Any successful connection resets the streak and removes the warning, so a bad afternoon costs you nothing. So does fixing it by hand: turning the mode back on clears the streak and the "turned off automatically" notice, whether you do it from the dashboard, with /24-7 enable, or from the web player, and simply picking a different voice channel restarts the 7 day window from zero.

If the server's Premium subscription lapses, 24/7 stops holding the connection and the normal idle timeout applies again.

Filling the silence

An empty 24/7 channel is a silent one, unless you give the bot something to play. There are three options, all Premium.

Default songs

The Default Songs card on the dashboard takes up to 10 entries, each a song name or a link. They are queued in order whenever the bot connects in 24/7 mode with nothing to play.

Default playlist

Pick one of your own saved playlists and the bot starts it whenever it connects idle.

/defaultplaylist state: True playlist-name: lounge
/defaultplaylist

/defaultplaylist with no options shows the current setting. state turns the feature on or off, playlist-name chooses the playlist. The command requires Manage Server and the server needs Premium. The same setting lives in the Default Playlist card on the dashboard.

The playlist has to be one of yours, see playlists.

Autoplay

Turning on autoplay makes the bot pick its own tracks when the queue empties, which pairs naturally with 24/7 mode.

The idle timeout, for everyone else

Without 24/7, FlaviBot disconnects after 10 minutes of inactivity, meaning nothing playing, or nobody left in the channel.

Premium servers can shorten that on the dashboard with the Inactive Disconnect Timeout slider, down to 1 minute. Ten minutes is both the default and the maximum.

The bot posts a short notice when it disconnects this way, so nobody wonders where it went.

Restricting the bot to certain voice channels
The announcement channel, worth setting so a permanently connected bot does not scatter messages around