First steps after inviting
Confirm the bot is alive, pick a prefix, enable the modules you need and verify each one works.
1. Confirm the bot is alive#
Run the built-in core command:
,helpA picker appears listing every module with its commands. If nothing answers, the bot is offline or lacks View Channel / Send Messages in that channel.
The core module (help and the command switches) is always on — it cannot be disabled, so a reply to ,help proves the connection and prefix both work.
2. Enable the modules you want#
Every module except core ships disabled. Enable what you need either from the dashboard or with the management commands:
,enable module utility
,enable module moderation
,disable module utilityBoth commands require Administrator. The dashboard equivalent lives under your server's Commands & modules page — see Module toggles for how the switch cascades to individual commands.
3. Set your prefix (optional)#
The default prefix is ,. Check it any time with ,prefix; change it with:
,cgprefix ?Prefixes are 1–5 characters and cannot contain spaces. Slash commands are unaffected by the prefix.
4. Verify each module with a harmless command#
| Module | Try this |
|---|---|
| Utility | ,ping, ,serverinfo, ,remindme 10m stretch |
| Moderation | ,prefix (read-only) |
| Logging | ,logging status after setting a channel |
| Security | ,security status |
| Tickets | ,ticket info in an open ticket |
| Server Stats | ,stats |
| Automation | ,automation list |
5. Configure the dashboard-facing features#
Sign in at /dashboard, pick your server and walk through:
- Logging — set the log channel, choose which of the twelve event types to receive.
- Security — turn on anti-invite and/or anti-spam and set thresholds.
- Tickets — configure the panel, publish it to a channel.
- Server Stats — create statistic channels and activity roles.
- Custom commands — build your first KAL v2 command.
Every one of those pages documents its fields in Dashboard & server management.