Authors CurseForge

You may want to do :

local name, env = ...
_G[name] = env
setfenv(1, setmetatable(env, { __index = _G }))

To emulate what standard lua would look like:

module(name, package.seeall)

It's a good thing they are adding a way to retrieve completed quest history.
My only concern with this is that they are only giving quest id. If no api is provided to retrieve quest data we'll have to rely on a quest db.
would it be possible to build such db automatically from a wowhead automatic datamining? (in all available languages?)
The following information would be interesting for each quest id
quest name
quest zone
is daily
start npc (or start item)
end npc
previous quest id if in a quest chain
next quest id if in a quest chain

About dam time...

Quote from gagou

It's a good thing they are adding a way to retrieve completed quest history.
My only concern with this is that they are only giving quest id. If no api is provided to retrieve quest data we'll have to rely on a quest db.
would it be possible to build such db automatically from a wowhead automatic datamining? (in all available languages?)
The following information would be interesting for each quest id
quest name
quest zone
is daily
start npc (or start item)
end npc
previous quest id if in a quest chain
next quest id if in a quest chain

Several addons already maintain a database of quest data. Usually they get and distribute these data with the permission from one of the major database sites (usually Wowhead).

You can take a look at EveryQuest (only basic information) or LightHeaded (includes quest starters, enders, series, rewards) for two examples of addons that can easily incorporate the new quest completed data.

Sounds like time to start thinking about producing a quest database library that quest addons can plug into.

Quote from HunterZ

Sounds like time to start thinking about producing a quest database library that quest addons can plug into.

I believe you can already reference the quest data distributed with LightHeaded. However, it can require a lot of overhead due to the huge amount of data included with its comments.

I'm guessing that if someone made a community-maintained quest data library (sort of like periodic table but for quests), it would end up being a huge mess.

i started mining quest data for item rewards for libpt, but never got around to finishing it up. the mining wasn't too hard to manage. only was looking at quest level and rewards. i decided that i should probably not take ownership of such a thing until i had a mod ready that actually needed the data first...

I really see no point to having a lib for this. If there was a need, a lib would have been made. More specifically, there's no need for a common format... if an addon needs to mine the data, just do it for yourself.

What implication is this going to have for an addon like TourGuide? Will it be able to figure out which quests have been missed, and which ones have been completed?

Yep.

QueryQuestsCompleted() / QUEST_QUERY_COMPLETE / GetQuestsCompleted() is nice, but useless!

Current PTR (0.3.0.10571):
- QUEST_QUERY_COMPLETE is available every minute. (completing a quest does not change this timer)
- Only Quest ID is returned.
- No chance to get QuestText/QuestDescription and any other quest related info.

So far this is a completely useless feature, unless Blizzard wants to give stupid 3rd-party-websites a new playground.

I think Blizzard will NEVER provide some API calls to get detailed information for completed quests nor for all available quests. The amount of server/client data that would transmitted (even if you can get this data only once a minute, which makes sense btw, but why not 5min or 1h) is simply too big!
Unless QuestMapUpdateAllQuests/QuestMapGetNumQuestsForPOI/QuestMapGetQuestInfo and so on... is giving back any data: useless!!!
Sure, I wanna know which quests I missed on my >8300 quest ride...but Loremaster or other Achievements does not need such feature, they are too easy anyway. Hey, all quests are too easy. Who the fuck needs an addon for quests?

imagine:

title, description, level, faction, isTradeSkillQuest, isClassQuest, isGroup, isComplete, isDaily = GetQuestInfo(id)

-> pure overkill!

I kinda disagree that it's useless. Addon-side info is a solved thing. Just knowing if a quest has been completed or not has been missing. Blizz provides the missing pieces, and quite an array of addons will benefit, for example loremaster supporting addons, tourguide, questhistory etc etc. You can now query if others in the party have done any old quest not just the ones you can share. Pretty good addition really.

Quote from OrionShock

Posible, yes. Will Tek add that in... I hope

http://github.com/tekkub/TourGuide/tree/24cdf4197f5cecb5f037129d44a46c98c3acc83a

You people are slow.

And Kunda, just because you can't find a reason to use it doesn't make the API useless. It's *exactly* what many of us have been asking for for a *very* long time. We don't give a rat's ass about details, those can be mined, the user's quest history cannot.

LightHeaded, EveryQuest, TourGuide are great addon but none of them provide their data in other language than English.
Instead of doing an addon that would contain all the data they need why not give addon author access to a data repository which contain all basic quest data. They can then choose which data to use and which format to store the data in their addon.