Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

The Joys of SOA


miglor's Avatar


miglor
03.29.2012 , 04:47 PM | #1
Why is it that even after all this time, countless patches later, SOA still remains the most buggy, glitchy painful boss to take down?

Our raid team is pretty much rakataed out. We've 1-shotted all the HMs almost with our eyes close. Last night, after 1-shotting KP HM and all of EV HM up to SOA, we just hit a brick wall. Some weeks are just like this. Everything else is fine and working as intended, but SOA just makes everyone cry and hate the game.

So after 20 tries, we just gave up. Of the tries we had:
3x where pieces of the floor were missing, prompting badness when you get out or into the mindtrap
2x where the pylons would drop on SOA, but did not drop his shield
1x where someone would get mindtrapped when we were about to hit phase 3. Seems all good then right as phase 3 is about to start, he gets magically transported to a non-existent mindtrap and gets stucked there
3x invisible lightning ball that no one can see decides to randomly wipe people
2x our tanks would dye randomly while dpsing next to SOA after the pylon drops (they were at full health when after the pylons came down)
4x battle rez would not work/take when a person died one phase and we proceeded to the next phase (has to do with lousy platform logic?)

It just makes for an excruciating time. Being at the mercy of these bugs are not 'fun'. How can these still exist? You guys only have TWO Ops right now!! TWO!!! And this boss continues to make everyone hate EV, not for the challenge, but for the sheer randomness of luck and wipe-tastic bugs.

Merraith's Avatar


Merraith
03.29.2012 , 04:56 PM | #2
Zone resets fix the floor pieces missing. From our experience, as soon as we never wiped during a transition phase, we've never had issues with floor pieces missing whether we reset the zone or not.

Invisible lightning balls means you need to turn nameplates on, and that someone wasn't exploding their ball fast enough.

Not sure what the issue is with a mind trap at transition...they changed that so it auto releases someone once his shield goes up. If you're having him cast it right as the transition is going, that's just really bad timing, have never seen that happen in 3+ months.

Battle rezzes, I don't know why people have problems with this. My only guess would be you can't do it during a transition but if you rezz someone during the phase they died in shouldn't have any issues (we haven't).

If tank is too close to pylon dropping, it will do damage to them. As for it not hitting Soa, the working theory in some threads that some have semi confirmed is if you have him positioned too far on the "cracked" ground around the outer area in phase 3, sometimes the pylon won't register as having broken his shield. Our tank manages to position him properly for every pylon drop, pretty sure he just tries to keep him off the outer area as much as possible while still being on the edge of where a pylon is landing.

Will full Rakata you should be demolishing HM Soa. With titles done we run it on HM every week and the only issue we've ever run into on HM/NM for the most part is lighting balls getting off an extra shock at times. On NM it can be a pain but on HM it's pretty much never an issue...especially in full Rakata.

miglor's Avatar


miglor
03.29.2012 , 05:18 PM | #3
Most weeks we 1 or 2 shot SOA. But last night was a nightmare. Some much glitchiness and lousy luck.

Last night was the first time we've encountered some of the bugs. With the missing floors, we reset it as well. But sometimes it happens again. Makes no sense.

As for the mindtrap, what happened was someone was mindtrapped right before end of phase 2. Soa goes to next phase and the game releases said person. All is fine and dandy as we negotiate the platforms down. Then 2nd to the last platform, he gets magically teleported to a non-visble mindtrap. Needless to say we could not get him out.

As for the pylon dropping and the tank dying, the tank that died was actually not close to soa when it happened. Pylon drops, he eats his ball and jumps to soa. As he was DPSing him down...poof...he dies. One of the healers said for some reason his DPS kept dropping by 5-6k increments, even though he was no where near the next ball as other melee did not take damage.

Maybe the "invisible" ball was someone taking so long eating their ball, but from what we've seen, they DID eat their ball. There is no reason for it to still exist and spawn right smack in the middle of melee.

Just so damn frustrating.

miglor's Avatar


