CurseForge

v2026.32-10-gc43de30

Download

Details

Filename

SilverDragon-v2026.32-10-gc43de30.zip
Uploaded by

Kemayo
Uploaded

Sep 5, 2026
Size

803.25 KB
Downloads

32
MD5

a26f2c0bde99ed9c868f8d7011739692

Supported WoW Retail Versions

12.1.0
12.0.7

Supported WoW Mists of Pandaria Classic Versions

5.5.4

Supported WoW Wrath of the Lich King Classic Versions

3.4.5

Supported WoW Classic Versions

1.15.9

Supported WoW Burning Crusade Classic Versions

2.5.6

Changelog

SilverDragon

v2026.32-10-gc43de30 (2026-09-05)

Full Changelog Previous Releases

Mists: sync data from handynotes again
This picked up all the unique loot
lootminer: keep stdout for the generated Lua
Makes it easier to pipe things around, rather than needing to do some
cleanup.
tools: cope better with being throttled
429s were being silently dropped rather than treated as a sign than
the mining was doomed until we were unthrottled.
Mists: sync data from handynotes
This filled out loot_shared extensively via the new mining script
Rewards: cope with INVTYPE_NON_EQUIP_IGNORE gear in tooltips
It was jumbling items together because I wasn't expecting a path through
TooltipLabel that could return "".
sharedloot: find the loot a group of rares share
A zone's rares often (depends on expansion) share a pool of rare gear,
plus an item or two of their own. I was eyeballing this, which worked
okay but was a bit failure-prone, and left going back and redoing early
expansions daunting.
It's still a bit fiddly and requiring some tweaking and judgement calls,
but automating the bulk of it makes it approachable...
Mists: re-sync now that syncdata strips the " +N" label tag
syncdata: drop the miner's " +N" tag when building a label
GetClosestLocationForMob: respect per-coordinate conditions
Keep per-coordinate conditions when merging a mob's imported points
My HandyNotes data is ultimately per-coordinate, and we're squashing it
into SilverDragon's per-ID model. This mostly works, but occasionally
there's outliers like the Bloated Snapdragon where coordinates have
different conditions. In those cases whatever condition came last won,
which produced inaccurate results (worse than before the import,
because then I tended to just show all the points and let the user
figure it out).
Now split it out so that if there's different requirements they'll be
stored, and the map overlay will check them per-coord.