22.2 Known Issues - 1000 Win Portraits - Heavy Armor Treasure - Mercs Equipment
The usual Known Issues post, check back later to see if fixes have gone out or things have been added.
Quote from BlizzardHello all, follow this post for information and updates about Known Issues with the 22.2 patch.
- If Google Play users cannot see the update when it becomes available on other mobile devices (expected to be around 1 p.m. PT today), we recommend the same workaround as with the prior updates that did not immediately appear on Google Play: open your profile icon in the top right → open “Manage apps & device” → select “Updates available” → select “Update All.” That should cause the update to appear on your devices once available.
- Players who have not yet updated to the 22.2 Patch will not be able to see this week’s new Tavern Brawl until after they update to Patch 22.2.
- As documented in the 22.2 Patch Notes 191, the patch will be launching with Kael’thas, Silas Darkmoon, and Chenvaala temporarily deactivated in Battlegrounds while we work on an issue found in testing.
- The Immovable Object remains… unmoved. Unfortunately, we were not able to fix the bug with the “You Are Not Worthy” achievement in Patch 22.2. The fix is being worked on and planned for a future update.
- [Resolved 1/25] We are aware that the Heavy Armor treasure is not currently working as intended. We expect the issue to be resolved in a hotfix we are putting together for later today.
- [Updated 1/25] We are aware that some Mercenaries’ Equipment are shown as unlocking at Task 1 and 6, instead of Task 2 and 7. That appears to be a visual bug only, with the Equipment actually unlocking at the intended Tasks like before. The solution to this visual bug is planned for Patch 22.4.
- [Resolved 1/26] We are tracking reports of issues with the Shop. Update: Upon investigation, it does not appear there were any widespread Shop issues related to this patch. We will continue to track any individual reports we receive.
- [Resolved 1/27] We are aware of a bug that made 1000-win portraits no longer available after the patch launched. We’ve identified the problem and are working on a how to resolve it in a future update. The fix to this issue is rolling out to each region now.
- We are investigating issues with the Battlegrounds leaderboard not locking at the end of last season and with some players’ ability to properly roll into this next Battlegrounds season.
- [Resolved 1/26] We’re aware that the first time you add Attack to your hero after playing Wildheart Guff, that Attack gain does not count for progressing Lost in the Park (the Druid Questline). We are resolving this issue in Ranked Standard with a hotfix update tonight and plan to resolve the issue fully in a hotfix within the next day or two. Update: This issue will be resolved for all Modes with today’s hotfix.
- [Partially Resolved 1/27] There is a bug where if you don’t own a Mercenary, but do have enough Coins to craft the Mercenary, the game will offer you the option to put that Mercenary into the Training Grounds. But since you don’t own the Mercenary, the server rejects that selection and nothing happens. We’re investigating this bug. In the meantime, you can restart your client to remove the Mercenary you don’t own from your Training Grounds slot and put a proper selection in there. Update: Update: There was an edge case where players who placed on Merc they did not own and one Merc they did own into the Training Grounds would then be unable to interact with the Training Grounds. After today’s hotfix, those players will be able to interact with the Training Grounds again after either exiting to the main menu or restarting their client. A more permanent fix is planned for 22.4 which will avoid this issue by blocking players from placing Mercs they don’t own into the Training Grounds.
- [Resolved 1/25] We are aware of an edge-case bug where selecting the Mysterious Stranger during a Bounty can cause a client crash. This issue will be fixed in a hotfix going out today.
- [Added 1/25] We are investigating an issue involving players getting stuck when finishing a Heroic Duels run that they started in an older patch.
- [Resolved 1/26] We are aware that Elemental Chaos in Duels is being improperly treated as a Battlecry effect. The team is looking into correcting this issue soon. Update: We determined that more new Duels cards also improperly received this treatment. All those cards were corrected in today’s hotfix.
- [Added 1/25] We are tracking an issue where Duels runs are setting players to the wrong life totals based on how far they are into that run. We are investigating the cause of this issue and the solution to it.
- [Resolved 1/26] We discovered that the combination of Tentacle of C’Thun (C’Thun’s Battlegrounds Buddy) and Titanic Guardian (Pyramad’s Battlegrounds Buddy) could cause an infinite loop that resulted in a game crash. After today’s hotfix, neither Buddy will trigger off the other gaining stats.
- [Resolved 1/27] We are aware that the refund period for cards that were changed with the 22.2 Patch was cut short for a short time today. This is resolved in today’s hotfix. Please confirm the dust amount before you disenchant your cards as the hotfix will be rolling out region by region.
~~
1/25 Update: The team is smoothing out a few launch issues, so the 22.2 mobile release has been slightly delayed. We know how excited our mobile players are, so we’re trying to get the release out as soon as possible.
1/25 Update 2: The mobile patch has started rolling out on storefronts and should be available on all devices soon.
1/25 Update 3: Patch 22.2 is now available in the Google Play store. You may need to use the workaround listed above to make the update show up. The patch is now available on all devices.
1/25 Hotfixes: We rolled out a small hotfix earlier today resolved the Heavy Armor bug mentioned above. We are now in the process of rolling out another hotfix that 1) fixes the Mysterious Stranger bug mentioned above; and 2) partially resolves the Guff Questline bug mentioned above. The Guff-Questline fix in this hotfix will fix the bug in Ranked Standard only. We are planning another hotfix to fix the bug in all other modes and formats; we are hoping to release that hotfix tomorrow.
~~
1/26 Hotfix: We are in the process of rolling out a hotfix that will: 1) correct some Duels spells that were improperly treated like Battlecry effects; 2) prevent an interaction that caused some game crashes in Battlegrounds; and 3) will complete the Guff-Questline bug fix that was partially hotfixed yesterday. These three fixes are further documented above. In this hotfix, we will also move the Duels Treasure Shadowcasting 101 from Pool 1 to Pool 2 Ultra Rare.
~~1/27 Hotfix: We are in the process of rolling out a hotfix that will: 1) allow players who placed a Merc they don’t own in the Training Grounds to exit to the main menu or restart their client in order to reset the Training Grounds; and 2) re-instate the full Dust refund period for eligible cards that were changed in Patch 22.2. Please confirm dust values before disenchanting any cards, to make sure that the hotfix has been rolled out in your region.
Earlier today, in a separate update, we also addressed the missing 1000-win Portraits. That update should be completing soon.
We will continue to monitor the patch launch and update this post when we have more information.
Day 5 locked out of Duels, and counting.
What a great Duels update followed by a insignificant Duels hotfix!
I cant use my card backs???? WTF?? Anyone else?
You're also a programmer and you still have this opinion? What do you program, toasters? Anyone worth their programming salt will know it is virtually impossible to test every possible scenario in a system as complex as a card game, which has millions of interactions. Again, not making excuses for them, but it is easy to wrap one's head around how this can and will happen often.
All these bugs with all the different modes and the client itself, but the Shop with those Gold Pack Bundles...that works flawlessly
Ah yes, the always insightful comparison of gameplay vs shop. If you were a business, which one would you prioritize? Do you think they're equivalent in effort to get right? A system (payment processing) that a single person could maintain is equal in scope to a game that takes hundreds to develop, hmmmm, very hard to understand indeed
Im not making excuses for them, nor am I disagreeing with your point. But it gets boring to see this exact comment every single time :\
also what is worth noting is that shop is actually pretty shit and works pretty bad
they aleady know that are going to get fired and no one work anymore xD BUAAUHAUHAUAH dat hearthstone team is the best
Because based in any video game ever, this is a bug fix, not an update rollout. They’re making it sound like they need some grandeur update to rollout a single bug fix.
it’s like of caring, not ability.
Right and how do you know they don't need an update to fix this? This could potentially be an issue with the client and the server, thus requiring a patch to fix.
Of course they won't just release a patch for one bug fix, it's not worth the developer time it would take to deploy a patch for a minor issue. Minor as in importance, not difficulty in fixing.
This could also be a huge bug requiring multiple changes to the code that requiring more time or simply it's not a priority for them right now. Remember they are still a company, everything runs on cost/benefit.
Only 22.2 bugs. I mean that's a marked improvement. Good job devs 😉
The new card back you can get for free is also bugged after you make it your favorite you can use it and it works but then it switches to the default one
the card back animation is one of my biggest disappointments in this game.
WHAT HAPPENED TO THIS BEAUTIFUL ANIMATION?!
I rly dont get it, you can say mistakes happends, but every single patch consistently? Give me a break...
I’m not a programmer. I don’t know what goes into the ins and outs of bugs, and the turnaround time of their resolutions. However...
“we were not able to fix the bug...”
and
”the fix is being worked on and planned for a future update...”
I call absolute bs. How hard can it be to fix a bug with a simple achievement? A future update lol? Not even committing to the next one. Just a future one. I personally don’t care about achievements, it’s the absolute principle of the matter.
The company hides behind veils of lazy, lack of communication, and lack of caring. Find yourself blizzard. And if you can’t, I hope Microsoft can, though I harbor more doubt that hope.
Blizzard is a shell of what they were. A shell of a shell rather. I’m so glad they paid some penance in 2021. Absolutely disgraceful.
Just give everyone the achievement, christ. Enough with the incompetence. They obviously didn't test anything.
How do you know that it is a simple achievement? Because it's easy to parse and understand?
Yes, on the surface "Prevent 100 damage with the Immovable Object." looks simple: just track the damage prevented, right?
Well, for starters we don't see the prevented damage. Only the final damage you take. Ok, so just check if you have the weapon equipped and track damage you take?
What does count as damage though? Is healing just negative damage? How does armour figure into that equation? What other things are under the hood that we know nothing about but complicate things even further?
And why would they commit to the next update if they neither know how to fix the achievement nor what the next update will be?
If they said it will be the next update and they need to fix something else before fixing the achievement, they do what?
We don't need to see the prevented damage, obviously the numbers are calculated in the background so the game should know them.
It should be fairly simple to track and add those numbers. But evidently it isn't because there are some saucy meatballs in that spaghetti.
Well, I am programmer and I can tell you, that most of the time it's not that easy. Sometimes bugs are caused by very small oversights, such as the lack of a comma or minus sign in a single line of code (among thousands), but sometimes issues lie much deeper, in a flawed (limited) design from years ago, when the developers weren't even aware that some mechanics would be added to the game in the future. Sometimes you have to rewrite an entire system to fix one little thing, which is quite difficult, especially if you didn't design it yourself, but developers before you who don't work there anymore.
Which numbers and how are they calculated exactly?