Questie

Questie

122M Downloads

Bug with some quests not showing up in Tracker

Gogo1951 opened this issue ยท 12 comments

commented

[[8] The Ravaged Caravan (751)] - check this one out? It should have some objective. It used to show on the map... I'm 99% sure.

image

No marks where the turn in should be.

image

commented

Just for the sake of being thorough... made sure the quest appears correctly in WotLK.
image

Off to repro this in Classic...

commented

I think this is a Questie data VS API issue. As you can already see on wowhead the wotlk version has an "Explore zone" objective, which the classic version does not.

https://www.wowhead.com/wotlk/quest=751/the-ravaged-caravan
vs.
https://www.wowhead.com/classic/quest=751/the-ravaged-caravan

And from what I know there actually is no "Explore Zone" objective, but you just need to return to the NPC. That also explains both issues: First you don't see a correct objective in the Tracker because there is not a real one and since the quest is not complete you don't see the turn in icon.

commented

This bug should be on Wotlk @Dyaxler not Classic Era

commented

@Gogo1951 so you're playing in Classic Exclusively? Just wondering because some of your other bugs have me scratching my head. In the future, please tell us which expansion you're using. ;)

I think I can build in a "check" to display "completion/description" text in place of a missing objective. I'll put it on my to-do list.

commented

Then his quest would show "Explore Zone" as an Objective whereas on the Classic version, that line is blank.

commented

I play Wrath Classic mostly.

commented

I play Wrath Classic mostly.

Okie... so the screen shot is from which expansion? I need to know where to begin looking at why this happens. And... roll a horde cow and repro it locally so I can see what the returns on the DB are. :D

commented

Oh, and even the Quest Finisher is present.

image

commented

Hmm... works fine in Classic too. Maybe we fixed this issue since release...

image

commented

I'm not seeing the same thing on a Blood Elf Warlock. Odd. I even refreshed. But I'm out of that zone.

Appreciate you trying to reproduce this, but all I can say is I saw it bug out -- at least for Blood Elf Warlocks.

commented

We've been doing a ton of bug squashing so it's entirely possible that I have the "fixed bits" in my local build. :D

commented

Closing this for the upcoming release. Feel free to report back if you encounter this issue again!