Build System

What Is a Build?

A build is a gear specification. Think of it as a checklist that says to be verified for this content, you need these items. Every build has a name, and it belongs to an activity.

Builds contain categories, and categories contain items. When the bot scores a submission, it works through each enabled section and checks how much of the required spec it can find in the submitted evidence.

Game and Evidence Source Editors

The build editor changes based on the pack's game and the selected evidence source. This keeps New World OCR builds from feeling like ESO export builds, and keeps each supported game from inheriting the wrong assumptions.

Disabled editors keep their saved state where possible. Switching evidence source changes which spec the bot uses for live checks.

Activities

An activity is a grouping label for your builds. Common examples: Raids, Dungeons, PvP, Wars. When you set up a gearcheck channel with /gearcheck setup activity:raids, the channel will only show builds that belong to that activity.

This keeps things organized. Your raiders see raid builds. Your dungeon runners see dungeon builds. Nobody has to scroll through a list of builds they do not care about.

Categories

Categories are the gear types within a build. For example, a build might have categories for Weapons, Armor Perks, Amulet, Ring, and Trophies. Each category gets scored separately, and the category scores combine into the overall build score.

Categories can have different weights, so you can make some categories count more than others toward the final score.

Items

Items are the individual things being checked within a category. If your Armor Perks category needs Refreshing, Freedom, and Resilient, those are three items. In OCR builds, each item gets matched against extracted text. In structured builds, fields are compared against parsed export data.

When adding items, think about what text or structured field the bot will see in the submitted evidence. The name should match what actually appears in-game or in the export, and you can add aliases to catch variations.

Aliases

Aliases are alternative names for an item. They exist because OCR and human-entered specs are not perfect, and because games sometimes display things differently than you would expect. The bot uses fuzzy matching where appropriate, so it can handle small typos on its own. But aliases help in cases where the difference is bigger.

For example:

• An item named Sword and Shield might also appear as SnS or Sword & Shield in screenshots.
• OCR might read Refreshing as Refrshing or Refreshlng.
• A perk might be shortened in the UI compared to its full name.

Good aliases make the difference between a 60% score and a 95% score. If your members are getting lower scores than expected, check aliases first.

Excludes

Excludes prevent false positives. Sometimes an item name is a substring of another item, and the bot might match the wrong one. For example, Refreshing is part of Refreshing Move. If your build needs Refreshing but not Refreshing Move, you can add Refreshing Move as an exclusion on the Refreshing item.

When the bot sees Refreshing Move in the OCR text, it will not count it as a match for the Refreshing item. This keeps your scores accurate.

Build Health and Screenshot Reading

The dashboard includes build-health tools for catching risky specs before members run into them. For OCR builds, the scanner can surface alias collisions, exclusion suggestions, source-pattern issues, and recurring misses from previous checks. For structured evidence, the same idea applies to missing fields, unsupported sections, and sections that are enabled in the editor but absent from member exports.

Use these tools after creating a build and again after real submissions start coming in. They are meant to turn why did this fail into a short list of concrete edits.

Weights

Not all categories are equally important. Weights let you control how much each category counts toward the final score. By default, every category has a weight of 1.0. You can increase a weight to make a category count more, or decrease it to make it count less.

For example, if trophies are harder to get and more important for your content, you might give the Trophies category a weight of 1.5. That means it contributes 50% more to the final score than a category with weight 1.0.

Thresholds

Thresholds determine what status a member gets based on their score. There are four status levels:

Rule Types

Each item in a build can have a rule type that controls how it affects scoring:

Game Data Search (New World)

New World packs have access to the full game database in the web build editor. Type a perk or item name to search, and selecting a result auto-fills aliases, excludes, and description fragments for accurate OCR matching. You can also type custom names without selecting from the dropdown.

Trophy Detection (New World)

Enable trophy detection on builds to auto-detect combat trophies from trophy grid screenshots. Select which types are required (Angry Earth, Wildlife, Lost) and the bot handles the rest. Ultimate Combat Trophies count toward all types. Target is always 3, one per house. Requires the trophy_detector_nw plugin to be enabled.

Editing builds on the web dashboard

The web Build Editor is the full authoring surface for builds. It does everything the /pack commands do (categories, items, aliases, weights) and adds what the commands cannot: the OCR risk scanner, revision history, and, for Elder Scrolls Online, the structured rules and evidence source that /pack cannot author at all (see the note below).

Open your Dashboard , pick a server and pack, then open a build to land in the Build Editor. Its work is organized into tabs:

The ESO Spec tab only appears for Elder Scrolls Online builds. The Plugins tab shows attribute and trophy detection only for games that support them.

Pack view and sharing

The pack detail page that lists your builds has a couple of controls worth knowing:

• Model / Library toggle: switch between the activity-role-spec model view and a flat library list of every build in the pack.
• The Library view is the quickest way to find and open a single build when a pack has many.
• Public Requirements toggle: generate a shareable read-only page of the pack's requirements that members can view without Discord.

Templates vs Custom Builds

You can start from a template pack or build everything from scratch. Templates are pre-configured builds with categories, items, and aliases already set up. They save a lot of time if your game has one available.

You can also install a template and then customize it. Installed templates are fully editable, so you can add, remove, or change anything after installation. There is also a third source: the web Community Marketplace, where guilds publish and discover packs built by other communities. Browse it on the Community Marketplace in the dashboard, then install any listing into your own server (Pro plan required to install) with an optional custom pack name. Publishing a pack to the marketplace is the web counterpart of /pack share, and installing from it mirrors /pack import-code. Some listings also carry a Curated badge: GearCheck staff flag a pack as Curated when they approve it, so seeing that badge on a marketplace card or its preview means staff already checked it as a solid starting point.