A quick reference to sources of Enchanting materials.
Release notes for Disenchant Predictor
Disenchant Predictor 3.1
[ download ]
Saturday, April 18th, 2009
- Updated TOC to indicate compatibility with WoW Patch 3.1.
- Now uses Ace3 library for saved settings and options UI (any previously saved preferences will be reset to default).
Disenchant Predictor 3.0.2
[ download ]
Thursday, January 29th, 2009
- Fixed an issue where preferences could fail to be saved between sessions.
- Updated Korean localization from ‘chkid’.
Disenchant Predictor 3.0.1
[ download ]
Wednesday, October 15th, 2008
Fixed an issue that could cause disconnects when mousing over items.
Disenchant Predictor 3.0
[ download ]
Monday, October 13th, 2008
- Updated for compatibility with WoW Patch 3.0 and Wrath of the Lich King.
- Tooltips for reagents now use an inline graphic to indicate which expansion’s items they disenchant from.
- Includes preliminary data to support predicting disenchants for Wrath items:
- We don’t yet have enough data to predict all Wrath disenchants. Disenchant Predictor will show details in the chat window if you disenchant something that doesn’t match its expectations — send them in so future releases can be more accurate!
- In Wrath content, there’s no longer a correlation between items’ required level seen in-game and the internal item level that determines disenchant results. So, tooltips for Lesser/Greater Cosmic Essence and Small/Large Dream Shards can only say “disenchants from lower/higher level Wrath items”.
- Removed the Auto Loot option, as the one built into WoW works for Disenchanting now.
- Now uses the Interface Options panel for configuration.
Disenchant Predictor 2.4
[ download ]
Monday, March 24th, 2008
- Updated TOC to indicate compatibility with WoW Patch 2.4.
- Updated German localization by “Zara”.
Disenchant Predictor 2.3
[ download ]
Monday, November 12th, 2007
Updated TOC to indicate compatibility with WoW Patch 2.3.
Disenchant Predictor 2.2.1
[ download ]
Friday, October 12th, 2007
- Fixed
autoloot
option to work again following WoW Patch 2.2. - Corrected disenchant source text on tooltips for Burning Crusade reagents.
- Fixed an issue where we could lose track of what your’e currently disenchanting if the cast was interrrupted.
- We now check for whether a disenchant comes out as predicted regardless of whether the
autoloot
option is turned on. - The
autoloot
option also controls whether the “Disenchanting [item]…” text appears in the chat window. - Added Simplified Chinese localization by Colin Cao and Traditional Chinese localization by Katun.
Disenchant Predictor 2.2
[ download ]
Tuesday, September 25th, 2007
Updated TOC to indicate compatibility with WoW Patch 2.2.
Disenchant Predictor 2.1.1
[ download ]
Friday, July 20th, 2007
- Refined disenchant tables for shards and crystals produced by high-level items; all should be correctly predicted now.
- Updated the list of non-disenchantable items.
- Uses a simpler, more reliable means of hooking item tooltips.
- Added support for the Ace AddonLoader — when that addon is present, Disenchant Predictor will load in the background shortly after login (reducing initial load time).
Disenchant Predictor 2.1
[ download ]
Monday, May 21st, 2007
- Updated TOC for WoW Patch 2.1.
- Fixed an issue with tracking disenchants: we should no longer get confused if the casting of “Disenchant” is interrupted.
Disenchant Predictor 2.0.4
[ download ]
Saturday, February 17th, 2007
- ItemLevel 100 blue items disenchant to [Large Prismatic Shard] instead of Small, breaking the normal pattern. Our predictions now account for this.
- Fixed some issues with hooking tooltips when other tooltip-modifying addons are present.
Disenchant Predictor 2.0.3
[ download ]
Sunday, January 14th, 2007
- Updated for compatibility with WoW Patch 2.0.3 and the Burning Crusade release.
- Refined disenchant tables a bit for high-level items: blue items from ZG and AQ20 should now be predicted correctly.
- Simplified code for adding text to item tooltips thanks to new API in WoW 2.0.3 — this should fix issues with the same info being added to a tooltip multiple times or sometimes being missing, as well as allow us to work with more third-party addons that show item tooltips.
Disenchant Predictor 2.0.2
[ download ]
Friday, December 8th, 2006
Fixed error (introduced in 2.0.1) when mousing over items.
Disenchant Predictor 2.0.1
[ download ]
Thursday, December 7th, 2006
- Fixed possible blocked action errors in tooltip-hooking code.
- Fixed blocked action error when looting.
Disenchant Predictor 2.0
[ download ]
Monday, December 4th, 2006
- Updated for compatibility with WoW 2.0 (and the Burning Crusade Closed Beta).
- We now print a line to the chat window when you begin disenchanting an item, making it easier to follow which reagents came from where when discenchanting many items.
- We also track whether a disenchant comes out as predicted, and print an error message in the chat window if we see a reagent we weren’t expecting (with diagnostic info and a request to contact us so we can improve prediction in future releases).
- Redesigned the prediction algorithms to use an item’s own level (a statistic not visible in the default UI, but now available to addons) rather than the required level to equip it. This means:
- We now have more accurate predictions for Burning Crusade high-level items (which include greens of required level 57-60 whose item levels are 80-90, and thus disenchant differently than old level 57-60 greens).
- We can now predict disenchants for quest rewards or other items which have no level requirement.
- Streamlined some older code for better efficiency.
- WoW 2.0 now adds a line to the tooltip showing the required enchanting skill to disenchant an item, or that it’s not disenchantable at all — we catch this now and won’t display predictions for an item once we’ve learned it can’t be disenchanted.
- NOTE: Predictions for Burning Crusade items/reagents are still tentative based on what data we’ve acquired so far. If you see an item disenchant into something that didn’t match our predictions, please let us know!