Can a programmer explain how they wouldn't know how far they were from being ready?

I get that things take time, and I am okay with waiting. I am just curious…

How doesn’t a company like Blizzard have a realistic timeline on things they’ve pretty much already done? Adding fixes isn’t new to them. Saying 2PM then 3PM then 7PM… Like… wouldn’t they realistically know that they aren’t even close to being ready at 2PM?

2 Likes

I can cite an example of how Blizzard has done this in the past on different projects and it speaks towards a lot of Blizzard’s internal issues.

Remember when Diablo 3 went into Alpha/Beta and at first we heard “THIS IS GOING TO BE THE BIGGEST ALPHA/BETA BLIZZARD HAS EVER HAD” then they back peddled and let the game exist in that “Alpha/Beta” stage for 6 months while all we could do was King Leoric runs?

That ENTIRE situation occurred because the “new” Battle.net Team ASSUMED that the infrastructure for Starcraft II and Diablo 3 were the same and ASSUMED they already developed the tools so they were essentially ready to hook it up to Bnet and hit “Go Live”. Well, they were wrong on every front. Different server architecture was being used, different back end code was being used, different everything was being used. This is ENTIRELY why the game was delayed by 6 months and then ultimately 9 months. ONE Department thought they could be lazy and it made the entire project look bad.

It’s MY GUESS that what’s going on right now is some clowns (yes, this term is apprioiate here) are trying to make a script/tool they spent the last few weeks working on WORK with live data. Either they DIDNT properly backup the character data and are now trying to fix the live data or they are being stubborn trying to make it work.

We should roll back the servers to the last working point and go and hope that wasnt over 24 hours ago.

But to me knowledge, don’t they have a stand-alone team specifically for WoW? Maybe they are just all incompetent but at this point, you’d think they would know how to perform tasks they have done a million times before.

“team” is a strong word

from my professional opinion, the janitor tripped over the extension cord running to the tool shed that houses everything classic-wow related so they’re in a scramble to get someone to drive into the office to plug it back in. i get it.

I’m gonna need you to be a little more pessimistic, your optimism is shining too bright :smiley:

in b4 brickle comes to simp for blizz

1 Like

From the Customer Support forum.

Proud of you son

1 Like

Imagine its a jenga tower and they just want to remove a layer and lower the tower a level.

They removed the layer and a bunch of random blocks went bye bye.

They have to find the blocks and make sure the tower is whole before playing the game.

That’s the simplest version, the more honest version is they’re lazy and messed up again.

1 Like

Over on the CS Forum, they stated that the Server Team hasnt been too communicative about how long its going to take, so, in lieu of a real estimate, they advance it ahead every hour for an hour.

Those of us who joking said that were legit right.

They are a small indie dev, they cannot afford a test environment. They still have physical hamsters. They cannot clone a live server then patch it they dont have virtual machines. Backups are expensive too, cant just roll it back before the maintenance then work it out internally.

Can you imagine right now at blizzard, a bunch of unshowered beer bellied live with parents programmers with doritos all over their shirts yelling GREG what did you do how do we fix this now /sigh…

Those all got axed during the investigations, best we can do is an intern that can change lady pictures into fruit bowls.

1 Like

Lol. Do you know what they were exactly doing? Maintenance for a huge game like isn’t always trivial.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.