Start your Kompendium bot

This guide is for the person setting up and running a Kompendium bot. Follow it in order the first time. You can return to any step later from the dashboard.

1. Create or open the right instance

Open the dashboard, create an instance, and give it a recognisable name. If you already have several bots, use the Instance Switcher in the left sidebar and check the selected slug and owner before editing anything.

Every instance is separate: its Discord token, player data, collectibles, images, enabled modules, messages, and settings are all kept apart. A change to one instance never changes another bot just because it uses the same dashboard account.

2. Connect Discord

Create a Discord application and bot in the Discord Developer Portal. Invite it with the bot and applications.commands scopes, and give it the permissions it needs in the channels where it will operate. At minimum, it needs to view the channel and send messages; extra features may need embeds, attachments, or other permissions.

Copy the bot token from Discord and open Setup in Kompendium. Choose Start fresh, type the bot name, paste the token, and press Complete setup. The token is secret. Do not send it to another person or put it in a screenshot. If it leaks, reset the token in Discord and replace it in Config.

Read Dashboard tour for the exact meaning of Setup, Start, Restart, and Provision / Deploy.

After setup, return to Dashboard. If the bot is not running, press Provision / Deploy and wait for the status to change. Use Restart after changing a token or privileged intent.

3. Set the bot’s foundation

Open Config. Set the singular and plural words for what players collect, such as player and players. If your bot uses money, enable Currency in Modules first and then set the currency name. Add the Discord IDs of trusted co-owners, admin servers, and staff roles before testing admin commands.

If you plan to use member data, message-name catching, or presence features, enable the matching privileged intent in both the Discord Developer Portal and Config. A dashboard switch cannot grant an intent that Discord has not approved.

4. Pick gameplay modules

Open Modules and enable the systems your community actually needs. Required modules stay on. Optional modules such as currency, trading, packs, auctions, or social features can be enabled one by one. Press Manage for a full settings page for that module.

Do not turn everything on just because it exists. A focused first version is easier to test, explain, and moderate. You can enable a new module later without changing the rest of the bot.

5. Configure spawns

In Discord, use /spawn channel and select the channel where players should see drops. Then open Spawn in the dashboard. Choose a catch method, sensible minimum and maximum spawn times, a timeout, and basic anti-camping limits. Save and test a few spawns in a private channel.

The Spawn page has advanced weighting and activity controls. Leave those at their starting values until normal spawn timing is working. The Spawn System guide explains every field when you are ready to tune it.

6. Make the presentation yours

Open Cards and select or create a card template. Add your collectible data and artwork. Then open a module’s Manage page to edit player-facing command replies. The response editor uses a Discord-style preview, shows character limits, and only offers variables that are safe for the selected command.

7. Verify before inviting players

Run a normal player command such as /inventory collection, make one test spawn, catch it, and test any module you enabled. Use Dashboard’s Sync commands if slash commands are missing after a change. Check Logs & Activity and the Data job log if an import or runtime action does not complete.

Once those basics work, invite players. Keep a manual backup from the Data page before major migrations, resets, or large edits.