Patch 23.0 Known Issues – Mi’da Bounty in Mercenaries, Early Core Set Cards

Update: New known issues got added. Players who were locked by the Mi’da bounty can access Mercenaries again. They’re also aware that players who already had full Naxxramas set didn’t get a Diamond version of Loatheb.

Patch 23.0 is massive, and while it fixed tons of bugs, it sadly also introduced some new ones. There were already a few known issues when the patch was shipped, and players are discovering new ones as we speak.

So far the most important one is Mi’da Bounty in Mercenaries crashing and locking you out of the game mode. The bounty was temporarily disabled and affected players will get restored once devs figure out a fix. Other than that, most of the issues so far seem to be visual-only, so not a big deal.

We’ll keep the post updated. You can read about all of the currently discovered issues below:

Hey all,

Patch 23.0 is a big one, bringing with it the new Voyage to the Sunken City expansion, the Core Set update, and the next Hearthstone Year! There’s a lot going on, so follow this post for information about known issues in Patch 23.0.

~~

Patch 23.0 will be shipping with a few known issues:

  • The Sunken City Warlock collection achievement will be based off the wrong set’s cards at launch, so it might show progression (or even completion) before the expansion even launches. This will not impact the collection achievements that give diamond/coin rewards, as those are tracked in a different way. This will be resolved via hotfix shortly after the patch goes live.
  • Three cards being added to the Core set in this year’s update (Bronze Explorer, Darius Crowley, and Wrathscale Naga) will show in your collection at the when Patch 23.0 goes live (April 5), instead of at the Core Set update (April 12). This is a visual-only bug. Those cards will not be playable as part of the Core until all the Core updates are live.
  • The graphic on the Mercenaries daily Fighting Pit rewards chest will be a bit more colorful than intended. This will be corrected in a future update.

~~

  • [Updated (twice) 4/5]: The team is aware that completing the Mi’da Bounty in Patch 23.0 will cause a crash that locks you out of the Mercenaries Game Mode. The team is looking into the cause of that crash and solutions to it now, but in the meantime the team has disabled the Bounty. We will open the Bounty back up once we have a solution. Second update: players who were locked out by this bug prior to the Bounty being blocked can now play Mercenaries Mode again.
  • [Added 4/5]: The team is aware that the Diamond Loatheb card—a reward for owning a complete Curse of Naxxramas collection—is not claimable by players who already owned the entire Curse of Naxxramas set prior to this patch going live. The team is working on resolving this issue.
  • [Added 4/5]: The team is aware that the conversion from the Honor Track to an Achievement gave players a celebration for each phase of the Honor Track they had already completed during the battle for Alterac Valley. This is a visual-only bug.

We will continue to track Patch 23.0 and update this post when we have new information to share.

Source

Stonekeep

A Hearthstone player and writer from Poland, Stonekeep has been in a love-hate relationship with Hearthstone since Closed Beta. Over that time, he has achieved many high Legend climbs and infinite Arena runs. He's the current admin of Hearthstone Top Decks.

Check out Stonekeep on Twitter!

Leave a Reply

6 Comments

  1. Sonriks6
    April 6, 2022 at 9:02 am

    Hey! Mercenaries XP trick was fixed with 23.0?? If I relogin past 1 hour no +XP you restart the level instead 🙁

  2. USGroup1
    April 6, 2022 at 3:30 am

    There have been many, many bugs in Mercenaries mode ever since they added it in the game. It looks like the team that is responsible for Mercenaries mode consists of only new diversity hires.

  3. H0lysatan
    April 5, 2022 at 7:24 pm

    Patch has already gone out, but I haven’t see the gem/banner thingy that shows teaser from all expansions, maybe later?
    Ah, Hydra was a serpent too. Why not make this a Serpent Year? Meh.

    And the known bugs it’s just the tip of the iceberg for now. As soon as we reach the 12th, more bugs will appear. Typical Blizzard. Hire more QA people, instead of laying them off. Geez.