Opponent dossier: one player in depth

Finding opponents and saving rivals

Open Opponents to compare Rivalries beside your verified MMR impact. Nemesis has the lowest 95% Wilson upper bound among opponents with at least four decided games; Favourite has the highest lower bound. These bounds temper small records. Most played counts meetings, while Hot rematch requires at least two recorded meetings in the past seven days. The cards respect the current filters and grouping; incomplete recent coverage stays unavailable.

1. 1
   Select a star on an opponent row, phone card or dossier header. Up to 50 players are saved privately to your account, using known linked identities rather than display names.
2. 2
   Choose Rivals for one card per saved player, with your record, last meeting, streak and usual opener. This view groups the player's accounts while preserving your table grouping choice for other views. Stars remain saved when a filter hides their games.
3. 3
   Read the sample labels: streak and usual opener use at most 20 recent matching meetings across a bounded 500-account batch. A 20+ streak is a lower bound. Sparse or unlabelled history stays unknown.
4. 4
   Pulse 30-day movement refers to the displayed primary account, using real observations near each boundary and a six-hour cache. The exact dates and cache age are available on the card. Missing observations or busy public lookups stay unknown.

Live now appears only when a fresh public viewer-cache observation confirms the approved channel is live. Its observation time is in the badge title. The list does not start live-status requests or poll providers; no badge can mean offline or unknown. A starred opponent also receives the RIVAL tag in the overlay when their identity matches; a matching display name alone cannot set that tag.

Regulars selects players with at least five games; Played this week means a meeting in the past seven days; Lost to most sorts by losses, highest first, and highlights that choice. All opponents returns to Last played, newest first, while keeping your search and other filters. These are separate from Rivals. On phones, Sort opponents includes Wins, Losses and the same sortable fields as the table; its direction button reverses the selected field. Cards are real dossier links, with notes and alias disclosures outside the link; returning restores the recorded list window and position. On desktop, Race shows the group's recorded races and sorts by its most recent account's race. Region badges use recorded region or the toon region.

Columns remembers this device's choices. Pulse ID, MMR won and MMR lost start hidden; Last MMR and Net MMR also start hidden without verified pairs. The Net MMR tooltip contains both won and lost totals. Reset restores the default columns and local list controls. The list starts with 100 rows, including expanded account rows; Show 100 more extends the same window on phone and desktop.

Export CSV beside the list heading downloads every matching, sorted row, including rows outside the render window. Grouped rows include merged accounts. The file includes its filter scope and export time, UTF-8 BOM, quoted text and a spreadsheet formula guard; measured negative MMR stays numeric. The Notes preview column contains the list's bounded private preview. Incomplete lists must finish loading before export.

The dossier's All replays export follows its analyzer dates, account and other filters, linked-player choice, local map/build/strategy selection, result filter and an explicitly selected analyzed sample. It exports up to 5,000 matching games, newest first, across all table pages; a status message discloses truncation. It shares the replay library's serializer and once-per-minute account limit. Hidden and pending-deletion games are excluded. See CSV columns.

Click any row in Opponents to open that player's dossier. It is private to you and built only from your own games against them, filtered by the filter bar like the rest of the analyzer.

What's on the page

Read or copy the brief

The brief starts with your record in the current dossier scope. It keeps sample counts visible and omits missing facts. Copy brief copies those lines; if clipboard access is unavailable, select and copy the text in the field. The all-time series beside the header uses stored meeting dates, so the oldest loaded replay is never presented as your first meeting. For large histories, streaks say that they use the latest 1,000 meetings, best streaks are labeled as sampled, and a current streak reaching the sample boundary is a lower bound.

The sticky section chips follow the section on screen. Tendencies puts H2H charts before map and strategy rows, then predictions. History keeps replays directly above your notes. Ladder combines current race ratings and ladder context. Identity & data quality starts collapsed for normal profiles and opens automatically for an unrevealed barcode or unresolved account.

Read the key timings and phases

The Timings section loads detailed analysis when you reach it, alongside Likely strategies next. It shows how many games were analyzed and whether the metadata or replay-detail sample is capped. Needs build orders: 4 of 9 games have one means only four analyzed games contain a recorded order for the selected perspective; missing recordings are not treated as zero-time builds. Likely strategies next has its own scope: recent matching meetings across all dates, independent of the analysis date window and local history selections.

Choose a matchup and Theirs or Yours. Rows need at least two observations. The median and middle-half bar summarize the recorded first timing; the shared axis ends at 10:00+, while the recorded clock remains visible. Last seen is the clock in the latest sample. Trend arrows say getting earlier, getting later or stable. The win-rate label and n describe the games where that timing was recorded.

Select a timing row to filter History to its linked analyzed games. Its chip uses the same clearable dossier filter bar as map and strategy selections. The replay card says Analyzed sample replays. Game links retain that sample context without putting a long list of replay IDs in the URL. On an individual game, choose Use selected scope to enable standard Older/Newer navigation, or return to History to choose another sampled replay.

