PugProofSign in with Battle.net

Mythic+ conduct signals

Know the group before the key starts.

One bad review isn't a signal. One failed run isn't a signal. One guild's grudge isn't a signal. PugProof only surfaces conduct that's repeated, independent, and corroborated — never skill, never public comments, never a blacklist.

Full lookup →·How we keep it fair

Reading the signal

Six plain-language states. No raw scores.

The addon and site only ever show an aggregate state — never a toxic score, raw averages, or rater names.

Hall of fame

This season's standout teammates.

Players most often marked as great teammates across independent verified runs. Positive recognition only — there is no public worst list, by design.

Illustrative · live once uploads begin
Weighted by independence

A public caution needs at least 3 independent incident clusters, from 3 distinct raters, across 2+ different days, within 90 days. Four players from one wipe count as one cluster — not four reports.

Comments never go public

Typed notes are visible to moderators only. They're scanned for slurs, threats, and personal info, and are never exported to the addon or attached to a public signal.

Everything decays

Signals fade with time — roughly a 90-day half-life — so a rough patch doesn't define someone forever. Appeals exist before any public caution is shown.

Boundaries

What PugProof is not.

The design says no to the things that turn reputation tools into harassment tools.

How the data moves

Local capture, server-side weighting, cacheable lookup.

Evidence is gathered on your machine and moved by a companion app — the way Wowhead and TSM do it — so gameplay stays smooth and the public signal is just a snapshot.

  1. Addon records local group rosters and post-run ratings on your machine
  2. Companion app uploads validated batches to the API
  3. Server separates private notes from public, weighted signals
  4. Worker clusters incidents and exports a cacheable snapshot