All of Noxie’s runtime settings live in a singleDocumentation 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.
config.json file at the project root. The file is read once at startup via the load_config() helper. You can override the bot token at any point without touching the file by setting the NOXIE_TOKEN environment variable. Everything else must be configured in config.json before starting the bot.
Full example
Field reference
Bot & connection
Your Discord bot token, obtained from the Discord Developer Portal. This value is used to authenticate the bot process with the Discord gateway.Can be overridden at runtime by setting the
NOXIE_TOKEN environment variable — if the env var is present, it takes precedence over this field. If this field is missing or still set to the placeholder value "YOUR_BOT_TOKEN_HERE", the bot will refuse to start.The permanent global command prefix that is always active across every guild, regardless of any per-guild custom prefixes that server admins configure. The trailing space is intentional — commands are invoked as
noxie hunt, not noxiehunt.This prefix cannot be removed or overridden by guild admins. It is always appended to the prefix list returned by prefix_callable.OxaPay (donations)
Your merchant API key from the OxaPay dashboard. This key authenticates crypto invoice creation requests sent by the
/donate command. Without a valid key, donation commands will fail at the invoice creation step.The base URL for the OxaPay REST API. In normal operation this does not need to change. It can be pointed at a staging or mock endpoint during development and testing.
The Discord channel ID (as a string) where completed donation events are logged. Set to
null to disable donation logging entirely. When set, Noxie will post a confirmation message to this channel every time a donation is successfully confirmed by OxaPay.Database
Path to the SQLite database file, relative to the project root. The directory and file are created automatically on first run — you do not need to create them manually. All five tables (
economy, inventory, badges, donations, guild_prefixes) are initialized at startup.Hunt behavior
The per-user, per-guild cooldown in seconds between hunts. After a successful
/hunt or noxie hunt, a user must wait this many seconds before hunting again in the same guild. The cooldown is tracked and enforced by the bot — exceeding it triggers a cooldown response with a sleepy mood banner.CV2 accent colors
These decimal color values are applied to the CV2 container borders rendered in hunt result messages. Each rarity has its own accent color so players get an immediate visual signal of what they caught.Decimal accent color for Common hunt CV2 containers. The default value
7930727 corresponds to #790367 (a deep purple). Applied to all hunts that do not match a higher rarity.Decimal accent color for Rare hunt containers. Default:
16766720 → #FFD700 (gold).Decimal accent color for Epic hunt containers. Default:
10027263 → #9900FF (vivid purple).Decimal accent color for Legendary hunt containers. Default:
16744272 → #FF7F50 (coral orange).Decimal accent color for Mythic hunt containers. Default:
16711782 → #FF0066 (hot pink). Mythic hunts also trigger the evil mood banner.Economy
The base Glow Shard reward range for a Common rarity hunt, expressed as a two-element array
[min, max]. The bot picks a random integer in this range and awards it to the hunter’s balance. Rarity multipliers are applied on top of this base range for higher rarities.The base Vibe Coin reward range for a Common rarity hunt, expressed as a two-element array
[min, max]. Vibe Coins are rarer than Glow Shards and serve as the premium currency tier. Rarity multipliers scale this range upward for Uncommon through Mythic hunts.The number of Glow Shards awarded per 5 donation awards 2,500 Glow Shards.
The number of Vibe Coins awarded per 5 donation awards 250 Vibe Coins.
Environment variable
The bot token can be supplied via theNOXIE_TOKEN environment variable instead of storing it in config.json. When the variable is set, it takes precedence over the bot_token field in the config file.
The rarity multipliers that scale Glow Shard and Vibe Coin rewards above the Common base range are defined in the hunt system, not in
config.json. The values in economy.glow_shards_per_hunt and economy.vibe_coins_per_hunt represent the Common baseline only. See the Economy documentation for the full per-rarity reward table.