12.0.008
Details
-
Filenamedgks-12.0.008.zip
-
Uploaded by
-
UploadedNov 20, 2026
-
Size1.28 MB
-
Downloads837
-
MD5bb05b749f42cb41e1f1f48eeea0ececb
Supported WoW Retail Versions
- 12.0.1
- 11.2.7
- 12.0.0
- 11.0.2
Supported WoW Forever Versions
- 1.60.1
Supported WoW Mists of Pandaria Classic Versions
- 5.5.3
- 5.5.0
Supported WoW Cataclysm Classic Versions
- 4.4.2
Supported WoW Wrath Titan Reforged Versions
- 3.80.0
Supported WoW Wrath of the Lich King Classic Versions
- 3.4.5
Supported WoW Classic Versions
- 1.15.8
Supported WoW Burning Crusade Classic Versions
- 2.5.5
Changelog
lightweight tag 3b7a754e7d463c5fb66b8567f33456eaca2fdf34 12.0.008
Author: GitHub <[email protected]>
Date: Fri Nov 20 15:45:34 2026 -0800
commit 82a91985ece18aeaf01a9cc9b0e1eac4563fab7d
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 15:13:09 2026 -0800
Detect kills and killers in battlegrounds
The likely-killer guess compared "unitNtarget" with UnitIsUnit, which
always returns a secret for compound tokens on retail, so it never
matched. It now compares UnitGUID of the enemy's target with ours; the
player cache uses the same GUID check.
Killing blows by party and raid members on other players (PARTY_KILL on
retail, the combat log on Classic) are recorded as team kills, with the
killer's name, class and spec. They never count toward our own stats.
Team kills by guild members are shared and count as that member's kill
in the guild views, with duplicate reports of the same kill, and the
killer's own record of it, counted once. An option turns them off.
History sync now runs during battlegrounds, arenas and open-world combat,
and waits only during chat messaging lockdown or in dungeons, raids and
scenarios.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit 82a91985ece18aeaf01a9cc9b0e1eac4563fab7d
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 15:13:09 2026 -0800
Detect kills and killers in battlegrounds
The likely-killer guess compared "unitNtarget" with UnitIsUnit, which
always returns a secret for compound tokens on retail, so it never
matched. It now compares UnitGUID of the enemy's target with ours; the
player cache uses the same GUID check.
Killing blows by party and raid members on other players (PARTY_KILL on
retail, the combat log on Classic) are recorded as team kills, with the
killer's name, class and spec. They never count toward our own stats.
Team kills by guild members are shared and count as that member's kill
in the guild views, with duplicate reports of the same kill, and the
killer's own record of it, counted once. An option turns them off.
History sync now runs during battlegrounds, arenas and open-world combat,
and waits only during chat messaging lockdown or in dungeons, raids and
scenarios.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit bd941989f662f9dfcced5e018a3da7a64d9af130
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 14:47:28 2026 -0800
Remove the old emote token file
dgks_emotes.lua only set EMOTE1_TOKEN to EMOTE415_TOKEN globals on
Classic-family clients, overwriting globals the game defines itself.
Nothing in the addon reads them, and the emote choices now come from
dgks_emotelist.lua.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit bfafb355bb0207d58be1c27dad66ddc7565c1380
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 14:44:46 2026 -0800
Offer every targetable emote in the emote choices
The killshot, duel win and duel loss emote choices were three hand-written
lists that missed over 100 targetable emotes and offered five slash-command
aliases (BELCH, BLOWKISS, DOOM, KNUCKLES, SMELL) that DoEmote ignores.
They now share one list generated from the game's EmotesText and
EmotesTextData tables for retail, Classic Era, Mists Classic, TBC
Anniversary and Forever: 241 emotes on Classic-family clients and Forever,
plus 11 retail-only ones on retail. Saved choices are repaired at load:
aliases become their emote and anything the client cannot do resets to
the default.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit 1a079b1519d2d737a79b9c83c3089cf1840b4fe2
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 14:36:19 2026 -0800
Record class, spec and location with kills and deaths
A player cache remembers other players seen on the target, focus,
mouseover, nameplates, arena frames and (Classic) the combat log, with
GUID, class, race and level. Nearby enemy players are inspected quietly,
at most one every 2 seconds and never while the Inspect window is open,
to cache their spec; an option turns this off.
Kill and death records now store the opponent's class, race, level and
spec where known, and the author's spec. Killers named only by the Death
Recap are looked up in the cache by name. Location is the zone and
subzone, shown as "Subzone, Zone".
History lists show spec and class and a Location column, tooltips show
both players in full, and the death recap window's title names the
killer's spec and class and its subtitle the location.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit b8e5e8236512d973373ec3132f6218f7204a1510
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 14:27:02 2026 -0800
Put stats, history and settings in one tabbed window
/dgks and the minimap button now open a single dG KillShot window with
Overview (record and streak tiles, Top 5), History (the five history
tabs) and Settings tabs. Settings has sub-tabs for General, Broadcasts,
Duels, Screenshots, Ranks, Text Output and History; the reset buttons
moved to Settings > History. The window remembers its last tab, and
Escape closes it.
/dgks history and /dgks settings open the window on those tabs; minimap
right-click opens Settings. Blizzard's Settings panel keeps one page with
a button that opens the window, replacing the seven sub-pages.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit bd9219d1bb25f5d420c94997814c69023e15a803
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 14:06:01 2026 -0800
Add a death recap window that opens when you die
Lists the damage taken in the last 10 seconds, oldest first and ending
with the killing blow: time before death, ability with icon, attacker,
damage (crits marked) and health after the hit. Hovering a row shows
overkill, absorbed, resisted and blocked amounts.
On Classic the hits come from the combat log. On retail and Forever they
come from Blizzard's Death Recap, which keeps only the last few hits;
secret values there are displayed as handed over and never calculated
with. A General option turns the window off, and /dgks deathrecap
reopens the last recap.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit 92cb6048d92dcfbce7bdf7becce205689503a1fa
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 14:00:27 2026 -0800
Explain unknown killers and record the likely one
The Death Recap is now read the way Blizzard's own frame reads it: the
first event caused the death, and hideCaster hides its caster. An empty
recap is retried for up to 5 seconds.
When no killer can be named, the death records why instead of "Unknown
because of retail": Hidden by the game, Hidden attacker, Environment or
No death recap. These and the old unknown texts stay out of Top predators,
the opponent tabs and player tooltips.
When the recap is hidden or empty, an enemy player who was targeting us
when we died (or turned to us in the last 8 seconds) is recorded as the
likely killer, labelled "(likely)". It can be turned off.
/dgks recap prints the raw recap of the last death, with hidden values
shown as such.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit aec7ba6a7f9cb2f720ef38a433f6c9ae28c43921
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 13:48:40 2026 -0800
Add a Guild opponents tab to the history window
One row per enemy the guild has fought: guild kills, deaths and duels
against them, how many members fought them, the top killer and when they
were last seen. Hovering a row lists each member's record against that
enemy. Search matches the enemy or a member. Opponent names are matched
across realm spellings, as in the player tooltips.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit 776ffe094274c38adef4baa9b915a63344ec2f93
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 13:40:33 2026 -0800
Add a minimap button
A skull button on the minimap edge: left-click opens the history window,
right-click opens the options, drag moves it around the minimap (round or
square), and hovering shows kills, deaths, K/D and streaks. On retail the
same actions are available from the Addon Compartment. A "Show minimap
button" option on the General page hides it.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit 1782a6f0dc87c1ab1848bb9dca8b790c165f84bb
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 13:35:20 2026 -0800
Show history on the main page and in player tooltips
The main dG KillShot page now opens with stat tiles (kills, deaths, K/D,
duels, current and best kill streak, current and worst death streak) and
side-by-side Top 5 prey and predator lists with ranks and class colours,
all read from personal history. The history settings moved from their own
page into a History section on the main page, replacing the Last 20 Kills
list, and the page redraws when history changes.
Mousing over a player adds how often you and your guild have killed them
and been killed by them. Names are matched across realm spellings, counts
are cached, and a new option turns the lines off.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit f9da7aa1c0893a1da1cca372c133b6bc52de0387
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 13:19:07 2026 -0800
Add kill and death history with guild sync
Personal history (per character, kept forever) records every kill, death,
duel win and duel loss with opponent details, zone, instance type, levels
and streaks. The old kill and death lists are imported once.
Guild history (account-wide, one copy per guild) holds every member's
records and is kept in sync over the guild addon channel: new records are
sent live, members exchange summaries of what they hold, and missing
records are requested by whisper. Records are never edited, so copies
cannot conflict. Guild history is pruned after a configurable number of
days (default 90).
/dgks history opens a window with personal and guild history, per-opponent
totals and a guild leaderboard, with search, type and period filters and
sortable columns. A new History options page holds the sharing and
retention settings.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit ba5fddef5c149b0aba2330575a0483f5ae21455e
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 12:55:57 2026 -0800
Detect Classic clients correctly and keep helpers local
The Classic check read metadata from an addon named "MyAddOn", so it never
matched and Classic clients ran the retail code path. It now compares
WOW_PROJECT_ID against the known Classic project IDs; Retail, Forever and
unknown clients keep the retail path.
sortListByLength, spairs and getSortedList were globals; they are now local.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit ba5fddef5c149b0aba2330575a0483f5ae21455e
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 12:55:57 2026 -0800
Detect Classic clients correctly and keep helpers local
The Classic check read metadata from an addon named "MyAddOn", so it never
matched and Classic clients ran the retail code path. It now compares
WOW_PROJECT_ID against the known Classic project IDs; Retail, Forever and
unknown clients keep the retail path.
sortListByLength, spairs and getSortedList were globals; they are now local.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
commit 013af15b21fe6217fd266a9856fcbb00c9e521a7
Author: Lance Inman <[email protected]>
Date: Fri Nov 20 12:55:57 2026 -0800
Stop tainting Blizzard's floating combat text
On clients with secret values (12.x retail and Forever), sending killshot text to
Blizzard's floating combat text from addon code tainted its frame. Blizzard's own
combat text then errored on every secret number for the rest of the session
("attempt to compare local 'lowestMessage' (a secret number value, while
execution tainted by 'dgks')"). The pcall safety net could not catch it, because
the error happens later in Blizzard's code.
When the output is "Floating Combat Text", or "Default" with no SCT or MikSBT
loaded, the text now goes to the error frame on those clients instead.
Co-Authored-By: Claude Opus 5.5 <[email protected]>