Skip to content
Tutorials

Screenshot Reading

Use Reading accuracy to find repeated OCR misses, source patterns, affected builds, and useful troubleshooting samples.

Builds and Evidence
Who uses it
Build editors and staff investigating OCR issues
Where it lives
Dashboard > Insights > Reading accuracy
Goal
Staff can turn repeated OCR problems into build edits, saved samples, or better member instructions.
On This Page5 sections

Before You Start

  • OCR-based checks have been run.
  • View analytics permission.
  • At least one build with screenshot evidence.

Steps

  1. Filter by the problem

    Use build search when one build is failing. Use item search when a specific perk, stat, or requirement is repeatedly missed. Use source and language filters when failures seem tied to collage, tool screenshots, or non-English OCR.

  2. Expand the finding

    Open the issue detail to see affected builds, examples, source hints, and suggested next actions. Do not change aliases blindly if the issue is actually a bad source pattern.

  3. Jump to the build or checks

    Use links to inspect the build spec or the gear checks behind the finding. The goal is to get from pattern to exact fix quickly.

  4. Save examples for recurring issues

    If the issue is real and recurring, export a scrubbed OCR sample from a representative session so support can reproduce it without exposing private member data.

Check It Worked

  • Done/hidden rows can be restored if you need them again.
  • Source pattern filters are not mistaken for item filters.
  • Build links point close to the affected build work.
  • A recurring issue has either a fix or a saved sample for follow-up.

Common Pitfalls

  • Using Reading accuracy for export-based evidence problems.
  • Marking items done without fixing the underlying build or source issue.
  • Adding broad aliases that create false positives in other builds.