Manage a Minecraft Bedrock Whitelist From Discord

Before you start

• A running Minecraft Bedrock server on Pterodactyl, with whitelist enforcement configured on that server.
• A Pterodactyl panel URL, server identifier and Client API key with websocket.connect and control.console permissions for that server.
• A connected Discord bot with Game Server enabled, a live status channel and selected whitelist manager roles.
• For member requests, a configured console channel hidden from @everyone and a designated approver role with access to that channel.

1. Connect the running Bedrock server

   Create your account through the sign-up link, connect your bot and enable Game Server in Modules. Open Settings for your Discord server. Enter the Pterodactyl panel URL, Client API key and server identifier. Keep the key in the settings field rather than posting it in Discord.

   Enable the live panel and choose its status channel. Save the settings and use Test connection to check the saved connection. Whitelist commands require that live panel configuration, an authenticated connection and a running server. This guide configures access management for an existing Bedrock server; it does not create or host the Minecraft server.

2. Choose managers and optional request approvers

   Enable whitelist commands in Game Server settings and enter the Discord role IDs allowed to add, remove and list entries. These commands check the selected roles; Discord Administrator or the module’s separate power-control admin roles are not an automatic bypass. Do not use @everyone as a whitelist manager role.

   If members should ask for access, enable whitelist requests and set an approver role. Configure a console channel hidden from @everyone, with access for the bot and your approvers. Request buttons appear there. A console channel visible to @everyone or a thread is rejected. When a console channel is configured, direct commands also check that it is private.

3. Add, remove and list Bedrock gamertags

   Use /whitelist add with the gamertag option from an account holding an allowed role. Enter a classic Bedrock gamertag, not a Java username or a modern display name with a #suffix. The accepted format is 1 to 15 ASCII characters, beginning with a letter; letters, digits, commas and single spaces are allowed, with no trailing or repeated spaces.

   Review the confirmation and select Confirm to submit the whitelist addition, or Cancel to stop. The confirmation belongs to the person who requested it and expires after one minute. Use /whitelist remove with the gamertag option for removal; it uses the same confirmation flow.

   Use /whitelist list to request the current list from the server console. The bot displays recognized whitelist output, not arbitrary console logs. If no recognized response arrives within eight seconds, it reports the timeout and asks you to inspect the panel console. It does not show a cached list.

4. Review member access requests

   With requests enabled, a member can choose /whitelist request and enter a gamertag. The bot posts a request with Approve and Deny buttons in the private console channel. The request does not verify that the requester owns the named Minecraft account; your approver must assess it.

   Only a member holding the configured approver role can approve or deny that request. Approval submits a whitelist add command; denial does not add the gamertag. The request expires after ten minutes. After a decision, the bot closes the request buttons and records an audit entry.

   Pending requests and confirmations are held in memory. A bot restart invalidates the old buttons, and relevant connection or role-setting changes can also expire them. Ask the member to submit a fresh request if the previous one is no longer valid.

5. Read failures and verify the result

   A disabled response means the whitelist/live-panel configuration is incomplete or unavailable for that Discord server. A denied response points to the selected roles or request settings. An offline response means the server is not running; a connection response means the authenticated connection is unavailable. Fix the indicated issue before retrying.

   Commands are rate limited, and a member cannot stack multiple pending actions. If you get a rate-limit or pending-action reply, wait or finish the existing action. A private-channel failure requires checking console-channel access. After an uncertain send, inspect the panel console before submitting the same change again.

   Test with a gamertag you control, check the resulting server list and verify your server’s whitelist enforcement. The module sends individual commands; it does not enable server-side enforcement, synchronize Discord roles into the whitelist, or provide a Java whitelist connection.