As title says, the turn in quest this week for leatherworking is bugged. Rather than being completed once per character, it can only be done once per account.
I happened to have another character on another account online at the same time and noticed they had the quest as well and progress was shared, but they couldn’t turn it in.
2 Likes
I came here to report something different but I am going to assume related.
I go through all my characters on Tuesday and pick up all the various weekly quests (which takes a long freaking time and it would be great if we could do something about that but I digress) and then work through them during the week. So on my LW I picked up Drums Here! but did not complete it.
When I switched to another character I got the message “The quest Drums Here! has been removed from your log”. Well no duh, this isn’t a LW. I switched back to my LW, sure enough the quest was gone but still available to pick up. Tried again, switched to another toon and got the same message.
Which tracks with it being currently considered an account-wide quest, but which you can only have on a LW.
So since I have three LWs that will want to do it this week, I’ma wait and see if it can get fixed before Monday.
I did not even consider that maybe it was considered an account wide quest, but yes - my hunter ran into the same issue. Completed the weekly on shaman and hunter does not have access to it.
First time I’m encountering this bug. Already reported it and opened a GM ticket
Same issue here.
I got the quest on my 1st alt with Leatherworking, but then i tried to get the quest with my 2nd and third LW and they didnt get it.
Seems to be a bug.
I can confirm that when my only Leatherworker completed “Drums Here!” (questID 70571), that same quest became completed for other characters on the same and different realms and factions, none of which had Leatherworking chosen as a skill. This was checked with the following command:
/run print(C_QuestLog.IsQuestFlaggedCompleted(70571))
1 Like
Same thing happened to me although when I went back to pick it up, it stuck.
GM response to me was that I had picked it up 5 minutes before the ticket and completed it about 30 minutes later. Neither is correct as I did not go back to that character to complete the quest until after completing it on my main.
Unsure if anyone else has had any resolution to this.
Bump for the blizz response on this, same thing happen to me on my main and alt…both have LW and should be able to complete the weekly LW quest to make something like BS and others, but was only able to complete it on one character. There was down time today, but no fixes…WTH.
I just encountered the same issue. I accepted/completed the quest on my first LW char earlier this afternoon (completed it a few minutes after accepting). I noticed later this evening that another of my characters (a tailor/scribe) had credit for completing it. Logged in a couple of other non-LW characters, and they also had credit. I’m on my other LW alt now (first time logging in this week), and she doesn’t have the quest available, and the script says that she completed it (she definitely hasn’t).
So I was wondering why this quest I picked up on my rogue kept disappearing. To test, I picked it up again, logged out, logged on priest (nonLW), and sure enough I got the error that the quest was removed. So def account wide. OFC logged back on rogue and it was available for pickup for the millionth time. This is not helpful as I need to complete it on rogue AND sham. This has been the buggiest xpac ever.
Looks like this week there just isn’t a leatherworking quest for me.
2 Likes
The quest is still flagged as completed account-wide. Looks like instead of being set up as “weekly” it was marked “account-wide” instead.
Hopefully they can fix it soon, and give leatherworkers the profession knowledge points we’re missing out on.
1 Like
Also experiencing this:
- Last week, had the same issue as others reported: quest was removed when switching characters, had to reacquire
- This week, no quest is available
Definitely hope this can be resolved before reset, or that we can be compensated for the missed knowledge