GETGUD TRACKER — GUILD BETA NOTES
=================================

Thanks for testing this.

This is a real beta:
I am specifically looking for weird class/spec behavior, report inaccuracies,
UI problems, and anything that breaks during actual raid/dungeon play.

Please do not spend a bunch of time configuring around something that looks
wrong. If it feels wrong, report it.

Best feedback format:

Class / Spec:
Content:
What happened:
What you expected:
Screenshot (if possible):

Useful examples:
- "This passive showed up as a tracked spell."
- "My boss pull ended 8 seconds late."
- "This pack got split into two reports."
- "Potion usage didn't show up."
- "Keybind labels are wrong on my setup."
- "Uptime says 72%, but the gap list does not explain why."
- "The addon used way more CPU after 30 minutes."

Current build:
v0.10.3 Guild Beta

Author:
NRML

Tagline:
Press buttons. Find gaps. Get better.


v0.10.2 item-use check
----------------------
- Carry a combat potion in your bags.
- Open Spells before using it.
- It should appear under Items / Trinkets and default Tracked.
- Use it during a pull; it should remain under Items / Trinkets.
- It may appear on the visual timeline, but it must NOT change mechanical
  gap/uptime math.


v0.10.3 group telemetry feedback
--------------------------------
Requires at least two players running v0.10.3.

Test:
- both players use a combat potion
- one player Lusts / uses drums
- check the same pull on both clients
- finish an M+ before deciding queued sync failed

Please include:
- number of GetGud users in the group
- total group size
- content type
- whether sync appeared immediately after combat or only after M+ completion

Most important failures:
- wrong player attributed to a potion/Lust
- same event counted twice
- events assigned to the wrong boss/trash pull
- telemetry coverage number is wrong
- queued M+ events never appear after completion
- addon-message spam/throttle errors
