• World of Warcraft Addons
Advertisement
  • World of Warcraft
  • Average Rating:

  • Your Rating

  • Share
  • Report Abuse

Fizzwidget Disenchant Predictor

Download the Curse Client

Project Updated:
Files Updated: --
Category: Miscellaneous
Tags:

, , and [Edit Tags]

Project Manager: Gazmik
Current Version:
Downloads Today: 23
Downloads Total: 83,982
Favorites: 893
Comments: 35
  • About Fizzwidget Disenchant Predictor
  •  

Fizzwidget Industries products are no longer hosted at Curse. Please check fizzwidget.com for the latest updates.

  • Downloads (0)
  •  
File Name Release Type Game Version Downloads Date
Addon Curse.com Beta 2.3.3 0 9/29/2008
Advertisement
  • Comments

Add Comment

Add

You need to login or register to post.

Benefits of Registration

  • Interact with hundreds of thousands of other gamers on an open social network.
  • Post your stories, news, images, videos, and other content to share.
  • Create a network with your fellow gamers or join an existing one.
  • Gain reputation for everything you do.
  • Golconda said 

    Not abandoned, just probably not posted - check out: http://fizzwidget.com/

  • Tekao said 

    I think this has been abandoned... Who will pick this up? There obviously needs to be a few changes made (item link not changing on multiple disenchants is irritating).

  • drewwid said 

    http://img101.imageshack.us/img101/4198/fizzwidgeterrorlm6.jpg

    The above image shows that the fizzwidget needs to add a disenchant predict to the epic item shown above

  • BBR said 

    hm i thought i posted this earlier..

    anyway, if you alt+click a link in guild chat, multiple times, then the enchant predictor is able to add multiple of the same lines to the tooltip.

    i've had it add up to "8 times" the linke that some item would disenchant into a large brilliant shard... seems like the duplicate check is failing for some methods.

    -

    It's bugged still. if you disenchant multiple items, the chatlog will display the first item you disenchanted multiple times. e.g. -> Disenchanting Green wand of randomness Disenchanting Green wand of randomness Disenchanting Green wand of randomness

    instead of Disenchanting Green wand of randomness Disenchanting Blue sword of something Disenchanting Green staff of fiery wrath

  • BBR said 

    Most blue items from ZG will disenchant into small prismatic shards. the addon does not list this properly.

    same for Ruins of Qiraj ofcourse

  • Marsti said 

    Would be nice to only show infos if enchantrix isn't loaded or doesn't know the item.

    PS: Weapons (i.e. 36-40) does enchant most into nether essence and sometimes into dust (see Enchantrix). But DP says "most dust, often essence"

  • Dagnome said 

    It seems whenver I mouse over my Imperial Regalia (the quest peice to get the AQ40 caster staff) it throws an error... not sure why just yet.

    Opps... realized I have the wrong Addon :) It's actually Fizzwidget's Adspace throwing the error... I'll repost this there ;)

  • Cogwheel said 

    This mod improperly hooks GameTooltip:SetOwner which may cause problems with some addons (mostly aesthetic, but still annoying). I have submitted a bug report to the author, but would also like to post a fix here. Open Interface\AddOns\GFW_DisenchantPredictor\GFWTooltip.lua. Change lines 404-407 to look like the following:

    function Hook.GameTooltip_SetOwner(this, owner, anchor, offsetx, offsety) Orig.GameTooltip_SetOwner(this, owner, anchor, offsetx, offsety); gameToolTipOwner = owner; end

  • Alright, folks! I've got a solution to those pesky "Config" issues, and maybe more! Straight from the goblin's mouth!

    > I came across a similar situation myself recently, in doing some > extensive work for an upcoming release of ReagentCost... some changes > in the base WoW client have made it rather persistent about storing > nil values at even the slightest suggestion, overriding values that > should be set up during the addon loading process. It'll take more > defensive coding to prevent such situations, and I'll be making sure > that gets into all of my addons for a future release. > > For now, you should be able to work around the problem by deleting the > SavedVariables files for the affected addons: go to your World of > Warcraft folder, and within it go to WTF/Account/ACCOUNTNAME/ > SavedVariables and delete GFW_AdSpace.lua, GFW_AdSpace.lua.bak, > GFW_DisenchantPredictor.lua, and GFW_DisenchantPredictor.lua.bak.