Discord Panel Bot

Most Discord bots for Pterodactyl are separate programs: you need another server, Node.js, a config file with an API key, and something that keeps the bot running. Discord Panel Bot runs inside your panel. Discord sends every slash command to the panel over HTTPS, the panel checks Discord's signature and answers. Nothing to host, nothing to keep alive.

For your users

• /link connects their Discord account: the bot sends a link, they sign in on the panel and confirm
• /servers lists their servers with state, RAM and CPU
• /server shows one server: state, address, node, CPU, memory, disk, uptime, with Start, Restart, Stop, Kill and Refresh buttons
• /power start, restart, stop or kill
• /command sends a console command
• /backup list and /backup create
• /watch sends a direct message when a server stops, crashes or comes back
• Server names autocomplete while typing; answers are only visible to the user

For you

• Status board: one message in a channel, updated every minute, with your nodes and up to 25 servers (e.g. a public server status)
• Node alerts: a message to your team channel when Wings on a node stops answering, and when it's back
• /nodes: Wings status, servers and allocated RAM and disk per node
• Turn console commands or backups from Discord off, limit watches per user, see and disconnect linked accounts

Safe

• Every request is checked against your Discord application's public key; unsigned requests are refused
• The bot follows the panel's permissions: subusers can only do what their permissions allow, buttons only appear when they may press them
• Linking is confirmed on the panel, with links that work once and expire after 15 minutes
• Actions show up in the server's activity log, marked "via Discord"
• The bot token is stored encrypted; the bot only needs to view channels, send messages and embed links
• Server names are escaped, so nobody can ping @everyone with a server name

Setup

The admin page walks you through it: create a Discord application, paste three values, set the interactions URL, invite the bot, register the commands. About five minutes.

A Blueprint extension that lets your users control their Pterodactyl servers from Discord: status, start and stop, console commands, backups, and a direct message when a server crashes. Admins get a node overview, alerts when a node goes down, and a status board that keeps itself up to date.

No extra hosting. Most Discord bots for Pterodactyl are separate programs that need their own server, Node.js and an API key in a config file. This one runs inside the panel: Discord sends every command to the panel over HTTPS, the panel checks the signature and answers. There is no process to keep alive and nothing to update apart from the extension.

What users can do

• Server names autocomplete while typing, only the user's own servers are suggested.
• Answers are only visible to the user who ran the command.
• Buttons only appear when the user may press them; pressing one checks the permission again.
• The bot sees exactly what the user sees on the panel: own servers and servers they are a subuser of, with the subuser permissions set there.
• Power actions, console commands and backups appear in the server's activity log with "via Discord".

What admins get

• Status board: one message in a channel of your choice, updated every minute, with the nodes and up to 25 servers you choose (name, address, state, uptime). Good for a public "server status" channel.
• Node alerts: a message in a team channel when Wings on a node stops answering, and when it is back.
• Settings: turn console commands and backups from Discord off, limit how many servers one user may watch, or turn the bot off entirely.
• Connected accounts: see who connected which Discord account, and disconnect any of them.

Requirements

• Pterodactyl Panel 1.15.x (tested on 1.15.1)
• Blueprint beta-2026-08 or newer
• The panel reachable over HTTPS from the internet (Discord only sends commands to HTTPS)
• The panel's scheduler cron job (part of every Pterodactyl install) for the status board, node alerts and watch messages
• PHP with the sodium extension (included in PHP 7.2 and newer)

Installation

Upload texuspanelbot.blueprint to your panel directory (normally /var/www/pterodactyl) and run:

cd /var/www/pterodactyl
blueprint -install texuspanelbot

Then open Admin > Extensions > Discord Panel Bot. The page walks you through the setup:

1. Create a Discord application in the Developer Portal (New Application). Its name and icon are what your users see.
2. Enter the Application ID and Public Key (page General Information) and the bot token (page Bot, Reset Token). The panel checks them with Discord before saving; the token is stored encrypted with the panel's app key. No privileged intents are needed.
3. Set the Interactions Endpoint URL on General Information to the address shown on the admin page, e.g. https://panel.example.com/extensions/texuspanelbot/interactions. Discord tests it right away; it is accepted once step 2 is done.
4. Invite the bot with the link on the admin page. It only asks for: view channels, send messages, embed links, read message history.
5. Register the commands. With your Discord server ID they appear there instantly; without one they are registered globally, which can take up to an hour the first time. Register again after turning console commands or backups on or off.

Users then type /link in Discord, open the link, sign in on the panel and confirm.

Security

• Every request from Discord is checked against your application's public key (Ed25519), and old timestamps are refused. Requests without a valid signature get "401 invalid request signature", as Discord requires.
• Linking needs the user to be signed in on the panel and to confirm. Links are random, work once and expire after 15 minutes. One Discord account belongs to one panel account.
• Every action checks the panel's own permissions at the moment it runs, including suspended servers and servers that are being installed or transferred.
• The bot token never leaves the server; it is stored encrypted and only sent to Discord.
• Names from users are escaped, so a server called @everyone can't ping anyone.

Troubleshooting

Removing

blueprint -remove texuspanelbot

Remove the Interactions Endpoint URL in the Developer Portal as well, or delete the application. Blueprint leaves the extension's tables (panelbot_links, panelbot_codes, panelbot_watches) in the database; drop them if you don't plan to reinstall.

0.1.2 (2026-10-11)

• The update notice also works in the package from the licence site and the marketplaces; in the previous version it stayed hidden there.

0.1.1 (2026-10-11)

• Update notice: when a newer version is out, Admin > Extensions and the licence box on the admin page show it, with what is new. With the optional update helper (set up once as root), the update runs with one click after a backup of the panel files and the database.

0.1.0

• First release: slash commands for servers, status, power, console, backups and watches, node overview for admins, status board and node alerts, account linking through the panel.