Diablo II: Resurrected 2.4 & Ladder Update - March 24th

Hi all

We wanted to provide an update to the Diablo community regarding the latest on the 2.4 balance changes patch and our very first Ladder season. First, we just wanted to thank everyone for the feedback and testing over the last several weeks as we honed in on various database, server, and balance changes that will be arriving with this update for D2R (Diablo 2: Resurrected).

Originally, we planned to have this update out by the end of this month, but unfortunately ran into some snags. I know your first reaction may be “HERE WE GO AGAIN!” which everyone has every right to say as getting this update perfected for Ladder has been quite a journey. But we did want to explain some of the circumstances that lead to this adjustment in dates and at the same time provide you with updates on the new expected release of 2.4 and the start of Ladder to ensure players have enough time to plan for the race that occurs with the start of each Ladder season.

So, what happened here? As you may recall, we have been working through extensive updates on the backend and database services for the game. Over the last few months, the team has been implementing these updates to the server and database using learnings from PTR (Public Test Realm) and from the immense help the community provided during these testing phases. Last week, we had some extended downtime for D2R which was to implement the final batch of changes from our PTR to our production environments. During this update, we unfortunately ran into quite a few showstoppers that did not appear on PTR but were present in production environments. Due to that, we extended the maintenance as we needed to roll back the changes so we didn’t affect users and could get the game back up and running.

What were these showstoppers?

1. We experienced an issue where a good swath of stashes did not convert correctly. The database unfortunately did not migrate to the new format and was not seen in the PTR until we moved it to Production. This was due to PTR testing being brand new to the game.

2. There was a missing index on the database which was causing things to go much slower in production and this was not noticeable on PTR. This then led to slow joining and creation of games. We were able to add the index, but additional time was required to look over the database performance and ensure we did not have any other new slow points.

3. Lastly, because PTR was just one single regional database, we experienced a few additional database issues on production, as that has multiple regions, and thus didn’t surface some of the errors we were seeing. Thankfully, this will be addressed in future PTRs since there will be multiple regional databases going forward.