The same detailed request supplies your game-phase trajectory, recorded compositions and transitions. These cards describe the analyzed sample shown in the scope line. Missing detail or a failed analysis does not prevent the brief, metadata history or notes from loading. Keep the desktop app up to date and use its replay re-sync when older games need build orders.

Narrow it down

The scope line shows the analyzer filters used here. Show all time removes the date and patch window for this dossier only; it leaves the global filter bar unchanged. Use analyzer dates restores that window. If this range has no games but your recorded history has some, the page shows the last meeting date and offers Show all time. Leaving the opponent resets the override.

Click a map, their strategy, or a build pairing to narrow the dossier. The active filters stay visible under the header. ‘(filtered)’ labels mark the narrowed stats; remove one chip or use Clear all to widen the view. A selected strategy and build pairing replace one another. Timings and phase cards keep the analysis scope shown above them. Likely strategies next keeps its separate all-date recency scope. Large histories explain when the filtered summary uses the latest analyzed games; replay history searches the full matching history unless a timing sample is selected.

Scouting notes and read-aloud

• The replay history sits directly above your notes in History. The list also shows a private note preview, and its Has notes toggle finds opponents you have written about.
• Press Ctrl+Enter (or Cmd+Enter on a Mac) in the editor to save. A failed save keeps your text and offers Retry. The 500-character limit stays the same; the counter appears below 100 characters remaining.
• Unsaved drafts stay in this browser tab and restore when you return to the same opponent. Discard returns to the saved note. Following All opponents or the breadcrumb asks before discarding unsaved work; Keep editing is the default action.
• Write what you want to remember, for example Hides tech after early pressure, and press Save notes. Notes are private.
• When the desktop app detects this player at the start of a game, your notes show on your private scouting overlay.
• Turn on Read notes aloud to hear them at the start of the game too. It needs the voice readout on, with Scouting report (pre-game) ticked: see Voice readout.

Pulse ID or MMR missing

SC2 Tools looks up each opponent on SC2Pulse to find their Pulse ID and current MMR. Until that works, the header shows their toon instead of a Pulse ID, and MMR and ladder context stay empty.

1. 1
   Open Identity & MMR diagnostics on the dossier. It shows whether their Pulse ID was found, their toon, region and when MMR was last fetched.
2. 2
   Press Retry SC2Pulse there. It asks SC2Pulse again right away, then refreshes the profile, ladder panels and channel links together.
3. 3
   If it's found, the Pulse ID, MMR and ladder context fill in, and your older games against them are updated too. If it still isn't, SC2Pulse doesn't list the player yet, often because they haven't played enough ranked games this season. Try again later.

Select Data looks wrong? beside the Pulse account line to open diagnostics inside Identity & data quality. An unresolved account opens this panel automatically; missing MMR alone does not. Its summary separates a profile SC2Pulse has not found from one with no current ladder rating. Retry SC2Pulse refreshes the profile, ladder panels and channel links together. A busy analysis retries with increasing delays; a missing record says Not in your history, while network failures keep a Retry action.

The replay card's Show filter selects all results, wins or losses without changing the header stats. Its Map selector shares the dossier's map filter. If older or newer pages exist, sorting by a field other than date applies only to the currently loaded page; the caption makes that limit explicit.

Barcodes and real identities

A barcode is a name made only of look-alike characters such as IIlIlI, used to hide who's playing. When SC2 Tools knows who it is, from SC2Pulse or from an identity confirmed by our team, their real name shows next to the barcode.

• Possible identity matches compares this barcode with the players in your own replays: build patterns, control groups and replay actions. These are private leads, never proof, and the panel says how strong the evidence is.
• Know who it is? Open Identity & data quality, select Know who this is? Suggest an identity, then pick their known account and explain the match in at least 10 characters. Press Submit for review. The form stays collapsed until requested for ordinary accounts.
• An administrator checks the evidence. Once approved, the identity shows for everyone. Your submission shows Awaiting review, Approved or Not approved, with a note from the reviewer.

The public profile

Once at least 5 different SC2 Tools players have faced this opponent, a Community profile button appears in the header. That page is open to everyone and combines all of those players' games: race, record, strategies seen and maps, counted from the opponent's side. It never shows names, battle tags, or who contributed.

Group the same player

Group same player is saved to your signed-in account from the list or dossier, and also applies to live scouting across devices. Approved shared identities and already-cached Battle.net account links combine up to 20 of your accounts within your own history. The header lists their names and records. First/last meeting dates span those accounts; notes remain attached to the exact current account. A matching name alone never merges players. See alternate accounts.

How much data it needs

• Everything works from one game, but tendencies and predictions mean little until you've played someone a few times.
• Map rows with fewer than 2 games are marked as a low sample in H2H trends.
• Likely strategies next uses the shared recency/map-weighted opening forecast, with effective n, a confidence label and count-only reasons. Its explanation describes the fixed formula and optional three-game cached ladder prior. An incomplete source stays unavailable. See how the forecast works.

Every number comes from replays with fixed rules, never AI. To read the list of all your opponents, see Opponents.