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
Optionally Requires:
- Informant (for vendor availability)
LibPeriodicTable (for vendor availability)
Trade Skill Interfaces Supported:
- GnomeWorks
- AdvancedTradeSkillWindow
- Skillet
- 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.
A note regarding vendor availability:
LSW utilizes supplied item databases to determine when an item is readily available from a vendor. Occasionally this may not be accurate, usually because the item is a trade in for another item and not buyable with gold. I have provided a simple way to over-ride the vendor database:
/script LSWConfig.vendorOverride[item#] = (true/false/nil)
The item# is the item ID for the specific item. It is a single number. For example, 2589 is Linen Cloth.
Setting the value to "true" means the item is available at the vendor.
Setting the value to "false" means the item is not available at the vendor.
Setting the value to "nil" means to use the provided databse.
There is now also a right-click option to override the vendor availability and also to hand enter specific prices for items.
A note about frame/auction support:
LSW utilizes a plug in scheme to handle support to handle pricing and frame support. I am unlikely to add additional plugins directly into LSW. The goal of the plugin system is to provide basic templates that other addon authors could employ to provide LSW support on their end while at the same time providing functionality for a base set of common mods. Addon authors are free to contact me regarding the plugin system if issues arise or the system doens't make sense.
Facts
- Date created
- Oct 10, 2007
- Categories
- Last update
- Dec 11, 2011
- Development stage
- Release
- Language
- enUS
- License
- All Rights Reserved
- Curse link
- LilSparky's Workshop
- Downloads
- 265,817
- Recent files
- R: 119release for 4.3 Dec 11, 2011
- A: r119 for 4.3 Dec 11, 2011
- B: 117beta for 4.2 Aug 21, 2011
- A: r117 for 4.2 Aug 21, 2011
- A: r116 for 4.2 Jul 17, 2011
- Reply
- #195
instamat Mar 02, 2012 at 22:16 UTC - 0 likesI'm using LSW + ATSW and have Show Item Levels enabled. Most of the recipes show a number, but some say "f..." in white where the item level would normally be. What does that "f..." mean?
- Reply
- #194
norsk00 Feb 21, 2012 at 01:12 UTC - 0 likes@lilsparky
I'm having this same issue, I never set the price of Lesser Celestial Essence but it was set at a very low fixed price. Luckily I noticed before it did any damage. I can't seem to remove the fixed price though, if I uncheck the box I'm still forced to enter a fixed price amount which innately rechecks the use fixed price option. So for the time being I've set the item to use a valid fixed price, but I'd like to know if there's a way to turn this option off.
- Reply
- #193
lilsparky Dec 17, 2011 at 04:27 UTC - 0 likes@NARk: Go
and you never set it to a fixed cost manually in the past?
- Reply
- #192
NARk Dec 16, 2011 at 13:23 UTC - 0 likesHi,
I love this addon but i'm having some trouble with Reagent Cost beeing set as Fixed for some reagents. Sometimes i have to manually right-click the reagents cost and override the value to reflect auction cost, because it was set to a fixed value. For example, Maelstrom Crystal was set to 12g or something like that, and the cost of my enchantings was totally wrong for a long time till I noticed it.
- Reply
- #191
lilsparky Dec 03, 2011 at 17:58 UTC - 0 likes@cimmerianer82: Go
it scans bop on the fly and caches it once it determines an item's status. you could remove your sv file to clear this data.
or you could do this while playing:
which would clear the entire BOP database. that just means it has to re-scan tooltips or any item it hits to see if it's BOP. honestly, i should probably have it do this on every patch just to avoid the problem of BOP changes.
- Reply
- #190
cimmerianer82 Dec 03, 2011 at 12:08 UTC - 0 likesHey, huge fan of this addon. Am just wondering how can I change it so chaos orbs are no longer listed as bop in the cost overview?
- Reply
- #189
AnrDaemon Nov 26, 2011 at 01:05 UTC - 0 likesAww, blast...
Hovering over "Reagent cost overrides"...
This is my signature. There's many like it, but this one is mine.
- Reply
- #188
AnrDaemon Nov 26, 2011 at 01:02 UTC - 0 likesStill does not show item levels (broken since r99)
In r117 it show "f..." ("function" ?) instead of levels. Tailoring->Item Enchancements (Spellthreads, ahha...) and Tailoring->Cloth are affected.
Strangely enough, levels for Bags and Nets are shown just fine, Enchanting is fine as well.
- Reply
- #187
lilsparky Nov 07, 2011 at 02:57 UTC - 0 likes@pikezeppelin: Go
i generally don't tag things as "release". lsw was tagged as release automatically ages back when the wowace->curse automigration system went into place. betas are pretty much as stable as anything tagged "release" that you'd see from me. because there's a "release" version out there, i suppose i could just go ahead and tag the latest beta as "release" but it seems kinda gratuitous...
- Reply
- #186
Oukami Nov 04, 2011 at 20:51 UTC - 0 likes@pikezeppelin
You might want to check the files tab, because the last beta release was only 2 months ago, not sure where you're getting the "Betas and Alphas for more than and year" idea from. I've been using 117 beta since release with no issue.