Quests complete after gossip/loot and in between
yoshimo opened this issue ยท 4 comments
There seems to be a new type of tracking quests used in BFA.
On Zuldazaar there is the frog loa, Kragwa. All over the place are his minions, smaller frogs hidden in caves and behind trees. You can talk to them and tell them to go home.
This seems to complete a quest, but we do not track that yet as there is no loot event like the treasure chests.
"New quest completed 53426", -- [1676] "frog moved on the sethrak front", -- [1677] "Player: X (-863) 863:25.82,40.47", -- [1678]
"more krogwa frogs", -- [1714] "New quest completed 53420", -- [1715]
maybe we can automate this a bit more and include the proper npc-id of the target.
This would be also intresting for the split war campaign of the horde in BfA where depending on your gossip choices the quest chains differ from each other.
I think we should keep infos like "interacted npc &gossip option" and "ObjectID which we just looted" (via GetLootSlotInfo(1)) as well as the items received. That would help to get the Shadowland info in a more detailed way. They like to give you items that immediately starts quests.
Similiar to HandyNotes:Shadowlands dumpt all completed quests in regular interval and note down the players position when quests changed their completed state. Not sure how we can get the objectid of the new treasure type yet, where there is no loot window open. Maybe we will figure that out later.
We should also do a "/grail cb" after every turnin to see quests that complete each other.
I think doing things like "/grail cb" is fine for those gathering data, but it would be a little overkill for normal play. Perhaps since people are turning in quests at the time, the overhead would not really be noticed that much and we can play around with being able to do that. I would have to figure out a way to record this properly so it can be gathered to make the proper ODC: codes. It is getting more difficult for some things that mark quests complete if Blizzard does not provide hooks. Luckily we can record anything that posts the event, and it seems to work pretty well. There is only one case where I have had a problem recently, and that is truly an edge case which the vast majority of people will never encounter.