Broken encounters in 2.5

Pecannius said:
I thought about needing to make that disclaimer butt no, no group heals at all. And I checked parses compared to 2.0 wins and we had even more dps. Wonder if it was changed recently or some other strange crap is happening.
Click to expand...
relgons/classbracer/tools/that sk thing/bstlord shit could all be variables too.
 
Pecannius said:
-Claw Commander: Severely broken. Regains / regens way too much life in phase 2. Impossible to get under 20% or so.
-Researcher Thekrak: Severely broken. Back to the "old" Thekrak that likes to 15k nuke people.
-A Reanimated Priest: Moderately broken. Back to the "old" priest" who likes to AE the bejeesus out of everyone.
-Sorrow: Moderately broken. Goes into his nuking frenzy after post 3rd wave DURING the 3rd wave instead, making it nearly impossible to kite a buttload of adds while someone is taking a bunch of dmg. This is not how it worked in 2.0.
-An Overgrown Szithri (Abyss): Mildly broken. Does a fair bit more melee damage than before, although I don't have logs to prove it.
-The Murkwater: Mildly broken. When he does his GFlux phase, people randomly get wedged into the wall, I believe /rewind fixes it.
Click to expand...
Sorrow is 100% fine. So is CC.
 
Tevinter said:
relgons/classbracer/tools/that sk thing/bstlord shit could all be variables too.
Click to expand...
Yes, all accounted for. Killed it over 10 times in 2.0 with no issues like this.
In the 2.5 attempt, everyone but the tank was under 2% and he still wasn't budging, even with keeping the tank under max health to avoid tools procs.

Nwaij said:
Sorrow is 100% fine. So is CC.
Click to expand...
Was Sorrow tweaked in 2.5? Because I know for a fact there's a huge difference compared to 2.0. But I suppose you could argue that the 2.0 version of Sorrow hasn't been "correct" in years. Just curious.
 
I'm not aware of any tweaks nor changes to Sorrow, and I killed it several times in 2.5. Maybe you are mistaken on the source of the nuking frenzy you described above?
 
Pecannius said:
I thought about needing to make that disclaimer butt no, no group heals at all. And I checked parses compared to 2.0 wins and we had even more dps. Wonder if it was changed recently or some other strange crap is happening.
Click to expand...

well I've done it on this current patch with 2 people dying on the second phase so idk what to tell you
 
Pecannius said:
I thought about needing to make that disclaimer butt no, no group heals at all. And I checked parses compared to 2.0 wins and we had even more dps. Wonder if it was changed recently or some other strange crap is happening.
Click to expand...
I know when I killed it several weeks ago his last few percent 0% lasted. Bit longer. It we had a pretty good grp and warrior self heals makes that fight easier and not worse. Mabye just try it again I'll even go with you if you want? See if I can tell you what we did differently?
 
i hate when the healer starts casting their folerit belt right when mobs start doing more damage
 
Thanks, will try cc again, no idea what was going on. Also re-looked at logs, and just had some weird occurrences with Sorrow, does seem unbroken.
 
It probably didn't help that the first time with CC we had 2 tank classes in group - that was a definite buggyness.
 
(Relayed via vintage folk) - Towers of Agony tower event tried real hard to crash the whole server tonight. The crew called it quits and didn't reattempt after making it the second floor and subsequently seeing 50+ zones crash
 
It started right after we got to the stairs to go to the second floor. I am not sure if anyone in raid had gone on ahead to the second floor. The UI net meter kept going from 100 to 99% in an infinite cycle, and slowly characters disappeared from view. On mumble they were saying they the zone crashed, but IRC had started talking about how the server was lagging and multiple zones were crashing. At one point we couldn't actually get through login. It did simmer down finally enough to get us back into kill a few mobs and one of the named. For log I am including this: We finished raiding at 10:30. I think we started the event around 10. All time zones are EST. I hope this helps looking into server logs.
 
Rikunda said:
It started right after we got to the stairs to go to the second floor. I am not sure if anyone in raid had gone on ahead to the second floor. The UI net meter kept going from 100 to 99% in an infinite cycle, and slowly characters disappeared from view. On mumble they were saying they the zone crashed, but IRC had started talking about how the server was lagging and multiple zones were crashing. At one point we couldn't actually get through login. It did simmer down finally enough to get us back into kill a few mobs and one of the named. For log I am including this: We finished raiding at 10:30. I think we started the event around 10. All time zones are EST. I hope this helps looking into server logs.
Click to expand...

now the server will know when we did this encounter. thanks for giving out our very important timers.
 
Crash probably not related to that encounter -- had a similar crash the day before and another today.
 
Nebi said:
now the server will know when we did this encounter. thanks for giving out our very important timers.
Click to expand...
Server corrections precede important timers for an event no one does anymore. If there is a connection they would need a timeframe for looking at logs. If there is not a connection, no one does that event anyways. The event is always up.
 
Rikunda said:
Server corrections precede important timers for an event no one does anymore. If there is a connection they would need a timeframe for looking at logs. If there is not a connection, no one does that event anyways. The event is always up.
Click to expand...

It's a shame because that's a fun event in a cool zone!
 
The lvl 45 adept Icefeather is fine except the blind aoe is broken
The lvl 52 adept Lord Commander Ragarati is fine except his rampage is broken.
 
You must log in or register to reply here.
Back
Top Bottom