Counter Reader BETA

Trigger an Auto Clicker from a Number on Screen

Read a visible number, time, or date on your screen and run a supervised action when it meets your rule.

By Osenpa Published Reviewed

Short answer

Counter Reader uses optical character recognition (OCR) to read a visible number, time, or date. A rule can then compare that value with the one you set.

Select the smallest useful screen area and tell the app what kind of value to expect. Test both a match and a non-match before you connect a click or another action.

Counter Reader is labeled BETA

OCR can misread small, blurred, decorative or changing text. Use harmless test data and supervise important workflows. Unreadable text is reported as unreadable; it does not become zero or an invented date.

What you need

Install the local Counter Reader OCR component from Settings before this test. It is about 20.3 MiB. After it is installed, screen reading and rule matching run on this PC. Prepare a harmless test window that can show a large black number on a plain background.

Create a number-based condition

1. Identify the visible value

Show a large 8 in the test window. Keep labels, icons and other numbers outside the value you plan to read.

2. Select a small screen area

Open Counter Reader. Choose a rectangle around only the 8. You should see a selected area instead of No area selected.

3. Read the number

Choose Number. Run a test scan. You should see 8 as the raw and numeric value. If it is wrong, make the selected area smaller and increase the contrast in the test window.

Counter Reader live test showing the raw OCR text, numeric value and reading confidence.
Check the live reading before you build a rule. The raw text and numeric value should describe the same number.

4. Build the comparison

Choose greater than or equal to. Enter 10. The 8 should be shown as a non-match.

5. Add a finite timeout

Choose Timeout. Put a harmless Delay in THEN and Stop in ELSE. A finite timeout lets you see what happens when 10 never appears.

Counter Reader rule with a numeric comparison and separate actions for a match and timeout.
Set the comparison and a finite timeout only after the live reading is correct.

6. Test the match

Change the visible number to 10. Run the condition. You should see 10 in the live reading and the THEN action should run.

7. Test non-match and unreadable states

Change the value back to 8. The timeout should end in ELSE. Then replace the number with ABC. The app should report an unreadable value instead of treating it as zero. Keep F12 available as the permanent Emergency Stop.

Advanced value and reading controlsTime, date, several rules and repeated reads.

Counter Reader can also interpret Time, Date or Date and Time. For numbers, confirm decimal and thousands separators. For time or date, choose the visible format, language and time zone so an ambiguous date is not read in the wrong order.

Comparisons include less than, less than or equal, equal, not equal, greater than or equal, greater than, between and outside. With several rules, choose whether every rule or any one rule must match.

Start with automatic preprocessing. Agreement and stability can require the same result across several reads. This takes longer but reduces action on one bad frame. Single scan checks once. Timeout has a finite ELSE result; Until matched does not.

Checkpoint: read three known states

Pause before attaching a click. Confirm one matching value, one non-matching value and one unreadable sample. Continue only if the three states stay distinct across repeated scans.

Local model and privacy detailsWhat downloads and what stays on the PC.
  • Counter Reader needs a local OCR model before first use.
  • The model is downloaded only from an allowed official source or pinned package fallback and is checked against its expected SHA-256 value.
  • Screen images and recognized values are processed locally and are not uploaded for OCR.
  • An update check and a requested OCR model download are separate network actions from the automation itself.
  • Input Variation does not change OCR values, match decisions, scan timing or cooldown. It only makes small timing or click-position changes within the limits you set and cannot bypass bot protection.
Watch for

What makes OCR unreliable

  • Tiny, blurred or decorative characters
  • Several numbers inside one large search area
  • The wrong decimal, date, time or language format
  • A moving value without enough agreement or cooldown
Verify the result

Counter Reader checks

  • A known value is read correctly several times.
  • A known non-match takes the ELSE or timeout path.
  • Unreadable text never becomes a valid number or date.
  • Re-test after changing display scale, target pixels, selected area, value format or reading settings.
  • F12 stops a harmless test immediately.
Counter Reader BETA

Osenpa Auto Clicker

Read a visible number, time or date locally and connect a tested match to an editable supervised workflow.