Did you guy's know that maitenance broke something major last night?

I agree with you that a rollback would be expensive and likely a waste of resources but the fact is the game is in this current state where for a lot of people, EC HM is the only thing holding them here. Like it or not, its true. For my guild about half re-activated their WoW accounts over the past few weeks due to F2P and getting bored with the Endgame, now we can't even do the last thing holding us here? Its like the straw that broke the camel's back.

Worse yet that it seems like they didn't even test it, yes, it would be expensive, yes it would waste a few days of their internal development, but yes, when you screw up bad and you are already in a bad situation, sometimes you have to swallow the cost.

You ought to fire your QA team.... oh wait, you already did that...

How many people is "a lot"? It's certainly not a majority.

So, you think that pushing an emergency rollback is going to improve the situation? Maybe your clan will be able to run your EC/HM. And maybe a few hundred other players who were just playing the game will spend the next day re-downloading the game due to issues with a hasty backwards-patch. But who cares, right? As long as you get to grind that one 30 minute section of the game a couple more times. Those other losers can just deal with the problems. Its their fault for not spending all their time running EC/'HM, amiright?

I guess my continued problem here is that so many gamers --and especially MMO players-- have crushingly selfish outlooks on games. They want the game to give them what they want now, even if it hurts other players, the game, and the company that is making the game. There is no thought toward the common good or the community or anyone who isn't "me".

The correct solution from a software development --and community-- perspective is to push a fix for the bug as soon as possible, not trigger a risky rollback that can introduce problems into an even larger group of users.

One has to wonder about this. On the surface it would seem to be absolutely valid. On the other hand I'm struggling with the idea that Bioware could release a patch without testing it's impact............at all?!

Nobody is really that careless are they? There has to be another explanation.

Now now, you should know as well as I do that if she answered that question honestly she would probably be the next one out the door. Not saying she won't be anyway once the forum is moved to social.bioware.com, but no need to tempt her into terminating her contract early.

Its happens all the time in many industries. Overworked folks with too little time, and not enough oversight, will check off something as done when it actually wasn't.

A 'lot' is all relative I guess, but even a 'few' is too many. I was told by 2 of our regular 'A' team Denova players last night that they were cancelling their accounts. Not being able to tackle Denova on our raid night simply highlighted how little there is for them to do.

Maybe it has something to do with f2p, you know 5000 cartel coins for a defuse kit

Yay? Good for them? I don't see how that has anything to do with this topic. More MMO vultures flying off to pick at a different corpse. <shrug>

The game has plenty for people to do. But there's no guarantee that everyone is going to like doing that. You apparently like running the exact same quest with the exact same people on the exact same night every week. I'd rather saw off my leg. Of course, you'd probably rather eat a bag of sawdust than roll a fifth character. I have eight. If your guild buddies are bored, they should find something fun to do.

The point of my comments was purely to argue against advocating risky (stupid) actions on Bioware's part, namely pushing a version rollback, to allow a small minority of players to run a single FP for what will amount to no more than a handful of times. If all those players ever do is that one FP, then I'd say their concerns hold even less value.

Why would a rollback be risky? They have a lot of practice with patching the game; they just have to craft a patch which undoes the last patch. In any iterative design there would be times when things had to be rolled back this shouldn't be the first time atleast internally that something like that had to happen. In fact the best way to approach it is not to treat it like a roll back but to simply locally undo the last changes.

I actually write software for a living; I know how easy it is with revision control systems to go right to the place where you made your edit (in fact, theres a program for that) and put it back to its old state. Depending on the complexity of the edit you may have other repercussions however this should be fairly easy.

First step; undo what you did, second step, re-do it but ensure you get your intent met as well as the bug fixed; two steps takes longer but that first "undo step" should be very fast and would allow other people to continue working. If they did their due diligence and caught this bug earlier thats exactly what would happen; hell in my company it would have gated the release and the coder responsible would have been up all night removing his code for the release.