When the resolve bar is full you cannot be stunned, mezzed, pulled, or knocked back/knocked down. You can, however, still be rooted. While it may be due to lag or just poorly written code, a full resolve bar doesn't always keep you from being CC'd. I've been focused in Huttball to the point where my resolve bar was full but stuns were still keeping me from acting. I think everyone will have their own anecdote about how the resolve system is broken but I think it's mainly due to how the system tries to account for lag. If enough people stun/CC you at once, SWTOR just throws its hands up and says, "Ok, you are all valid stuns"..... I've even yanked people on my vanguard who had a full resolve bar. It's frustrating as can be. My advice: line of sight. In Huttball you can walk along the farthest edge of the platform from your enemy and they can't get line of sight on you. In voidstar, hump those pillars. Same for civil war. In Novare, god help you.

Same thing has happened on Prophecy of the Five. The best of the best are the only ones queuing and now even they have nobody to fight so they are playing regular warzones too. My guild tries rwz at least once per day and we always end up facing the same full-geared teams over and over. Preseason or not, it was a bad idea to release rwzs and force people to play those who are far beyond their rank. Enough stop queuing to make it as if they never released rwz at all...

I had to leave Vulkar Highway where I have 2 50's and many alts with a legacy level of 30 or so. I rerolled on Fat Man and it really pissed me off. I'll not be resubbing when GW2 comes out. All that work rendered pointless in less than 6 months. Just stupid.

Depending on what the cause was, I agree. But we don't know the cause. As end users, it's not our place to know. It's our place to pay and play or not. I, for one, will continue to pay and play.

Guys, I said right from the start that you should be angry. I also said that this was a fail. And if you don't understand the power Murphy has in IT, you've never written software or deployed it. It's just that simple. Here's the crux of the Time-To-Market Conundrum: Software is science. It's all math. Ones and zeros in complex mathematical patterns. It's cut and dry. But like all science it takes time. Now couple that with capitalism and what you have is pretty much division by zero. To meet the needs of the business, the software developers and all their supporting staff must live right on the edge of insanity from the time they create a proof of concept to well after the application goes live. This is why so many people have anecdotes about Microsoft and buggy software, yadda yadda. Until there is an open source MMO, things will be this way. My point in the original post was two-fold: 1. I'm a software developer and I feel for the Bioware team. 2. Bioware has done a fantastic job thus far in response to their failures. There's a saying in the corporate software development world: I can develop your software with the least amount of money possible, with the best results, in a short period of time; but you can only pick two of those. I honestly believe that what happened today was a deployment screw up. Someone fat-fingered a command line switch when installing the database updates...

yes!!

Let's move beyond how EA will handle this internally and look at what goes on in online software development: http://www.swtor.com/community/showthread.php?t=409957

Appreciated! They already gave us a free full day. I remember when I played Lord of The Rings Online and they had severe rollbacks and extended outages. They did NOTHING to compensate players who lost rare boss drops, etc... Like I said, Bioware is being proactive. Software = problems. The difference is in how you respond. So far the response is on par with my expectations.

