Hi there,
Since 9.1 hit live I got one of my tailoring legendary piece reset from rank 4 (max experience) to rank 1 with 0 experience.
I used to have all tailoring pieces up to rank 4, but now only the Grim-Veiled Cape got reset, while all others are fine.
I also saw some other players reporting this bug, like in this thread: Legendary recipes were reset to rank 1 - #2 by Mechaboomer-grizzly-hills
Since crafting the legendaries is a big deal only in the first days of a patch, is there anything that can be done to solve this?
Thanks in advance,
Felbud
The overall issue was hotfixed, but for those impacted weâll need to manually resolve the issue. Please submit a ticket, Felbud. You can use the link in the following Support Article.
https://support.blizzard.com/article/000291552
6 Likes
Thank you for the quick reply, @Vrakthris! Ticket submitted.
1 Like
There must be better solution than that. All legendary base items ranks have been reseted. You will be overwhelmed thousands of tickets. Part players of wonât be able to submit tickets and will lose millions of gold.
1 Like
Not everyone is affected by this. So tickets are the only way.
4 Likes
I assume every average admin creates backups before changes. âOur developers have fixed the issue that was causing this problem.â Everyone understads it caused by 9.1⌠The only âfixâ here is restoring data from bacups for solving overall issue.
I donât think think you understand just how much information that weâre talking about here. Millions and millions of characters and the data associated with them is astronomical.
This isnât some simple right-click and âundoâ.
If players feel they are still not seeing the right items or weâre otherwise effected by this, then they need to put in a ticket.
7 Likes
They didnât change player data, they changed the game engine.
âRestoringâ the backup would only roll-back the version number of the game engine. It wouldnât undo player data.
Your hypothesis might be correct if the upgrade to 9.1 had to do with the player data. It doesnât. It only had to do with the game engine. Blizzard fixed the game engine to no longer cause this problem, but any data already generated would need to be manually fixed.
4 Likes
I agree this isnât some simple right-click and âundoâ. Only professionals may handle it professionally instead of putting astronomical work on already overwhelmed support.
Is it possible to do globally what Game Masters have to do manually? At the developer, admin level.
You do know the devs couldâve easily made tools for the GMs to help in this event, right? There isnât messing with the game coding itself or anything like that.
Youâre putting a lot of presumption into this. Bottom line, this isnât the place to discuss how they fix things. Youâve been told what is required to fix anything affected by the issue prior to the hotfix going out. If you want that fix, youâre going to need to file a ticket. Anything else here is unnecessary. If youâd like to submit your ideas or suggestions, GD is the place to go, or use the in-game suggestion interface.
1 Like
Possibly, but it would depend on the cost/benefit ratio. Meaning the cost of developing, testing and applying the âfixâ versus what it costs to do it manually on the case-by-case basis. The tool to fix the already incorrect data may require uninterrupted access to the player database which could mean downtime for the whole game, not just the ones with the issue.
The number of players affected by the issue versus the number of players not affected by the issue.
The problem is not game-breaking. It doesnât stop you from playing. These are other considerations for whether or not they use a scanning tool to address this or not. That is even assuming they are able to properly scan for the issue.
You are adding a new level of issues to the problem too. What if your issue was an outlier that wasnât fixed by the âtoolâ. You would still be needing a GM to manually fix it. What about players who didnât encounter the bug? What if the âtoolâ used to fix your issue caused issues in theirs?
3 Likes
The bottom line is if i didnât accidentally notice this topic i could spend another 10-20 mill to relearn what i lost as a result of devs "good job
The bottom line is all impacted players are victims. They dont have to read forums and submit tickets.
The bottom line is players have to wait days for response, and reciving copy-pasts when they need real help. Because support is overwhelmed unnecessary stuff.
Bottom line is this: Coming to the CS forum with a chip on your shoulder isnât going to magically fix anything, nor would acting like you know the magic bullet to anything will fix it, either.
Being insulting towards folks you want help from isnât useful or needed here.
5 Likes
The copy-paste response is given because it addresses most cases. It also includes the directions to reopen your case if the copy-paste response does not resolve the issue. The queue for reopened tickets is shorter than the one for the original tickets for two reasons. One, it is a separate queue from the first queue you are in. Two, the ones which are fixed with the copy-paste response are no longer in the queue.
If you feel there should be another solution to this, you need to post in Professions or General Discussion as the Devs donât take feedback/suggestions from the Customer Support forum and the SFAs here are not liaisons with them.
2 Likes
When working to resolve an issue our Devs always look for a solution that allows them to fully resolve the issue. Trying to not only prevent the issue from happening to more players but also to see if they can undo whatever happened to those who were impacted. A viable solution isnât always available either be from a technical standpoint or that the time required to develop and implement the resolution isnât really feasible.
No. If it were a viable option it would be the one that we use.
I think this has been covered as best as it can be so Iâm going to lock it up. Thanks, all!
5 Likes