SiIencE wrote...
The one thing i'm rather confused about is why would we need to put messages on Twitter (can't be bothered to make an account) to report problems while there's this forum?
And why has there not been an official statement from BW/EA? Guess we're kinda left in the dark, i mean did they get hacked or did the last update make the servers go fubar?
It wasn't working flawlessly but at least we were able to play (i was) been waiting for about 5 hours now and i'm and guessing many others still get that lame ass online code redeem crap.
I also work as a support tech for a software/hardware company and if there was something wrong like this the customers shouldn't have to ask for a explanation the supplier should come with either a statement or try to explain what's wrong. Sure this is just a game but it shows how much EA/BW care for their customers.
This is probably the least relevant forum to post it on, since this one exclusively deals with multiplayer; this is a general EA/Origin outage, it would seem, since I've been told that some people have been having problems with their Kingdom of Amalur game, as well. Regardless of that, the better place specifically for addressing this is the PC Technical Support forum, since this actually prevents people from being able to access their DLC features in their single player playing, as well, not just their ability to play online.
And, anyway, they did go through and post a statement regarding this on various threads, both in the multiplayer and the PC Technical Support forum. You can find the result by clicking the big image/text that says "BIOWARE" on any of the threads, and it will filter out the original post and then any Bioware posts. Coupled with the tweet on twitter, I'd say that's actually doing a pretty decent job of communicating with the customers. Not the greatest, perhaps, but a decent job and they haven't been hiding in the dark.
I imagine trying to figure out what the problem is and fixing it is more important than having someone come in specifically to tell people speculation on what the problem is - considering that when it happened, the majority of the staff was likely no longer at work, it's not really practical to recall someone from their PR Team just to address this, especially since it'd require them to figure out what's going on from tech people that are likely working on the problem.