Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/developer51709/Noxie/llms.txt

Use this file to discover all available pages before exploring further.

Before you can run Noxie, you need a Discord bot application with the right settings. This page walks through the Discord Developer Portal from scratch — creating the application, enabling the privileged intents that Noxie requires, setting bot permissions, and generating an invite URL that grants Noxie everything it needs in your server.

Setup Steps

1

Create a new Application

  1. Go to https://discord.com/developers/applications and sign in.
  2. Click New Application in the top-right corner.
  3. Give it a name (e.g. Noxie) and click Create.
You will land on the General Information tab for your new application.
2

Create a Bot user and copy the token

  1. In the left sidebar, click Bot.
  2. Click Add Bot (or Reset Token if a bot already exists) and confirm.
  3. Under the username field, click Copy to copy your bot token.
  4. Paste the token into config.json as the value of bot_token, or set it as the NOXIE_TOKEN environment variable.
Your bot token is a secret. Anyone who has it can control your bot. Never commit it to a public repository. If it is ever exposed, click Reset Token immediately to invalidate the old one.
3

Enable Privileged Gateway Intents

Still on the Bot tab, scroll down to the Privileged Gateway Intents section and enable both of the following:
IntentWhy Noxie needs it
MESSAGE CONTENT INTENTNoxie reads the full text of messages to handle prefix commands such as noxie hunt, noxie donate, and noxie help. Without this, Discord will not deliver message content to the bot.
SERVER MEMBERS INTENTNoxie resolves member information (display names, roles) when building profile displays and awarding badges.
Click Save Changes after enabling both intents.
Without MESSAGE CONTENT INTENT, all prefix commands will silently fail. Noxie will still respond to slash commands, but noxie hunt, noxie inventory, and other prefix-based interactions will not work.
4

Set Bot Permissions

Navigate to OAuth2 → URL Generator in the left sidebar. Under the Permissions section, enable the following:
PermissionWhy it is needed
Send MessagesRequired to send any response at all — hunt results, profile cards, donation flows.
Embed LinksNoxie’s CV2 containers use rich embed-style attachments for mood banners and creature cards.
Attach FilesMood banner images are sent as file attachments alongside CV2 containers.
Use Slash CommandsRequired for all slash commands (/hunt, /donate, /profile, etc.) to be usable in the server.
Read Message HistoryNeeded to fetch and interact with previous messages in certain flows.
These permissions are also visible and adjustable under the Bot → Bot Permissions section.
5

Generate an Invite URL

In OAuth2 → URL Generator:
  1. Under Scopes, check both:
    • bot
    • applications.commands
  2. Under Bot Permissions, check the five permissions listed in the previous step.
  3. Copy the generated URL at the bottom of the page.
The URL will look similar to:
https://discord.com/api/oauth2/authorize?client_id=YOUR_CLIENT_ID&permissions=274877975552&scope=bot%20applications.commands
6

Invite Noxie to your server

  1. Paste the generated invite URL into your browser.
  2. Select the server you want to add Noxie to from the dropdown.
  3. Click Authorize and complete the CAPTCHA if prompted.
Noxie will join the server and, if it has permission to send messages, post a greeting in the first available text channel.

After Inviting Noxie

Once Noxie is in your server, there are two things to be aware of: Slash command propagation. On first start, setup_hook calls await self.tree.sync() to register slash commands globally with Discord. Global commands can take up to one hour to appear in the command menu. They are registered once and persist across restarts.
While waiting for slash commands to propagate, you can test Noxie immediately using prefix commands. The global prefix noxie is always active — try noxie hunt or noxie help right away.
The noxie prefix is permanent. The string noxie (with a trailing space) is a hardcoded global prefix that cannot be removed or overridden, regardless of any custom prefixes added via /prefix add. Administrators can layer additional custom prefixes on top of it.

Build docs developers (and LLMs) love