Discord Bot Setup

Run one bot process per key system to let buyers redeem keys, reset their HWID, open support tickets, and pull their personalized loader — all from your Discord server.

What the bot is

The Discord bot is one of the three clients of your Quark key system. The website hosts the database and API and is the single source of truth; the Windows software and the Discord bot are both clients of it. Anything you change in one place syncs to all three, so a key redeemed through the bot, a HWID reset from the dashboard, and a license edited in the software all describe the same record.

You run one bot process per key system. If you operate several key systems, each one gets its own bot application, its own token, and its own process. The bot does not talk to your buyers' executors — it only talks to the Quark API on their behalf and manages roles, channels, and messages inside your Discord server.

Step 1 — Create the Discord application

Step 2 — Invite the bot to your server

The bot must be invited with the correct scopes and permissions or its commands will not register and it will not be able to grant roles or create ticket channels. Build an invite URL with these two scopes:

• bot — lets it join as a bot user
• applications.commands — lets it register slash commands like /panel and /redeem

And these permissions, which map directly to what its commands do:

• Manage Roles — to grant and remove the buyer role on redeem and whitelist commands
• Manage Channels — to create and close ticket channels under your ticket category
• Send Messages — to post panels, embeds, and replies

You can generate the URL in the Developer Portal under OAuth2 → URL Generator: tick the two scopes, tick the three permissions, then open the resulting link and pick your server. Or build it by hand — replace YOUR_CLIENT_ID with your Application ID:

https://discord.com/oauth2/authorize?client_id=YOUR_CLIENT_ID&scope=bot%20applications.commands&permissions=268435472

Step 3 — Configure the .env file

The bot reads its configuration from a .env file in the bot folder. Create it (copy .env.example if one is provided) and fill in all six values:

BOT_TOKEN=your-bot-token-from-the-bot-tab
CLIENT_ID=your-application-id
GUILD_ID=your-discord-server-id
API_BASE=https://quarkexploits.com
KEY_SYSTEM_ID=your-key-system-id
API_SECRET=the-secret-shown-once-on-key-system-creation

Step 4 — Install and start

The bot is a Node process. From inside the bot folder, install its dependencies once, then start it:

npm install
npm start

On start the bot registers its slash commands, connects to Discord, and locks itself to the server in GUILD_ID. Once it is online you should see its commands appear when you type / in your server. If commands do not show up, confirm the bot was invited with the applications.commands scope and that CLIENT_ID is correct.

Single-server lockdown

The bot is deliberately built to run in exactly one server. It locks itself to the server you set in GUILD_ID, and if it is ever added to any other server it leaves that server automatically. This is a protection: it stops someone who gets hold of your invite link or token from pointing your key system's bot at a different community, and it keeps one bot process tied cleanly to one key system. Do not try to run a single bot across multiple servers — spin up a separate application and process per key system instead.

Hosting the bot

The bot needs to stay running for its commands to work, so it has to live somewhere that keeps a Node process alive around the clock. Running npm start on your own PC works for testing, but the bot goes offline the moment you close it or shut down. For anything real, host it on a platform that keeps the process up:

• Railway — simple to deploy a Node app from a repo, set the six variables in its dashboard
• A VPS — full control; keep it alive with a process manager like pm2 or a systemd service
• Pterodactyl — if you already run a game/bot panel

On any host, set the same six environment variables you put in .env. Never commit the .env file or paste the token/secret into a public place.

Commands

The bot ships with a full command set. The most important ones for a working key system are described below; the rest are listed after.

How the key ones fit together

A typical setup is: run /panel once to post the redeem hub and /ticketpanel once to post the support hub. From there, a buyer uses /redeem (or the panel) to link their key — that binds the key to their Discord account, gives them the buyer role, and hands back a loader personalized to their license. When someone changes machines and hits the HWID lock, /reset clears the bound HWID so it can re-bind on their next run, with a cooldown so it cannot be spammed. HWID can also be reset from the dashboard if you prefer to do it yourself.

Toggling commands auto-syncs

You control which commands are available from the software. When you toggle a command on or off in the Quark software, that change auto-syncs to the bot — because the website is the single source of truth and the bot is just a client of it. You do not need to restart the bot or edit any code to enable or disable a command; flip it in the software and the bot reflects it.