Common setup problems
Fast diagnoses for the issues that come up right after inviting: silent commands, dashboard errors and permission surprises.
The bot ignores every command#
Work through this list in order:
- Module disabled. Everything except the core module ships disabled. Run
,enable module <name>or flip the switch on the dashboard. - Command disabled inside an enabled module. Enabling a module never re-enables commands you switched off individually. Check the command list on the dashboard.
- Wrong prefix.
,prefixshows the active prefix. After a prefix change the old prefix stops working immediately. - Server kill switch. If the whole server was disabled (
,disable serveror the dashboard toggle), only theenablecommand still works β that is the recovery hatch. - Missing channel permissions. The bot needs View Channel and Send Messages in the channel you are typing in.
The dashboard says a server is missing#
The dashboard only lists servers where you are the owner or hold the Administrator permission. A moderator role β even with Manage Server β does not count. See Account & access.
The dashboard shows "You don't have access to this server"#
This is the server-level guard, not an account problem: your Discord session does not carry owner/Administrator status for that guild, or the guild id in the URL is wrong.
Saving anything fails with "The bot is currently offline"#
Every dashboard save is applied by the bot over a websocket, and the dashboard fails closed: if the bot is offline you get a clear error (HTTP 503, bot_unavailable) and nothing is saved β no half-applied settings. Wait for the bot to reconnect and save again.
A command answers with a Discord permission error#
Kharat runs commands and lets Discord reject actions the bot lacks permission for. If ,ban fails with a missing-permission error, grant the bot Ban Members (and keep its highest role above the members it should moderate). The full per-module permission table is in Inviting Kharat & permissions.
Security actions do nothing#
Both security features (anti-invite, anti-spam) require:
- the security module enabled,
- the feature switched on in the security config, and
- for anti-spam to act, the message author must not hold Administrator, Manage Messages or Manage Server, and must not be on the exemption lists.
Still stuck?#
The troubleshooting guide covers runtime errors in depth, and the FAQ answers the most common "does Kharat do X?" questions.