CLASSIC ERA / HARDCORE · OPEN COMMUNITY DATA
Every proc.
Part of a bigger picture.
Collect your observations. Compare Open World, dungeons and raids. Help build a dataset we can all inspect.
Community observations — not verified combat logs or proof of different proc chances.
THE DATASET
Compare the observations
| Effect | Area | Total procs | Combat minutes | Procs / combat minute | Contributors |
|---|
Rates use total combat procs ÷ total combat time. Zero-proc fights count. Exposure can overlap across effects; it is not unique playtime.
A higher bar is an observation, not a verdict.
Attack speed, targets, equipment and ability choices influence rates. This version does not count eligible hits, estimate proc probability or calculate confidence intervals. Extreme rates are quarantined, but plausible fabricated numbers cannot be reliably detected.
CONTRIBUTE
Your next proc can help.
Install the addon
GabbaProcTracker records your own effects. The companion reads only the saved export after a reload or logout.
Get the addon ↗Connect the companion
Find WoW automatically, choose characters and enable uploads. App packages and signed updates are hosted on GitHub.
Companion downloads ↗Choose what you share
Without names is the default. You can explicitly share your character name and realm. Uploading is optional and can be paused.
See the exact data policy ↓Join the initial data collection
The first version uses single-use operator invitations to limit abuse. Enter your invitation to receive an upload token. Paste it into the companion; never post it publicly.
OPEN SOURCE. EXPLICIT CHOICES.
Know exactly what leaves your computer.
What is sent
Effect IDs, area groups, counters, combat exposure, retained segment data, export time and persistent collection/character identifiers. Name and realm only in named mode. No account folder names, local paths, chat, inventory or entire SavedVariables file.
Without names ≠ untraceable
Persistent identifiers make these data pseudonymous. IP addresses are processed for network delivery and abuse limits. Named contributions can reveal a character's identity. Removing a name cannot erase copies someone already downloaded.
How data are checked
Lua is parsed as data, never executed. The server checks sizes, known effects, counters, ownership and duplicate snapshots. Public statistics include accepted community submissions, not independently verified gameplay. Suspicious data are withheld.
Storage, deletion and limitations
Private daily backups expire after seven days; deleted contributions may remain in those backups until then. We retain the latest cumulative totals and up to 301 supplied history segments per collection. The public API does not expose character UUIDs, device tokens or detailed timestamps. A valid device token can hide stored names or delete its contributions and revoke itself. Contact the operator for device transfer. History gaps remain possible. Authentication tokens are stored hashed on the server. The app prefers the system keychain and does not silently fall back to a plaintext token file.