miglor
03.29.2012 , 05:19 PM | #4
As for the battle rezzes, its only soa that we have probs with. Our theory is someone dies on a platform somehow, that drops, causing LOS issues with the body.

KiranK's Avatar


KiranK
03.29.2012 , 09:39 PM | #5
Our woes. Cyclone + Ball lightning = death. Platforms fail to align. Battle rezz loads tank outside of the instance. Mind trapping the tank resets the encounter. Pylons fall, but don't break his shield. Double damage ball lightning. This is just tonight. This boss is so random and buggy it's retarded.
There's no QQing in baseball.

lukemia's Avatar


lukemia
03.29.2012 , 09:57 PM | #6
Don't forget how gay it is that the speeder doesnt take you all the way to the puzzle boss when you reset the operation ;]

Just fueling your fire ;]

The only issue we ever have is when we bring in new people and they dont know how to take the balls. Also we only use 1 tank during raids so when she's dead and we dont have a battle rez we reset.

As for being a healer and the only sorc in our raid group i have learned to not depend on the battle rez because it doesnt seem to work half the time. Also i have noticed if i use it in one fight and the 5 min cooldown/debuff goes away it still wont let me rez anyone.

Ossian_Mills's Avatar


Ossian_Mills
03.29.2012 , 10:18 PM | #7
This has happened to us multiple times. Every time tonight we made it to the bottom of Soa he bugged on us. After submitting a bug report I got this conversation below (or not - no cut/paste and deletes the text after so much)in response.

To summarize it being angry I wanted my gear drop and was furious so asked for that in bug report. The customer service guy in live chat stated that the fault lies with the developers. So i asked to speak with a dev (of course they cant talk to me) the rest of the conversation was basically canned responses but the thing I have taken away is this:

1. The stance of customer service is that all of this is the responsibility of developers and the bugs and is a known issue
2. Since it's the developer's fault (says customer service) I will from now on keep up with repair bills from bugged wipes for my entire guild ops. Then at the next guild summit I or someone from my guild will be there to ask for those credits from a developer directly. I suggest all high level guilds do this. directly from James or Georg Zoeller.
3. The fact that a bug known from beta has not been fixed is unacceptable. If BioWare doesn't start addressing things timely people WILL leave this game for another.

the convo: Okay so i was going to post the convo but cannot cut/paste it due to a combination of massive frustration on my part. plus once u scroll up so far the above conversation is deleted apparently.... but oh well... i then said that needs to be submitted as a bug report/game update

Ossian_Mills's Avatar


Ossian_Mills
03.29.2012 , 10:22 PM | #8
Quote: Originally Posted by Ossian_Mills View Post
3. The fact that a bug known from beta has not been fixed is unacceptable. If BioWare doesn't start addressing things timely people WILL leave this game for another.
I should rephrase this to say Bugs - in plural

Ossian_Mills's Avatar


Ossian_Mills
03.29.2012 , 10:27 PM | #9
Quote: Originally Posted by Merraith View Post
Invisible lightning balls means you need to turn nameplates on, and that someone wasn't exploding their ball fast enough.
This is simply not true. I have name plates turned on and a majority of the times the ball lighting nameplates will only stay up one i have targeted them as in once u target and target again it will stay.

Also the lighting balls have "dead bodies" which makes the fact of not always displaying ball lighting problematic sine you cannot tell the difference between the two

ocping's Avatar


ocping
03.29.2012 , 11:19 PM | #10
Quote: Originally Posted by Ossian_Mills View Post
This is simply not true. I have name plates turned on and a majority of the times the ball lighting nameplates will only stay up one i have targeted them as in once u target and target again it will stay.

Also the lighting balls have "dead bodies" which makes the fact of not always displaying ball lighting problematic sine you cannot tell the difference between the two
/signed

I have nameplates turned on and can confirm 100% the invisible lightning balls are in fact previous balls that have already exploded on the intended target but failed to despawn and are somehow invisible until they hit their next target, which of course, is unannounced.

How do I know this? I was hit by this bug twice personally.