As paying customers of a product that is currently broken, many of you are mad at EA/Bioware. You should be. They let us down today. However, as an online software developer myself, I'd have you consider the following: 1. Software ain't easy. 2. Online software is even harder. 3. To-date EA has been VERY quick to address our concerns. 4. Bad things happen to good people (see Murphy's Law). If you feel a tl;dr coming on, it's ok to stop reading now. The rest is just more detail to support my assertions above. I Know What I'm Saying I have written, upgraded, and deployed many online enterprise applications whose complexity pales in comparison to that of an MMO, so please try to understand that my assertions come from a place of long and painful experience. The More Moving Parts, The Greater The Chance For Failure SW:TOR is a complex system of systems. I know that sounds odd, but it's true. What we think of as SW:TOR is composed of *at least* the following: 1. A software client (the game you execute on your desktop and play). 2. A server (not the physical machine(s) but the software at EA that coordinates the interactions of all of us with the game and with each other). 3. A database (what the "server" mentioned above uses to remember what has gone on in the game such as items in your bag, your stats, your toon name, your lockouts, etc...) 4. Networking "stuff" such as routers, load balancers, firewalls, switches, fiber routers for database storage. Each of the above can be viewed as a system of it's own. Together they combine to form Voltron...er....SW:TOR as you know it. Each of them are comprised of even more "parts" or sub systems. Each sub system can break. Systems Are Made By People Each of the aforementioned systems undoubtedly has an "owner" at EA/Bioware. By "owner" I mean they are responsible for developing and/or maintaining each sub system in some way. The more people involved in the development or deployment of an online "system" such as SW:TOR (or any online system for that matter), the greater the risk for miss-communication. It may come down to a single person mistyping a single character. You never know. People are fallible and will mess up from time-to-time. The margin for error in such a complex system is very very slim. Judging by previous patches, EA has a solid dev/deployment team. If human error is to blame, it's simply a mistake. Developing An Update Is A Monumental Undertaking Midnight oil was burned. Spouses patience was tested. Microsoft Project was ridden hard and put away wet. I have no doubt that there were all-nighters pulled in order to bring us patch 1.2. There were fights between project managers and developers. Hair was lost. Some people probably had to re-evaluate their decision to go into software development. Considering the time from original release to now, I'd say EA performed a minor miracle with patch 1.2. My point here is that we may want to take the time to appreciate the personal sacrifice of EA devs and their supporting business staff. These guys just ran a 6 month gauntlet that would make a grown man cry. Development Is Not Deployment I've been both a developer and an application hosting engineer. The guy who writes the software isn't usually the guy who puts it on the live server. To deploy is to place the software on the live server. This usually means running some upgrade routine on the "server" software or replacing it. Maybe adding some new physical hardware. Finally, running routines against the database to bring it in line with the new changes installed on the "server" software. The database part is usually the most tricky. Don't ask why. It just is. One slip of the keyboard can ruin the whole thing and cause you to have to do it all over again (I recently did this to a development database and I'll now lose an entire day restoring the backup). Murphy Is Our Co-Pilot Murphy's Law states: Anything that can go wrong will go wrong. Let's assume just for the sake of argument that the Bioware team is infallible. Even a perfect man cannot account for a bad line of code in a piece of supporting software. If your software depends on that software and that software suddenly misbehaves, it could ruin your software without warning. Nobody is to blame. Bad things just happen. What I Think Happened I'm going to go out on a limb here and say that Murphy caused the rollback which is resulting in 8 hours of sudden downtime. Consider if you will: 1. The patch went out this morning as planned. Bioware had no indication that the update failed. 2. They told us right away that the maintenance would take 8 hours, which is the normal maintenance window. This means they are restoring the backup they took last night and rerunning the upgrade routines. 3. Bioware has been so attentive to our needs and bug reports in the past that I just don't buy negligence or incompetence as the cause for the down time. They patch us like once a week in order to keep the amount of changes they deploy at one time very low; thus reducing potential for catastrophe. In Conclusion I don't expect anyone to read this and suddenly not be mad at EA/Bioware. As someone who has gone through catastrophic upgrades himself (a client was once down for 4 days, during which I didn't sleep at all, and we lost millions) through no fault of his own, I just wanted you guys to get a glimpse of Bioware's point of view. They cannot provide that kind of insight themselves, so I figured I'd do it for them.

Stealth burst dps should remain hidden until the best time to strike. Now you've been forced into that position. In a group, I would have you wait on the edges until a key player is about to go down but keeps getting heals from God. THEN you strike, turning the tide. That said, I will echo your LAWL with a lawl of my own: LAWL. You guys deserved that nerf and I'm happily destroying all the ops on my server who used to 3shot me.

With around 900 expertise, you'll hit for the same you did before the patch in pvp. Some skills will hit for a lot more: Master Strike, Slash. In pvp, my Focus guardian is even deadlier than before the patch... I cannot speak to pve, however. I have no pve gear and am told that pvp gear doesn't stack up well against pve mobs after the patch.

For the record: I'll take Power Rangers over Scooby Doo any day.

Well, that's one thing i liked about this patch. I can purchase the craftable Trooper armor set and xfer my mods from my BM set into it. A trooper with a lightsaber looks better imho than a jedi in spandex. I fear the cost of xfering my War Hero mods to whatever good looking armor I choose at that point.

I have to say I love SW:TOR and I was mostly pleased with the 1.2 patch. My one complaint, which carries over from before the patch, is that Jedi Knight and Consular armor looks beyond silly. When I first saw the War Hero set for Jedi Knight I thought to myself, "Didn't I see that dude on Scooby Doo?" It looks silly. It looks like it was designed by someone from Hanna Barbara in the 60's (google it if you're too young to remember). Was the intention to have the empire laugh to death on the battle field? It certainly doesn't illicit feelings of awe or terror. Compare it to the armor of the Sith Warrior. Now THAT is a nice design. It looks awesome. It makes you want to play the game. I know what you're thinking: "Hey hater, you just gonna complain or you got suggestions?" Yes, here's my suggestions about Republic armor: 1. Just because pubs are the good guys doesn't mean they have to look silly. I understand their look should reflect the spirit of their faction. Consider the lvl 40 pvp set. The huge metal shoulders say "There is no death, only the force. And I'm about to reunite you with the force, bro". Why not have the War Hero or BM armor be along the same lines but with more metal? How about golden metal? Or BIGGER metal??? 2. Take a page from the Sith Warrior designer. Start with their armor and make the color light, smooth the jagged edges, etc... 3. Make the friggin helmet smaller. Many a time I thought to myself when looking at the BM helm, "This would be more tolerable if it wasn't the size of a mascot helmet." Scale it down so we don't look like bobble heads. 4. Shoulders, shoulders, shoulders. Since WoW, large dramatic shoulders have said to the world, "I'm awesome and so are my huge shoulders." The BM chest made Sentinels and Guardians look like mincing ballet performers because of their tight fit and lack of proper shoulders. No, that lego chip on the left shoulder doesn't count. 5. The Columi set looked far better than the pvp set. Why go from flowing robe/big shoulders to skin-tight super hero outfits? If you were going for the Samurai look, do it up! Plated lower robe, dramatic shoulders, dramatic Samurai face plate, helm with horns, etc... 6. The Trooper BM set did a great job of saying, "I'm a good guy but you'd run from me if you know what's good for you." The helm for the Commando was kinda big but it was scary. This post is mostly for the Bioware devs/designers. I'll understand if I get tl;dr. But I think Jedi Knights and Consulars out there will agree.