PlayerTracker: Know Who You've Run With, and How They Actually Play
A passive TBC Classic addon that silently builds a persistent profile on every PUG you touch: loot, rolls, deaths, consumes, disconnects and a 0–100 Trust Score — all accumulated forever, account-wide, with zero cooperation required from anyone else.
Every WoW Classic player knows the feeling. You zone into a heroic with four strangers from LFG, and twenty minutes in somebody ninjas a BoE, somebody else has pulled without a flask for the third boss in a row, and the tank ragequits on a wipe. You vaguely remember running with two of them before. Which ones? Were they fine? Were they the reason last week's Karazhan fell apart?
You have no idea. Your brain is not a database.
PlayerTracker is. It's a brand-new KATforge addon for TBC Classic that sits quietly in the background, watches every player you group with, and builds a persistent profile on them forever — across every character, every session, every server reset. By the fiftieth heroic you run this month, every stranger in your LFG channel is either green, yellow, or red at a glance.
The Observation Problem
The reason PlayerTracker works is that it asks nothing of anyone else. No opt-in, no shared database, no server sync, no cooperation from the people you're watching. The moment you share a group with a player, you silently start recording: their rolls, their loot, their deaths, their role, their buff bar at the start of every boss pull, and whether they were still online when the group disbanded.
A single run is noise. A hundred runs is a pattern.
The design principle is simple: what someone claims in their LFG macro is worthless. What they actually did across thirty pulls is not. Every feature in the addon exists to widen the gap between those two things.
The Trust Score
Every player you've grouped with gets a single number, 0 to 100, colour-coded throughout the UI — green for reliable, yellow for neutral or thin data, red for consistent problems. That number is the sum of seven behavioural factors: death rate weighted by content difficulty, Need-roll percentage, completion rate (clears ÷ entries), heroic and boss experience, consume compliance, time grouped, and quest cooperation.
The score is blended toward 50 based on how often you've actually grouped with the player, so one lucky run can't push someone to 95 and one bad night can't send them to 5. At one grouping the score is mostly neutral; by ten groupings the raw math dominates. Your own positive/negative rating gets applied on top as a ±20/−35 modifier, so your direct judgement always wins over the algorithm.
The Consume Score
Separate from the Trust Score, every player gets a Consume Score: a passive, 0–100 measurement of how consistently they show up buffed. At the start of every boss pull, PlayerTracker queues a buff scan of every group member. Flask, battle elixir, guardian elixir, food buff, weapon oil, and scrolls are all checked. The scan is only committed on a boss kill — wipes don't count — so over time you build a real per-player percentage for each consume type.
The end result is that the one player in the PUG who has been stealthily skipping their flask for the last three months suddenly has receipts.
Loot, Rolls, and Disconnects
Three of the things people lie most about in pugs are loot, rolls, and disconnects. All three get tracked automatically.
A ninja looter reveals themselves across dozens of runs without you having to remember a single incident. A chronic bailer shows up in the disconnect column the next time they join your group — PlayerTracker counts every online→offline transition mid-instance, and yes, it cannot distinguish a rage-logout from a real disconnect, so both count.
Instance History and Relationships
Every dungeon and raid you've run with a player is tracked separately, with entries and clears split out. An audited 372-boss lookup table — covering every Classic and TBC dungeon and raid through Sunwell — turns boss kills into real clear data. Repeatedly entering Karazhan without ever finishing it is a completely different signal from actually clearing it, and PlayerTracker makes that distinction explicit.
Every player record also includes the full set of other players you've ever run alongside them, each with their own score. Over time this becomes a social graph of your server — useful for spotting guilds that travel together, and for noticing that the highly-rated healer you trust keeps bringing the same two DPS you don't.
Acting on It
A database is only useful if it's fast to query in the moment. Three features push the data back into chat and tooltips where decisions get made:
World tooltip integration. Hover any tracked player anywhere in the world, and their Trust Score and note are appended to the standard WoW tooltip. No window to open.
Right-click menu. Right-clicking any name in the list opens a single-purpose menu — no submenus, no hunting. Rate the player, edit their note, whisper them, invite them, post their stat line to Party, Raid, Guild, Say, or any channel you're joined to.
Group-entry banner. When a group forms and you zone in, PlayerTracker posts one line per player it has a record for, including your note on each of them. If you've flagged someone negative, that note is now sitting in your chat window before the first pull.
!ptwho — Chat Queries for the Whole Group
Any guild, party, or raid member can type !ptwho Playername in chat, and
PlayerTracker will post a full stat line back to that channel. It's a small
feature with an outsized effect — a guild officer vetting a PUG applicant
mid-raid can pull every officer's collective memory of that player into
guild chat with seven characters of input.
The Privacy Line
PlayerTracker is local. Your database lives in
WTF/Account/<you>/SavedVariables/PlayerTracker.lua and is never
transmitted anywhere. Your ratings and notes are yours alone, forever.
There is exactly one thing the addon broadcasts without your explicit
action: if "Announce PT" is on (the default), zoning into a new instance
posts a single banner line to party or raid chat like
PlayerTracker active! Played with:3 New players:2. It's there so groups
know the feature exists — pugs are visibly more honest when they know
someone is recording. If you want completely silent operation, flip the
checkbox off and the only thing that ever reaches chat is what you
explicitly send yourself.
Get It
PlayerTracker v1.10a is live on CurseForge for TBC Classic 2.5.5, tested on Dreamscythe. Install it, group with a few people, and come back in a week — you will already be surprised by what the data shows you about the players you thought you knew.
Download PlayerTracker on CurseForge →If you're upgrading from an older version, no export or import is
necessary — /pt selftest runs five structural database invariants at
every login and auto-heals stale state. If you were already using
CharacterNotes, /pt importcn pulls every note and rating across in a
single pass, non-destructive by default.
Groups you've already run don't show up retroactively. The clock starts the moment you install. Every PUG after that is a data point.