document privileged intents and dev mode in the bot readme

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
leanderandClaude Opus 5.5 committed 2026-11-03 01:58:45 +01:00
1 parent 75a1524f0e
commit ec27820f64
1 file changed
+5 -1
+5 -1
View File
@@ -4,12 +4,16 @@ A multi-purpose Discord bot for the Discord server of The Norwegian Student Soci
## Get started
0. Create a bot user / obtain a bot token. [See this guide](https://discordpy.readthedocs.io/en/stable/discord.html)
0. Create a bot user / obtain a bot token. [See this guide](https://discordpy.readthedocs.io/en/stable/discord.html). Also enable all three _Privileged Gateway Intents_ (Presence, Server Members and Message Content) under "Bot" in the Developer Portal. The bot requests all intents and won't start without them
1. Make a copy of the `.env.example` file and rename it to `.env`
2. Make sure all the fields are filled
`BOT_CONFIG_MODE` decides where the slash commands are synced. With `dev` they're only synced to the server in `BOT_DEV_GUILD`, where they show up right away. With `prod` they're synced globally. In both modes, `BOT_DEV_GUILD` is also the server where the bot assigns Galtinn roles.
Use a separate bot user when developing locally. If you run `dev` with the production bot's token, the server in `BOT_DEV_GUILD` gets both the global commands and the copies, and every command shows up twice. The bot logs a warning when that happens. In `prod`, commands left in `BOT_DEV_GUILD` from earlier `dev` runs are removed automatically.
Given a user with a access to a database the bot will create all the necessary tables by itself.
You have two options to run the bot: