Skip to content

Config page

Open Config when you need to change the basic rules and identity of the selected instance. This page does not create collectibles or configure spawn timing. It controls the settings that other parts of the bot depend on.

Changes on this page are not saved the moment you type. After an edit, use the bar at the bottom of the dashboard and press Save Changes. Choose Discard if you want to undo all edits made since the page was opened or last saved.

Bot name is the name Kompendium uses when referring to the bot in its dashboard and responses. It can contain up to 64 characters. Change this when you are rebranding the bot or correcting the displayed name. It does not rename the Discord application account by itself; change that in the Discord Developer Portal if you want the Discord profile name to match.

The Bot token field is blank when a token is already stored. That is deliberate: leaving it blank keeps the current token. Only paste a value here when you are replacing the token or connecting the instance for the first time. Use the eye icon to reveal or hide the value while entering it.

After saving a new token, go to Dashboard and press Restart so the runtime reconnects to Discord with the replacement token. Treat a token as a password. If it has ever been exposed, reset it in Discord first, then paste the new one here.

The three intent switches must match the privileged intents enabled for the bot in the Discord Developer Portal. Turning on a dashboard switch does not enable that permission in Discord by itself.

  • Server Members lets Kompendium use member information needed by features such as the leaderboard. If it is off, member-dependent features are disabled.
  • Message Content lets the bot inspect normal chat messages. Standard button-based spawning can work without it, but chat-based catch modes and better short-message activity scoring need it.
  • Presence gives the bot access to Discord presence information. Only enable it when the matching Discord setting is enabled and your bot actually needs it.

If an intent is turned on in one place but not the other, the runtime can fail to use that feature. After changing intents in Discord or Config, restart the bot.

Collectible singular and Collectible plural decide the words shown throughout the bot. For example, a football bot might use player and players; a card bot might use card and cards. Keep them short, clear, and grammatically matched. Each field allows up to 32 characters.

Currency name is only editable when the Currency module is enabled. It accepts lowercase letters, numbers, spaces, dashes, and underscores. This is the label players see after balances and rewards, such as credits or buckaroos. Enable the Currency module first if the field is disabled.

Maximum trade per day is the number of trades one player may complete between daily resets. Set a value that limits abuse without making normal trading frustrating. The page enforces at least one permitted trade.

Set Favourite emoji to the emoji shown when a player marks a collectible as a favourite. It is a display choice only; it does not change rarity, ownership, or card art.

The Stat bonuses switch turns bonus ranges on or off for the listed stats. When it is on, each collectible can use the configured stat fields and bonus ranges. When it is off, the bonus minimum and maximum fields become inactive.

Each row has four editable parts:

  • Stat name is the full label shown to players, such as Attack or Speed.
  • Short is the compact label, limited to three characters, used where there is little space.
  • Bonus min is the lowest extra value the stat may receive.
  • Bonus max is the highest extra value the stat may receive.

Press Add stat to make another custom row. Press the x at the end of a custom row to remove it. Some default rows cannot be removed, so their x button is disabled. Rename those instead if you want different wording. Make sure the minimum is not greater than the maximum and use names your players can understand.

This section controls who may use the bot’s management tools in Discord. These are Discord IDs, not names. In Discord, enable Developer Mode, then right-click a user, server, role, or channel and choose Copy ID.

Paste a numeric channel ID into Log channel to send administrative action logs to that Discord channel. The bot needs permission to view and send messages there.

Turn on New server log if you also want an embed posted in the log channel when a server completes its spawn-channel configuration. Leave it off if you do not want those notices.

Use Co-owners for Discord user IDs that should have the same permissions as the main owner. Enter an ID, press + Add, and confirm that it appears as a tag below the field. Remove a tag if the person should no longer have owner access. Only add people you completely trust.

Admin servers is a list of Discord server IDs where administrators are allowed to run administrative commands. Add each server with its ID and + Add. This is useful when you want staff tools available in a private management server without exposing them in every server where the bot is installed.

Full access roles grants the complete admin toolset to members who hold one of the listed Discord roles. Partial access roles is for staff who should have a limited set of management commands. Add role IDs one at a time with + Add. Removing a tag immediately removes that configured role from the next saved rules.

Use co-owners for people, roles for groups of moderators, and admin servers for the places where sensitive commands can be used. Do not rely on a role name alone: the stored value must be its numeric Discord role ID.

Reset data is intentionally separated from ordinary settings. It clears the selected bot’s data, stops its runtime, and returns setup to the beginning. It is not a way to fix one setting or one collectible.

Before confirming a reset, use Data to create and download a manual backup. The reset dialog also offers configuration and SQL export links so you can make a recovery copy. Only continue if you want to rebuild this instance from scratch. Resetting one instance does not reset other instances, but it is still a destructive action for the instance currently selected in the sidebar.