Look, I get it. Stuff happens in a live service game. As frustrating as it is, there’s no avoiding it sometimes.
When those things do occur and you are required to take the servers offline with zero notice aside from a shutdown counter in-game, the least you could do is have the guts to put “unexpected maintenance” on the launcher. Or “emergency maintenance”. Anything other than gaslighting the players by calling it “scheduled maintenance”
9 Likes
agreed. you can’t just label something to avoid taking blame.
6 Likes
Not only this, but putting it on the bulletin AFTER THE FACT, rather than any time in advance would be grately appreciated. People can at least expect the game to be down in advance lmao.
1 Like
I kind of feel like to be able to call it scheduled it should be something stated prior to it actually happening. A 15 minute counter in game is not stating it prior 
My simple rule of thumb is this - if you’re adding it to the launcher after the servers are already down or in the process of shutting down, it’s not scheduled.
I don’t think that is too much of a hot take.
3 Likes
We call it demand maintenance in IT. Something is either going to break catastrophically or has already happened. Never called it “scheduled” unless we had a service interruption notice though.
Yaaa gotta see I agree. This wasn’t what you can call “scheduled maintenance” semantics maybe but, words do matter, as per your own contract, maybe use the correct ones blizzard.
2 Likes
The unmitigated gall to call something “scheduled” 30 min after it has already happened is absolutely crazy. Not to mention that it said the maintenance would be from X time to X time, but it actually started like 10 min BEFORE that time. Something else man…
In this manner “Scheduled Maintenance” is being normalized as the goto statement.
We know better, we want the real answer, but we won’t get answers until it is done, if at all.
Researching and inspecting possible solutions, sharing them and commenting on them, keeps us busy within the Blizzard Universe.