Description: Create a new named queue for this server.

Usage: /queue_create queue_key:<key> display_name:<Name> [log_channel:#channel] [description:text]

Example: /queue_create queue_key:commissions display_name:"Art Commissions" log_channel:#queue-logs

Permissions: Manage Guild or Bot Owner

Extra Info
  • queue_key is a short codename that must be unique per server, for example support, art, bots.
  • display_name is what users see in panels, for example "Art Commissions Queue".
  • log_channel is optional. If set, admin actions and notes log there.
  • description shows under the queue title in panels.

Description: Set or clear the log channel for a queue.

Usage: /queue_setlog queue_key:<key> log_channel:#channel-or-none

Example: /queue_setlog queue_key:commissions log_channel:#queue-logs

Permissions: Manage Guild or Bot Owner

Extra Info
  • Passing a channel sets the log channel for this queue only.
  • Passing "none" (or clearing the option in the UI) removes the per-queue log channel.
  • Logs include joins, claims, done, moves, clears, and admin notes.

Description: List all queues configured in this server.

Usage: /queue_list

Example: /queue_list

Permissions: Manage Guild or Bot Owner

Extra Info
  • Shows queue key, display name, active/paused state, and log channel for each queue.
  • Archived queues are hidden from this list.

Description: Permanently delete a queue and its entries.

Usage: /queue_delete queue_key:<key> confirm:true|false

Example: /queue_delete queue_key:oldqueue confirm:true

Permissions: Manage Guild or Bot Owner

Extra Info
  • Requires confirm:true to actually delete anything.
  • History events are kept for stats, but the queue and its panels are removed.
  • Use this for queues you no longer plan to use.

Description: Preview the queue panel layout before posting it.

Usage: /queue_panel_preview queue_key:<key> panel_type:public|admin [max_visible:1-20]

Example: /queue_panel_preview queue_key:commissions panel_type:public max_visible:5

Permissions: Manage Guild or Bot Owner

Extra Info
  • Reply is ephemeral so only you see the preview.
  • panel_type:public is the user-facing view.
  • panel_type:admin shows admin-only buttons such as claim, done, remove, move, and pause/resume.

Description: Post a live, auto-updating queue panel to a channel.

Usage: /queue_panel_post queue_key:<key> panel_type:public|admin [channel:#channel] [max_visible:1-20]

Example: /queue_panel_post queue_key:commissions panel_type:public channel:#commissions

Permissions: Manage Guild or Bot Owner

Extra Info
  • If no channel is specified, posts in the channel where you ran the command.
  • When you post a new panel of the same type in a channel, older panels in that channel for that queue are marked inactive and removed.
  • Panels survive bot restarts using stored message IDs in the database.

Description: Post or refresh an admin-focused panel for quick management.

Usage: /queue_adminpanel queue_key:<key> [channel:#channel]

Example: /queue_adminpanel queue_key:commissions channel:#commission-staff

Permissions: Manage Guild or Bot Owner

Extra Info
  • Admin panel includes buttons for claim, next, done, remove, move, and pause/resume.
  • Shows a "Currently working on" section and a short "Up next" list.
  • Not visible to regular users if placed in a staff-only channel.

Description: Add a user to a queue with optional description and position.

Usage: /queue_add queue_key:<key> user:@User [description:text] [queueorder:number]

Example: /queue_add queue_key:commissions user:@Bean description:"Logo art" queueorder:1

Permissions: Staff only (you configure who can use this)

Extra Info
  • Users do not add themselves. Staff add entries manually.
  • If queueorder is omitted or invalid, the user goes to the end of the queue.
  • Use queueorder for priority cases (for example paid rush).

Description: Pull the next waiting user in a queue to "Currently working on".

Usage: /queue_next queue_key:<key>

Example: /queue_next queue_key:commissions

Permissions: Staff only

Extra Info
  • Automatically picks the first waiting entry, marks it as working, and updates the "Currently working on" field.
  • The user is removed from the visible "Up next" list.

Description: Claim a specific entry, optionally moving it into your own queue.

Usage: /queue_claim queue_key:<source> entry_id:<id> [target_queue_key:<key>] [note:text]

Example: /queue_claim queue_key:commissions entry_id:42 target_queue_key:commissions note:"Taking this one"

Permissions: Staff only

Extra Info
  • If target_queue_key is omitted or matches the source, it just claims in-place.
  • If target_queue_key is different, the entry is transferred to that queue and claimed there.
  • Good for multi-creator setups where each staff member has their own queue key.

Description: Mark a claimed entry as completed and record timing stats.

Usage: /queue_done queue_key:<key> entry_id:<id> [note:text]

Example: /queue_done queue_key:commissions entry_id:42 note:"Delivered via DMs"

Permissions: Staff only

Extra Info
  • Calculates wait time and handle time and stores them in the database.
  • Entry status becomes done and it no longer appears in the main queue list.

Description: Remove an entry from the queue with an optional log note.

Usage: /queue_remove queue_key:<key> entry_id:<id> [note:text]

Example: /queue_remove queue_key:commissions entry_id:18 note:"User cancelled"

Permissions: Staff only

Extra Info
  • Entry is deleted from the queue and positions are compacted.
  • Note is sent to the queue log channel so staff know why it was removed.

Description: Move an entry to a new position in the same queue.

Usage: /queue_move queue_key:<key> entry_id:<id> new_position:<number> [note:text]

Example: /queue_move queue_key:commissions entry_id:18 new_position:1 note:"Priority client"

Permissions: Staff only

Extra Info
  • Only works on waiting or working entries.
  • Other entries are shifted up or down to keep positions 1..N.

Description: Bulk clear entries in a queue based on scope.

Usage: /queue_clear queue_key:<key> scope:waiting|all [note:text]

Example: /queue_clear queue_key:commissions scope:waiting note:"Resetting queue for next month"

Permissions: Manage Guild or Bot Owner

Extra Info
  • scope:waiting cancels all waiting entries.
  • scope:all cancels waiting and working entries.
  • Completed work (done) stays in history for stats.

Description: Pause a queue so new work is not taken.

Usage: /queue_pause queue_key:<key> [note:text]

Example: /queue_pause queue_key:commissions note:"Closed for the weekend"

Permissions: Manage Guild or Bot Owner

Description: Resume a paused queue.

Usage: /queue_resume queue_key:<key> [note:text]

Example: /queue_resume queue_key:commissions note:"Reopened"

Permissions: Manage Guild or Bot Owner

Description: Show recent stats for a queue based on stored history.

Usage: /queue_stats queue_key:<key> [days:1-90]

Example: /queue_stats queue_key:commissions days:30

Permissions: Staff only (recommended) or Manage Guild

Extra Info
  • Includes completed count, average wait time, and average handle time for the window.
  • Uses the data that is recorded whenever you mark entries done.
  • Results can be posted ephemerally or publicly depending on your preference.

Use one shared queue_key (for example commissions) and let each staff member use /queue_next or /queue_claim. The bot tracks who claimed each entry and shows it in logs and stats.

Whenever an entry is claimed or taken with /queue_next, that user is shown in the top section of the panel as the active work item, and they are removed from the "Up next" list below.

  • Every join, claim, completion, move, clear, and transfer is stored.
  • Entries track wait time and handle time so you can see how long things sit and how long they take.
  • When the bot leaves a server, queues are archived instead of being hard deleted so stats are preserved.