TBC Anniversary support

[entroscopy]

Doesn't work in TBC Anniversary. Worked in Classic Anniversary. Throws following on login:

Date: 2026-02-16 16:01:31
ID: 1
Error occured in: Global
Count: 1
Message: Interface/AddOns/KillTrack/KillTrack.lua line 33:
   attempt to call global 'GetAddOnMetadata' (a nil value)
Debug:
   [Interface/AddOns/KillTrack/KillTrack.lua]:33: in main chunk
Locals:
NAME = "KillTrack"
KT = <table> {
 Tools = <table> {
 }
 Name = "KillTrack"
}
NO_NAME = "<No Name>"
(*temporary) = nil
(*temporary) = "KillTrack"
(*temporary) = "Version"
(*temporary) = "attempt to call global 'GetAddOnMetadata' (a nil value)"

AddOns:
  Swatter, v12.x.x (Midnight)
  KillTrack, vv2.31.0
  BlizRuntimeLib v2.5.5.65895(EU) <enUS>
  (ck=5d)

[ButteredGroove]

I can reproduce this on TBC Anniversary.
Root cause is API mismatch: some clients expose GetAddOnMetadata/IsAddOnLoaded as globals, others under C_AddOns.

A cross-client fix is to use compatibility shims in KillTrack.lua:

local GetAddOnMetadata = (C_AddOns and C_AddOns.GetAddOnMetadata) or _G.GetAddOnMetadata
local IsAddOnLoaded = (C_AddOns and C_AddOns.IsAddOnLoaded) or _G.IsAddOnLoaded

KT.Name = NAME
KT.Version = (GetAddOnMetadata and GetAddOnMetadata(NAME, "Version")) or "Unknown"

And later:

if IsAddOnLoaded and IsAddOnLoaded("Glamour") then
    ...
end

This fixes the login crash (attempt to call global 'GetAddOnMetadata' (a nil value)) on Anniversary while keeping compatibility with clients that use C_AddOns.

I made these changes to the install of KillTrack in my Addons folder and it works now. I only tested using TBC anniversary.

[ButteredGroove]

Looks like fixes for this are sitting in PR #39 👍