!bansong

Requirements and availability

Enabled command, connected eligible platform, configured authority and cooldown; individual handler requirements also apply.

Picker contexts: command.

Behavior

Block the currently playing song.

Limitations

• Defaults describe a fresh configuration; existing settings and migration normalization may differ. Platform toggles do not guarantee that a provider API supports the command.
• Command triggers/aliases may be customized; use the effective configured trigger.

Contract details

Usage

!bansong

Defaults

{
  "enabled": true,
  "aliases": [],
  "requiredAuthority": "moderator",
  "cooldownSec": 0,
  "globalCooldownSec": 0,
  "platforms": {
    "twitch": true,
    "youtube": true,
    "kick": true
  },
  "responseTemplate": "\"{title}\" has been added to the blocklist."
}

Aliases

[]

Response Variables

[
  "title"
]

Examples

Usage notation: <required>, [optional]; replace placeholders before sending.

!bansong

Related entries

• {title} in !bansong

Source and verification

Source-reviewed for 2.8.0. Connected-service validation remains subject to release UAT.

• server.js — DEFAULT_COMMANDS.bansong
• src/features/media/mediaCommands.js — handleSongRequestCommand

Source revision: 472fb34b484eeef0b663d28cacb628a7b9f14ff1