Downloads

Pro Tracker & Database — encounter tracking, boss database, damage calculator and battle simulator.

Windows

64-bit. Nothing to install.

Linux

Run uname -m if you're not sure which.

x64 — regular PCs, Intel/AMD (almost everyone)

Download

ARM64 — Raspberry Pi 5 and similar

Download

macOS

Apple menu › About This Mac tells you which.

Apple Silicon — M1, M2, M3, M4

Download

Intel

Download

Android

Companion app — not the tracker. Read first.

Pro Tracker & Database

Read‑me information

Windows

Extract the zip anywhere and run ProTrackerDatabase.Avalonia.exe. There is nothing to install and no setup step.

"Windows protected your PC"

SmartScreen shows this for any program it hasn't seen many people run, which includes this one. Click More info, then Run anyway. It isn't a warning about anything found in the file — it's a warning that the file isn't code-signed, which costs money per year and this project doesn't pay for.

If tracking doesn't find your game window

Use Set Screen Boundaries in the toolbar to draw the battle area manually, then send a report from Report a Problem so the automatic detection can be fixed for everyone.

Where your data lives

Sessions, hunt logs and settings are kept in %LocalAppData%\ProTracker. Copy that folder to move everything to another PC, or to load it into the Android companion.

Linux

Easiest path — extract the zip, open a terminal in the extracted folder, and run:

bash linux-start.sh

Use bash linux-start.sh rather than ./linux-start.sh the first time. A zip made on Windows and unzipped on Linux loses the file's execute permission, and running it through bash sidesteps that. The script fixes its own permission for next time.

That one command installs the packages the tracker needs (wmctrl, imagemagick, the Tesseract/Leptonica OCR libraries) using whatever package manager your distro has — apt, dnf, yum, pacman, zypper or apk — installs the .NET 10 SDK to your home folder if it isn't present, applies the OCR native-library fix, quiets the GNOME bell, and starts the app. It's safe to run again on every new build.

If it can't do something automatically

It tells you exactly what happened and what to run by hand — it won't fail silently. That covers no network access to your distro's repositories, and immutable Fedora variants (Silverblue, Kinoite, Bazzite) where packages can't be installed live.

Manual install

Debian/Ubuntu: sudo apt install wmctrl imagemagick libtesseract-dev libleptonica-dev Fedora/RHEL: sudo dnf install wmctrl ImageMagick tesseract-devel leptonica-devel Arch: sudo pacman -S wmctrl imagemagick tesseract leptonica openSUSE: sudo zypper install wmctrl ImageMagick tesseract-ocr-devel leptonica-devel

On Fedora Atomic / immutable systems, regular dnf is blocked — use rpm-ostree install with the same package names, then reboot before running the app.

Wayland

Window capture sees X11 windows, which includes XWayland — how most Wayland desktops still show X11 apps, so this is usually a non-issue. A window under native Wayland with no XWayland layer is invisible to it. Check with:

echo $XDG_SESSION_TYPE

Logs

~/.local/share/ProTracker/Logs/

macOS

Getting it to start — do this first

A freshly extracted build will not open by double-clicking, and nothing will appear at all. A zip made on Windows can't carry the "this file is a program" permission macOS requires, and macOS quarantines anything downloaded from the internet. From Terminal, in the folder you extracted:

bash macos-start.sh

Use bash macos-start.sh rather than ./macos-start.sh the first time, for the same permission reason. That one command restores the executable's permissions, clears the quarantine flag so Gatekeeper allows the launch, sets up the OCR libraries through Homebrew if it's installed, and starts the app.

Manual fallback

chmod +x ProTrackerDatabase.Avalonia xattr -dr com.apple.quarantine . ./ProTrackerDatabase.Avalonia

If macOS still refuses with "unidentified developer" or "Apple could not verify", approve it under System Settings › Privacy & Security › Open Anyway and run it again. The app isn't notarized with Apple — that's what macOS is objecting to, not anything found in the file.

Intel or Apple Silicon

Use the matching build. An arm64 build cannot run on an Intel Mac at all. The Intel build does run on Apple Silicon through Rosetta, if Rosetta is installed (softwareupdate --install-rosetta).

Two permissions it needs

Under System Settings › Privacy & Security, the app must appear and be ticked in both lists, not just one:

  • Automation — reads the PRO client window's position and size.
  • Screen Recording — captures pixels from that window. Without it captures come back blank rather than showing an error, so if tracking silently picks nothing up, check this first.

Known limitation

Capture grabs a region of the screen rather than the window's own buffer, so another window overlapping the PRO client while it scans will be captured instead. Keep the client unobstructed if detection misses things intermittently.

Logs

~/Library/Application Support/ProTracker/Logs/

Android companion

This is not a tracker. Live encounter tracking needs the game window and OCR, and a phone has neither. What the companion gives you is the reference half of the desktop app, running the same code on your own data: Boss Database and boss details, Pokédex areas, Search, Previously Battled and each opponent's history, Lifetime Stats, the Team Builder and the battle Simulator.

Installing

Extract the zip and install the APK. Android will ask you to allow installing apps from this source — that prompt appears for anything not from the Play Store.

Getting your data onto it

Open the Data tab and import a zip of your desktop's %LocalAppData%\ProTracker folder. Everything reads back under the same names — boss records, PVP history, lifetime stats, Pokédex areas and the encounter log.

The first launch unpacks about 3,200 sprite files and takes a few seconds. That only happens once per app version.