lilsparky has made some great contributions in the mods he has made for wow. I have looked to his code a number of times and it helped me pick up LUA. Once again I found information I need in his code. One important detail I needed to enable KTQ to work with enchant scrolls is matching the produced scroll with the skill that makes it. All the other crafts produce an item and that info can be gathered with a built in wow api. The only reason enchant scrolls did not work was because I lacked that information. This is where lilsparky saves us. For LilSparkysWorkshop, he already had to make that list.
I will be adding LilSparkysWorkshop as a required mod for KTQ in the next release. I could easily copy and past the code into KTQ, its still easier for me to interface with LilSparkysWorkshop for that. It helps give him credit and while I have to maintain the api interface, it is less code I have to maintain. Code reuse is a good thing.
I have also resolved issues people have with the main branch of Skillet. I check the version now and KTQ makes that adjustment. It turns out that the craft queue api in both of them is still fairly close. In my next upload of KTQ, it will include this fix. This is the most common issue that people have with this mod that I only support the lilsparky branch of skillet and not the main one.
I just have to say, awesome!
Comment by debussy — November 13, 2009 @ 3:48 am
Thanks for a great addon!
Life before KTQ is like life before frozen pizza.
You got by, but it was a pain.
Comment by Roger — November 13, 2009 @ 4:25 am
omg. <3. ktq makes life so much better.
Comment by chazzzle — November 13, 2009 @ 5:20 am
I asked this question in your KTQ-post but I guess that’s not the best place for that. I’ll try here.
I’m really interested to know what prices KTQ use to queue up glyphs: Min. Buyout or Market average?
Thanks for a great tool. I’m looking forward to the update.
Comment by cooc — November 13, 2009 @ 10:03 am
Can’t wait!
Comment by akin — November 13, 2009 @ 10:28 am
Awesome Job, looking forward to the release!
Comment by Kramxel — November 13, 2009 @ 2:20 pm
The price KTQ uses is from the simple stats module of auctioneer. It looks at the lowest price from the last scan. I did that because the target group of people using KTQ also combine it with QA2 and that what QA2 looks at when posting.
I know many more people than my target group use it, but looking at it from that view may make the features easier to understand.
Comment by Kevmar — November 13, 2009 @ 3:39 pm
Hi,
I’ve been planning on writing a tool just like this for a while… but never got around to it. Thank you so much for making this available!
I set up the tool and it works great, however there are a couple tweaks that I made to it that others may be able to take advantage of (or you may want to include in the main trunk… up to you)
These include:
1. Using Auctioneer Market Value instead of Lowest Price.
290c317,318
– local imgSeen, image, matchBid, matchBuy, lowBid, lowBuy, aveBuy, aSeen = AucAdvanced.Modules.Util.SimpleAuction.Private.GetItems(itemLink)
> local sellPrice, numSeen = AucAdvanced.API.GetMarketValue(itemLink)
295,297c323,325
0 then
< if lowBuy ~= nil then
if numSeen > 0 then
> if sellPrice ~= nil then
>
I found if some moron was posting a glyph for 20g that normally sells for 5s, the tool wanted to make them for me if my min threshold was lower than the morons price
2. Use Altoholic:GetAccountItemCount rather than GetItemCount… for me this was including glyphs in my raiding characters guilds guild bank… and those aren’t mine to sell, so it was mucking up my crafting.
190c194,196
local myItemId = Skillet:GetItemIDFromLink(itemLink)
> local count1 = Altoholic:GetItemCount(myItemId) — call this first, otherwise next line fails
> local count = Altoholic:GetAccountItemCount(“Default”, myItemId)
3. Created two new groups for seperating and organizing crafting. My approach is to make all the glyphs whose name starts with A-K and send them to one char and the glyphs whose name start with L-Z and send them to a second char. I created two new group keywords Glyphs1 and Glyphs to and use lua string pattern matching:
138a139,142
> elseif queueString2 == “GLYPHS1″ then
> KTQQueueItem(stackSize, “Glyphs1″)
> elseif queueString2 == “GLYPHS2″ then
> KTQQueueItem(stackSize, “Glyphs2″)
239a246,266
> – Glyphs 1
> if string.find(skillName,”Glyph of [ABCDEFGHIJK]“) ~= nil and group == “Glyphs1″ then
> return true
> end
>
>
> – Glyphs 1
> if string.find(skillName,”Glyph of the [ABCDEFGHIJK]“) ~= nil and group == “Glyphs1″ then
> return true
> end
>
> – Glyphs 2
> if string.find(skillName,”Glyph of [LMNOPQRSTUVWXYZ]“) ~= nil and group == “Glyphs2″ then
> return true
> end
>
> – Glyphs 2
> if string.find(skillName,”Glyph of the [LMNOPQRSTUVWXYZ]“) ~= nil and group == “Glyphs2″ then
> return true
> end
>
These are just rough changes on my part, I haven’t made any attempt to set anything up as properties or parameters, but they work well for me and tweak the tool to do exactly what I want.
Thanks again for setting this up. It’s a great project!
- Max Schilling
Comment by Max Schilling — November 14, 2009 @ 7:45 am