Error Codes FAQ

Common Discord API errors and how to fix them

Mute Command Failed Error SCP-MUTE HTTP 403

Moderation

The /mute command failed. This usually means the bot cannot assign the Muted role or create it.

Solution

Give Scrapline a role with Administrator (or at minimum: Manage Roles) and drag it above the Muted role and above the target member's highest role in Server Settings → Roles.

  1. Go to Server Settings → Roles
  2. Drag the Scrapline role above the Muted role
  3. Ensure Scrapline's role has Manage Roles (or Administrator) enabled
  4. If Muted doesn't exist, the bot will create it. Ensure it has Create Role permission
  5. Try the mute command again

Common Causes

  • Bot role is below the Muted role in the hierarchy
  • Bot role is below the member being muted
  • Bot lacks Manage Roles permission
  • Bot lacks Create Role permission (when creating Muted for the first time)

Missing Permissions (Mute/Warn/Kick/Ban) Error 50013 HTTP 403

Moderation

The bot lacks permission to perform the moderation action. For mutes, the bot needs Manage Roles and a role higher than both the Muted role and the target.

Solution

Move the Scrapline role above the Muted role (and above members you want to mute). Grant Manage Roles and, for creating Muted, Create Role.

  1. Server Settings → Roles → drag Scrapline above Muted
  2. Right-click Scrapline's role → Edit → enable Manage Roles
  3. For first-time setup: enable Create Role so the bot can create the Muted role

Common Causes

  • Bot role is below the Muted role
  • Bot role is below the target's highest role
  • Manage Roles is disabled for the bot