How It Works
How detection, matching and templates work under the hood — useful if you want to tune reliability or capture your own templates.
Detection system
Detection works in a few layers: a fast text-appearance match at the pixel level; the ROI system, which limits the search to where the template should appear (e.g. the "Start Race" button is centre-left, so it only searches there) — this also makes detection tens of times faster; and optional OCR text hints — the keywords each screen should contain, which OCR reads off the screen to confirm a match. OCR is on by default because many displays need text confirmation; FAFE CPU-tunes OCR so it stays lighter on stutter-prone CPUs. You can still turn it off in Settings if needed.
There's a single built-in template set that auto-scales to your resolution, so Race, Buy and Auto Wheelspins work out of the box. Advanced users can capture their own templates and draw a custom Detection area (ROI) for a different game language or custom screen.
Match value (threshold)
Imagine being shown two images and asked how similar they are, as a %. That's the match value — except the system compares at the pixel level, so even if they look identical to your eye, the system might see only 50% similarity. The slider in Settings decides what % similarity counts as a pass. Built-in templates auto-scale to your resolution, so there's no resolution to choose.
Choosing a template
As a rule, pick a screen element that only appears on that step — e.g. the timer top-left, or "Restart" on the results screen.
Other factors: variability — avoid a translucent background that changes by location; size — a bigger region has more pixels to match (fewer false positives) but is harder to pass and slower to scan, so experiment; language — built-in templates cover Traditional Chinese and English game UI; for other languages or a custom screen, capture your own templates and draw the Detection area.