Skip to content
Tutorials

Creating Packs by Evidence Type

Choose OCR, export-based evidence, or mixed evidence before building your pack so the editor, member prompts, and score reports all line up.

Builds and Evidence
Who uses it
Guild owners, managers, build editors
Where it lives
Dashboard > Game Packs > Pack > Build Editor
Goal
A pack whose builds clearly tell members what to submit and whose scoring rules match that evidence.
On This Page5 sections

Before You Start

  • A guild where GearCheck is installed.
  • Permission to create or edit packs and builds.
  • At least one activity you want members to verify for.

Steps

  1. Start with the game and evidence source

    Create or open a pack, confirm the game, then decide how members prove the build. OCR is for screenshots. Export-based evidence is for pasted or uploaded structured text such as Markdown or TONL. Each supported evidence source should make the member's submission path clear before you start building requirements.

  2. Use the editor that matches the selected source

    Use OCR Spec for screenshot matching. Use Markdown or TONL-style spec editors for export-based evidence. Keep inactive editors disabled unless you intentionally want to switch the build to that source.

    • OCR Spec: categories, items, aliases, excludes, targets, Build Health.
    • Markdown/TONL Spec: character fields, equipment, skills, stats, passives, and source-specific sections.
    • Mixed packs: keep each build explicit so members do not guess what to submit.

  3. Write member-facing instructions around the evidence

    Before testing, read the Discord prompt that members will see. It should say screenshots for OCR builds and export text or files for export-based builds. If the prompt feels generic or wrong, fix the evidence source before inviting members to use it.

  4. Test with real evidence

    OCR builds should be tested with real screenshot text and saved OCR samples from gear check details. Export-based builds should be tested with a real export from the game or tool. Do not treat a manually typed sample as enough for a guild-facing build.

Check It Worked

  • The build editor shows the intended source as enabled.
  • The member Discord prompt asks for the same evidence source.
  • The score report labels the evidence source clearly.
  • Exports or screenshots from a real member produce a sensible checklist.

Common Pitfalls

  • Leaving OCR enabled for a build that should parse Markdown or TONL.
  • Creating aliases for export fields that should be exact catalog-backed values.
  • Using one generic pack for multiple games when the evidence rules are different.