LilSparky's Workshop

This project is abandoned.

Whether this project is out of date or its author marked it as abandoned, this project is no longer maintained.

If you wish to take this project over, please report it and state your intentions.

LSW First Aid w/ Standard Interface

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.

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of lilsparky lilsparky Oct 14, 2010 at 16:04 UTC - 0 likes

    thanks, i'll make that change and push a new rev out.

  • Avatar of SYNWrath SYNWrath Oct 14, 2010 at 07:59 UTC - 0 likes

    I am an avid user of LSW and made a few small changes to get rev 98 working better in 4.0.1

    In the function CostButton_OnEnter around line 1695 I changed:

         -- local skillID = this:GetID()
         local skillID = button:GetID()

    For me, that's all it took to get my hover price itemization working again

    Last edited Oct 14, 2010 by SYNWrath: Better explanation
  • Avatar of tlai tlai Oct 13, 2010 at 16:55 UTC - 0 likes

    How is support for patch 4.0.1 looking

    Last edited Oct 13, 2010 by tlai
  • Avatar of lilsparky lilsparky Sep 22, 2010 at 00:48 UTC - 0 likes

    turn on errors please, cuz it sounds like there might be an issue. i also hate the blizz ui frame, so i use swatter (part of auctioneer) but i know lots of people use bugsack as well.

    i'll see if auctionator has a callback for when new data is available and if it does, i'll be sure to plug into it.

    lsw gets a lot of blame for delays because of the way i check the cache to ensure everything is up to date. what happens is that when i get an update event (fired pretty often from the server) i iterate over the recipes and make sure they're all up to date. usually they are, so the processing is negligible. however, this process is throttled to only check a set number of recipes each frame (50 i think) until it's checked them all. the progress bar is designed to show itself only after it's taken more than half a second (i think) to check the recipes (the thought being that it's pointless to flash a progress bar for .1 seconds).

    what happens, tho, is that some other addon might kick in during this process and cause the frame rate to drop. since the update system is throttled to update only 50 recipes per frame, even if the processing is instant, if a ton of processing happens to delay a frame (or slow down the frame rate) lsw's progress bar will show up and it'll look like lsw is the culprit.

    when you do a tradeskill, you fire off bag update events, so any inventory recording mod could easily be the actual cause of the hiccup.

  • Avatar of dkived dkived Sep 21, 2010 at 23:09 UTC - 0 likes

    I'm having a couple issues with LSW. The first is that sometimes LSW doesn't load properly -- this might be the same issues as Rotab's issue.... with the way WoW handles Lua errors I can't stand having the option to display them on. I'll try turning it back on tho to get a full error message. With the Blizzard trade skill UI, it looks as if LSW is disabled (no columns, no data, no 'w/LSW' or trade skill link in the title). In GW, the columns for pricing data are there without values and the frame drawn around the skill list does not include those columns.

    The second issue happens only when using GW. It looks like LSW wants to recache data after every trade skill action - this results in WoW freezing up for a moment after every 1.5 sec smelt. Not a critical issue, but fairly annoying at any rate.

    Oh, one other minor annoyance: once I've used LSW, if I scan the AH again I have to right-click on an LSW column and set the pricing model in order to get LSW to update the prices. I use Auctionator FYI.

    Last edited Sep 21, 2010 by dkived
  • Avatar of bsmorgan bsmorgan Aug 21, 2010 at 18:27 UTC - 0 likes

    I believe r98 is reporting itself as r97.


  • Avatar of lilsparky lilsparky Aug 02, 2010 at 20:23 UTC - 0 likes

    i need to rethink the caching a bit. i wanted it to be automatic, but that causes problems. i think instead i'll have an option to cache (or not) different auction streams. that might work better.

  • Avatar of ZoalPrime ZoalPrime Aug 02, 2010 at 13:38 UTC - 0 likes

    Hello Mister LilSparky,

    I've been having a problem with the caching on the latest revision of this addon. I will scan the AH on one character using Auctioneer. When I log into my crafter some items will be missing values. Notably today: Saronite Bars, Eternal Earth had no values when looking at my Blacksmithing. I even went back to my character at the auction house and specifically searched and updated those items - when I logged back into my crafter those specific items were still missing values.

    It is not until I physically went to the AH on my crafter and searched for those items that LSW showed me the auction values for them.

    This is not unique to Saronite Bars and Eternal Earth however - I've noticed items missing values on other professions as well.

  • Avatar of lilsparky lilsparky Jul 27, 2010 at 15:26 UTC - 0 likes

    well, it's optional in the same way auction house mods are optional.  informant (part of auctioneer) provides the vendor source data.  so if you use auctioneer/informant, you don't need libpt's vendor data.

  • Avatar of MrLavender MrLavender Jul 27, 2010 at 12:16 UTC - 0 likes

    Ah, I see. I don't really consider that optional then...the addon simply doesn't work correctly without it.

    Thanks for the reply and for your work on LSW.


Date created
Oct 10, 2007
Last update
May 29, 2013
Development stage
  • enUS
GNU General Public License version 3 (GPLv3)
Recent files
  • A: r155 for 5.3.0 May 29, 2013
  • A: r154 for 5.3.0 May 29, 2013
  • A: r153 for 5.2.0 May 28, 2013
  • A: r152 for 5.2.0 May 13, 2013
  • A: r151 for 5.2.0 Mar 21, 2013