Quests 32468 - 32471 keeps completing and unflagging
bartekleon opened this issue · 7 comments
Those are S.E.L.F.I.E. camera quests, they do this thing for many years, nothing we can do about it 😥
I believe it was reported to Blizzard but nothing has changed.
I realised that if value
is false
you could literally just check if the quest has been already completed or not if app.CurrentCharacter.Quests[key] == 1 then
so for simplicity code would look something like that i guess 🤷🏻
the only thing that would need to be check is edge cases - some quests that might be saved as completed
but shouldn't be -- repeatable quests or something like that
I have no idea why it is happening tho
@kmdrGroch because of repeatable quests (and other hidden triggers)
@kmdrGroch Yea that whole else
branch is specifically to report any QuestID which is no longer flagged as complete on your character. This happens quite a lot due to how Blizzard tracks various actions in the game, so restricting that from showing at all is detrimental to its purpose.
@Darkal31 experiences this issue as well on one character, but this is entirely on Blizzard constantly switching those QuestID's on and off... and ATT detecting those changes :/
Maybe can add a special table that those of you with the issue can uncomment in the code manually to prevent the spam, but it seems a little unnecessary to add extra logic for everyone to prevent a situation that has only ever been reported by two people.
that has only ever been reported by two people
@ImUnicke nah, not by two people, I have this issue too, but it doesn't trigger on every completed quest, just from time to time
In fact, just search "camera" in DfA Discord, it's been discussed plenty of times. You can even log out at the unfortunate time to have these quests marked as not completed which led to them being marked as "missing from API" on the site.
It's just a Blizzard issue on their side for whatever reason for specific accounts/characters. The quests aren't being triggered to the client, ATT is just noticing that they've changed state due to other events triggering the quest refresh. Keep spamming those bug reports I guess...