• posted a message on Niggles

    This would actually happen only if the 'Equipment Set Item Sold' and 'Uncollected Appearance Sold' were both enabled, which is a bug in and of itself. It isn't related to Bagnon, as the error trace would suggest, rather the Blizzard API 'SortBags()' function, so it would happen if you clicked the standard button in the default UI. The next version will have a fix. Thank you.

    Link Removed
  • posted a message on Niggles

    I don't have a rogue so I can't test this currency at all. However, I think I know what is causing the problem and I've made some changes that will be in the next version. Some currencies in the past seemed to have extra information in the values returned by the Blizzard API and the real value had to be arrived at by dividing by 100. This no longer seems to be the case so the division will be removed in the next version and that will hopefully fix your problem.

    Link Removed
  • posted a message on Niggles

    Does this happen every time you log in or only occasionally? I have seen this problem in the past but I've never been able to reliably reproduce it. The reload required to add debug code has always 'fixed' the problem, making it impossible to track down what is going wrong.

    Link Removed
  • posted a message on Niggles

    I was working on the feature when 7.3 landed and it was a choice of backing it out or releasing it when it wasn't really ready. In hindsight I should have backed it out but I thought it was in better shape than it actually was. Sorry about that.

     

    I have added a check for 'soulboundness' because the soulbound refundable items with appearances take a very different route through the underlying API. This makes it very tricky to detect them removing an appearance reliably. I'm therefore going to rely on users seeing the chat message about the item's appearance being uncollected. The Niggles warning should now only appear when BoE items with uncollected appearances are sold.

     

    The method of determining if the appearance has been collected has also been changed. The original method gave some false positives. The new method (hopefully) shouldn't. You may have to send items to a character of the 'right' class but any item that triggered a warning should show the uncollected appearance message in its tooltip.

    Link Removed
  • posted a message on Niggles: Pet Teams

    Surging Mana Crystal is (sorta) in the opponents list, but as 'Font of Mana, Seed of Mana & Essence of Mana'. This is inconsistent with some of the other 'pet tamers' and I will change it to 'Surging Mana Crystal' when i can but I need it to come up as a daily so I can gather the required info,

     

    When I have the time, I will look into the format of the Rematch strings and see if I can work out a way of using them as an import string but due to RL pressures I can't promise when.

    Link Removed
  • posted a message on Niggles

    Yes, the Blizzard API has changed for 'PlaySound()' in a non-backward compatible way. The next version, which should be available later today, has a fix for this bug.

    Link Removed
  • posted a message on Niggles

    Doing a global profile is somewhat tricky due to the way the code is currently structured. I will see if I can find the time to look into the idea further but it isn't something I can do quickly I'm afraid.

    Link Removed
  • posted a message on Niggles

    The next version, which should be available later today, uses a completely different method of determining item levels, due to this and other issues. Please try that version and let me know if you still see a problem.

    Link Removed
  • posted a message on Niggles

    Sorry for the slow response. Any time I've had to work on this addon has been spent trying to resolve issues around low level item warnings. The next version, which should be available later today, has a fix for this bug. Thank you for letting me know about it.

    Link Removed
  • posted a message on Niggles: Pet Teams

    This is due to a change in the Blizzard API for playing sounds, which causes an error every time a sound is played using the old form of the API. Double-clicking on a team plays a sound so an error occurs at the moment. I am working on fixing the problem at the moment, along with adding the new pet breeds and any new pet tamers that are accessible.

    Link Removed
  • To post a comment, please or register a new account.