Don't waste your time with Tesseract here, I tell ya. You'd only get all sorts of unnecessary hassle. And what's most important, you'll be frustrated by accuracy.
But in your case that wouldn't be dumb iteration over the entire image, but a single check in a fixed location whether the template image has exactly same pixels as the input image. You can arrange it like this:
- Crop out samples of all digits (each sized 85x60) -> digit0.png .. digit9.png
- Crop out the same sized rectangle from a fixed location of your source image - e.g. score digit #0 -> score0.png
- Do file compare score0.png to digit0.png
- If no match - try digit1.png
...
- Match found - this is your score digit #0
- Take next score digit
...
- Proceed to time digits
...
- Done
Above approach probably would adapt for other games, and you'd manage to use same digit samples.
File compare might be replaced by XOR and then calculating the mean of all pixels (should be 0 if match).
There can be other methods of comparison. You get the point.
You'd better invest your time into accumulating a collection of score digit coordinates in each game, than into a struggle with quirky OCR results.
Well, unless you're eager to.