Documentation
Back to tutorials

OCR

OCR Optimization and Build Health

Use Build Health, aliases, excludes, source hints, and saved samples to improve OCR without making matching too permissive.

Who uses it

Build editors and OCR troubleshooters

Where it lives

Dashboard > Game Packs > Build Editor > Build Health

Goal

OCR builds become more accurate while avoiding broad aliases and false positives.

Before You Start

  • An OCR-based build.
  • Real failed or partial sessions to inspect.
  • Permission to edit builds.

Steps

1

Run Build Health

Open the build and review scanner findings. Look for alias collisions, unsafe description phrases, missing excludes, repeated misses, source-language mismatch, and source-pattern warnings.

2

Apply safe fixes carefully

Suggested excludes and aliases can help, but every change affects future checks. Avoid generic two-word phrases unless the scanner and real evidence prove they are safe.

3

Use OCR Insights for live patterns

Build Health explains a specific build. OCR Insights shows repeated live failures across sessions, sources, languages, and builds. Use both before deciding a fix.

4

Save examples for hard cases

When a recurring OCR issue is fixed, keep a scrubbed sample so the behavior can be checked again. This is especially important for collages, wrapped text, compressed screenshots, and non-English OCR.

Launch Checklist

  • Fixes do not create new false positives in nearby items.
  • Aliases remain specific to the item.
  • Excludes block the false positive that caused the issue.
  • Saved samples exist for recurring production problems.

Common Pitfalls

  • Adding broad description fragments as aliases.
  • Fixing one item by making another item impossible to match.
  • Ignoring source format when the issue is collage or third-party screenshot layout.

Related