Earlier tonight while half way through Thad on what was an otherwise perfect run, we had a total wipe on both sides from charges going off. At first we thought some people fucked up, until we checked our combat logs and found that half the raid nuked the other half. We thought it was our mod screwing up, so we had everyone disable it, but on the very next attempt we realized people were nuking other people on the oppisite side of Thaddius.

Has anyone else had this problem? The server was mostly stable the entire night, no crashes, no lag, no server hic-ups.

Thoughts?

it's lag on the part of the people blowing the others up. i've hit people on the positive side when on my screen i was at the BACK of the negative side. the server is processing you being further back, and then your client registers you at where you got to on your own screen, so that's where your body shows up.

Yup. Sounds like your two groups were too close to one another or someone didn't make it to his/her side on time.

How the hell are you supposed to mitigate stuff like this happening?

move faster, or lag less.

edit: oops, sent too fast :-P after my first few times when i blew people up and my screen told me i was safe on the other side, i started moving in at the polarity cast animation rather than my debuff changing. of course, i'm a hunter, so i have to be at range to attack, which put me slightly farther back than everyone else, so it was just putting me in the same starting position as the rest of the raid, so i can't speak for how to help them except the above :)

Jump.

Okay, so that might not actually work, but there are other events you can send that tell the server your location. Walking/running only gives the server a vector, not a location.

I have done some research about how often server update your position and basicaly jumping does not work. The best possible way to update your position is to press any direction key ( forward, backward or strafe ) or just double ckick forward key when you reach your camp.

Yeah, this was a top culprit when we were learning the fight, and always happened even on "new hardware" servers. People just had to learn to ignore the number and stare at their buff list for a good 2-3 seconds regardless to make sure that they were, in fact, supposed to remain stationary.

Anyone understand what causes each attempt to get progressively laggier? We did this encounter 3-4 times, got him to 9%, then tried again, next time we were having 1-2 second pauses, then the next 2-3 second pauses, then the next 3-4 second pauses, etc.

Skeletons?

I thought it was skeletons too, but it was definately server side lag, because everyone was getting them at the same time. And the skeletons do have a decay rate.

Shouldn't be skeletons anyway since there's no need to release (unless you're alliance and have no one soulstoned).

Correct.

Strafing will force an update, whereas simply moving forward does not. To test this:

1. Stand outside and click on your mount.
2. Just before the casting completes, hit autorun to move forward.
3. ---> You will start running and finish casting the mount spell.

We discovered this back on Ragnaros when rogues would still step back out of range of his AE, but get punted anyway. Strafing while you do it eliminates this possibility.

I will say on the night we first killed him, lag got progressively BETTER as the night went on, because we started at 11pm, and finished at midnight. As the server latency frees up, the fight becomes simpler.

The reason for the lag is a bit complex, but you'll notice your ping doesn't go to shit.

Whats happening is when the polarity buff lands it tries to send 10 gallons of information down a pipe thats only designed to handle 5 gallons. Basically it stutters here even though your ping (the speed the water flows) is unchanged. Its just information overload... and often times this leads to disconnects.

Now, if you couple this effect with "True latency" you are in a world of hurt... and this is the 7pm to 9pm type of deal where you're getting 500ms true latency on everything you do.

As for what jaegermaestro said... You basically have X amount of error plus latency... that can be as high as whatever latency is. For us we've seen in low lag situations setting a cutoff timer to 59.6 seconds was sufficient - maybe graphical lag carries behind that.

However, our mod designer ultimately came up with a more eloquent solution, and I'll ask him what that was later tonight - it had something to do with the stacking buff, and it was much faster once it was coded in.

We use the left/right strategy incidently, as it was (at the time) the only possible way we could beat him on our absolutely horrible server... (search thaddius on google video for the low qual version).

Every time we've tried not releasing, we have ended up having the entire instance stuck in combat.

Before 20 other people explain this, you need to wait for the encounter to completely reset before taking your soulstone, otherwise you will be in permanent combat.

It is probably worth ressing on the platform... why risk potential lag? I tend to agree w/the previous posts that skeletons create lag. They certainly aren't helping things!

I believe this is true also. I hear some people liken the problem to the razorgore problem. But back then you coudl actually see that the amount of data being sent to your client progressively built up try after try. That isn't the case for Thaddius.

When we first were working on him we actualy kept at him all the way through the start of primetime till past. And the lag got worse up to a certain point and then started getting really good towards the end of the night. Even with a bazillion skeletons there.

Our solution to the lag involved being an eastern raiding guild on a west coast server cluster. Our raid times start at 4pm server time. For the first hour or so, we don't have too much lag. If we attempt to do Thaddius anytime after 5pm PST, the casting lag is just terrible. Even raiding earlier than our clusters prime time, we still get 1-2 seconds of casting lag every time.

For many of us, we preemptively start moving as the charge is changing. If you stay the same, you go back, if you change you keep going.

As far as being able to res in the room, wait until Thaddius returns, the doors open, and the wights are back with the Lightning attached to them. Hunters shouldn't be feigning death, as you can avoid durability loss anyways. If they're looking to keep buffs, just make sure whomever soulstones or takes off Divine Intervention only takes it off after the hunter has lost their charge.

After the kill it's still somewhat annoying needing to spread out for a minute, but at least now we're not kept in combat.

we don't do thaddius before around 10:30 pm because it's pretty much unplayable on ner'zhul in prime time.

We were struggling with Thaddius for weeks due to server lag. Sargeras got Server upgrades Wed night and we killed Thaddius/Gothik the following Thursday night. There's really no work around for lag on this encounter if your server sucks short of doing it at 3AM.

lol @ anyone using the line strat

Circle Strat ftw

Not that it matters, but I believe the diamond strat has fewer points of failure since someone can stand still if they forget which way to go without killing anyone.

Anyhow, this fight is frustrating. We wasted probably a good 7 hours of our timer this week on Thaddius because the server conditions weren't allowing us to kill him. Eventually we just went to work on Loatheb and came back to kill Thaddius for the week on Monday night when the lag was only somewhat terrible. Since he's the last boss in his wing I suspect we'll start putting him off till near the end of the week, it's better to miss him than waste progression time because the server is unforgiviing.