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
The feature is implemented, but OCR can still misread small, blurred, decorative or changing text. Use harmless test data and supervise important workflows. If the text cannot be read, Counter Reader reports an unreadable result. It does not turn unreadable text into zero or invent a date.
Create a number-based condition
1. Identify the visible value
Choose one value whose meaning is clear, such as an item count, a timer or a local date. Do not include a nearby label, icon or second number unless it is part of the same value.
2. Select a small screen area
Choose a rectangle around the value. A small area reduces unrelated text and speeds up each scan. You can also use a monitor or visible selected window, but a minimized or protected window is not a reliable source.
3. Choose the value type and format
Select Number, Time, Date or Date and Time. For numbers, confirm decimal and thousands separators. For time or date, select the visible format, language and time zone. A format such as month/day/year should not be interpreted as day/month/year by accident.
4. Build the comparison
Choose less than, less than or equal, equal, not equal, greater than or equal, greater than, between or outside. For example, a rule can match when a visible count is greater than or equal to 10. With several rules, decide whether every rule must match or any one rule is enough.
5. Tune reading quality only when needed
Start with automatic preprocessing. If the preview is wrong, improve the selected area and contrast before changing confidence or processing settings. Agreement and stability settings require the same result across repeated reads, which can reduce action on a single bad frame but also makes the trigger slower.
6. Choose the wait behavior
Single scan checks once. Timeout keeps checking until its limit and can use ELSE when no match arrives. Until matched has no finite non-match result, so ELSE is unavailable. Set a sensible scan interval and cooldown so one stable value does not trigger faster than the task can handle.
7. Add a safe THEN action
Begin with a harmless delay or one visible click. Add an ELSE action only after testing a deliberate non-match. Keep F12 available as the permanent Emergency Stop during every early run.
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.
Beginner example: wait for a count of 10
Place a harmless test window on screen with a large value of 8. Select only the number, choose Number, and set the rule to greater than or equal to 10. Use a timeout and make ELSE wait without clicking.
Change the visible value to 10 and confirm that THEN runs once. Then replace it with unclear text and confirm that the app reports an unreadable value instead of treating it as zero.
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
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.
- F12 stops a harmless test immediately.
Osenpa Auto Clicker
Read a visible number, time or date locally and connect a tested match to an editable supervised workflow.