v1.6.5 - Fix RP attributed to the wrong match

Fix: RP showing on the wrong match

ALS often posts a match's RP a few seconds before the tracker reads the summary screen. The RP resolver only looked for changes after that moment, so it skipped each game's own result and grabbed the next game's. That shifted RP by one match, and if a game was missed, its RP landed on the previous match.

• The starting RP now comes from the last reading taken just before the match's result could post, and the RP change is searched for from that point.
• A quick game the tracker never logged no longer gets added into the next match (e.g. -43 and -48 showing as -91 on one row).
• Early leavers (RP posting minutes before the summary screen) are still handled by the baseline chain.
• Replaying the full 11-day stream-PC ledger: 87/88 matches get the right RP, vs 50/88 before.

New: repair_rp_from_ledger.py (source only)

Fixes per-match RP already in Supabase using an rp_ledger.jsonl from the PC that runs the tracker. It previews by default, and --apply writes the changes after saving a backup.

Update

Download ApexTracker_share.zip, close the tracker, and replace the program files. Keep your existing config.json and .env.