Moderator Guide

Mods keep the gearcheck system running smoothly. You handle the edge cases that the bot can't figure out on its own: bad OCR, wrong threads, support tickets, and everything in between.

Who Counts as a Mod?

By default, anyone with one of these permissions can use mod commands:

• Administrator permission
• Manage Messages permission

You can also configure a specific mod role using /mod set-mod-role role:@Officers. Anyone with that role will have access to all mod commands, even without Manage Messages.

Score Overrides

This is probably the mod tool you'll use the most. When someone has the right gear but OCR gave them a bad score, you can set a score floor.

The override sets a floor, not an exact score. If the member later submits a better screenshot and gets 90%, the score stays at 90%. The floor only kicks in when the OCR-based score is lower than the override.

When to use overrides

• You can clearly see the gear is correct in the screenshots, but OCR missed things due to image quality.
• The build spec is missing aliases, and you don't want to make the member wait while you fix them. Override now, fix aliases later.
• A game update changed item names, and the build spec hasn't been updated yet.

Thread Transfers

Sometimes the wrong person starts a gearcheck thread, or someone needs to verify on a different character. The transfer command lets you change who owns the thread.

This updates the thread ownership and resets the workflow. The new owner starts fresh with the build selection. Run this command inside the thread you want to transfer.

Dashboard Refresh

If the dashboard in a thread gets out of sync (for example, if buttons stop responding after a bot restart), you can force a refresh:

This regenerates the entire dashboard message with fresh buttons and the latest state. All existing scores and progress are preserved. The old dashboard message gets replaced with a new one.

Monitoring Active Workflows

Want to see who's currently going through a gearcheck? The active command gives you an overview of all in-progress workflows.

This shows you thread names, owners, selected builds, and current status. Useful for keeping an eye on things during verification sessions, or for finding threads that got abandoned.

Thread Info

For a deep look at a specific thread, run /mod info inside that thread. You'll see the thread owner, which builds they've selected, their scores, any overrides that have been applied, and the current workflow state.

This is the first thing to check when someone reports a problem with their gearcheck. It tells you everything the bot knows about that thread.

Support Tickets

Members can submit support tickets with /support. Tickets go to the configured support user (set by the admin with /admin set-support-user) and are also visible to mods.

Viewing Open Tickets

This shows all open tickets for the server, along with who submitted them and when. Review each ticket, take action (override, fix a build, etc.), and then resolve it.

Resolving a Ticket

Marks the ticket as resolved. The member who submitted it won't get a notification, so you may want to follow up in the thread or DM them if the situation warrants it.

Cleanup

Over time, threads get archived or deleted, but the bot's config entries for those threads stick around. The cleanup command prunes stale data.

This removes config entries for threads that no longer exist. It's safe to run at any time and won't affect active threads. Good practice to run periodically in busy servers.

Audit Log

If an admin has configured an audit channel with /admin set-audit-channel, the bot logs key events there automatically:

• Score calculations and status changes
• Mod overrides and who applied them
• Role assignments and removals
• Thread transfers
• Build changes (creates, deletes, edits)
• Failsafe lockouts

The audit log is your paper trail. If there's ever a question about what happened or who did what, it's all there. We recommend setting this up early, especially in larger servers.