v2026.32-7-gbe2ac8e

Details

  • Filename
    SilverDragon-v2026.32-7-gbe2ac8e.zip
  • Uploaded by
  • Uploaded
    Sep 5, 2026
  • Size
    802.70 KB
  • Downloads
    16
  • MD5
    83f6853285e494192bfbaec22f412193

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-7-gbe2ac8e (2026-09-05)

Full Changelog Previous Releases

  • 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 normally roll one pool of gear plus an item or two of their
    own, and there was no quick way to see where the split falls. This groups the
    drop tables by which set of mobs drops each item, and can print the result as
    a loot_shared block. Two things make the answer usable: era sites such as
    mop-classic give a far cleaner table for old content than the retail page,
    and the share of an item's droppers that are rares tells a real pool apart
    from a zone drop the rares also roll.
  • 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.