Module toggles

The switch hierarchy#

Kharat stores three levels of switches per server:

server enabled            <- master kill switch (dashboard home)
  module enabled          <- one per module (utility, moderation, ...)
    command enabled       <- one per command inside the module

A command runs only when all three are on. The core module (help plus the switch commands themselves) is infrastructure and is always on.

Doing it from the dashboard#

The Commands & modules page lists every module with:

• a module switch,
• submodule switches (the utility module's Invite Tracker is a submodule),
• the full command list with individual switches, and
• bulk actions to enable or disable everything at once.

Each switch is saved through the same websocket apply-and-confirm flow as the rest of the dashboard — see Dashboard overview.

Doing it from Discord#

The management commands require Administrator:

,enable module utility
,enable submodule utility invitetracker
,enable command utility ping
,enable commands
,disable command moderation ban

,enable commands (or ,enable server) is the recovery path: when the whole server is switched off, every other command is silent except enable — that single command keeps working so you can never lock yourself out.

What ships enabled#

Automation is a module too#

The Automation module (keyword auto responses) follows the same rules — its responses only fire while the module is enabled. Its content is covered in Automation responses.