DOCUMENTATION · v1.4.0

QBoty documentation.

A simple guide to the current QBoty bot, based on the v1.4.0 project documentation.

Quick start

Invite QBoty with the official link, then use !help to browse its interactive guide. Administrators can run !setup to configure the Queue Management and Ticket Support modules.

QBoty uses interactive Discord components for most actions. The configured bot command prefix defaults to !, but server deployment may change it using BOT_PREFIX.

Command reference

CommandPurposeAccess
!helpInteractive help menuEveryone
!queueQueue Hub in current channelEveryone; management actions restricted
!ticketSupport tickets or ticket administrationEveryone; admin settings restricted
!setupServer modulesOwner or Manage Server
!embedAnnouncement StudioOwner or Administrator

Legacy action commands such as !join, !next and !ticketsetup are intentionally retired. Use Discord buttons and menus instead.

Multi-Queue Hub

Run !queue in the desired text channel. QBoty posts one shared Queue Hub for that channel; subsequent uses refresh or link to the existing hub.

  1. An administrator creates a uniquely named active queue in the channel.
  2. Choose an optional queue host and whether Auto Counts should be enabled.
  3. Members select the relevant queue from the hub and use its controls to join or leave.
  4. The host or administrator can use Next, Done, Skip, Lock/Unlock, Manage Players and settings controls.

For more than 25 active queues in one channel, the hub offers a Browse All flow.

Auto Counts

Auto Counts is optional for each queue. When enabled, completed queue turns can create a record and an embed in a designated counts channel. The first Next calls the first player; later Next actions complete the previous player before calling another.

Important: Auto Counts tracks completed turns, not verified RuneScape boss kills. Skip, Remove, Leave and Close are not completion events.

Support Tickets

Members can open tickets using !ticket or a published Support Center panel. Administrators use !ticket to choose staff roles, ticket category and transcript destination, preview the panel, and publish it.

Current supported ticket types: Report, Staff, Creator and Other. Ticket staff can claim tickets and manage member access. Closing a ticket requires confirmation and delivery of the HTML transcript to the configured log channel before deletion.

Members may have at most one active ticket per server.

Announcement Studio

Server owner or administrators use !embed, then select Create Announcement → Write Content → destination channel → Preview → Publish Announcement. The preview is private to its editor.

Server Settings

Use !setup to independently enable or disable Queue Management and Ticket Support for a server. QBoty uses guild-specific MongoDB records, allowing different Discord servers to keep separate configurations.

Support tickets already opened can still be closed after new Ticket Support is disabled in settings.

Need help? Visit the official community link when one has been configured by the website owner.