Tier Testing Bot

The Tier Testing Bot manages player verification, evaluation waitlists, and regional testing queues inside Discord for Minecraft communities.

About

This bot is designed to streamline the tier evaluation process for Minecraft servers. It handles player verification, regional queue management, tester coordination, cooldown enforcement, and tier-based queue priority — all through Discord.

Main Features

• Account verification via username validation.
• Automatic region-based waitlists and role assignments.
• Dynamic player testing queues managed by staff/testers.
• Cooldown and queue tracking to prevent rejoining too early.
• DM notifications for players when status or position changes.
• Automatic persistence — queues and states are restored after bot restarts.

1. For Server Admins / Setup Managers

These users configure and maintain how the bot operates within Discord.

/waitlist

• Creates the main Evaluation Testing Waitlist embed in a selected channel.
• Displays buttons: Verify Account and Enter Waitlist.
• Used by players to begin their verification and queue entry process.

/help

• Lists every available command and description.
• Visible only to staff, testers, or owners with proper permissions.

/forcecooldown [user] [reason]

• Manually applies a cooldown to a player, blocking them from rejoining the waitlist for a duration.
• Logs this action in the configured audit log channel.

/username [user]

• Retrieves a user’s verified Minecraft username.
• Used to confirm identity or check verification status.

2. For Testers

Testers are staff members responsible for running and managing evaluation queues.

/start

• Opens a testing queue in the regional queue channel (EU, NA, AS, AU, etc.).
• Marks the tester as “online.”
• Displays an embed showing:
  • Current players in queue
  • Active testers
• Pings users to notify them that a new queue is available.
• If a queue already exists, adds the tester to it instead of reopening it.

/stop

• Ends a queue for the executing tester.
• If other testers remain, the queue stays open and updates accordingly.
• If no testers remain, the queue closes and shows a red “No Testers Online” message with a timestamp.

/equeue

• Forcefully stops and clears the queue in that channel.
• Removes all users from memory and updates the message to “No Testers Online.”

/skip

• Removes the first player in the queue (next in line).
• Sends them a DM notifying that they were skipped.
• Automatically updates the queue display afterward.

/addtester [user]

• Adds another user as an active tester to the current queue (requires regulating officer permissions).

/remove [user]

• Removes a tester from the current queue manually.

/leave

• Removes you (tester or player) from all queues you are currently in.
• Useful if you accidentally stay registered in multiple queue channels.

/testing-status

• Displays active queues across all regions with their current tester count and player lists.

3. For Players / Applicants

These users are being evaluated for placement into specific tiers.

Step 1: Verify Your Account

• Click Verify Account on the waitlist embed.
• A popup form appears where you enter your Minecraft Username.
• The bot checks if the account is valid.
• If valid, you receive a success embed confirming verification.

Step 2: Join the Waitlist

• Click Enter Waitlist after verifying your account.
• Fill out a form selecting your:
  • Region (EU, NA, AS, AU)
  • Preferred Server
• After submission:
  • You’re added to the active waitlist.
  • The bot assigns your regional role automatically.
  • You’ll be notified when it’s your turn.
• If you have a High Test Role (HT1–HT3), you skip the queue and a private High Test Ticket opens automatically.

Leaving the Waitlist

• Click the Leave Waitlist button to withdraw.
• The bot removes you from the list and revokes related roles.

4. Queue System Summary

The queue system connects testers and verified players in regional channels.

• When testers start a queue with /start, a queue embed is created.
• Players click Join Queue to enter.
• Player positions update automatically.
• The bot DMs players when:
  • Their position changes
  • They are skipped
  • They leave the queue
• Clicking Leave Queue removes the player instantly.
• If the queue is full (default 20 users), new joins are prevented.

5. Automatic Features

• Cooldowns: Players must wait between tests. Duration varies by role type (e.g., boosters, high testers, or regular users).
• Region Roles: Assigned automatically based on user’s selected region.
• DM Notifications: Players receive DMs for position updates, skips, or queue removals.
• Queue Persistence: Queues remain active even if the bot restarts, ensuring continuity.

Quick Role-Based Overview

Important Notes

• All management happens entirely within Discord — no external dashboard required.
• Commands and buttons are permission-locked by role hierarchy.
• Queue size defaults to 20 players per region (configurable in the bot settings).
• Audit logs automatically track cooldowns, skips, and queue management events.