Tijdens de originele release van Diablo III konden gamers urenlang niet inloggen door de befaamde Error 37. Volgens lead producer Alex Mayberry zal dit probleem niet aanwezig zijn bij de start van Reaper of Souls, de launch loopt beter. Blizzard is al weken bezig met prestaties van de servers te verbeteren en fouten op te lossen. Dankzij de recente 2.0.1 patch moet Diablo III: Reaper of Souls moet alles goed gaan wanneer Reaper of Souls gestart gaat worden.
I think it’ll be fine. When 2.0.1 went live a couple of weeks ago, that was the same codebase as Reaper. I mean, it is Reaper with Act 5, Crusader and Adventure Mode turned off. Come tonight when it’s time to launch, we just turn those things on.
We planned it out this way. We planned to give ourselves a good month of time where we could get the code out, get people on and resolve issues. The worst part is going live and having all these issues and having to resolve them while players are upset. It’s much easier to do this pre-patch and then have the time to react to the things we saw, especially on the server side.
Everything’s looking really good for tonight… Volume of people plus new code usually equals problems, so we’ve got the code out, we believe the infrastructure’s in place – I don’t anticipate that degree of problems that we had at the initial launch. I think it’s going to be fun.
Interesse in Diablo III: Reaper of Souls? Wij geven de game twee keer weg, waaronder een Collector’s Edition. Doe snel mee met de prijsvraag!
