Do the right thing- schedule maintenance BETWEEN TW, not during
Not really sure who came up with the absolutely brilliant idea of scheduling server maintenance during TW, but bear with me a second, wouldn't it make just a LITTLE bit more sense to do something that you have a history of failing at in between TW rounds? That way, you're not throwing a wrench into the whole works for an hour plus as you try to patch the servers but ultimately end up screwing things up for a ton of people in the process?
2
Replies
you're right, I should've known better. logic has a tendency to get my account suspended.
Sad that it has come to this, but still very much true.
Lol this guy got jokes
Until it’s not 30 minutes and due to the global nature and complex guild structures it does create a bit of havoc.
like the last 30min update that lasted 4 hours, or the one before that, or the one before that....
this is by far the longest any of my threads have stayed in general since like 2016. i wonder if they only pay moderators during controversial content updates.
The 4 hour was a crash unintentional.
they know when it might have more of an effect and they have tried to work around events or vise versa, they would know better than us what has a bigger chance to cause an issue.
The weekly updates do not consist of half hour+ anticipated down times, and are usually just a triggered client restart. This is inevitably going to cause people to lose battles at 20:15 UTC, and likely going to cause more issues when they come back online but the servers aren't working properly, as is usually the case when we see 30 min+ scheduled down times. Obviously they know enough that this is going to be a bigger-than-normal disruption with messaging saying they're expecting it to last 30 minutes, so why not just do it tomorrow when there isn't a major event going on? The track record of these server maintenance rollouts is horrendous, I've been playing this game long enough to know that.
no ****. those crashes are always unintentional, it hasn't stopped them from happening every time they've scheduled major VM maintenance.
Exactly. The 4 hour crash was unintentional. I don't think they intend on breaking the game for 4 hours, but wouldn't it be smarter to do the update that could turn into a 4 hour crash unintentionally during a time where there are no guild events actively happening....
Not even saying anything against the programmers for the crash. Electronics can crash, it happens, but shouldn't they know that's a possibility when they're attempting the likely difficult task of fixing servers? Does seem like a poor choice of timing.