With the new connect-based player, the player is immediately paused when it starts up to get into a consistent state.

We could instead poll the state of the player, and use that to initialize the bot state.

Simply typing !afterstream in chat should not save a blank note.

Completely remove [[irc.channel]] in favor of a [irc] channel argument.

Move currency configuration to root of config.

We can now only configure the bot to be present in a single channel.

These are currently stored in secrets.yaml.

Will also need a web-based flow to input these if they aren't set.

Given the character limit per message in chat, it would be good if I could see the full song list via the web UI.
It would also be easier to read given everything is basically one big paragraph in Twitch chat.

https://setbac.tv/player/louis6321 doesn't update when I do !song purge

To reduce the amount of times we need to authorize the bot we can try to attempt to refresh the token using the stored refresh token.

This doesn't have an explicit expiration time, so we catch any error that occurs during the refresh phase and treat it as a failure.

In relation to #3 (https://setbac.tv/player/louis6321), can you please add the position number to the left of the song name so when there's 30 songs in the queue or whatever, it's easy to see the number of one that a mod may wish to promote (or remove once/if #7 is implemented).

The shuffling is currently fully randomized and will probably pick the same song over and over.

Instead we should implement a shuffle that builds a queue out of all the shuffled fallback items to make sure every song plays at least once.

CC: @Jqnxyz @osurce

Support using the !clip command to create clips.

So far:

• lindn

Outputs something like:

The time for the streamer is 08:41 CEST

With the following settings:

• time/enabled - if the command is enabled.
• time/timezone - the timezone that the time command should output.
• time/template - the template that the command should respond with.

On stream OBS reading text file:

In chat it's fine though:

spotify:track:0p9xAAKEYgwgrl6ba6dkWp

Implement a web-based overlay to replace the write-to-file approach with a richer experience.

Modules that need to be implemented:

• Current song
• Countdown

Testing

To test out this feature, you can run setmod from the project directory like this:

path/to/setmod/tools/setmod.ps1 -WebRoot path/to/setmod/bot/web

The web content will eventually be bundled in the bot so we don't have to specify a separate web root. But this is currently used to ease development.

Then navigate to https://localhost:12345/overlay

Performing !song close or !song open commands does not provide the user with a confirmation that the song queue has closed/opened. This may cause concern that the bot may be broken and/or the command did not register.

Volume can currently only be set through configuration. This should be a setting so that it is persisted across restarts.

Mentoring Instructions

Note that this would require a setting per player:

• player/spotify/volume
• player/youtube/volume

You have to add a schema for it here:
https://github.com/udoprog/setmod/blob/master/bot/src/settings.yaml

Calling !song volume should only manipulate the setting of the currently active player. This is tracked here:
https://github.com/udoprog/setmod/blob/master/bot/src/player.rs#L1490

!song volume translate to the Command::Volume command defined here following :
https://github.com/udoprog/setmod/blob/master/bot/src/player.rs#L179

Which is processed here:
https://github.com/udoprog/setmod/blob/master/bot/src/player.rs#L1735

The trickiest part here is that we would have to subscribe to a stream of updates. This is done through the init_and_stream function, and there are a few examples of it in the codebase.

This is probably better since it's guaranteed to be within Spotify's TOS.

To e.g. allow a user to post non-white-listed links:

!permit setbac 5m bypass-host-whitelist

So that settings can be persisted across restarts, like selecting the audio device in the UI.

Also deprecate the [[aliases]] configuration key for the next major release.

Currently "echo_current_song" only allows for true/false.
It would be good if it had something like "commands_only" meaning that it will echo if it's the result of a command in chat (e.g. !skip), but it won't echo by itself at the end of a track.

Instead it just hangs with the following log:

2019-06-07T14:50:38.827262600+02:00 INFO setmod - shutting down...
2019-06-07T14:50:38.833215900+02:00 INFO setmod - bot was shut down

And never starts up again.

When player/max-queue-length is set to x, the bot allows x+1 songs to be queued.

Currently the list of moderators is hard-coded in the configuration.

Promotions are messages which are posted to the channel at regular interval.

Would love the ability to promote songs to play next.
Example: !song promote 7 (this would promote the song that's #7 in the queue to play next).

Support clicking to change audio device in Admin UI.

These checks are otherwise hard-coded and make it hard to test different authorization combinations.

Instances that should be replaced are:

bot/src/command.rs:77:        if self.is_moderator() {
bot/src/command.rs:125:    pub fn is_moderator(&self) -> bool {
bot/src/command.rs:164:        if !self.is_moderator() {
bot/src/irc.rs:648:                            if ctx.is_moderator() {
bot/src/irc/currency_admin.rs:234:                if ctx.is_moderator() {
bot/src/module/song.rs:52:        let is_moderator = ctx.is_moderator();
bot/src/module/song.rs:124:            if subscriber_only && !is_moderator {
bot/src/module/song.rs:150:                    is_moderator,
bot/src/player.rs:863:        is_moderator: bool,
bot/src/player.rs:871:            if !is_moderator {
bot/src/player.rs:918:        if !is_moderator {
bot/src/player.rs:947:        if !is_moderator && user_count >= max_songs_per_user {

They should each be replaced with a scope, like:

if ctx.has_scope(auth::Scope::BypassPlayerConstraints)) {
}

That allows us to test these scopes by tweaking them in the Authorization tab.

Right now all the commands are handled in a single match statement in process_command.

Introduce a settings player/backup-playlist so you can set backup playlist while the bot is running.

twitch token should include login of who it belongs to. Use this in place of streamer configuraiton key.

Alternatively it might be possible to fall back on [irc] channel and strip the hash prefix.

This will also require the use of the signalling mechanism used in Settings, so it might be an idea to incorporate this set into the Settings abstraction somehow.

Please allow song deletion by queue position number, e.g. !song delete 3

Allow mods to run a command to check the bot's version. Likely used as part of a troubleshooting process.

Can the streamer be immune to the mod command cooldown implemented in #6 please?

Show the weather at the streamer's location.

In case you want the bot to run, but not control your local Spotify player you should be able to detach the player so it is no longer controlled by the bot.

CC: @louis6321

Multiple moderators might run !song skip at the same time, skipping too many songs.

Introduce a cooldown to prevent this, so that you can only e.g. skip songs every N seconds.

Currently !song promote <number> swaps the promoted song with the first song instead of putting it at the head of the queue.

CC: @louis6321 @Jqnxyz

suggested by @louis6321

Support defining a command as:

!command edit "/why?^/" {{name}} - because

Add ability to blacklist songs by id.

Allow listing and removing afterstream reminder in the UI

Requested by @louis6321