Troubleshooting

A few things to check:

• Is the bot online? Check the member list. If it's showing offline, the bot might be restarting or experiencing downtime.
• Does it have the right permissions? The bot needs permissions to read messages, send messages, and manage threads in the channels where it operates. Check the channel permission overrides as well as the bot's role permissions.
• Are commands synced? Slash commands can take up to an hour to sync after the bot is first invited. If you just added it, give it some time. You can also try restarting your Discord client to force-refresh the command list.

The gearcheck dashboard only appears in threads created in channels that have been set up with /gearcheck setup. If the channel hasn't been configured yet, threads created there won't trigger anything.

Also make sure the thread was created after the channel was set up. Threads that existed before setup don't retroactively get dashboards.

If the channel is set up but the dashboard still isn't appearing, check that the bot has permission to send messages and manage threads in that channel.

The score is based on what GearCheck could read from your submitted evidence. Click the Show Details button on your score breakdown to see exactly which items or fields matched, which were "maybe" matches, and which were missed.

Common reasons for lower-than-expected scores:

• Blurry or compressed screenshots
• UI elements covering the gear text
• Missing aliases in the build. Admins can fix this with /pack edit-item.
• Items not included in the build spec at all
• The build expects one evidence source, but the member submitted another format

See the How Scoring Works page for a detailed explanation.

Make sure the build is using the matching ESO evidence source. A Markdown Spec expects the default CharacterMarkdown export. A TONL Spec expects the advanced TONL export. If the build is still using OCR Spec, the bot will look for screenshots instead of parsing the text export.

For Markdown, paste the export text directly or attach a plain text file. For TONL, include the complete export. Partial exports can miss sections and lower the score.

Use a server RaidHelper API key, not a user settings API key. In RaidHelper, the server-wide key comes from the non-user settings API key command. GearCheck uses that key to list server events and match signups to GearCheck builds.

If auto-detect does not find an event, add the channel to the watched-channel list or paste the RaidHelper event ID directly. Events outside the watched server, deleted events, expired events, or keys without access will not resolve.

Check the rule's starting point first. Verification rules, review queue rules, support ticket rules, RaidHelper rules, and billing rules each receive different data. If a rule combines event families that do not belong together, GearCheck may warn you or skip incompatible fields.

Also verify the destination, quiet hours, cooldown, dedupe scope, enabled status, and whether the member opted out of user-level notifications. Use the test button on the rule to confirm delivery.

Merge fields depend on the trigger family. A review queue rule has verification and thread fields. A ticket rule has ticket fields. A billing rule has billing fields. If a template uses a field that does not exist for that event, it may render blank or fall back to a raw ID when no display name is available.

Edit the rule and use the merge-field picker for that starting point. The picker is safer than copying fields from another rule.

Discord requires the bot's role to be above the role it's trying to assign in the role hierarchy. Go to Server Settings, then Roles, and drag the bot's role above the verified role.

Also confirm the bot has the Manage Roles permission. Without it, the bot can't assign any roles at all, regardless of hierarchy.

If buttons on the dashboard or score breakdowns stop responding, it usually means the bot restarted. Discord buttons are tied to the bot's session, and when the bot comes back online, it should recover automatically.

If buttons still don't work after a minute or two, try running /mod refresh in the thread to regenerate the dashboard with fresh buttons.

A build might not show in the dropdown for a few reasons:

• Wrong activity. The channel is set up for a specific activity, like raids, and only builds assigned to that activity appear. Check what activity the channel uses and what activity the build belongs to.
• Role gate. The build might be gated behind a role that the member doesn't have. Check with /gearcheck build-info to see if a role gate is set.

If you score very low on the same build multiple times in a row, the failsafe system locks the build for you. This prevents score spamming.

To get unlocked, ask a mod to review your screenshots and either override your score or unlock the build. They can see your submissions in the thread using /mod info.

Template installation requires a Subscriber plan. If you're on the Free plan, the command will be rejected. Check your tier with /admin settings.

If you are on the right tier and it still fails, make sure you have Manage Serverpermission. Also check that the template name is correct. The autocomplete dropdown will show you available templates.

Share codes can have usage limits and expiration dates. If the code was already redeemed the maximum number of times, or if it has passed its expiration date, it won't work anymore.

Ask the person who generated the code to create a new one with /pack share. They can also check the status of their existing codes with /pack my-shares.

Importing shared packs also requires a Subscriber plan on the receiving server.