Set up Utilities Bot

You control this installation. The bot needs your own Discord application, server, host, token and private configuration. The base package sends TXT ticket transcripts; voice recording and an HTML transcript website are separate add-ons.

1. Create the Discord application

  1. In the Discord Developer Portal, create an application and bot. Copy the Application ID and the bot token. Do not share the token.
  2. Enable Server Members Intent and Message Content Intent on the bot page. The latter is required for owner prefix commands and automod.
  3. Invite your bot to the server for this installation with the bot and applications.commands scopes. Give it the Administrator permission (permission value 8) so every feature works. Put its highest role above any role it must grant or remove.
  4. Copy the server ID and your own user ID using Discord Developer Mode. The application ID, server ID and owner IDs are Discord snowflakes: 17–20 digit numbers.

2. Prepare the host

Use Node.js 22 or newer with persistent storage. From the package directory:

npm ci
npm run setup

The setup helper creates config.json, .env and data/ only if missing. Edit config.json using the configuration reference. Put only the bot token in .env:

DISCORD_TOKEN=

Set file permissions to 0600 for .env, config.json and license.json. They are ignored by Git. Do not upload them with public code or send your Discord token to the seller.

Provide your first Application ID and server ID in the private delivery step so the package can be checked with a working example configuration. Put the delivered license.json in the package root. The licence identifies you and the purchased features; additional servers you own or manage do not need registration or a new licence. For each additional installation, make a separate private copy of the package with its own config.json, .env bot token and SQLite data. Run npm run deploy and npm start for that copy. Never publish the source or share it with another server operator.

3. Validate, deploy and start

npm run check
npm run verify
npm run deploy
npm start

check tests the package without Discord calls. verify checks your private config, token and signed licence. deploy registers slash commands only in the configured server. start logs the bot into Discord. Keep it running using a process manager or service supervisor. The bot will refuse to start if its token, configuration or signed licence is missing or invalid.

The first start is owner-only setup mode. Use ,status to check channels and ,panel to post a ticket panel. Configure automod, quarantine and staff positions before opening the bot to the team. After testing with a non-owner account, use ,lockdown off to let configured moderators and administrators use their commands. Ticket opening and /report remain available while the setup lock is on.

4. Check each feature

  1. Use /help and /perm status to confirm the bot loaded and your owner ID is recognised. For permission requests, configure a private approval channel and test /perm select group:Moderation command:warn with a non-owner account; approve it as an owner, then test /perm remove.
  2. In a channel chosen for support, use ,panel. Open a ticket as a non-owner, send messages, and close it as a handler with /ticket close. Confirm the private ticket log receives a .txt file and the opener receives a copy by DM. channels.ticketLog is required before closure.
  3. Test /warn and /case with a consenting test member; verify the moderation log. A failed Discord action must not be reported as a successful case.
  4. Test /report and confirm it reaches the private report channel. If that channel is unavailable, the bot saves the report and tells the reporter that delivery failed.
  5. Set automod.logChannel, review automod rules, and use ,automod test MESSAGE. It starts in watch: check the private log before turning it on in config and restarting. Test safe GIF links, ordinary external links, a configured scam host, mention spam and a blocked file with controlled messages.
  6. If you want quarantine, configure its role and room, run /quarantine setup and test hold/release with a consenting member. If you want staff applications, configure the review channel, questions and position roles, run npm run deploy, and test an application and appointment. See Staff applications and records.
  7. Set the colours in appearance if you want a different embed palette. Test a ticket panel, welcome post, reaction-role panel, giveaway and announcement in controlled channels. Existing giveaway messages from this bot are refreshed as embeds when it starts; the bot cannot edit messages written by another bot.

5. Backups and operation

The bot stores records in data/bot.db by default and makes daily SQLite snapshots under data/backups/. Backups on the same host do not protect against losing that host; copy encrypted snapshots to storage you control and test a restore. Keep ticket logs private because they contain TXT transcripts. Review the process log after Discord or dependency upgrades.

Automod is configurable and can delete, warn, timeout, quarantine, kick or ban according to your rules and strike ladder. It starts in watch so you can review verdicts before enabling actions. An unknown link alone is not proof of a scam. Keep false-positive risk in mind when changing brandHosts, blocked words or severe actions.