Discord Developer Portal walkthrough

This page covers the Discord side of a Kompendium bot. Kompendium runs the game, but Discord owns the application and bot identity. Keep the Developer Portal open in another tab while you set up an instance for the first time.

Open discord.com/developers/applications. The opening list is only the applications you own or can administer. Choose the correct one before changing anything; one wrong token or intent switch can affect a different bot.

General Information: the application profile

Select an application, then General Information in the left navigation. This page contains the Application Name, App Icon, Description, Application ID, and Public Key.

For normal Kompendium setup, change the name, icon, and description here. The Application ID and Public Key are identifiers; neither is a bot token and neither belongs in Kompendium’s token field.

Bot: the account players see

Choose Bot. This page configures the Discord bot user.

Profile and username

Set the bot username and avatar here. This controls the member-list account and message appearance. It is separate from the name of a Kompendium instance, so it is normal to set both while branding a bot.

Token: how Kompendium logs in

Under Token, choose Reset Token if Discord asks you to generate one. Copy it once and paste it directly into Kompendium Setup or Config. Discord deliberately does not reveal the same token later.

Treat it as a password:

Never share it in Discord, screenshots, recordings, source code, or GitHub.
Never paste it into public troubleshooting messages.
If it is exposed, use Reset Token, replace it in the correct Kompendium instance, and restart that instance.
A token belongs to one Discord application. It is not a global Kompendium key.

If a token error appears, first confirm you pasted the Bot token with no extra spaces and restarted the correct instance. Resetting a token invalidates the old value everywhere it was used.

Privileged Gateway Intents

At the bottom of Bot, Discord shows Privileged Gateway Intents. These are permission gates for sensitive live event data. Match every enabled one with the corresponding switch in Kompendium Config.

Discord switch	What it permits	When to use it
Server Members Intent	Member-related server data and events.	Member/player lookup, membership-aware features, or features that need server member information.
Message Content Intent	The content of ordinary messages.	Typed catch answers, prefix/message-based behaviour, or any feature that must read a player’s message.
Presence Intent	Presence/activity updates.	Only for a feature that deliberately uses online/activity state. It is not required for slash commands alone.

Turn an intent on in Discord, save, then turn it on in Kompendium Config and restart. Turning it on in just one place is not enough. Leave privileges off if you do not need them. Discord’s Gateway documentation has the current verification and approval rules.

Installation: invite the bot to a server

Select Installation in the left navigation. You may see Installation Contexts, Install Link, and Default Install Settings in a different visual order, but choose the following values.

Installation context and scopes

Enable Guild Install. Guild is Discord’s name for a server. Choose Discord Provided Link under Install Link. In Guild Install’s default settings add:

bot — adds the bot account to the selected server.
applications.commands — authorizes the app’s slash commands.

User Install is optional and does not replace a server installation for a collectible bot that needs to send messages and make channel spawns.

Bot permissions

Selecting bot reveals the permissions picker. Begin with:

Permission	Reason
View Channels	See configured spawn and command channels.
Send Messages	Send drops, replies, and normal text.
Embed Links	Show rich command and card responses.
Attach Files	Upload card images and generated media.
Read Message History	Work with channel context where needed.
Use Application Commands	Allow slash-command use.

Save, copy the generated install link, open it in a browser, select the test server, and approve. You need sufficient server permissions to add an app. Do not grant Administrator merely because it is quick; add a specific permission only when a feature needs it.

Check the installation inside Discord

Open the target server and find the bot in the member list. Then type / in a channel that it can view and use. Once the Kompendium instance is running and commands are synced, its command groups should appear.

If commands are missing:

Confirm the app was installed to this exact server.
Confirm the selected Kompendium instance has this application’s token.
Use Sync commands in Kompendium Dashboard and wait for the restart.
Check channel permissions and Discord Server Settings → Integrations for the app.

Portal map

You want to…	Go to…	Then do…
Rename or brand the application	General Information	Update the name, icon, and description; save.
Get or replace the bot login secret	Bot	Reset/copy Token; paste it only into the intended instance.
Let the bot read typed catches	Bot	Enable Message Content Intent, then match it in Kompendium Config.
Let member features work	Bot	Enable Server Members Intent, then match it in Kompendium Config.
Make an invite link	Installation	Enable Guild Install; select `bot` and `applications.commands`; choose least permissions.
Change command access for one server	Server Settings → Integrations	Manage the installed app’s command access.

You do not need an Interactions Endpoint URL, OAuth redirect URI, client secret, or custom OAuth flow for the normal hosted Kompendium bot setup. Those are for other kinds of Discord applications.

Continue with Set up a bot from zero or Add your first collectible.