GnomeWorks TradeSkill Frame -
a complete replacement for the blizzard trade skill frame.
early alpha just to test some things out.
You must login to post a comment. Don't have an account? Register to get one!
hmm... okay, well, i'll try to take a look at that. see if manually switching to the proper tradeskill lets the processing occur. it could be related to how gw switches tradeskills.
Hmm, queue processing seems to be borked in r231 (still not showing up packaged, but I checked it out via svn).
What's happening is that when I click the process button on the queue to make something, nothing happens. Well, almost. If what's next to be made is something I put in the queue directly (or used QueueProfitable to put it in the queue) then nothing happens. If it's something that needs to be made in order to make something in the queue, then the processing happens. The example I have is: Queued Pyrium Weapon Chain, in my bags was Pyrite Ore. The processing button prompted to smelt Pyrite, clicked, smelting done. The button changed to Process Pyrium Weaon Chain, clicked, nothing.
r231 should allow browsing of alt's recipes (if you've looked at them in gw). again, not really tested a ton.
well, presumably r230 will show up once the packager is running again...?
okay, r230 should be 5.4 compatible for the most part. not exhaustively tested, but it seems to work. there'll like be an occasional hiccup if it hits old links or is looking for old links.
the "all recipes" links won't do much for you. also, it's unlikely your alts will be available at the moment. to me, that's be biggest problem with the new system -- you have to have interacted with the unit whose link you wish to open in the current session. the likelihood of doing that for an alt is pretty much nil. THAT is something i could see them adjusting (forcing your alts to remain in your cache or something).
anyway, like i said. r230 should be usable as a ui replacement. without the recipe level scanning, it'll become more and more outdated as things change. i may revert to supporting external data sources since we'll all be scanning data from the same places (wowhead). the live scanning method was 100% accurate immediately for every patch (wowhead's data often takes some time to update).
honestly, i wish they'd just provide that kind of data via the api. it would make everything so much easier.
Has there been any news?
I'm going through serious GnomeWorks withdrawal :-)
i'm keeping an eye on things, albeit from a considerable distance. i'm not too surprised they went to a pure guid system instead of the encoded links. i suspect it's built more like the guild recipe stuff which kind of forgoes the whole link thing. perhaps they'll revert to links, but i'm not holding my breath.
ironically, when i first started my fork of skillet, tradelinks didn't exist so i encoded the tradeskill data as it was scanned for each user and then saved with the saved vars. it would be possible to revert to that kind of system perhaps. in fact, that's how smelting works for non-smelters. there are no smelting links so i have pre-generated smelting data. can't remember if it learns smelting recipes as it encounters smelters or whether it's hardcoded only.
this would fix the data collection, but not the live scanning for things like complete recipe lists and up-to-date recipe levels (it's interesting to see how often these change). honestly, i'm not sure why blizz don't just let us get that info via the api, but i'm sure wowhead doesn't mind.
Yeah, there's some chance that you could remove all the multi-char stuff and just do individual-player queuing of recursive recipes, vendor/bank interaction, etc. and it'd still be a lot better than other stuff out there, but the way the addon is currently coded it's a non-trivial piece of work to make that change. Since blizz seems to have acknowledged the bug now, and they seem to think that it's something they ought to fix, there's a decent chance they'll fix it. I'm suffering along with the rest of you while I have to use the default crafting UI. Engineering is basically impossible with having to manually recurse through recipes, and I nearly threw a brick through a window while doing the recursion necessary to manually craft the 3 levels of noodle cart for cooking... But the change Blizz needs to make is likely one they can do server-side without needing a client update, since the API doesn't need to change, just the string they return to us with the bitmap of available skills.
I'm keeping an eye on it, because I'm in pain.
In the meantime, Skillet has a beta for 5.4 that folks can use. I used it for a while the last time gnomeworks was significantly broken so that I had something besides the default interface to use.
Blizzard has acknowledged that there is a problem, although they don't have an ETA for a fix:
At least this implies that there has not been a design change, but rather a bug, which would mean that hopefully it's not permanent.
I wonder if this is related to new/modified code for the newly implemented connected realms feature. Since referencing toons on a realm connected to your own will require that the realm name be appended to the character name (e.g. "Jane-Aerie Peak" instead of simply "Jane"), everything that addresses toons within a virtual realm has to be able to accommodate this. It seems likely that this particular bit of code was overlooked.
I use GnomeWorks constantly and especially love the ability to queue items and then fetch mats from vendors and banks for crafting. I would strongly support the idea of a temporary limited version of GW that could be used to perform these core functions, until Blizz fixes the bug and allows re-enabling of all of GW's features.