LilSparky's Workshop adds auction-derived pricing information for trade skills right into the trade skill recipe frame. Each skill is evaluated for material costs and potential value of the item created. These two numbers are listed next to each skill in an easy-to-read format.
Supported Auction Scanners:
- Auctioneer
- AuctionLite
- AuctionMaster
- Auctionator
Supported Vendor Databases:
- Informant
- "GetSellValue" compliant mods (SellFish, ItemPriceTooltip, Valuation, ItemDataCache, plus many others)
Optionally Requires:
- LibPeriodicTable (to identify items that are sold by vendors)
Trade Skill Interfaces Supported:
- AdvancedTradeSkillWindow
- Skillet (trunk and "lilsparky" version)
- Blizzard's Standard UI
- Doublewide Tradeskills
- Tradeskill HD
Auction pricing models can be selected by right-clicking either the value column or the cost column (each can have a different pricing method attached).
The Value column can be left clicked to cycle through the different valuation methods for the resultant item: Auction Value (a), Vendor Value (v), Disenchant Value (d) or the greatest of the three different values (the default). Any instance of an item Value being greater than the Cost to create it will have a highlighted Value entry. Optionally, the Value column can be displayed as a percentage of the Cost column.
The Cost column simply sums up the costs for each reagent and reports the total.
Both columns can be combined into a single "Profit" column which simply reflects the Value minus the Cost.
Tooltips for each column give more details about the price breakdowns LSW is considering.
Facts
- Date created
- 10 Oct 2007
- Categories
- Last update
- 11 Sep 2009
- Development stage
- Release
- Language
- enUS
- License
- All Rights Reserved
- Curse link
- LilSparky's Workshop
- Recent files
- #16
sn0n Sun, 19 Apr 2009 21:58:18@Dracos99, worked for me also. ty! puts me lightyears ahead of the 3.1 curve. ;) LoL
- #15
Dracos99 Sun, 19 Apr 2009 15:18:19a quick look at old code vs. new code shows ASTW seems to have turned most of the table structures into locals Line 40 seems to be the issue local atsw_skilllisting={}; removing the local seems to resolve the issue, but I dont know if it will have any effect...Im not a LUA expert, so lilsparky will have to figure out how to connect to the new local or get ATSW to revert to a global variable or function. Hope this info helps get workshop working with ATSW again
- #14
lilsparky Sun, 19 Apr 2009 05:37:20i plan on getting back to lsw soon! should still work under 3.1, but i think atsw's latest version changed something that causes a problem with lsw... i'll be looking into it.
- #13
Radoznali Sat, 18 Apr 2009 11:32:18update for 3.1?
- #12
Manaman Thu, 26 Mar 2009 16:01:01I know my auctioneer has data for most of the high end "Scroll of"s but LSW does not appear to show any of that data. And I just confirmed I am running 0.91beta.
- #11
lilsparky Wed, 18 Mar 2009 18:12:00i *think* the 0.91 should provide that info. the problem i have found in testing (on my server anyway) is that of the hundreds of different enchants, only a few ever get listed so it's difficult to determine if the data is making it into lsw or not.
- #10
Manaman Wed, 18 Mar 2009 08:55:34Any chance the auction data for enchants could be setup to show the AH price of the scrolls of that enchant.
- #9
lilsparky Sun, 22 Feb 2009 04:58:47i'll have to check that out. a few months back, i had a conversation with a guy who was saying the skill up% was simply linear like that, but i dunno how true it is. i wrote a skill up tracker to help me figure it out, but i don't skill up enough to have much data. :)
i'd love to factor that in, tho. cost * skillup% = cheapest way to get a point (of course, it's all probabilities so it's not a lock).
- #8
riveth_ Sun, 22 Feb 2009 03:58:10It would be really nice to see an option to sort by probability of getting a skill point and/or estimated cost per skill point. Over at EJ, there was a discussion which suggested that to determine the probability of getting a skill point, one simply does (gray - current)/(gray - yellow) for given recipe.
- #7
lilsparky Sun, 23 Nov 2008 09:49:11v0.80b is just a fix to the .toc file (forgot to change the version number there)