File Details
v4.6.7-TBC-bcc
- R
- Feb 20, 2026
- 804.69 KB
- 6
- 2.5.5
- Classic TBC
File Name
xCT_-v4.6.7-TBC-bcc.zip
Supported Versions
- 2.5.5
xCT+ TBC Classic
v4.6.7-TBC (2026-02-20)
Full Changelog Previous Releases
- Clean up .pkgmeta: remove move-folders for deleted xCT+Options
- Remove xCT+Options — dead code, never loaded
LoadOnDemand addon that nothing ever called LoadAddOn() on.
All options code lives in modules/options.lua as part of the main addon. - Fix release packaging: move xCT+Options to top-level addon folder
Added move-folders to .pkgmeta so the BigWigs packager correctly
places xCT+Options as a sibling of xCT+ in the zip, rather than
nested inside xCT+/xCT+Options/ which WoW can't load. - v4.6.7-TBC: Fix combat damage not displaying in real combat
Two bugs identified and fixed:- xCombatParser playerGUID nil race condition
- playerGUID is a local upvalue initialized to nil, set only when
PLAYER_ENTERING_WORLD fires on the library's private frame. - In edge cases (timing, reload order), playerGUID stays nil,
making args.isPlayer always false, silently dropping all
outgoing/incoming damage/healing events. - Fix: lazy-init playerGUID in CLEU handler if nil.
- Fix: fallback in x.CombatLogEvent to use x.player.guid as
backup for both isPlayer and atPlayer checks.
- playerGUID is a local upvalue initialized to nil, set only when
- ShowAbsorbs() nil call in OutgoingMiss handler (regression from v4.6.6)
- ShowAbsorbs() was renamed ShowOutAbsorbs() in v4.6.6 but
OutgoingMiss still called the old name, causing Lua error on
any absorb miss event. - Fix: updated call to ShowOutAbsorbs().
- ShowAbsorbs() was renamed ShowOutAbsorbs() in v4.6.6 but
- xCombatParser playerGUID nil race condition

