Blizzard Entertainment has sprung a surprise Diablo 4 beta update 1.04 (PS5 version 1.004), and this should primarily be for fixes early access players have experienced last week. Read on for what’s new in the Diablo 4 beta update patch notes for March 24.
Diablo 4 Beta Update 1.04 Patch Notes | Diablo 4 Beta Update 1.004 Patch Notes | Diablo 4 Beta Update Patch Notes for March 24:
- Related Reading: Diablo 4: Ashava The Pestilent World Boss Guide
Size: 410MB (PS5)
Blizzard has not acknowledged the patch just yet, but we do know one of the major changes from last week’s beta to this coming weekend’s, and it’s the inclusion of two new playable classes!
The #DiabloIV Beta shall be open next weekend – with additional classes such as the Druid and the Necromancer.
Till the beasts and dead roam the land. https://t.co/4VVTEupGdr
— Diablo (@Diablo) March 19, 2023
In addition to that, Blizzard has shared the list of known issues with the Diablo 4 beta:
- If the player triggers the Lorath introduction cutscene while the world is in daylight, the player’s and Lorath’s shadows will shimmer in-game until the Prologue is complete. This issue will not occur if the player skips the cutscene.
- In-game voice chat may not function correctly for all players.
- Performance optimizations are still in progress. Players may encounter some performance issues, particularly on older hardware across different platforms.
- The ‘Play’ tab at the top of Character Selection is clickable but currently does not lead to another menu in the beta.
- During the beta players will be able to select from a wide variety of work-in-progress “Text Language” options beyond English. English will be the only available option for “Spoken Language” during the beta, but other languages will be available at launch.
- Player 2 may experience issues joining games with a pre-existing hero while playing couch co-op during the Prologue.
- Players playing Hardcore in local couch co-op on console may not be able to return to character select until both players die. This will be addressed at launch.
- Some console users may be experiencing issues getting through queues. We are actively looking to correct this issue this weekend.
- Players joining another in couch co-op will not see a displayed queue time. The game may seem unresponsive despite the player being in queue and attempting to join the session.
- There is currently an issue of imprinting Codex of Power effects on rare totems.
Finally, Blizzard has also set the expectations for players regarding this weekend’s beta that starts tomorrow.
With your help, we learned a lot during our Early Access Beta weekend. We intend to learn a lot more this weekend during our Open Beta, and we want to talk to you all about what you can expect and how your participation directly impacts Diablo IV development.
- Queue Times: When we open the gates again this Friday to absolutely everyone, we are expecting a lot of people. There will be lengthy queue times, particularly on Friday when we first launch and during peak regional windows. This past weekend helped us to forecast the capacity we expect this weekend, and we will be using that capacity to intentionally stress our systems in preparation for launch. In summary, while we know it can be frustrating, we need queues to properly stress test our services and we are designing to ensure we have them some of the time.
- Maintenance: As we monitor the population or encounter in-game issues to address, there may be times when we will take the game offline temporarily to deploy infrastructure adjustments or fixes.
- Bugs and Feedback: When you are in-game, whether you’re continuing to build your character from last weekend or trying Druid or Necromancer for the first time, we want to hear from you. The team will be monitoring the forums, where there are dedicated sections for bug reporting and technical support for PC and console, as well as general discussion, where you can leave feedback around anything Diablo IV.
We’re expecting another host of server issues once the open beta is live, and if there’s any server downtime, we’ll be sure to let our readers know.