Forum Discussion Thread
- Editing - how to maintain PeriodicTable.
- Usage - how to include and use PT sets in your mod.
- API - how to use PeriodicTable in your mod.
- Forum - discussion thread.
- Brush up on your chemistry knowledge.
Periodic Table adds organizes many WoW items and spells into sets. Like most Ace addons it's focus is efficiency. PT is a LibStub library for managing these sets (ex: Misc.Spell.Mount, Consumable.Food.Edible.Cheese, Misc.Minipet, ClassSpell) for other addons.
If you are looking for an Ace'd alternative to ReagentInfo (the tooltip display) check out Mendeleev by MoonWolf, which you can find on Curse or WoWI.
Item sets are stored as a comma-delimited strings and parsed out into a table only if requested. This speeds up load time and ensures that memory is only used for sets that are actively used.
If you are interested in using PT with your mod feel free to read the source code (there's not a lot). The comments will tell you everything you need to know.
Modules
PeriodicTable's "modules" are simply sets of sets. Particular mods can link the exact sets they need.
- ClassSpell - Spells for all classes with subsets for each tree.
- Consumable - Foods, Potions, Elixirs, Buffing items including type (fruit, meat, etc), quality (inedible, buff) and HP-recovery info.
- CurrencyItems - Items purchasable with various currencies.
- Gear - Socketed gear, Trinkets, Vendor Badge gear
- GearSet - Set Gear. Tier, Reputation, PvP, etc.
- InstanceLoot - Loot tables for instances and the bosses in those instances (only higher-level instances currently)
- InstanceLootHeroic - Loot tables for heroic instances
- Misc - Random stuff like Currency, Containers, Mounts, etc.
- Reputation - Rewards and Turnins for factions
- Tradeskill : Profession recipes
- TradeskillLevels : Profession recipes with level requirements
- TradeskillResultMats : Some kinda mats required sets for the recipes it looks like
Facts
- Date created
- Sep 21, 2008
- Category
- Last update
- Oct 07, 2016
- Development stage
- Release
- Language
- enUS
- License
- GNU Lesser General Public License version 2.1 (LGPLv2.1)
- Curse link
- LibPeriodicTable-3.1
- Reverse relationships
- 48
- Downloads
- 314,634
- Recent files
- Reply
- #28
Innovindil Jul 22, 2016 at 15:29 UTC - 0 likes@MuffinManKen: Go
Will do. Thanks Ken.
- Reply
- #27
MuffinManKen Jul 22, 2016 at 11:26 UTC - 0 likesComments are not the best way to report issues. I recommend entering tickets. Make a single ticket per problem and try to be as detailed as possible.
- Reply
- #26
Innovindil Jul 22, 2016 at 06:26 UTC - 0 likesHey folks ... PT3.1 is great for helping me filter my bags by section, but a lot of WoD data seems to be missing (Tier 17+), or is unclassified (Most Garrison and Quest items). Any chance of a more comprehensive update for WoD and Legion items?
Thanks!
- Reply
- #25
Innovindil Jun 25, 2015 at 01:23 UTC - 0 likesHello ... would it be possible to get Tier 17 and 18 added?
Thanks!
- Reply
- #24
nebula169 Jan 03, 2015 at 06:32 UTC - 0 likes@MuffinManKen: Go
should add Garrison related stuff ! eg, follower upgrade items (Consumable.Follower?) and work order turn in items (Misc.Currency.Garrison? Tradeskill.Gather.Garrison?)
thanks for keeping this updated
- Reply
- #23
MuffinManKen Jul 25, 2014 at 15:38 UTC - 0 likesI created a new addon that adds a few new sets:
http:www.curse.com/addons/wow/libpt-muffinsets
- Reply
- #22
Innovindil May 21, 2014 at 21:40 UTC - 0 likesHey there ... I've noticed that the GearSet has a couple different formats
Pre MoP looks like this:
MoP looks like this:
Any chance we can get it all formatted to the PreMoP standard? I have my bag addons filtering by ilvl and with each update i hve to manually copy/past the T14-T16 to the old format.
Since the class is now in front of the ilvl it wont let sort T14+ by ilvl into bag/bank groups. I'd have to make a group for each class+ilvl which is more worked than needed.
Thanks!
- Reply
- #21
Elkano Sep 23, 2013 at 08:37 UTC - 1 likeI'm still around breathing :) sadly, comments here are easy to miss... LPT has been split into separate data libs for a long time; as a lib it's meant to be run embedded by default so you'd only add those parts you need. That said, in the five years LPT-3.1 has been around by now a lot has changed within WoW. Some of these changes didn't fit that well into the data structures in place. Also, the amount of data has grown... there are almost 90k different items in the client by now (well, some aren't used). So the history has resulted in some brownfields. Also, data mining them from WoWHead has always been a pain (parsing for JSON data, 200 items max, filters, wrong data, ...), WoWDB hasn't been any better (even though we were promised special API calls :/ )
The core library for LPT is still doing fine and I don't see any needed changes to it. Thus a new version with changed sets would imho still be a 3.x version. The data miner could use a some generic work, maybe splitting it into multiple files (core functionality, data set specific stuff) to make maintaining it a bit easier. For the data sets themselves, there are lots that need serious treatment, e.g. the instance data (currently there is a split into normal, heroic, lfr, though imho the only reasonable split, if any, would be group vs raid, using lfr/normal/hero and size [10/25] as sub-splits where applicable).
Regarding the "which addons use it", that info sure would be nice to have. There is this "reverse relationship" for projects but iirc it has been broken for ages.
volunteer CurseForge moderator
This posting is made of 100% recycled electrons.
- Reply
- #20
MuffinManKen Sep 11, 2013 at 18:19 UTC - 0 likesElkano is the Manager/Author, so I think he'd need to be on board for any major changes. I have no idea how active he is in WoW and/or addon development at this point.
- Reply
- #19
JCinDE Aug 28, 2013 at 01:59 UTC - 0 likes@ckaotik: Go
I'd suggest just advancing to LibPeriodicTable-4.0 rather than trying to tie it to a game version. LPT4 would be the core functionality and have no data libraries at all, though it might define a few suggested "official" high level namespaces and offer a template for a dataminer.
LPT3.1 data libraries could be upgraded, repackaged, or split as needed to create more specialized, more tightly controlled LPT4 versions. Authors that upgrade to LPT4 would embed the core and any necessary data libraries and possibly add specialized data within their own addons (AutoBar).
I'm sure I'm not the first to say so, but it would be nice if there were a way to officially know which addons use which data libraries and namespaces so that the impact of changes to them could be known ahead of time. Separating the data from the LPT core functionality would be a step in that direction too.