Modules and command responses

The Modules page is the switchboard for the selected bot. A module is a group of related commands and rules, such as collectibles, trading, currency, packs, or administration. Modules are configured per instance, so enabling Currency on one bot does not enable it on another.

The module list

Each module card tells you what the feature does and whether it is currently enabled.

• Press Enable to make an optional module available to the runtime.
• Press Disable to turn an enabled optional module off. Players can no longer use its commands while it is disabled.
• Required means the module is needed for the bot to run. It cannot be disabled.
• Unavailable means the current instance cannot use that module yet, usually because a dependency or required setup is missing.
• Press Manage to open the module’s dedicated full-page settings screen.

Enable a module before relying on its commands. Turning a module on normally preserves its settings and existing records; disabling it hides the feature rather than being a delete button. Still, test changes in a private Discord server before announcing a new game system.

The module settings page

When you press Manage, the page title changes to Module - [name]. The enabled switch sits next to the title so you can immediately see and change the module state. Back to modules in the top-right returns to the module list.

Some modules have ordinary fields at the top, such as a number, text value, dropdown, or checkbox. Hover or read the sentence below each field before changing it; it explains the value used by that module. These changes use the dashboard’s bottom Save Changes bar.

The command structure is deliberately placed below the main settings instead of filling the whole page. Expand Command details only when you need to see or rename command groups and descriptions. The expandable tree keeps the screen focused on the feature you are editing. On small screens, it stacks into a vertical layout.

Choosing a command to customise

For modules with editable player-facing responses, the main area says Choose a command and customize its response. Every listed row shows the full slash-command path, a short description, and either Default or Custom.

1. Open the module with Manage.
2. In the command-response list, click the row for the exact slash command you want to change. For example, choose /player balance, not the whole Player group.
3. The page opens a focused response editor for that command. The link at the top, All command responses, takes you back to the command picker.
4. Edit and save the response, then test that one command in Discord.

Only normal player-facing replies are editable here. Administrative commands and error replies are kept under Kompendium’s control so the bot can still give clear, consistent safety and recovery messages.

The Discord-style response editor

At the top of the editor, a small Discord conversation shows Mxlodix used /your command. Under it is the bot’s reply. This is the content you are changing, not a separate mockup that needs to be copied elsewhere.

Click directly in the reply text to edit a plain message. The character counter beneath it enforces Discord’s 2,000-character message limit. The dashboard will highlight text that is too long and will not save until it fits.

Use ordinary Discord formatting in the text:

• **bold** becomes bold in preview.
• *italic* becomes italic in preview.
• `code` becomes inline code in preview.

The small Preview switch beside the command line has two modes. With Preview off, the text is editable and the required placeholders are visible. With Preview on, the reply behaves like the final Discord message: the editor is locked, the required-placeholder note is hidden, and example values are substituted. This is the quickest way to check formatting before saving. Turn Preview off to edit again.

Variables and required values

The Insert variable buttons add placeholders at the cursor. A placeholder is replaced with real information when a player runs the command. Examples include:

• {player} or {user} for the relevant player mention or name.
• {balance} and {currency} for an economy balance and the configured currency label.
• {collectible_name} and {collectible_id} for a collectible involved in the result.
• {wager} for a game wager.
• {offer_one} and related offer values for a trade.

The buttons offered on a command are chosen for that command. Do not type a placeholder from another command just because it sounds useful; the bot may not have that value when it responds.

Some replies show Required below the editor. Those placeholders must stay in the message because the response would be incomplete or misleading without them. A blackjack wager line, for example, needs {wager}. Keep the placeholder exactly as written, including its braces. Preview replaces configurable values with believable examples and uses your instance’s configured currency label.

Editing embed replies and buttons

Some commands reply with an embed instead of one plain message. In that case, click the visible embed title, description, field name, or field value directly to edit it. Their limits are shown underneath: titles and field names allow 256 characters, a field value allows 1,024, and an embed description allows 4,096.

The Embed: [colour] button cycles through the available accent colours. Click a button shown below an embed to cycle its Discord button colour. Click the button’s visible text to rename it. Button labels have an 80-character limit.

If a command can have several successful outcomes, use the Response type dropdown to select the outcome you are editing. For example, a command may have a normal success response and a special result. Edit each available type separately; saving one does not overwrite the others.

Press Save response when you are happy with the selected reply. The reply is stored only for that command on the selected instance. The chip in the command list changes from Default to Custom after a custom response is saved.

Command details below the editor

Open Command details when you need the command tree rather than a reply. It shows groups, subgroups, and leaf commands. Where a module supports it, command group names and descriptions can be edited inline. Keep names short, lowercase-friendly, and easy to type. Command groups have a 32-character limit and descriptions have a 100-character limit.

Changing command names is a public-facing change: players may need to use a new slash-command path. After saving a command-structure change, go to Dashboard and press Sync commands, then test the new path in Discord.