Well if you could make it consistent for consistency's sake by copying all the relevant Elixirs to Consumable.Potion.Buff.Stat.* for now until we can kill it off in WotLK that'd be great. I'll try to move my Baggins config to Consumable.Cooldown.Potion.*(I assume something similar exists for Elixirs), but it's still kind of annoying. :P
I am confused. Why is it anoying? Is it hard to do? Is Baggins using the wrong ones by default? If it is you need to be posting in the Baggins forum.
As for elixers, as mentioned they are in
Consumable.Buff Type.Battle, Consumable.Buff Type.Guardian, Consumable.Buff Type.Flask
All Alchemy items are in Tradeskill.Crafted.Alchemy
As for fixing it so that we can later delete it, no chance. If it is "fixed" people may use it and then object to its deletion. If you truly need it fixed get the mod author to do it. Hopefully they will find and use the already fixed alternatives instead.
At first, I thought this was a problem with LilSparky's Workshop (http://www.wowace.com/forums/index.php?topic=9379.80), but apparently it derives from an error in the PeriodicTable database. Ghost Dye is listed as a vendor-buyable reagent (like Salt or Rune Thread) with a cost of zero, but is actually an Alchemist-made item that's pretty expensive. This throws off LSW's calculation for things like Ghostweave Pants, indicating that they're profitable to make when they are far from it.
Any chance for a 3.0 update? I thought of trying to do it myself but with the wiki pages gone I can't figure out how and am afraid to mess it up if I try and update manually.
Not sure what the proper way to get involved in PT maintenance is, so I posted a patch ticket on the project with fixes for the dataset problems I've found in migrating my Feed-O-Matic addon to PT. Hope this helps.
Not sure what the proper way to get involved in PT maintenance is, so I posted a patch ticket on the project with fixes for the dataset problems I've found in migrating my Feed-O-Matic addon to PT. Hope this helps.
It looks like Azethoth (Toadkiller) and Nevcairiel are the ones currently maintaining it, so you might want to try sending them forum PMs.
Looks like there is a "bug" in the version of tables in periodic table as a side effect of the SVN move. Since the version numbers are now lower, older tables are overriding newer ones. Also the Autobar is hard coded to use version 54697. So even if only new copies of the library is used Gear, Misc and Tradeskill will risk being overwritten by LibPeriodicTable-3.1-AutoBar.
Sweet. I look forward to getting a working version in Baggins (I tried to load the library as a separate addon, but Baggins didn't seem to recognize it).
Sweet. I look forward to getting a working version in Baggins (I tried to load the library as a separate addon, but Baggins didn't seem to recognize it).
Forgot to make the new placeholders in the subfolders, should be fixed now.
Looks like there is a "bug" in the version of tables in periodic table as a side effect of the SVN move. Since the version numbers are now lower, older tables are overriding newer ones. Also the Autobar is hard coded to use version 54697. So even if only new copies of the library is used Gear, Misc and Tradeskill will risk being overwritten by LibPeriodicTable-3.1-AutoBar.
I dropped the version AutoBar uses. It is meant to get overridden, not to overide after all. I still need to rework that scheme so it checks on a per set basis not per file.
So far I have rescued the API and an Editing page. I can not find the dataminer stuff though so if (Jerry?) could add some details about that it would be nice. I also added links from the main project page to these. Perhaps it will help with the rash of people incorrectly editing the output files, or auto generated sets.
Rogue Poison mats are no more. Can I just delete this set or will some mod spaz out?
About the version numbers. We can artificially inflate them, or just require people to upgrade to the new lower numbered versions.
we could change it to use @file-date-integer@ instead of $Revision: x $ though that would mean we would have to add special treatment if a svn checkout is used since then that keyword wouldn't be replaced. though a svn cehckout can theoretically be assumed as the latest version I think.
(see: http://www.wowace.com/knowledge-base/repository-keyword-substitutions/ )
we could change it to use @file-date-integer@ instead of $Revision: x $ though that would mean we would have to add special treatment if a svn checkout is used since then that keyword wouldn't be replaced. though a svn cehckout can theoretically be assumed as the latest version I think.
(see: http://www.wowace.com/knowledge-base/repository-keyword-substitutions/ )
Problem with something like that is it might cause problems for addons that are not hosted at wowace that bring in LibPeriodicTable-3.1 via svn:externals.
Someone already committed a fix to inflate them anyways it appears.
None of my Northrend herbs are being filtered through Baggins using the LPT r37. I'm using the following filters (which work fine with non-Northrend herbs):
PTSet.Tradeskill.Mat.ByType.Herb
I'm also not seeing a Mat.ByType filter for the "Crystallized" elements found in Northrend (nor their "Eternal" versions).
Would it be possible to add code to the dataminer to have the data of the sets sorted by the 'key'-id of the values so that a diff shows which ids have been added/removed.
Currently, it seems like the data can shuffle between to dataminer runs so you get a bunch of changes that are none.
None of my Northrend herbs are being filtered through Baggins using the LPT r37...
I ran the full miner and checked that in. It only affected ClassSpell.
This means you need to complain to your mod author so they can fix the PT3 stuff they use. For instance, most consumables are maintained by myself, and recently the pet related foods by Gazmik. We do this because our mods AutoBar and Feed-O-Matic rely on consumables. I have absolutely no idea who does the stuff you are interrested in, but you need to track them down to get action on your issues.
...sets sorted by the 'key'-id of the values so that a diff shows which ids have been added/removed...
I like it. I added a sort for the generated sets and am checking in the sorted results. I would like to have it sort specific non-generated ones as well + remove duplicates. Some day perhaps.
I ran the full miner and checked that in. It only affected ClassSpell.
All Northrend herbs are in the last version(s) of PT. Something else is the cause of the issue.
Adding the sort is a good idea. I thought about adding it myself when I rewrote the core of the dataminer, but never did. Note that running the dataminer with a debug level above 2 should print a 'diff' of each sets that changed.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I am confused. Why is it anoying? Is it hard to do? Is Baggins using the wrong ones by default? If it is you need to be posting in the Baggins forum.
As for elixers, as mentioned they are in
Consumable.Buff Type.Battle, Consumable.Buff Type.Guardian, Consumable.Buff Type.Flask
All Alchemy items are in Tradeskill.Crafted.Alchemy
As for fixing it so that we can later delete it, no chance. If it is "fixed" people may use it and then object to its deletion. If you truly need it fixed get the mod author to do it. Hopefully they will find and use the already fixed alternatives instead.
It looks like Azethoth (Toadkiller) and Nevcairiel are the ones currently maintaining it, so you might want to try sending them forum PMs.
This includes the following sets:
I also added the following currently empty sets:
Forgot to make the new placeholders in the subfolders, should be fixed now.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumID:39342
edit:
Also missing from Tradeskill.Gather.Milling
I dropped the version AutoBar uses. It is meant to get overridden, not to overide after all. I still need to rework that scheme so it checks on a per set basis not per file.
So far I have rescued the API and an Editing page. I can not find the dataminer stuff though so if (Jerry?) could add some details about that it would be nice. I also added links from the main project page to these. Perhaps it will help with the rash of people incorrectly editing the output files, or auto generated sets.
Rogue Poison mats are no more. Can I just delete this set or will some mod spaz out?
About the version numbers. We can artificially inflate them, or just require people to upgrade to the new lower numbered versions.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator(see: http://www.wowace.com/knowledge-base/repository-keyword-substitutions/ )
Problem with something like that is it might cause problems for addons that are not hosted at wowace that bring in LibPeriodicTable-3.1 via svn:externals.
Someone already committed a fix to inflate them anyways it appears.
PTSet.Tradeskill.Mat.ByType.Herb
I'm also not seeing a Mat.ByType filter for the "Crystallized" elements found in Northrend (nor their "Eternal" versions).
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorCurrently, it seems like the data can shuffle between to dataminer runs so you get a bunch of changes that are none.
I ran the full miner and checked that in. It only affected ClassSpell.
This means you need to complain to your mod author so they can fix the PT3 stuff they use. For instance, most consumables are maintained by myself, and recently the pet related foods by Gazmik. We do this because our mods AutoBar and Feed-O-Matic rely on consumables. I have absolutely no idea who does the stuff you are interrested in, but you need to track them down to get action on your issues.
I like it. I added a sort for the generated sets and am checking in the sorted results. I would like to have it sort specific non-generated ones as well + remove duplicates. Some day perhaps.
All Northrend herbs are in the last version(s) of PT. Something else is the cause of the issue.
Adding the sort is a good idea. I thought about adding it myself when I rewrote the core of the dataminer, but never did. Note that running the dataminer with a debug level above 2 should print a 'diff' of each sets that changed.