Skip to content
Setup Guide

Getting Started

Invite the bot, run the setup wizard, pick a starter pack and run your first real gear check. Custom packs take longer, but you control everything.

On This Page8 sections
The Setup Wizard runs these steps live.

It opens in your server's dashboard while the server has no packs, and saves as you go. This page is the read-ahead. Open the dashboard

  1. Invite the Bot

    Click the Invite Bot button on the homepage or use the invite link your server admin shared. The bot will ask for a few permissions during setup:

    • Manage Roles so it can assign verified roles automatically when someone passes a gearcheck.
    • Create Public Threads so it can create gearcheck threads in your designated channels.
    • Send Messages / Embeds for the dashboards, score breakdowns, and status updates inside threads.
    • Read Message History so it can find and process evidence posted in threads.
    • Attach Files for exporting packs and sharing score reports.

    You need Manage Server permission in your Discord server to invite the bot.

    Invite GearCheckOpen the dashboard

  2. Get Oriented

    Once the bot is in your server, you have two ways to get started:

    Discord Commands
    Run /guide setup to get a step-by-step walkthrough right inside Discord. It covers everything on this page and links to the right commands as you go.
    Web Dashboard
    Sign in on the Dashboard to manage builds visually, configure the setup wizard, view analytics, set up notifications, and manage game-specific evidence without typing commands. The dashboard becomes more powerful on paid tiers.

    What the wizard asks you for

    These are the setup wizard's own steps, in order. Only three of them gate a working check; the rest ship with defaults you can change whenever you like.

    1. Game Pack Required
    2. Starting Build Required
    3. Channels Required
    4. Also set up
    5. Launch

  3. Install a Template or Build From Scratch

    Builds are the specs your members need to match. They can be checked with different evidence sources depending on the game: OCR screenshots, ESO CharacterMarkdown exports, TONL exports, or another supported adapter. You have two options here:

    Pick the right evidence source

    For screenshot-first games, use the OCR Spec editor and tune aliases, excludes, and OCR insights. For ESO, use the Markdown Spec for the default CharacterMarkdown export, or TONL Spec when your guild wants deeper fields like passives and advanced typed data. The bot prompts members differently based on the selected source.

    Option A: Install a Template Pack

    Template packs are pre-built gear specs for specific games and activities, and installing one is the fastest way to get going on any plan. Curated packs never count toward the Free plan's custom build limit.

    TemplateGameBuildsMaintained by
    eso_dungeons_starter_packESO4Curated
    eso_trials_starter_packESO12Curated
    new_world_pveNew World32Community-maintained

    Install a starter pack

    /pack install-template pack:guild-builds template:eso_trials_starter_pack

    Packs that are not curated count toward the Free plan's custom build limit, so a Free server cannot install a large pack such as the New World one without Pro; the Pricing section on the home page lists the limit. Install from the setup wizard's Starter pack option or with /pack install-template.

    Option B: Build From Scratch

    Start by creating a build, then add categories and items to it. This gives you total control over what gets checked.

    Create a build under the Raids activity

    /pack create-build pack:guild-builds name:Main Tank activity:raids

    Add a category for weapons

    /pack add-category pack:guild-builds build:main_tank category:Weapons

    Add an item to that category

    /pack add-item pack:guild-builds build:main_tank category:weapons name:Greatsword aliases:GS,Great Sword

    Check the Build System docs for the full breakdown of categories, items, aliases, weights, and thresholds.

    Prefer a visual editor? You can create and edit all of this in the dashboard's Build Editor instead of the /pack commands, with tabs for the build spec, evidence source, plugins, an OCR Build Health scanner, and revision history.

  4. Set Up a GearCheck Channel

    Pick a channel in your server and tell the bot to use it for gearchecks. You need to specify which activity the channel is for, so the bot knows which builds to show.

    Use a channel for raid checks

    /gearcheck setup pack:guild-builds activity:raids

    After this, when someone creates a thread in that channel, the bot will post a dashboard with all the builds available for that activity. Members pick a build, submit the evidence that build expects, and hit Continue.

    You can set up multiple channels with different activities. For example, one channel for raid gearchecks and another for dungeon gearchecks.

  5. Configure the Mod Role

    By default, anyone with Manage Messages or Administrator permission can use mod commands such as overrides and transfers. If you want to give mod access to a specific role instead, set it up:

    Give mod commands to a role

    /mod set-mod-role role:@Officers

  6. Test Your Build

    Before sending your members through the gearcheck, test it yourself. The /pack test command lets you paste sample text and see how an OCR-style build matches it. For ESO builds, use the dashboard import and test flow with a real Markdown or TONL export so you can validate structured fields before members submit.

    Test a build with sample text

    /pack test pack:guild-builds build:main_tank text:Greatsword, Heavy Armor

    The bot will show you exactly which items matched, which were close, and which were missed. If something is not matching when it should, add more aliases to that item.

  7. Run Your First Real GearCheck

    You are ready. Tell your members to head to the gearcheck channel, create a thread, and follow the dashboard prompts. Here is what happens from their perspective:

    1. They create a thread in the gearcheck channel.
    2. The bot posts a dashboard. They pick a build from the dropdown.
    3. They submit the evidence the build asks for: screenshots for OCR, a pasted CharacterMarkdown export for ESO Markdown, or a TONL text file/export for advanced ESO checks. Then they click Continue.
    4. The bot parses the evidence, scores it against the selected spec, and shows a breakdown of matches, partial matches, misses, and review notes.
    5. If the score hits the verified threshold, the bot assigns the verified role if configured. If not, the member can try again with updated gear, clearer evidence, or the correct export format.

What's Next

Now that you are up and running, here are some things to explore: