PlayerTracker

v1.2d5 — 20260512 nutnhoney @ Dreamscythe | Interface: 20505 (TBC Classic 2.5.5) /pt · /ptr · /playertracker

What Is It?

PlayerTracker is a passive, private observation addon for TBC Classic that silently builds a persistent cross-session profile on every player you group with. It requires nothing from other players — no opt-in, no shared database, no configuration. It runs completely in the background and accumulates data forever, account-wide across all your characters.

Over time it answers questions no other addon tracks: Have I grouped with this person before? Do they roll Need on everything? How often do they die per run? Do they actually bring consumables? Do they bail mid-instance? Have we ever cleared Black Temple together? The next time that person appears in your LFG channel or trade chat, you will know at a glance whether they are worth inviting — or worth avoiding.

For guild officers vetting PUG applicants it provides hard evidence: actual clears, actual boss kills, actual roll behaviour, consume compliance, and disconnect history across dozens of real runs — not what someone claims in their application. For casual players farming Heroics, it turns every stranger into a data point that compounds in value the longer you play.

As of v1.2 PlayerTracker can also optionally share data with other PT users you trust through a peer-to-peer subscription system — your ratings and notes blend with those of subscribed peers into a Community Trust Score, while your private data stays local. The subscription system is entirely opt-in, can be paused via Stealth Mode at any time, and never sends anything to anyone you haven't explicitly subscribed to.

What Makes It Unique

• Entirely passive and private — no opt-in required from other players, no broadcasts without your explicit action, zero gameplay impact
• Cross-session persistence — data accumulates forever, account-wide across all your characters on the same machine
• Trust Score — every player receives a computed 0–100 score based on seven behavioural factors, color-coded red through green
• Guild Score — weighted average Trust Score of every player you've grouped with in their guild, gated on minimum exposure so a single bad apple can't tank a whole guild's score
• Community Trust Score — when you subscribe to other PT users, their measurements of a player blend with yours into a community average. Three independent score columns side-by-side: personal, guild, community.
• Consume Score — a separate 0–100 score measuring flask, elixir, food, oil, and scroll compliance, captured at boss-pull time without any player cooperation
• Disconnect tracking — per-player count of offline-mid-instance events, with per-run ratio, so chronic bailers are visible at a glance
• Context-weighted death scoring — raid deaths count 2.5×, heroic 1.5× vs. normal, so you aren't penalised for normal-dungeon learning deaths but are flagged for repeatedly dying in Hyjal
• Behavioural profiling — roll behaviour, death rates, loot history, and consume patterns show how someone actually plays, not what they claim
• Clear vs. entered — explicitly distinguishes entering a dungeon or raid from finishing it, tracked against an audited 372-entry final-boss table covering every Classic and TBC dungeon and raid
• PVP-aware — Ignore PVP mode prevents battleground and arena activity from contaminating your PvE stats
• Negative player warnings — private, immediate alerts when a negatively-rated player joins your group, with their note attached, before the first pull
• Subscription sharing — exchange ratings and notes with peers you trust through an opt-in addon-channel subscription system. No central server, no third-party hosting. Delta-sync on login, push-on-change in real time.
• Stealth Mode — one command pauses all PT addon traffic without cancelling your subscriptions. Inbound dropped, outbound silenced. Disable later and your subscribers auto-catch-up on changes via the existing delta-sync filter.
• Peer discovery — /pt scan guild|raid|party broadcasts a single addon ping to your channel and reports back every PT user with their version. Results cached up to 60 days; a cyan + indicator appears next to every cached PT user in the main /pt list.
• Addon-presence detection with friendly invite — when you subscribe to someone who doesn't have PT installed, they automatically receive a one-line whisper with a Curseforge download link. If they already have it, they get the popup instead — no whisper, no spam.
• Auto-date stamping on notes — every time you save a note, an (YYYYMMDD) date prefix is automatically maintained so you can see at a glance how stale a note is. Idempotent — re-saving the same note updates the date but doesn't duplicate it.
• Right-click player intelligence — rate, note, subscribe to, block, and share a player's stats to any channel without leaving the window
• Inline whisper and invite — [W] and [I] buttons on every row let you act without leaving the window
• World tooltip integration — hovering any tracked player anywhere appends their PT profile to the standard WoW tooltip
• !ptwho in group chat — any guild, party, or raid member can type !ptwho Playername in chat and PlayerTracker will post a full stat line back to the channel
• CharacterNotes import — one command (or menu item) imports all your existing CharacterNotes ratings and text notes into PlayerTracker, creating records for players you have never grouped with
• Self-testing database — five structural invariants run automatically at login and on demand via /pt selftest; if anything gets corrupted, you find out on the next login instead of weeks later when the numbers look wrong
• Auto-heal migrations — upgrading from older versions requires no export/import; the addon repairs stale state at first login

What It Tracks

Grouping History — Total sessions, total minutes, first and last grouped dates, days since last seen. Active session timing survives disconnects and reloads.

Instance Activity — Entries split across Normal, Heroic, Raid, Battleground, and Arena. Full clear tracking by last-boss kill for every Classic and TBC dungeon and raid through Sunwell, backed by an audited 372-boss lookup table.

Consume Compliance — At the start of every boss pull, PlayerTracker scans the buff bar of every group member and records whether each player had a flask, battle elixir, guardian elixir, food buff, weapon oil, and scrolls. Data is committed only on a successful boss kill. Over many sessions this builds a reliable percentage rate for each consume type per player.

Loot Economy — Every blue+ item that dropped while grouped (Seen), every item that player received (Got), and the Got/Seen ratio as a colour-coded percentage. Per-item loot history with item link, roll method, count, and time-ago. DE mats can be optionally excluded — the filter covers the full canonical Classic and TBC material list.

Roll Behaviour — Need, Greed, and Pass counts with percentages, captured from in-game roll messages. Ninja looters reveal themselves across dozens of runs without you having to remember a single incident.

Deaths — Death count via UNIT_HEALTH — works at range across a full 25-man raid. Deaths per group run, colour-coded red for chronic offenders, and broken down by content type in the expanded view.

Disconnects — Count of times a player transitioned from online to offline mid-instance, plus a per-run ratio. Note: WoW cannot distinguish an intentional /logout from a real network disconnect, so both count.

Roles — Tank, Healer, and DPS role counts captured automatically — what someone actually played, not what they claim. The Role column is sortable with a six-state cycle.

Relationships — Every player record includes the full set of other players you have ever run alongside them, plus shared quest completions as a measure of cooperation outside instances.

Player Ratings and Notes — Rate any player Positive [+], Neutral [~], or Negative [-] with a freetext note. Ratings feed into the Trust Score and appear throughout the UI and in world tooltips. Notes auto-stamp with the current date whenever you save them.

Peer Data (subscribed peers only) — For every active subscription, PlayerTracker stores the peer's view of every player you both know — their computed score, their role breakdown, their boss kills and clears per difficulty, their consume serialization. These contributions flow into the Community Trust Score column. Stored per-player under pd.peers[peerKey] and purged when the subscription ends.

PT Presence Cache — Every player you've ever exchanged any addon-comm traffic with (subscriptions, scan responses, addon-presence pongs) is recorded in PlayerTrackerDB.knownPTUsers with their version and a timestamp. Entries older than 60 days are auto-pruned at login. This drives the cyan + indicator in the name column and the PlayerTracker: vN (Nd ago) row in the detail view.

Trust Score

Every tracked player receives a Trust Score from 0 to 100, color-coded throughout the UI — green for reliable, yellow for neutral or unknown, red for consistent problems.

Score ranges

Components

Confidence blending — A player you have grouped with once should not score 95 or 5 on a single data point. The raw score is blended toward 50 based on group count — at 1 group the score is mostly neutral, fully raw at 10+:

final = rawScore × confidence + 50 × (1 − confidence)
confidence = min(1.0, groupCount / 10)

Rating modifier — Applied after blending. Positive adds 20 points. Negative subtracts 35. Always clamped to 0–100. Your direct judgement overrides the algorithm.

Detail view breakdown — Expanding any player row shows the Trust Score and the three factors that deviated most from their neutral baseline:

Trust Score: 71   Rolls:+11.0  Completion:+8.0  Deaths:-5.0

Guild Score

Every guild whose members appear in your database receives a computed Guild Score: a weighted-average Trust Score of every player you've grouped with in that guild, gated on minimum exposure.

Gate — Requires at least 3 distinct members with groupCount ≥ 1 AND a total groupCount across members of at least 10. Below that, no score is shown (insufficient data). This prevents a tiny sample from creating a misleading number.

Weighting — Each member contributes with weight min(groupCount, 10) — players you've grouped with extensively count more, but the weight caps so a single heavy-exposure player cannot solo-determine the guild score.

Display — In the main /pt window's Scores column, the Guild Score appears as g92 after the personal score. In the world tooltip it appears inline next to the player's guild name.

Community Trust Score

When you subscribe to other PT users (see Sharing & Subscriptions below), their measurements of every player blend with yours into a Community Trust Score.

How it's computed — For each player, the Community Trust Score is the average of:

• Your local ComputePlayerScore(pd) (counts as one contribution)
• Each subscribed peer's sentScore for that player (one contribution per peer)

Gate — Only shown when there's at least one non-local contributor (i.e. at least one subscribed peer has data on that player). With just your local view, the Community column is suppressed since it'd duplicate the personal score.

Display — In the main /pt window's Scores column, the Community Trust Score appears as c75 after the personal and guild scores. Three values total when all are available: 87 g92 c75.

Consume Score

The Consume Score is a separate 0–100 score that measures how consistently a player buffs up before boss pulls. It is captured passively — no other addon or cooperation required.

How it works — At the start of every boss pull PlayerTracker queues a buff scan for every group member. The scan is committed only when a boss kill is confirmed, so wipes are not counted. Over many sessions this builds a per-player percentage rate for each consume type.

Scoring

Scores for untested components default to 50 (neutral) so new data is not penalised. The Consume Score feeds into the Trust Score as the Consume component.

In the UI — The expanded Activity panel includes a Consumes row showing the score plus the rate breakdown:

Consumes:   26  Fl:29  Fd:70

The /pt Window

Open with /pt, /ptr, or /playertracker. The main list shows tracked players in a fully sortable table. Currently grouped players float to the top with a green [*] indicator.

Columns (v1.2d5 layout)

The % (loot drop rate) and Consumes columns that were in v1.10a's main row have been moved or removed. Consume score and rates now live in the expanded Activity panel; loot drop rate was retired as not very actionable.

Right-click a player name

Right-clicking any name in the list opens a single-purpose menu that keeps you out of submenus:

• Quick rating — set this player to positive, neutral, or negative directly from the menu. The change takes effect immediately and the row's colour updates on the spot. The auto-date stamp is applied on save.
• Add/edit note — freetext note field. Notes surface in the group-join warning, the world tooltip, and the expanded row. Notes are auto-stamped with (YYYYMMDD) when saved.
• Send Stats to… — post this player's stat line to Party, Raid, Guild, Say, or any channel you've joined (including custom channels like Trade or LookingForGroup). Colours are matched to WoW's default channel colours so the menu reads the way you expect.
• Subscribe to peer (full data exchange)… — initiates a subscription request with this player. They get a popup with your name + your Trust Score for them; they can accept, decline, or block.
• Whisper, invite, /who — one-click versions of the same actions the inline [W] and [I] buttons do.

This right-click menu is the fastest way to vet an applicant who you don't currently have in group: search for them, right-click the row, read the note, rate them, done.

Expanded player view

Left-click any row to expand inline:

• Trust Score with top three contributing factors
• Consume Score with full type breakdown (Flask / BElixir / GElixir / Food / Oil / Scroll)
• Note — click to edit, right-click for the full options menu
• PlayerTracker — version + age of cached presence info (e.g. v1.2d5 (2d ago)). Suppressed for own characters. Only shown when the player has an entry in knownPTUsers.
• ACTIVITY — date range, runs broken down explicitly per Normal/Heroic/Raid, deaths with per-type ratio, disconnects with per-run ratio, role history, quests, raid clears, Consumes (score + flask/elixir/food rates)
• LOOT / BEHAVIOUR — loot seen/got ratio, roll behaviour, Consumes appears under Rolls in the right column
• INSTANCE HISTORY — one dungeon per line, grouped by type
• SHOW LOOT — full paginated loot history with item links
• SHOW GROUPED-WITH — every player you have run alongside this person, with their score, and (if you have subscriptions) per-peer summaries of what each subscriber reports for that grouping

All sections default closed. Click any header to expand or collapse.

Tracking line on group entry

[PT] [~] Deathlord  8g N:6 H:2 R:0  RIP:2.50 dc:1 (13%)  6/1  17%  "ninja'd T5 helm, avoid"

Search filters

Click in the search bar to filter the list:

• class:druid — filter by class
• role:tank — filter by most-played role
• rating:+, rating:~, rating:- — filter by rating
• score:60 — score ≥ 60
• norm:5, hero:5, raid:3 — minimum runs per type
• item:nether — filter by received item name (single word)
• item:"Scryer's Bloodgem" — quoted phrase for item names with spaces
• dc:N — players with disconnects ≥ N

Header checkboxes

Title bar

When Stealth Mode is active, a [STEALTH] badge appears next to the title to remind you all addon-channel traffic is paused.

Bottom bar

Six buttons (positions: collapse left, sharing right):

The Utilities ▼ dropdown consolidates lower-frequency actions (Prune 90d and Import Character Notes) so they don't clutter the bar. Sharing... is also in the dropdown for completeness; it remains on the bar as a quick-access shortcut to the most common action.

Sharing & Subscriptions

PlayerTracker can optionally exchange ratings, notes, and trust data with other PT users you explicitly subscribe to. This is the foundation of the Community Trust Score column and the per-peer breakdowns in the detail view.

The model

There is no central server, no third-party hosting, and no anonymous broadcast. All data flows over WoW's CHAT_MSG_ADDON channel between two specific characters who have each accepted a subscription. Subscriptions are bidirectional — once accepted, both sides share their data with each other on equal footing.

Subscription lifecycle

   Alice runs /pt subscribe Bob-Realm
                  ▼
         [pending_outgoing]
                  │  SUB_REQ
                  ▼
         [pending_incoming]  (Bob's side, popup appears)
                  │  Bob clicks Accept
                  ▼
              [active]  ─── SUB_ACK + initial SYNC_REQ/DATA exchange
                  │
                  │  Alice runs /pt unsubscribe
                  ▼
              [ended]   (peer data fully purged via PTPurgePeerData)

Possible states:

• pending_outgoing — you sent SUB_REQ, awaiting their response
• pending_incoming — they sent SUB_REQ, awaiting your accept (visible in the Pending Requests tab)
• active — handshake complete, bidirectional sync running
• ended — you called PTUnsubscribe (peer data fully destroyed)
• stale — peer sent SUB_GONE (they dropped you); your local state remembers them with a Re-request button

How sync works

Three independent paths keep subscribed peers up to date:

1. Push-on-change — when you rate, edit a note, or click a rating dropdown, a single-record RECORD message goes out to every active subscriber immediately.
2. Login auto-sync — 30 seconds after PLAYER_LOGIN, a delta SYNC_REQ fires to every active subscription (skipping any synced within the last 5 minutes). Only records changed since the last successful sync flow on the wire.
3. Manual — /pt netsync or the Sync button in the Sharing dialog fires a delta SYNC_REQ to every active subscription immediately.

All traffic is paced at 2.5 messages per second through a single global queue, well under WoW's addon-channel rate limit. Long payloads are auto-chunked at 240 bytes and reassembled on the receiving end with a 60-second timeout.

Addon-presence detection

When you initiate a subscription, PlayerTracker also sends a lightweight SUB_PING probe. If the target has PT installed, their addon auto-responds with SUB_PONG carrying their version, which marks them in your knownPTUsers cache. If no pong arrives within 12 seconds, the target gets a single whisper:

[PlayerTracker] (automated) I want to share player-tracking data. Install
or upgrade to PlayerTracker v1.2+ at
https://www.curseforge.com/wow/addons/playertracker - ignore this if you have it.

The whisper covers both the "no PT at all" and "old PT version without ping support" cases. If they already have PT installed and updated, they get the popup instead — no whisper.

The Sharing dialog

Open via the Sharing... button or /pt sharing. Three tabs:

• Subscriptions — every subscription you have (active, pending outgoing, stale). One row per peer with their score, role, dungeon/raid stats, and management buttons (Unsubscribe, Re-request). Click Subscribe to new peer... at the bottom-left to initiate a fresh subscription. Sync force-syncs every active subscription.
• Pending Requests — incoming SUB_REQs awaiting your decision. Accept, Decline, or Block. Each row shows the requester's local Trust Score for context.
• Block List — peers whose requests are silently dropped. Click Add to Block List... to pre-block a player by name before they ever send a request. The Block ALL incoming subscription requests checkbox at the bottom-left blocks everything regardless of source.

The dialog defaults to the Subscriptions tab on every open.

Subscription data handling

When a subscription becomes active, the two clients exchange every player record they have on file (the initial sync). After that, every rate/note edit pushes a single-record update in real time, and the login auto-sync catches up anything missed while either side was offline.

When you unsubscribe (or the peer drops you), all of that peer's contributions to your local DB are surgically removed via PTPurgePeerData: the pd.peers[peerKey] slot is wiped on every player record they ever sent. Your own data is unaffected. Their Trust Score column entries that depended on peer averages recompute automatically.

Peer Discovery

Three explicit slash commands let you discover who else in your group/raid/guild is running PlayerTracker:

/pt scan guild     — broadcasts VER_REQ to your guild
/pt scan raid      — broadcasts VER_REQ to your raid
/pt scan party     — broadcasts VER_REQ to your party

Each requires you to actually be in the named context. After broadcasting, the scan collects responses (VER_RESP) for 8 seconds, then prints results to chat:

[PT] Scan complete: 3 PT users in GUILD:
   + Sugarpuffz   v1.2d5  (you)
   + Alice        v1.2d4
   + Bob          v1.2d

Yourself is always included with a (you) suffix so the count is honest. Results are cached in PlayerTrackerDB.knownPTUsers along with their version and a timestamp. Cache entries last 60 days; any subsequent inbound addon traffic refreshes the timestamp.

/pt users — the PT Users window

/pt users opens a windowed view of every cached PT user with their version and "Nd ago" age, sorted by most-recently-seen. The window has a Re-scan group/guild button that runs /pt scan (auto-picking the most-populous context: party > raid > guild) and refreshes the list when results arrive.

Indicator in the main /pt list

Every player in knownPTUsers (and not your own character) shows a cyan + prefix on their name in the main /pt window. Combined with the green * subscription indicator, you get four visual states:

• *+Alice — subscribed AND has PT (most subscriptions land here)
• +Bob — has PT, not subscribed (a discovery candidate)
• *Charlie — subscribed, presence cache empty (rare, usually old data)
• Dave — no PT info / never scanned

Indicator in the detail view

Expanding any cached PT user's row adds a PlayerTracker: v1.2d5 (3d ago) line in the Activity panel showing what version they were running last time you saw them.

Stealth Mode

/pt stealth on|off|status toggles a global pause on all PT addon-channel traffic.

While stealthed:

• All outbound traffic is silenced. No SUB_REQ, no SUB_PING, no RECORD push, no SYNC_REQ.
• All inbound traffic is dropped silently. No SUB_REQ popups, no inbound RECORD/SYNC, no VER_REQ scan responses.
• A [STEALTH] badge appears next to the /pt window title.
• /pt scan refuses to start, with a chat warning.
• Subscriptions stay intact and are not affected. They just pause.

On disable (/pt stealth off):

• A chat message confirms stealth is off.
• A SyncAll automatically fires to every active subscription. The existing delta-sync filter ensures subscribers only receive records that actually changed during the stealth window — pd.lastUpdated is still stamped on rating/note edits during stealth, even though nothing went on the wire.

Side effect to be aware of: while stealthed, peers attempting to subscribe to you will time out on the SUB_PING probe after 12 seconds and whisper you the download link, since from their side you look identical to "no PT installed." This is intentional — stealth means looking opaque.

/pt stealth          toggle on/off
/pt stealth on       enable
/pt stealth off      disable + auto-sync subscribers
/pt stealth status   show current state

Privacy — what other players see and don't see

Your PlayerTracker database is local. It lives in WTF/Account/<youraccount>/SavedVariables/PlayerTracker.lua and is never transmitted anywhere unless you explicitly subscribe to another PT user. Ratings and notes are yours alone by default.

The exceptions to silent operation are:

1. Announce PT (checkbox, on by default) — entering a new instance posts a brief banner to party/raid chat showing how many groupmates are already in your database. With this off, the addon never auto-announces anything.
2. Subscriptions (opt-in per-peer) — when you accept a subscription, your full player database is synced with that peer, and ongoing rating/note changes are pushed to them in real time. The only way data leaves your client is via an active subscription you accepted.
3. Scan responses — when another PT user runs /pt scan in a channel you're in, your addon responds with your version (no other data). Stealth Mode silences this.
4. !ptwho / Send Stats / Party Report — explicit user-driven posts of player stats to chat channels.

Your ratings, notes, and raw data remain private regardless of Announce PT's setting, unless you've actively subscribed to share with specific peers.

!ptwho — In-Chat Queries

Any player in your guild, party, or raid can type !ptwho Playername in chat and PlayerTracker will respond in the same channel with a full stat line:

[PT] [+] Sugarpuffz [95] | N:30(47%) H:25(60%) R:4(100%) | RIP:0.74 N:0.03 H:0.32 R:1.50 dc:1 (3%) | Consume:78 Flask:89% Food:72% | Loot:46/193(24%)

The response is plain text, safe for all channels. A 3-second per-name throttle prevents spam. The name lookup is case-insensitive. The requester always sees a local echo with full color formatting regardless of whether the channel send succeeds.

CharacterNotes Import

If you have been using the CharacterNotes addon, /pt importcn (or Utilities ▼ → Import Character Notes) will migrate everything into PlayerTracker in one pass:

• Imports all text notes — non-destructive, skips players where you already have a PT note
• Imports ratings (CharacterNotes positive/negative map to PT positive/negative) — only applies to players with a neutral or unset PT rating
• Creates new records for every imported player, even those you have never grouped with — so your existing reputation database is fully preserved
• Handles both flat and AceDB-nested CharacterNotes database structures automatically
• Reports a summary: Character Notes import: 47 notes 3 skipped 12 ratings

Safe to run multiple times — it's idempotent.

Commands

Slash commands

In-chat command

Aliases

/ptr · /playertracker