Community & Contributions
Beyond support, QBXWatcher runs the parts of the QuickBox.IO Discord server that welcome new members and collect what you want built next.
The onboarding quest
New members are walked through a short two-stage quest. It exists so you leave knowing the commands you will actually use — and, if you own a QuickBox Pro licence, verified.
Stage 1 — the vault
In the vault channel, type the passphrase the bot shows you: i seek the vault
Stage 2 — training grounds
Run any three commands from the training list — or verify, which finishes the quest outright
The passphrase is recognised in every supported language, so you can complete stage 1 in your own.
Suggested commands for stage 2 — any three count:
/verify-status
/version
/roll
/onboarding-progress
/leaderboard
/lore
/changelogCheck where you are at any time:
/onboarding-progressThe reply shows how many commands you have run, which ones counted, and what to try next.
Valid commands you run in the training grounds are removed a few seconds later so the channel stays readable for the next person. Your progress is already recorded by then.
Stage 2 completes on its own once you have run three commands from the list above. But if you own a QuickBox Pro licence, finishing / closes the whole quest out on the spot — there is nothing left to run. Whether the other verification route does the same depends on how you used it, so / is the reliable check. See Verifying Your License for the detail.
How the bot reaches you
Early in onboarding QBXWatcher asks whether account help should arrive by DM or in the channel where you mentioned it. Change your answer at any time with:
/user-preferenceThe same command manages your saved QuickBox servers.
Achievements and leaderboards
Taking part unlocks achievements. They are recognition only — they do not affect your licence, your subscription, or your support priority.
| Achievement | How you earn it |
|---|---|
| Vault Unlocked | You gained access to the vault |
| Training Complete | You completed the onboarding training |
| First Nudge | You were pinged during onboarding |
| DM Champion | You responded in DMs like a pro |
| Escalated Insight | You triggered a complex fallback and a moderator escalation |
| Jackett Helper | You used the Jackett help command |
| First Solve | You solved your first Reel Riddle |
| Riddle Regular | You solved 10 Reel Riddles |
| Sharp Eye | You solved a Reel Riddle on the very first clue |
| On a Roll | You solved 5 Reel Riddles in a row |
/leaderboard
/leaderboard category:commandsWith no category you get the overview. The categories are:
| Category | Ranks by |
|---|---|
| Dice Rolls | Results from / |
| Pings | Ping activity |
| Mentions | How often other members mention you |
| Commands Used | Total bot commands run |
| Onboarding | Onboarding progress |
| Reel Riddle | Score, solves, first-clue solves, and best streak in the guess-the-title game |
Lore and dice
/lore
/lore topic:list
/lore topic:random
/roll
/roll opponent:@member/ opens the QuickBox codex — the project’s history and running jokes. / rolls a d20; tag an opponent to duel them.
Community guides
Members with the guide-creator role can publish guides to the server’s guides forum. QBXWatcher handles the drafting workflow.
| Step | What happens |
|---|---|
/ | Apply for the guide-creator role. Staff review the application |
/ | Opens a form for a title and summary, then creates your draft thread in the drafts forum |
Upload your .md | Drop a Markdown file into the draft thread and QBXWatcher lays it out across the thread for you |
| Revise | Re-upload a corrected file to refresh the layout — the previous version stays above for reference |
/ | Tags the draft as Ready and notifies staff. Add reviewer notes with the optional notes option |
| Staff review | A moderator publishes the guide or sends it back with requested changes. Published guides are attributed to you |
Other guide creators can read your draft thread and offer feedback before it goes to staff.
Writing the file
/ asks for two things — a title (up to 100 characters) and a summary (up to 500). Everything else lives in the Markdown file you upload into the draft thread afterwards.
| Rule | Detail |
|---|---|
| File type | .md or .markdown only — other attachments are ignored |
| Size limit | 100 KB. A larger file is rejected with a message rather than silently dropped |
| Where to drop it | Straight into your own draft thread. You can upload at any point after the draft exists |
| Revising | Upload a corrected file and the layout is rebuilt. The earlier version stays above it for reference until the guide is published |
Guides are rendered as Discord messages, so write for Discord rather than for GitHub:
Do
- Use
#and##headers — two levels is plenty - Use
**bold**,*italic*and~~strikethrough~~ - Fence code blocks with triple backticks, and give them a language
- Use
-or*for lists, indenting sub-points by two spaces - Break sections with a struck-through rule, since Discord has no horizontal line
Don't
- Do not use Markdown tables — Discord does not render them
- Do not use raw HTML such as
<br>or<span> - Do not nest headers more than two levels deep
- Do not paste an entire config file — link to it or trim to the relevant lines
What publishing does
When a moderator publishes your draft, QBXWatcher creates a fresh thread in the public guides forum and moves the rendered guide into it. There is no window you have to be online for and nothing you need to post yourself — the bot already holds the laid-out version from your upload, and it carries it across in one step. Your byline goes on the published thread.
Once the draft is tagged Ready, the rest is staff-side. You will be notified when it is published, or told what to change if it comes back.
Beta Squad
The Beta Squad runs pre-release QuickBox Pro builds and reports back. It is open to verified members.
/beta-apply
/beta-view
/beta-remove/ opens a private form asking for your API key, the IP of the server you have activated, and any optional notes. Applications are reviewed by staff. Applications are rate-limited — if you apply again too quickly the bot tells you how long to wait.
/ lists your current Beta Squad installations and / unlinks one. Both accept an optional user option, which is restricted to staff reviewing someone else’s enrolment.
Beta Squad installations run code that has not completed release verification. Do not enrol a server you depend on.
Telling us what to build
Three commands feed the QuickBox Pro backlog. Each opens a short guided wizard and returns a reference ID you can quote later.
/feature-request submit
Title, category, the problem you are solving, your proposed solution, who benefits, and optional success criteria
/bug-report submit
Category, severity, summary, steps to reproduce, expected and actual behaviour, OS version, and optional logs
/app-suggestion submit
App name, project URL, category, why it fits QuickBox, install method and complexity, licensing, and subdomain or subpath
/feature-request list
Browse open requests sorted by votes, newest, or recently updated
Browsing what is already requested
/feature-request list
/feature-request list sort:newest page:2
/feature-request view id:<id>
/feature-request status status:in_progress| Subcommand | What it does |
|---|---|
| list | Paginated list of open requests. sort takes votes (default), newest or updated; page takes a page number |
| view | Full detail for one request. Pass the id shown in the list |
| status | Filter by state — open, planned, in_progress, completed or closed — with the same sort and page options |
| submit | Opens the two-step submission wizard |
| mine | Points you at the Account Portal — per-account filtering is not available in Discord yet |
| upvote | Points you at the Account Portal — voting happens in the portal |
Browsing and submitting work in Discord. Upvoting a request, and seeing the ones tied to your account, are done in the Account Portal at quickbox.io.
Each of the three flows is rate-limited to one submission every six hours. A part-finished wizard is kept for 30 minutes, so you can step away mid-form and come back — after that the draft is discarded and you start again.
Best practices
Do
- Search
/before submitting — an existing request is worth a vote more than a duplicatefeature- request list - Include the exact command, the error text, and your OS version in a bug report
- Quote the reference ID from your submission when following up in a thread
- Read the formatting guidelines before uploading a guide draft
- Use
/to choose whether account help arrives by DM or in-channeluser- preference
Don't
- Do not file a bug report for a support question — open a support thread instead
- Do not put several unrelated ideas into one feature request
- Do not enrol a production server in the Beta Squad
- Do not paste an API key into a channel — the Beta Squad form is private
FAQ
Related pages
Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.
- Dedicated Support
- Feature Previews
- Community Configs
- Active Discussions