Tracking Guide

MonTally supports two different detection models:

• OCR-based capture tracking
• Native tracker integration

Which one is active depends on the profile you are using.

Standard OCR Tracking

This is the classic MonTally workflow. The app captures a selected screen area and reads the encounter text from it.

Use this mode when:

• you are not using a native integration
• you want the traditional MonTally flow
• you need a flexible setup based on your screen layout

How It Works

1. MonTally stores a capture rectangle
2. It remembers which monitor that rectangle belongs to
3. It repeatedly captures that region
4. It processes the visible Pokémon names
5. It updates the active profile's encounter data

Because of that, OCR tracking quality depends heavily on correct capture setup.

Configuring the Capture Area

Open Settings and go to Encounter settings, then click Select Capture Area.

When setting the area:

• include the parts of the battle UI where Pokémon names appear
• avoid capturing unnecessary UI regions
• avoid huge areas when a smaller one works
• keep the area aligned with your actual game window position

Good Capture Area Setup

A good area is:

• small
• stable
• on the correct monitor
• free from overlays

A bad area usually causes:

• missed detections
• duplicate reads
• wrong names
• lower performance

Multi-Monitor Behavior

MonTally supports multiple monitors, but the selected capture area must match the monitor where the game is running.

If you move the game to another display:

1. reopen Select Capture Area
2. save the area again
3. continue hunting

MonTally stores a monitorIndex together with the area, so moving the game without recalibrating can cause the wrong display to be captured.

Detection Quality Tips

To improve recognition reliability:

• keep the game window in the same place during a session
• use a capture area that only includes the necessary encounter text zones
• avoid overlays on top of the encounter UI
• avoid stretching the game across two screens
• recalibrate after changing resolution, UI scale, or monitor layout

Tracking Controls in Settings

MonTally exposes several settings that affect tracking behavior directly.

Encounter Settings

• OFF/ON Enables or disables the encounter detection loop
• Selective Pokémon mode Lets you restrict counting behavior depending on your configuration
• Select Capture Area Opens the selector window for capture calibration

UI and Counter Visibility

• Show shiny percentage
• Show total encounters
• Reset counters when open
• Streamer mode

These do not change the underlying detector itself, but they do change how information is presented and reset.

Experimental Options

• Turbo mode Makes detection run faster
• Dynamic size system Adjusts transparent UI height automatically

Use turbo mode only if you actually need faster reads. A more aggressive loop is not always necessary for every setup.

Native Tracker Profiles

Some profiles do not use OCR detection at all.

For example:

• PokeMMO profiles use native tracker integration instead of the standard capture flow

That means:

• the main OCR detection loop is bypassed
• MonTally uses tracker state coming from the game integration
• capture-area issues are much less relevant for that profile

Read more in PokeMMO Integration.

Common Symptoms and What They Usually Mean

MonTally detects nothing

Usually caused by:

• wrong capture area
• wrong monitor
• hidden or obstructed name region
• tracking disabled

MonTally detects the wrong names

Usually caused by:

• too large a capture area
• overlapping UI
• unstable text region

Detection worked before but broke after moving the game

Usually caused by:

• moving the game to another monitor
• changing resolution or UI scale
• not re-saving the capture area

Recommended Workflow

For the most stable OCR-based setup:

1. launch MonTally
2. open the game
3. place the game on the desired monitor
4. configure the capture area once the window is in its final position
5. start hunting
6. only recalibrate if the game position, monitor, resolution, or relevant UI changes

Related Documentation

• Profiles
• PokeMMO Integration
• Data Management
• Troubleshooting