Awesome stuff @
Rooster, I'd love to see what you have so far.
I intend to collect the contents of all POK vendors (and technically any other zone you want to add) via a macro I'm going to write (probably after some sleep). The idea is to store it in a way that can be managed with loops to check all vendors and basically store the data as follows.
[Merchant1]
Name=Obviously this is where the merchants name will be.
ZoneFullName=Plane of Knowledge (I'll use this with the Travel.mac/EasyFind setup to navigate to the Zone)
Location=Y X Z coordinate so that I can issue /nav loc Y X Z from the macro. (Will get the location I am standing when it parses the vendors inventory, not the vendors actual location so that I don't navigate inside of the vendor)
Item1=
Item2=
Item3=
For the item, I'll have another nested loop to check their contents. The idea is for 1 to ${MerchantCount} (which will be counted before hand based on the highest Merchant# stored in the INI) check nested for 1 to ${ItemCount} which will be calculated based on the highest Item# for each merchant, check for the item I need, if not found check the next merchant, if it is found then check if my zone is the zone the merchant is in, otherwise navigate to that zone using MQ2EasyFind and the zoneguide (that setup already coded in my travel.mac). Once there, navigate to the Merchant#'s location, target them, /click right target, and buy the Quantity needed.
Seems like it's going to be a fair amount of code just for that portion, but I promise the harder part is going to be porting in the sections of farm.mac and manually inputing location information for dropped items to farm them.
But before I can set up a lot of this I'll basically be writing some utility macros that the public will never have, just to generate the INI's for me. Considering we are talking about somewhere in the neighborhood of 15,800 recipes that I need data on across all the tradeskills.
This won't be something that is done overnight as far as the completed project goes.
Of course, the format will support additional recipes, but at the moment I'm only trying to collect data for the recipes that would populate a /output recipe tradeskillname file from EQ.
http://eqrecipes.free.fr/ is a link to a list of the recipes we're trying to handle right now.
Once the recipes are fully populated for each tradeskill I also intend to generate another INI. IE: ShoppingList_Smithing.ini where I can parse the recipe file for each component and populate it into the INI. IE:
Smithing.ini
[ShoppingList]
Component1=ItemName|Quantity
Component2=ItemName|Quantity
Component3=ItemName|Quantity
etc. Which I can then use to compare to the merchant shopping list to add tags for VendorPurchased
Component1=ItemName|Quantity|Vendor|VenderName|VendorZone etc.
It's going to be interesting coding this. As the components are being individually completed and everything builds up to a more complete proof of concept I am getting a lil excited :-)