Not signed in (Sign In)
  1.  
    I've been working on some Enchantrix additions for a while and now I've reached a point where I can say that my additions are actually helpful.

    So far, I've used a few hacks to merge item disenchants by base item (e.g. Abjurer's Bands of <x>) and item type (level 43 armor). During this process, I've noticed some discrepancies, namely a few cases where a very low percentage of some reagend is reported as disenchant result from items that should not disenchant into said reagent (0.1% lesser nether and 0.2% illusion dust in case of Abjurer's Bands). I suspect this is because of bad data in DisenchantList and so, my next step in this project is to implement a sanity check for disenchant data by using a combination of tables similar to Enchantrix_LevelRules and GetItemInfo() (Blizzard API function). GetItemInfo() can reveal stack size and thus, filter out stackable items as unenchantable (e.g Thorium Headed Arrows and Hi-Impact Mithril Slugs).

    I'd also like to clean up the code a bit. The sigNR construct appears to be a designed similar to my own merging of base items except that the sigNR disenchants are never updated. Also, the fourth and last field in disenchant data remains an enigma to me. Is it ever used? I'd like to use it for highest observed reagent count per disenchant instead, with the hopes of expressing average disenchant count as a function of max disenchant (just an untested theory so far).

    I've also implemented a normalization step during merging of DisenchantList data. It seems some items have been submitted several times so I divide counts by greatest common divisor. The idea is that if item <x> has been submitted <y> times then all counts should be divisible by <y>.

    Abilities:
    imperative languages - 15 years of hobby programming in most popular, and some not so popular, languages (lua sucks btw)
    xml - know the syntax
    subversion - heard of it
    spelling and grammar - meh, I'm swedish, I'm supposed to sound like a muppet
  2.  
    Posted by: Aradan on Jan 14 2006, 03:36 PM
    I've been working on some Enchantrix additions for a while and now I've reached a point where I can say that my additions are actually helpful.

    So far, I've used a few hacks to merge item disenchants by base item (e.g. Abjurer's Bands of <x>) and item type (level 43 armor). During this process, I've noticed some discrepancies, namely a few cases where a very low percentage of some reagend is reported as disenchant result from items that should not disenchant into said reagent (0.1% lesser nether and 0.2% illusion dust in case of Abjurer's Bands). I suspect this is because of bad data in DisenchantList and so, my next step in this project is to implement a sanity check for disenchant data by using a combination of tables similar to Enchantrix_LevelRules and GetItemInfo() (Blizzard API function). GetItemInfo() can reveal stack size and thus, filter out stackable items as unenchantable (e.g Thorium Headed Arrows and Hi-Impact Mithril Slugs).

    I'd also like to clean up the code a bit. The sigNR construct appears to be a designed similar to my own merging of base items except that the sigNR disenchants are never updated. Also, the fourth and last field in disenchant data remains an enigma to me. Is it ever used? I'd like to use it for highest observed reagent count per disenchant instead, with the hopes of expressing average disenchant count as a function of max disenchant (just an untested theory so far).

    I've also implemented a normalization step during merging of DisenchantList data. It seems some items have been submitted several times so I divide counts by greatest common divisor. The idea is that if item <x> has been submitted <y> times then all counts should be divisible by <y>.

    Abilities:
    imperative languages - 15 years of hobby programming in most popular, and some not so popular, languages (lua sucks btw)
    xml - know the syntax
    subversion - heard of it
    spelling and grammar - meh, I'm swedish, I'm supposed to sound like a muppet

    Hello! Norganna (the lead Auctioneer developer) seems to be on vacation or something as he hasn't been seen around lately, so it seems like I'm the most senior dev around (other than Luke). So lets get the ball rolling.

    Needless to say, we are in dire need of Enchantrix developers. That being said, your ideas sound fenomenal. I wish I had the power to give developer status to applicants, but alas only norganna can do such things. In the mean time, you could join us at the IRC channel (irc://irc.datavertex.com/norganna) or just generally help out with forums questions. Thanks for your application.
World of Warcraft™ and Blizzard Entertainment™ are trademarks or registered trademarks of Blizzard Entertainment, Inc. in the U.S. and/or other countries.