Parse combat events only from the ClassicAPI combat log

Browse Source

The combat log detection flags started false and only flipped when the
first matching combat log event arrived, so the first buff, hit, heal,
DoT or kill of a session was shown twice: once from the CHAT_MSG text,
once from the combat log. ClassicAPI is required, so drop the flags and
every CHAT_MSG parser they gated, keeping chat parsing only for power
losses, item buffs, honor, reputation, skill and XP.

Keep every CHAT_MSG event registered for search pattern triggers, which
re-registers CHAT_MSG_SPELL_AURA_GONE_SELF so buff fade triggers fire
again. Delete the now-dead parsers, ParseForPartialActions and the
stray global MikCEL_ParseForOutgoingHits.

...

This commit is contained in:

Brues

2026-10-28 17:57:44 -05:00

parent 6f50252d8e

commit a506dcf7d2

2 changed files with 20 additions and 2773 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

MikScrollingBattleText/MikCombatEventHelper.lua

+17 -2770

File diff suppressed because it is too large Load Diff