Turning off a module hides its slash commands, buttons and select menus and stops its background behavior for that one server — it never deletes anything, so switching it back on restores everything exactly where it was left. This is how to keep a busy multi-feature bot from cluttering a server that only wants half of what it offers, without losing configuration or history in the process.
What a module actually controls
Every command and background behavior belongs to exactly one of fifteen modules. Disabling one blocks the slash commands, buttons and select menus tied to it, and stops any automatic event it would otherwise fire — a disabled Welcome module simply never posts a welcome embed, even if the channel and message are still configured.
- Catalog — posting, browsing, price checks, the public catalog message.
- Products — product and category creation commands and dashboard management.
- Invoices — generation, lookup and backup.
- Vouchers — creation and management of discount codes.
- Welcome / Leave — the join and exit embeds, as two separate modules.
- Verify — button verification setup, posting and clicks.
- Security — anti-spam and anti-nuke runtime protection.
- Tickets — panels, ticket channels, claim/close controls, transcripts, FAQs and auto-responders.
- AI Chat — optional AI replies in configured channels; off by default, unlike almost every other module.
- Rosters — sign-up panels and attendance tracking.
- Giveaways — giveaway commands, reaction counters, rerolls and participant views.
- Polls — poll creation, voting and voter views.
- TOS — the terms-of-service dashboard page and button responses.
- Utilities — admin tools like clear, embed, status, cloud and sync.
Turning modules on or off
The Modules page lists all fifteen as toggle cards, with "All On" and "All Off" buttons for a fast reset and a single Save. In Discord, /module does the same thing without opening the dashboard. Either way the change applies immediately — Discord's command registry may take a short moment to catch up, but the bot itself stops acting on the disabled module right away.
Disabling never deletes data
This is the part worth trusting before you experiment: turning off Tickets does not close or delete existing tickets, turning off Giveaways does not end an active giveaway early, and turning off Rosters keeps every past sign-up on record. The module switch only gates whether the feature's commands and automatic behavior run going forward. Flip it back on and the configuration, history and any in-progress activity from before are exactly as you left them.
Why disable a module at all
- Reduce clutter. A roleplay community that never sells anything does not need
/invoice,/voucheror the catalog commands cluttering the command list. - Stage a rollout. Turn on Tickets first, get staff comfortable, then turn on Giveaways and Polls later once the basics are running — instead of exposing everything on day one.
- Match the server's actual purpose. A private staff server might run Security and Utilities only, with everything customer-facing switched off.
- Pause something temporarily. Running a break from giveaways for a season? Switching the module off is faster than deleting configuration you will want back.
What module toggles do not do
They are a blunt on/off switch for an entire feature, not fine-grained permission control — you cannot use /module to hide just one command inside Tickets while keeping the rest, and you cannot scope a module to specific channels (a channel-scoped feature like an auto-responder has its own separate scope setting inside the Tickets module, unrelated to the module switch itself). For who can run the commands a module does leave enabled, that is a role question, not a module question — see setting up admin and staff roles.
Common questions
Will disabling Security stop anti-spam and anti-nuke from protecting my server? Yes — Security is the master switch for both. Even with it on, anti-spam and anti-nuke each still need enabling individually on the Security page; the module switch and the feature's own enabled toggle are two different layers.
If I disable Welcome, does it also disable Leave? No, they are separate modules. Turn off exactly the one you mean to.
Does disabling a module remove its data from the dashboard too, or just Discord commands? Both the Discord-side commands/events and the dashboard behavior are gated together — but the underlying data (products, tickets, invoices, rosters) is never touched by the switch either way.
Why is AI Chat off by default when everything else is on? Because it sends message content to a third-party AI provider — turning it on is a deliberate choice a server makes, not something that should be active without setup. Every other module defaults on so a fresh server has a working feature set immediately.
Can I see which modules are actually configured versus just switched on? The Overview page's setup checklist flags a module that is on but missing something it needs — like Security enabled with no log channel set — separately from the plain on/off state on the Modules page.
Manage yours from the Modules page of your server dashboard, and check the full modules reference for anything not covered here.