r61 is not using the new WoW 3.2 spell IDs for Molten Armor ability (Mage), causing issues. #9

  • New
  • Defect
Assigned to whitetooth3
  • _ForgeUser23487 created this issue Aug 6, 2009

    What steps will reproduce the problem?

    1. Log on a level 80 Mage who has the Glyph of Molten Armor active. Make sure he has the Molten Armor (rank 3) ability cast on himself. 2. Go into RatingBuster's options and be sure that the "Show spell crit from spirit (Molten Armor)" option is checkmarked & active.

    What is the expected output? What do you see instead?

    Expected: that +crit values would show up next to each spirit value in an item's tooltip as it did prior to WoW 3.2. Instead: notice that every item tooltip that has spirit in it is no longer showing a crit value next to the spirit values as they were properly prior to the 3.2 patch. Only mana regen.

    What version of the product are you using?

    LibStatLogic-1.1 r61, RatingBuster r230.

    Please provide any additional information below.

    LibStatLogic-1.1 r61 is using the old spell ID of "30482" for rank 3 of Molten Armor. In WoW 3.1, all ranks of Molten Armor used that spell ID. But that has changed in WoW 3.2, now they each have their own spell ID.

    30482 is now valid only for rank 1 of Molten Armor. Rank 2 is now spell ID 43045 while Rank 3 (noted above) is spell ID 43046. Which accounts for the crit values from spirit for Molten Armor rank 3 no longer showing in tooltips from RatingBuster now.

    EDIT: a further problem which may or may not be affecting things. Line 7891 of LibStatLogic-1.1.lua contains the following: ["glyph" ] = 56382, Glyph of Mage Armor. Which is wrong, that spellID number is for Glyph of Molten Armor (unchanged for 3.2).

  • _ForgeUser23487 added the tags New Defect Aug 6, 2009
  • _ForgeUser23487 edited description Aug 6, 2009
  • _ForgeUser23487 posted a comment Aug 8, 2009

    It was not a problem with the spelIDs, it was a problem with the WoW build numbers in the library. Blizzard does not apparently think 10000 comes after 9999 (current US client live build number is 10192).

    Have updated the library to account for this, its fixes the problem (well tested).

    Edited Aug 8, 2009

To post a comment, please login or register a new account.