1.4.2-9-g4b31136

Details

  • Filename
    Breakables-1.4.2-9-g4b31136.zip
  • Uploaded by
  • Uploaded
    Oct 6, 2016
  • Size
    156.70 KB
  • Downloads
    45
  • MD5
    1f0b25351dd45072f9fa0fa5f80a11a9

Supported Game Versions

  • 7.0.3
  • 6.2.4

Changelog

Parnic:
    - Added WoD combinables
    - Added support for combining smaller items into larger ones
    Certain types of herbs and ore can be looted that aren't millable/prospectable themselves, but can be used to combine (or unbreak, if you will...) them into an item that can be milled/prospected. It's convenient if the addon offers support for those situations so you can combine the combinables, then break the breakables.
    - Fixed the breakable button not working all the time
    We need to explicitly set the type of the button to spell in addition to specifying the spell name, target bag, and target slot.
    - Update more frequently
    I had set a bag check delay to ensure when the player looted masses of items at once that we didn't bog down the game. 1 second is way more than that case needs, so let's reduce it to 0.1 simply to prevent the "check 8 times when looting 8 items" performance problem but retain a responsive Breakables UI.
    - Added handling for disenchanting WoD/Legion items with a low Enchanting level
    - Added readme
    - Fixed sometimes choosing small stacks over large ones
    This is an ancient problem in Breakables where the merging mechanism was always combining the same breakable into a single entry in its internal array and disregarding what bag and slot each stack was in. If we retain the position of the largest stack, then Breakables can always pick the proper larger stack to break no matter what order they appear in bags. This won't help the case where a single stack is spread into stacks where no single stack is large enough to break, but the WoW client has built-in bag compression now, so that should be less of a concern.
    - Fixed sometimes choosing invalid items to break
    When the player had items where one was a substring of the other ("Whiptail" vs "Whiptail Stem", for example), the game client would sometimes pick the wrong one to break. In the Whiptail case, this meant the game could attempt to cast Mill on a Whiptail Stem if it appeared first in the player's bags, which doesn't work. All we can do with the target-item attribute is supply a name, so it's not really our fault that the game makes this decision, but we can work around it by using target-bag and target-slot instead of target-item where we can be explicit about what we're trying to break.
    - Different method of determining if a Mass Mill spell is known

Additional Files