v1.6.6 - Fix summary screens that were never logged

Fix: summary screens with a fused K/A/Kn line were never logged

The game's italic slashes on the Kills / Assists / Knocks line sometimes OCR as the digit 1, so 7 / 7 / 7 reads as 71717. That gives 71,717 kills, which fails the sanity check (more than 75 is impossible), so the tracker treated the screen as "still rendering" and retried. Every retry read the same frame the same way, so the match was dropped silently, even with the summary on screen for minutes. This happened to a ranked win on 2026-10-25.

• When the K/A/Kn line comes back with fewer than three numbers, the tracker now tries reading the 1s as slashes (71717 → 7/7/7, 101213 → 10/2/3).
• It only accepts a split when exactly one reading gives three believable stats. Ambiguous reads (e.g. 111111, which could be 11/1/1, 1/11/1 or 1/1/11) are still not guessed. They stay unread and get retried as before.
• Clean reads with three numbers are unchanged. The 4 reference screenshots still read 100%.
• New test_parse_kak.py (source only) covers the live case, partial fusions and the ambiguous cases.

Roster

config.json adds HeckaTrix to known_names and als_uids (1011198512420). The updater keeps your existing config.json, so on an existing install add him in Settings → roster (name HeckaTrix, UID 1011198512420), then Save and Stop → Start.

Update

Use the in-app update, or download ApexTracker_share.zip, close the tracker, and replace the program files. Keep your existing config.json and .env.