Troubleshooting

Troubleshooting

"A skill never reacts"

1. Check it's actually enabled on the relevant Skills panel (see Settings), and that the addon itself is on (/gabbarp on).
2. Turn on /gabbarp triggerdebug on, cast the skill a few times, then /gabbarp debuglog. This prints exactly why each attempt did or didn't produce a line, disabled, per-skill cooldown still active, blocked by the global spam gate, the random chance roll didn't hit, or no lines configured at all. Turn it back off (triggerdebug off) once you're done, it's noisy.
3. If the log shows nothing at all for that skill, it may not be one GabbaRP recognizes yet. triggerdebug also logs every combat-log event you personally trigger, not just recognized ones, which is the fastest way to see exactly what an unfamiliar skill or item actually fires as. Open an issue with that output if it looks like a genuinely missing skill.

"Imp Backtalk never fires"

/gabbarp impdebug on logs every nearby monster Say/Yell your Imp's own line gets compared against (not just your Imp's, every monster's, so expect noise). Turn it off again afterward.

"The wrong language is being spoken" (Local Language)

/gabbarp greetdebug on logs the language decision itself (solo/group-majority/guild-check, whichever applies) every time a line or greeting fires, including the guild-membership counts it computed. See Local Language for what the rules actually are before assuming it's a bug, the group-majority and per-target-welcome rules are easy to misremember.

Known limitation: Say/Yell and mouse clicks

Blizzard requires a real click or keypress before an addon is allowed to send a Say/Yell chat message, there's no way around this. By default (Safe delivery, see Settings), GabbaRP queues the message and sends it on your next real action (a skill or item use), so nothing gets eaten, just possibly a beat slower. The separate Instant delivery option trades that off for near-zero delay by capturing your very next click or keypress anywhere instead, for mouse players, that means one click gets "eaten" doing this instead of whatever you actually clicked (e.g. your next action bar press won't register, the queued message sends instead, and the button works normally on the click after that).

This only matters if you have a skill configured to send Say or Yell specifically (Emote, the default for most skills, isn't affected) while Instant delivery is selected. GabbaRP shows a one-time popup at login if any of your currently enabled skills are set that way. Switch the skill back to Emote in the line editor, or stay on Safe delivery, if this bothers you.

Reporting a bug

/gabbarp report prints a copy-pasteable diagnostic summary (addon version, schema version, client build, your class, and your current General settings), include it when opening an issue. If it's a "this specific line/skill is wrong or missing" report, a triggerdebug/debuglog snippet showing the actual combat-log event (see above) is the single most useful thing you can attach.