You can just create the custom sets you need locally in AutoBar; just namespace them properly.
Indeed, however it is not about custom sets, it is about naming whatever set you have and adding other metadata to it. It is also about exactly how you combine and sort certain sets. Notably ones with conjured items which should always be preferred over non conjured ones, since you can always get your food or water dispenser to make more.
Take PT3Browser, it lets English clients browse the nodes as is which is English. Unfortunately it does the same thing for all other languages as well which is only helpful if you can read English.
This is vaguely ameliorated by actually looking at the items in the set, but if you have never seen them before you are screwed since they are not going to be in your characters "item space" and you will just see a list of red item ids with a value.
Adding a name to a node or some collection of sets allows you to tell a user what the intent of the set is: so for example: "Scrolls", or "Caster Buffs". Scrolls you may guess from the contents, but Caster Buffs will not be so obvious. I have not looked at the other mods that use PT3 yet, but I would imagine Baggins, PT3Browser, etc. could all benefit from some localization and naming of sets. Currently it does not look like PT3Bar publicly exposes PT3 Sets so it would just use PT3
1) Absolutely need localized description of the nodes AutoBar uses, as well as the icon texture for it.
As far as localization goes, in the interest of keeping the PT data light, that's left to the addons using it. Take a look at something like Cartographer_InstanceLoot for an example.. it pulls the localized zone info from Cartographer itself and reverse-translates the boss names using Babble.
For user-access in an AutoBar-config type setting, you could use a similar approach. For example, if a user is selecting from different sets, maybe just translate the second chunk of the namespace for display?
Not sure what you mean for the icon texture.
2) A lot of AutoBar's categories are combinations of nodes, concatenated in specific ways sometimes (so conjured items can have precedence over other items for example).
I've got no problem with throwing special sets in with tweaked values for sane AutoBar usage. Coincides with #4 so..
3) AutoBar needs a few other labels for some groups:
targetted, noncombat (food & water items), location (AQ, Outland, etc.), battleground, notusable (soul shards, arrows, etc.), flying (or something like it for 2.1)
Well, alias sets are handled pretty efficiently. So, not quite sure how you want to access the data, but, as long as the groupings already exist, you can do something like
For groupings that don't exist, we can work on splitting the current sets up.
4) AutoBar only needs a subset of the full PT3 set
Well, it'd be easy enough to make the data AutoBar needs into it's own mini-embed file, as long as all the data it needs is in sets that're named ["AutoBar.*"]. That way, you'd only be loading the data you need.
Localization of all the fields in the PT3 sets would be a staggering task that would have to essentially include all of Babble as well as a ton of other localization -- which would be a massive beast that I wouldn't want to include in any addon that didn't deal with the entire data library (and even for those that do), because even with something like AutoBar, you'd end up with localizations you didn't need (and you'd need to display the direct localization, when it may make more sense to display a more natural one).
Any chance of expanding TradeskillResultMats to include misc info?
e.g 10 Motes of Water = Primal Water, 5 Knotehide Leather = Heavy Knotehide Leather etc
<Wall of text warning>
Ok, so boiling this all down with a concrete example: what I need is a layer that adds meta data to arbitrary nodes. For example Bandages: PT3 does a great job of mapping say "Consumable.Bandage" to a list of items. These are further broken up into Basic bandages and Battleground bandages which has subgroups for the Alterac Valley, Arathi Basin and Warsong Gulch Battlegrounds. But it is only a 1-many mapping, AutoBar needs to map several metadata attributes to particular nodes:
AutoBar needs to know:
* The localized names for "Bandages", "Alterac Valley Bandages", "Arathi Basin Bandages", "Warsong Gulch Bandages".
* The icon used to represent these 4 nodes, in this case "INV_Misc_Bandage_Netherweave_Heavy" for Bandages and "INV_Misc_Bandage_12" (Heavy Runecloth) for the other 3
* The fact that bandages are targetted (can be used on self or a friendly target)
* For each of the BG bandages the location that they are restricted to: Alterac Valley; Arathi Basin; Warsong Gulch respectively.
Note: Even though here there is a correspondence between the node & its label this is not always the case. As Nymbia mentioned sometimes a more natural description would be used.
Now clearly some of this info is of no use to other mods. Some of it I think is. Providing every single node with all possible info is obviously ridiculous and should not even be contemplated. However, if the nodes AutoBar is interrested in and say the Baggins ones are all done then you probably have say 90 - 99% of the interresting inventory mod categories covered.
At that point if someone were to write (or split out from existing code) a standard PT3 picker component it could have a simplified setting only showing those nodes which the collective wisdom of AutoBar and Baggins users already identified. Moreover, for our German, Spanish, French, Korean and simplified and traditional Chinese users they will be looking at something that is translated for them. They would still be screwed for the vast majority of sets in PT3 which are not translated, but those tend to be the ones they are not interrested in. (As noted, reverse translation can be used for some of the Boss loots etc.)
Potential Design:
* Ok, so I think for sure nobody wants any extra stuff in PT3 itself since a lot of mods use it as is without any further needs. A seperate library should thus load & deal with it.
* Metadata particular to a mod should split out into its own file.
* Perhaps PT3 is extended to be able to add a metadata field to a particular node, and a function added to retrieve it. A metadata lib then simply populates the field with its particular set of values.
* I think it makes sense for properties to be inherited. Thus in the example above Bandages are targeted, and thus so are the particular BattleGround bandages.
* Obviously this is all intimately related to PT3 so potentially it can all be handled with compressSplit and data.lua
Benefits:
* Internationalization, but only for the mods that need it, and then only for sets they are interrested in.
* PT3Browser would be able to be extended to provide translated views for sets that have metadata (ie those sets that are interresting to the mods a particular user has loaded)
* A common PT3Picker Interface. I know Baggins and AutoBar need to be able to pick PT3 sets and could thus benefit from a common picking mechanism that deals with the translation issues. PT3Bar may let users pick sets at a future date.
* AutoBar sets and the translation work associated would be externalized and available for use beyond just AutoBar. Same for any other mod that participates in the metadata scheme.
* AutoBar would go from a pretty lame user of PT3 to making full use of it.
This seems like the right place to suggest a category for flasks. Flasks do not appear to be counted as consumables in PT, so they'd need to be added there as well as an additional category say Consumable.flask
To make the changes take effect in the other files, run compresssplit.lua in the command line.
how exactly do i do that? i've added some rep turnins (for nethwerwing) and all the new netherdrake mounts but i can't seem to figure out how to get it to rebuild.
Consumable.Warlock.Spellstone and Consumable.Warlock.Soulstone appear to be switched with each other. I was using PT3Browser last night and noticed that the Spellstones were listed under the Soulstone heading and vice-versa.
Ark Inventory has started using pt3 and a lot of the categories are messed up. For instance, all the cloth was labeled as blacksmithing instead of tailoring.
What's pt3browser and where should I list my category suggestions?
To make the changes take effect in the other files, run compresssplit.lua in the command line.
how exactly do i do that? i've added some rep turnins (for nethwerwing) and all the new netherdrake mounts but i can't seem to figure out how to get it to rebuild.
Just commit what you've got, I'll take care of it.
Ark Inventory has started using pt3 and a lot of the categories are messed up. For instance, all the cloth was labeled as blacksmithing instead of tailoring.
thats an AI code issue, the asignment code is still in flux.
Quote from Nymbia »
Just commit what you've got, I'll take care of it.
changes uploaded. i did eventually manage to get the compresssplit lua to run but it didn't seem to make changes to some of the files in the subdirectories that i had changed in data.lua
figured out why, the flying mount entry was missing a comma at the end so it wasnt getting populated into the sub directory file properly - i fixed it and re-uploaded.
Not sure if I'm in the right place, if not, forgive me.
I'm using "King of the Jungle". I have a food ID 12212 Jungle Stew that doesn't show anywhere. I believe KotJ is using pt3 for items.
Does this need to be added to the pt3 library?
I love ace mods, but have no idea how they work!
Thanks
Slice
*edit*
Using pt3 browser I find this and many others under food - misc. KotJ does not have this category. I guess I will just manually feed for awhile.
I was looking at the Gear Tree, and it only has one branch. "Socketed" Obviously there should be a non-socketed branch.
Also, is there a way to make PT3Browser a windowed mod? It would make searching for an item's category easier since you would have the search field up statically and not have to keep it in focus to type in it.
The Item 'Stringy Vulture Meat' is missing from category 'Consumable.Food.Inedible.Meat'.
There should be a category for quest items. And a subdirectory of which reputation that quest is associated with. (This would include all quest items, above and beyond just the rep turnins.) Like this:
QuestItem.Alliance
QuestItem.Horde
QuestItem.Alliance.Darnassus
QuestItem.Steamwheedle Cartel.Booty Bay
QuestItem.Shattrath City.Lower City
There should also be categories for gear. Like this:
There should be a category for quest items. And a subdirectory of which reputation that quest is associated with. (This would include all quest items, above and beyond just the rep turnins.)...
There should also be categories for gear...
Well this is not exactly a mod. This is an item database and as such it is used by other mods. Now PT3Browser lets you browse the entire thing, but every other mod that uses it uses only a subset of the items. So really the only reason stuff gets put into Periodic Table is because some client mod(s) that use it needs it. In that sense this mod is already "100% complete".
So the question becomes: why do you need these items included? Are you writing a mod that will use them?
As an example, I have checked in a new set "Consumable.Quest.Usable" which has quest items you need to right click to use. AutoBar uses them for a button that lets you click them without opening your bags. Someone with the Baggins mod may use it to see what quest trash they have lying about and perhaps to make sure they dont leave the bank without them.
But this is just a subset of what you propose, so enquiring minds want to know where you are going with this request.
There should be a category for quest items. And a subdirectory of which reputation that quest is associated with. (This would include all quest items, above and beyond just the rep turnins.)...
There should also be categories for gear...
Well this is not exactly a mod. This is an item database and as such it is used by other mods. Now PT3Browser lets you browse the entire thing, but every other mod that uses it uses only a subset of the items. So really the only reason stuff gets put into Periodic Table is because some client mod(s) that use it needs it. In that sense this mod is already "100% complete".
So the question becomes: why do you need these items included? Are you writing a mod that will use them?
As an example, I have checked in a new set "Consumable.Quest.Usable" which has quest items you need to right click to use. AutoBar uses them for a button that lets you click them without opening your bags. Someone with the Baggins mod may use it to see what quest trash they have lying about and perhaps to make sure they dont leave the bank without them.
But this is just a subset of what you propose, so enquiring minds want to know where you are going with this request.
Would this have anything to do with ArkInventory directing us to use PT3Browser to make our categories for our bars now? (The default subcats are gone from the latest version(like trinkets, weapons). So we have to 'create" our own using PT3...is my understanding so far...)
Not sure if I'm in the right place, if not, forgive me.
I'm using "King of the Jungle". I have a food ID 12212 Jungle Stew that doesn't show anywhere. I believe KotJ is using pt3 for items.
Does this need to be added to the pt3 library?
I love ace mods, but have no idea how they work!
Thanks
Slice
*edit*
Using pt3 browser I find this and many others under food - misc. KotJ does not have this category. I guess I will just manually feed for awhile.
If any food should be classified for fruit/bread or whatever the pet eats, and it is classified under misc, then it is misclassified. So yes, you should suggest any food changes here.
Regarding the subject : Underspore Pod and Skyguard Rations should both be classified as fruit. I changed that in the data.lua file. Am i correct that you make sure the data is done with compressplit so it ends up in the right spot ?
any chance the API could be altered to ignore case on the set names? would make it so much easier for mod authors to allow manual user input of set names?
or could the API force all input set names to lowercase and have the setnames changed to lowercase in the files?
or could you add another API function that will return the proper name for a set given any case alternative?
There should be a category for quest items. And a subdirectory of which reputation that quest is associated with. (This would include all quest items, above and beyond just the rep turnins.)...
There should also be categories for gear...
Well this is not exactly a mod. This is an item database and as such it is used by other mods. Now PT3Browser lets you browse the entire thing, but every other mod that uses it uses only a subset of the items. So really the only reason stuff gets put into Periodic Table is because some client mod(s) that use it needs it. In that sense this mod is already "100% complete".
So the question becomes: why do you need these items included? Are you writing a mod that will use them?
As an example, I have checked in a new set "Consumable.Quest.Usable" which has quest items you need to right click to use. AutoBar uses them for a button that lets you click them without opening your bags. Someone with the Baggins mod may use it to see what quest trash they have lying about and perhaps to make sure they dont leave the bank without them.
But this is just a subset of what you propose, so enquiring minds want to know where you are going with this request.
Ark Inventory now uses this library to help sort the inventory. I would like to be able to sort my gear, and my quest items. That's pretty much the reason for the request. The turn ins are really helpful, but currently there is no category in pt3 for just gear in general, or quests in general. It's the only classification/category that I have to resort to AI's categories instead of PT3's categories.
As an item classification database, you'd think that it should include every item and try to be a /complete/ item classification database. I wouldn't mind collecting data and helping out. Data collection is something I'm pretty good at.
Rumsey Rum Dark should be labeled as Consumable.Buff.Stamina.Self, and any other categories that would match. (It's basically a lower-end version of Rumsey Rum Black Label, which is already in that category, so Rumsey Rum Dark can just match up with wherever that is listed.)
Indeed, however it is not about custom sets, it is about naming whatever set you have and adding other metadata to it. It is also about exactly how you combine and sort certain sets. Notably ones with conjured items which should always be preferred over non conjured ones, since you can always get your food or water dispenser to make more.
Take PT3Browser, it lets English clients browse the nodes as is which is English. Unfortunately it does the same thing for all other languages as well which is only helpful if you can read English.
This is vaguely ameliorated by actually looking at the items in the set, but if you have never seen them before you are screwed since they are not going to be in your characters "item space" and you will just see a list of red item ids with a value.
Adding a name to a node or some collection of sets allows you to tell a user what the intent of the set is: so for example: "Scrolls", or "Caster Buffs". Scrolls you may guess from the contents, but Caster Buffs will not be so obvious. I have not looked at the other mods that use PT3 yet, but I would imagine Baggins, PT3Browser, etc. could all benefit from some localization and naming of sets. Currently it does not look like PT3Bar publicly exposes PT3 Sets so it would just use PT3
As far as localization goes, in the interest of keeping the PT data light, that's left to the addons using it. Take a look at something like Cartographer_InstanceLoot for an example.. it pulls the localized zone info from Cartographer itself and reverse-translates the boss names using Babble.
For user-access in an AutoBar-config type setting, you could use a similar approach. For example, if a user is selecting from different sets, maybe just translate the second chunk of the namespace for display?
Not sure what you mean for the icon texture.
I've got no problem with throwing special sets in with tweaked values for sane AutoBar usage. Coincides with #4 so..Well, alias sets are handled pretty efficiently. So, not quite sure how you want to access the data, but, as long as the groupings already exist, you can do something like For groupings that don't exist, we can work on splitting the current sets up.Well, it'd be easy enough to make the data AutoBar needs into it's own mini-embed file, as long as all the data it needs is in sets that're named ["AutoBar.*"]. That way, you'd only be loading the data you need.
Localization of all the fields in the PT3 sets would be a staggering task that would have to essentially include all of Babble as well as a ton of other localization -- which would be a massive beast that I wouldn't want to include in any addon that didn't deal with the entire data library (and even for those that do), because even with something like AutoBar, you'd end up with localizations you didn't need (and you'd need to display the direct localization, when it may make more sense to display a more natural one).
e.g 10 Motes of Water = Primal Water, 5 Knotehide Leather = Heavy Knotehide Leather etc
Ok, so boiling this all down with a concrete example: what I need is a layer that adds meta data to arbitrary nodes. For example Bandages: PT3 does a great job of mapping say "Consumable.Bandage" to a list of items. These are further broken up into Basic bandages and Battleground bandages which has subgroups for the Alterac Valley, Arathi Basin and Warsong Gulch Battlegrounds. But it is only a 1-many mapping, AutoBar needs to map several metadata attributes to particular nodes:
AutoBar needs to know:
* The localized names for "Bandages", "Alterac Valley Bandages", "Arathi Basin Bandages", "Warsong Gulch Bandages".
* The icon used to represent these 4 nodes, in this case "INV_Misc_Bandage_Netherweave_Heavy" for Bandages and "INV_Misc_Bandage_12" (Heavy Runecloth) for the other 3
* The fact that bandages are targetted (can be used on self or a friendly target)
* For each of the BG bandages the location that they are restricted to: Alterac Valley; Arathi Basin; Warsong Gulch respectively.
Note: Even though here there is a correspondence between the node & its label this is not always the case. As Nymbia mentioned sometimes a more natural description would be used.
Now clearly some of this info is of no use to other mods. Some of it I think is. Providing every single node with all possible info is obviously ridiculous and should not even be contemplated. However, if the nodes AutoBar is interrested in and say the Baggins ones are all done then you probably have say 90 - 99% of the interresting inventory mod categories covered.
At that point if someone were to write (or split out from existing code) a standard PT3 picker component it could have a simplified setting only showing those nodes which the collective wisdom of AutoBar and Baggins users already identified. Moreover, for our German, Spanish, French, Korean and simplified and traditional Chinese users they will be looking at something that is translated for them. They would still be screwed for the vast majority of sets in PT3 which are not translated, but those tend to be the ones they are not interrested in. (As noted, reverse translation can be used for some of the Boss loots etc.)
Potential Design:
* Ok, so I think for sure nobody wants any extra stuff in PT3 itself since a lot of mods use it as is without any further needs. A seperate library should thus load & deal with it.
* Metadata particular to a mod should split out into its own file.
* Perhaps PT3 is extended to be able to add a metadata field to a particular node, and a function added to retrieve it. A metadata lib then simply populates the field with its particular set of values.
* I think it makes sense for properties to be inherited. Thus in the example above Bandages are targeted, and thus so are the particular BattleGround bandages.
* Obviously this is all intimately related to PT3 so potentially it can all be handled with compressSplit and data.lua
Benefits:
* Internationalization, but only for the mods that need it, and then only for sets they are interrested in.
* PT3Browser would be able to be extended to provide translated views for sets that have metadata (ie those sets that are interresting to the mods a particular user has loaded)
* A common PT3Picker Interface. I know Baggins and AutoBar need to be able to pick PT3 sets and could thus benefit from a common picking mechanism that deals with the translation issues. PT3Bar may let users pick sets at a future date.
* AutoBar sets and the translation work associated would be externalized and available for use beyond just AutoBar. Same for any other mod that participates in the metadata scheme.
* AutoBar would go from a pretty lame user of PT3 to making full use of it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumTo make the changes take effect in the other files, run compresssplit.lua in the command line.
how exactly do i do that? i've added some rep turnins (for nethwerwing) and all the new netherdrake mounts but i can't seem to figure out how to get it to rebuild.
What's pt3browser and where should I list my category suggestions?
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumthats an AI code issue, the asignment code is still in flux.
changes uploaded. i did eventually manage to get the compresssplit lua to run but it didn't seem to make changes to some of the files in the subdirectories that i had changed in data.lua
figured out why, the flying mount entry was missing a comma at the end so it wasnt getting populated into the sub directory file properly - i fixed it and re-uploaded.
I'm using "King of the Jungle". I have a food ID 12212 Jungle Stew that doesn't show anywhere. I believe KotJ is using pt3 for items.
Does this need to be added to the pt3 library?
I love ace mods, but have no idea how they work!
Thanks
Slice
*edit*
Using pt3 browser I find this and many others under food - misc. KotJ does not have this category. I guess I will just manually feed for awhile.
Also, is there a way to make PT3Browser a windowed mod? It would make searching for an item's category easier since you would have the search field up statically and not have to keep it in focus to type in it.
There should be a category for quest items. And a subdirectory of which reputation that quest is associated with. (This would include all quest items, above and beyond just the rep turnins.) Like this:
QuestItem.Alliance
QuestItem.Horde
QuestItem.Alliance.Darnassus
QuestItem.Steamwheedle Cartel.Booty Bay
QuestItem.Shattrath City.Lower City
There should also be categories for gear. Like this:
Cloth.Head
Cloth.Shoulder
Leather.Head
Leather.Shoulder
Mace.Two-hand
Mace.One-hand
Mace.Off-hand
If you include that, this mod would be like 100% complete.
If you need data collected, just tell me how to collect it and where to send it!
Well this is not exactly a mod. This is an item database and as such it is used by other mods. Now PT3Browser lets you browse the entire thing, but every other mod that uses it uses only a subset of the items. So really the only reason stuff gets put into Periodic Table is because some client mod(s) that use it needs it. In that sense this mod is already "100% complete".
So the question becomes: why do you need these items included? Are you writing a mod that will use them?
As an example, I have checked in a new set "Consumable.Quest.Usable" which has quest items you need to right click to use. AutoBar uses them for a button that lets you click them without opening your bags. Someone with the Baggins mod may use it to see what quest trash they have lying about and perhaps to make sure they dont leave the bank without them.
But this is just a subset of what you propose, so enquiring minds want to know where you are going with this request.
Would this have anything to do with ArkInventory directing us to use PT3Browser to make our categories for our bars now? (The default subcats are gone from the latest version(like trinkets, weapons). So we have to 'create" our own using PT3...is my understanding so far...)
If any food should be classified for fruit/bread or whatever the pet eats, and it is classified under misc, then it is misclassified. So yes, you should suggest any food changes here.
Regarding the subject : Underspore Pod and Skyguard Rations should both be classified as fruit. I changed that in the data.lua file. Am i correct that you make sure the data is done with compressplit so it ends up in the right spot ?
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumor could the API force all input set names to lowercase and have the setnames changed to lowercase in the files?
or could you add another API function that will return the proper name for a set given any case alternative?
or something else? any ideas?
Ark Inventory now uses this library to help sort the inventory. I would like to be able to sort my gear, and my quest items. That's pretty much the reason for the request. The turn ins are really helpful, but currently there is no category in pt3 for just gear in general, or quests in general. It's the only classification/category that I have to resort to AI's categories instead of PT3's categories.
As an item classification database, you'd think that it should include every item and try to be a /complete/ item classification database. I wouldn't mind collecting data and helping out. Data collection is something I'm pretty good at.