I am wanting to bring more notice to a change that come in a recent build of the 3.3 PTR.

You know how almost every week someone's asking about an addon that gives them a history of quests they've completed and our answer is always "No that information isn't available via the api therefore can't be done in an addon"

* NEW - QueryQuestsCompleted() requests that the server send the client a list of completed quest ids. Once the list is received the QUEST_QUERY_COMPLETE event is fired. (There is a limit on how frequently this can be called)
* NEW - tbl = GetQuestsCompleted([tbl]) populates a table (creating one if necessary) with the ids of completed quests. (The format of this table may change before release)

I did post this yesterday in my 3.3 thread but no one answered to say OMG! OMG

There was a severe lack of dancing bananas too

Front243 also posted something to the Carbonite forums too but he went unloved too

<----------------- adopts kicked puppy look

Not feeling the love here people

__________________
tuba_man on Apple test labs : "I imagine a brushed-aluminum room with a floor made of keyboards, each one plugged into a different test box somewhere. Someone is tasked with tossing a box full of cats (all wearing turtlenecks) into this room. If none of the systems catch fire within 30 minutes, testing is complete. Someone else must remove the cats. All have iPods." (http://community.livejournal.com/tec...t/2018070.html)

__________________
tuba_man on Apple test labs : "I imagine a brushed-aluminum room with a floor made of keyboards, each one plugged into a different test box somewhere. Someone is tasked with tossing a box full of cats (all wearing turtlenecks) into this room. If none of the systems catch fire within 30 minutes, testing is complete. Someone else must remove the cats. All have iPods." (http://community.livejournal.com/tec...t/2018070.html)

__________________
tuba_man on Apple test labs : "I imagine a brushed-aluminum room with a floor made of keyboards, each one plugged into a different test box somewhere. Someone is tasked with tossing a box full of cats (all wearing turtlenecks) into this room. If none of the systems catch fire within 30 minutes, testing is complete. Someone else must remove the cats. All have iPods." (http://community.livejournal.com/tec...t/2018070.html)

__________________
tuba_man on Apple test labs : "I imagine a brushed-aluminum room with a floor made of keyboards, each one plugged into a different test box somewhere. Someone is tasked with tossing a box full of cats (all wearing turtlenecks) into this room. If none of the systems catch fire within 30 minutes, testing is complete. Someone else must remove the cats. All have iPods." (http://community.livejournal.com/tec...t/2018070.html)

In some cases (not all, it seems), the data returned is in an inconsistent format.

Some portion of the data will take the form (when viewing the saved info):

{
true,
nil,
nil,
true,
}

while the rest will appear as:

{
[12345] = true,
[12857] = true,
[2345] = true,
[87432] = true,
}

In the first, you will have both "true" and "nil" as values and the keys (questids) are sequential. In the second, the keys are random and the value will always be true. It's easy to handle, but it helps to know it's there.