Quest.Raid.Horde/Alliance/Both = "QuestID"
Quest.Group.Horde/Alliance/Both = "QuestID"
How about something like:
Quest.Raid.HordeOnly = "QuestID:minlevel:questlevel:choice1xcount;choice2xcount:rewardxcount...,QuestID..."
Quest.Raid.AllianceOnly = "QuestID..."
Quest.Raid.Both = "QuestID..."
Quest.Raid.Horde = "m,Quest.Raid.HordeOnly,Quest.Raid.Both"
Quest.Raid.Alliance = "m,Quest.Raid.AllianceOnly,Quest.Raid.Both"
Quest.Raid.All = "m,Quest.Raid.HordeOnly,Quest.Raid.AllianceOnly,Quest.Raid.Both"
and the same for Group and Daily... then
The syntax m,set,set,set.." means that set is expanded to contain the contents of all the listed sets.
Another option if the size of the quest data is large is to split it into 3 groups.
QuestHorde.Raid = "..."
QuestAlliance.Raid = "QuestID..."
QuestBoth.Raid = "QuestID..."
Quest.Raid.Horde = "m,QuestHorde.Raid,QuestBoth.Raid"
Quest.Raid.Alliance = "m,QuestAlliance.Raid,QuestBoth.Raid"
Quest.Raid.All = "m,QuestHorde.Raid,QuestAlliance.Raid,QuestBoth.Raid"
and the same for Group and Daily...
The advantage of the later approach is that QuestHorde, QuestAlliance, and QuestBoth can be split into separate LoD addons, but it's not as clean.
okay, so i think the data is complete. should is push my files thru the svn or is there a different way to have somebody verify it's cool first? also, i decided to go with "/" instead of "#".
There are a few other sets (TradeskillResultMats, Tradeskill.Gem.Cut, Reputation.Turnin) already using ";" to separate values so it might be the better choice for consistency. Also "/" is also already used for to mean "per" in other sets. For example 300 rep per 5 items turned in might be written as 300/5.
we could change it to use @file-date-integer@ instead of $Revision: x $ though that would mean we would have to add special treatment if a svn checkout is used since then that keyword wouldn't be replaced. though a svn cehckout can theoretically be assumed as the latest version I think.
(see: http://www.wowace.com/knowledge-base/repository-keyword-substitutions/ )
Problem with something like that is it might cause problems for addons that are not hosted at wowace that bring in LibPeriodicTable-3.1 via svn:externals.
Someone already committed a fix to inflate them anyways it appears.
Looks like there is a "bug" in the version of tables in periodic table as a side effect of the SVN move. Since the version numbers are now lower, older tables are overriding newer ones. Also the Autobar is hard coded to use version 54697. So even if only new copies of the library is used Gear, Misc and Tradeskill will risk being overwritten by LibPeriodicTable-3.1-AutoBar.