cavedude
01-25-2008, 01:45 AM
Sorry it took so long to get to this one.
I admit, it bothers me that items that return on success and failure we currently require 3 entries for them. Even nailing them down to 2 would be acceptable (component count + failure count) and product count. So in that way, I like your code. The big issue I have with this is it offers no backwards compatibility. tradeskill_recipe_entries is the only table I dread working with using scripts partially because of the "broken" system (most recipes are using the multiple entry system, but I do occasionally find a recipe that isn't and needs to be fixed) but mainly due to the exceptions, and inconsistencies. Our tradeskills originally were pulled in from scripts, so quite literally since I've been with PEQ I have found (and hand corrected) hundreds of errors (incorrect item entries dealing with items that have identical names, incorrect/missing trivial, no fail entries, items that had incorrect entries as to whether it was a component or product, etc) I am certain there are more, and they always seem to pop up when I am trying to run a script. We currently have 9,508 recipes in the db, and a rough estimate of 3,195 recipes are effected (I say rough estimate because of the inconsistencies above it could skew my results.) As much as I'd like this change in, I'd much rather have a backwards compatible system put in place so those 3,195 recipes can be corrected over time, and not in one dangerous swoop.
I admit, it bothers me that items that return on success and failure we currently require 3 entries for them. Even nailing them down to 2 would be acceptable (component count + failure count) and product count. So in that way, I like your code. The big issue I have with this is it offers no backwards compatibility. tradeskill_recipe_entries is the only table I dread working with using scripts partially because of the "broken" system (most recipes are using the multiple entry system, but I do occasionally find a recipe that isn't and needs to be fixed) but mainly due to the exceptions, and inconsistencies. Our tradeskills originally were pulled in from scripts, so quite literally since I've been with PEQ I have found (and hand corrected) hundreds of errors (incorrect item entries dealing with items that have identical names, incorrect/missing trivial, no fail entries, items that had incorrect entries as to whether it was a component or product, etc) I am certain there are more, and they always seem to pop up when I am trying to run a script. We currently have 9,508 recipes in the db, and a rough estimate of 3,195 recipes are effected (I say rough estimate because of the inconsistencies above it could skew my results.) As much as I'd like this change in, I'd much rather have a backwards compatible system put in place so those 3,195 recipes can be corrected over time, and not in one dangerous swoop.