Maybe since the left a gap between seasons (never done that before), they will do something different with patch release too.
Too bad for people with jobs, trying to organise their time to play they new patch as soon as it hits live.
There was always a gap. It was only shorter (one week instead of two).
From my understanding, they wanted to patch the game at 5th Jan and catch as much exploits and bugs as possible before the season starts.
Something went terribly wrong and now they are in hurry to at least deploy it before Friday. Someone in Blizzard clearly fuc*** up something and thay want to hide it and it is a reason why they are so secret about it. Imo they will try to finish it at last hour and if the season will be delayed, we won't get any notification about it till Friday morning.
But why would they confirm that the patch will go live on Thursday in Asia? i mean it´s the same patch we´ll get.
Patchdays are always the same:
It is weird not seeing maintenance announcement just for d3 and hos. department funds been brought down ? for the patch , it's really not necessarily to be tomorrow for eu, could be just 1 day before the seasons hits or on season 5 launch. my speculations stand with their new moto. "Released On or Before x/x/xxxx "
I'm on n/a got the normal news feed stuff the launcher checked residency and patch indices and then went right to 2.3 when i hit play tho i just got the d3 launch logo been on my screen for over 15 minutes but the game never launched is anyone currently playing?
I´m pretty sure if they implement the patch with seasonstart, the season will be done at the start. There will be so many exploits(leveling/gear/gold) that didn´t went public on PTR like it was every patch since s1....
wondering if their having issues. I run a clan and am trying to invite and update roster. Since yesterday it's told me "D3 servers are busy or offline, please try again later" I've never seen that before. Other clan members noticed the clan chat was offline too.... maybe all their server-side patches were meant to help, but messed things up for the larger 2.4 update?