Skip to main content

​
A flag fails on iOS

If a command flag changed from -- to an em dash —, turn off iOS Smart Punctuation or replace the character with two ASCII hyphens. Only commands that document flags accept them.

​
A member can still send messages after mute

Headless configures mute roles, but Discord combines server permissions and channel overwrites. Check @everyone, member roles, channel exceptions, and the bot’s Manage Roles permission/hierarchy; see Moderation Setup for the roles prepared by .setupmute.

​
Headless is missing or left the server

These docs do not confirm an inactivity-removal policy. Check Discord’s audit log, who removed the bot, service errors, and bot status. Do not use another product’s removal reason to explain a Headless departure.

​
A voice action fails

Creating Headless VC rooms requires Manage Channels and Move Members; channel overwrites and role hierarchy also apply. Run .privatevc panel to review setup.

​
Setup

Use the official site to start installation. Discord shows the requested permissions before you confirm.Official site

​
Commands

Public examples use .. Each server can keep a custom prefix; slash commands are available when registered.
The Commands page uses the public registry published by the bot. In Discord, query a category with .help [section] or /help. If the service is unavailable, it does not fill the page with stale examples.Open Commands

​
Dashboard

Discord OAuth identifies your account and server; every operation checks your permissions again. The web app only shows or changes modules authorized for the selected account and server.Open Dashboard

​
Security

No. Headless separates native Discord permissions from Anti-Nuke capabilities and exemptions. Configure them explicitly.Read Anti-Nuke
No. Recommend is read-only; Setup first produces a preview. Changes apply only after the owner reviews and confirms that preview.View Anti-Nuke setup

​
Steps

1

Copy the error

Record the server, channel, command, and time without sharing tokens or private data.
2

Check the scope

Distinguish user authorization, bot permissions, and Discord channel overwrites.
3

Use safe diagnostics

Check available status/diagnostic commands before retrying an action that deletes or sanctions.
Do not repeat a destructive command or sanction as a diagnostic step. For a server departure, check the audit log first; without that evidence this guide cannot know the cause.