4.0.1, Pre Cataclysm patch

Sindy is 3 times more evil.

The voice alone makes Her > Deathchin.

I hope we weren't fools to have come to this place. I hear the icy winds of Northrend can consume our souls.

Currently writing a book too: "Your Pathetic Magic: How Not to Suffer When It Betrays You"

EDIT:

 Sure is dark in here

Gratz!
Who got the tentacle? Also lol @ someone getting "Over 9000" achieve.

Gratz!
Who got the tentacle? Also lol @ someone getting "Over 9000" achieve.

How do you get the Over 9000 acheive? Haven't played WoW in forever, neh.

Gratz!
Who got the tentacle? Also lol @ someone getting "Over 9000" achieve.

I don't remember; someone I don't know that well. It wasn't really all that hard since zerging phase 3 is fairly easy. All I had to do is spam Regrowth on the tank and the last 30% went down in a flash. The only thing that made us take like 7 attempts was a retarded tank that we forced to DPS after he wiped us enough. What was funny though, we went to Algalon right after this and someone used the tentacle in his room. After it ran out of time, it sucked itself under the floor, but since the floor is clear we could still see it and click on it. It stayed there for like 20 seconds.

How do you get the Over 9000 acheive? Haven't played WoW in forever, neh.

Get over 9000 achievement points.

Didn't screenshot it, but we also did [Many Whelps! Handle It! (10 Player)]. I think most of us had our computers crash when people started AoEing the whelps. Someone suggested we turn off our combat log just for that, and it ended up working out.

Didn't screenshot this either, but [Earth, Wind, and Fire (10 Player)] was totally pineappleing insane. I'm absolutely sure we would have failed were this still 3.3.3.

I think the game is trying to tell me something...*Points @ Dates*



Now if only the damn HH Reins would drop LOL

wow.....
I wish horseman's reigns would drop for me. I've gotten like 5 squashlings on my rogue already

anyone experiencing lag playing wow or sc2?

for me the game is unplayable, and on the sc2 forum, lots of people are complaining about lag :f6:

I haven't seen anything myself.

I was getting about quarter second lag all day yesterday. It does not combo well with the GCD Queue system lol

I was getting about quarter second lag all day yesterday. It does not combo well with the GCD Queue system lol

GCD queue system is so damn annoying..... ESPECIALLY for rogues. When we have full energy, it always uses my attacks twice when I mash keys because it's queuing up for the next GCd.

GCD queue system is so damn annoying..... ESPECIALLY for rogues. When we have full energy, it always uses my attacks twice when I mash keys because it's queuing up for the next GCd.

Then... don't mash keys.

I personally love it. Now I don't have to get pissed off when I swear I clicked a spell on time but I actually clicked it 50ms before my GCD ended so it didn't work.

This is why you're supposed to mash keys
[video=youtube;VgDjG_0ecTI]http://www.youtube.com/watch?v=VgDjG_0ecTI[/video]

The GCD queue system not only reduces DPS, but also slows reaction time to procs and causes energy classes (with 1 second GCDs) to use attacks twice.
It's not a good system.

This is why you're supposed to mash keys

 Spoiler

[video=youtube;VgDjG_0ecTI]http://www.youtube.com/watch?v=VgDjG_0ecTI[/video]

The GCD queue system not only reduces DPS, but also slows reaction time to procs and causes energy classes (with 1 second GCDs) to use attacks twice.
It's not a good system.

Two of those things you mentioned are a direct result of button mashing. Proc reaction time may slow by a GCD, but if you're waiting nearly the full second to press your button there shouldn't be a difference anyway.

Perhaps it's different for me since I've just been healing the whole time I've played the game. I also had a 1 second GCD, so spamming a button was just a way to run out of mana really fast, rather than minimize the time between the GCD ending and doing my next skill, so I can see why so many people did it and are now having trouble with this system. On my end, this system has been amazing -- I don't have to time my second perfectly and risk not casting a heal if I mess up. But really, is it so crazy hard to just train yourself to press your next button once right before the GCD ends rather than 70 times around when it ends? Regardless, the queue threshold will be adjustable in the near future, so I guess you can decide if you like it or not by then.

I believe the point he was trying to get at was execute phases. Rogues now have a skill to use / spam during <35% and with talents / glyphs, we energy cap really quickly and energy capping is an overall loss of DPS / rDPS, so spamming that one skill, then use a finisher, and rinse / repeat is the only way to not cripple ourselves and cause ourselves to massive drop in DPS before the soft / hard enrage hits and wipe the group.

This argument is apple to oranges, so it's rather pointless in trying to argue it IMHO.

Also lolPost4.0.1Kill

 Spoiler

No not execute phases... anytime a rogue has full energy. If I use shadow dance with full energy, and use a cheap shot, it will go off twice.

another example. My ambush and gouge are both on the same button (4). When I'm spamming ambush, trying to get it off as soon as I get behind someone, my gouge will go off right after I ambush. This not only wastes 4 seconds of energy, it wastes my GCD, ruins my burst, and messes up the opener I was planning on using.

It sucks... You spam keys (like the video mentions) to account for any error in latency. This applies to PvE and especially PvP. When the game punishes you for doing that, it makes it feel less responsive and more sluggish. Kind of like Aion

Found the problem of my lag, and of almost everyone else:

After finally looking into this, I noticed that the game data switched back over to using TCP this patch, and I /palmfaced. No wonder there are issues! Also, this explains too why some peoples issues were resolved, such as at some college campuses.

Any chance you could put in a request to allow users to switch between the two protocols (TCP and UDP) at the very least via a line in the Variables.txt file? Honestly, sometimes one is better depending on the user. The default should really be UDP, though, for the sake of the Aussies.

blizzard response:

Maged: There are internal discussions about TCP vs. UDP, and the pros and cons of each, obviously I'll toss the idea of a user-selectable option into the mix, and see what happens...

That said, they should (theoretically) be roughly equivalent in performance, barring someone being on a very lossy link.

We're also trying to sort out exactly what's going on, and so eliminating protocol as a variable is key.

Of course it's our job to fix it -- but we first need to make sure we know exactly what is wrong, so that we don't go stabbing in the dark (and breaking other things).

We can only test a finite number of variations in network configurations, and so there will naturally be some that crop up that cause us grief in one way or another.

Path MTU is an interesting find, as it's possible there is network gear "in the middle" that is ignoring the DF flag and potentially fragmenting and re-assembling data on its own -- and who knows if it's doing things properly? To be clear: I'm not saying that's "the" problem here, I'm merely offering an example.

We're still collecting and analyzing data, and I'm here now to hopefully get some back-and-forth with people actively having issues, so we can nail this problem down once and for all

I apologize to those who have been having (and continue to have) issues playing StarCraft 2. But I want to absolutely assure you that we have been working on things and will continue to work on them until they are solved.

http://us.battle.net/sc2/en/forum/topic/...200?page=2

Blizzard changed how the client reach the server, and now, some networks are experiencing problems handling too many TCP connections, that's why some dont have lag, and others do have. :/

At least they were quick to fix it. 2-3 days is pretty fast for a problem like that.

Grats on the heroic sindy kill btw. She's still a hard fight. They buffed her a bit from my understanding. Our guild leader/pally tank was saying that his slow effect thing lasts a lot longer so it's up almost 100% of the time. They buffed Putricide as well. You can't force a second ooz to not spawn by pushing the boss into the 2nd phase anymore. If he starts the cast, the ooze comes out.

They didnt fix anything, they just looking for a resolution as for now, been happening for the past 2 weeks :S

At least they were quick to fix it. 2-3 days is pretty fast for a problem like that.

Grats on the heroic sindy kill btw. She's still a hard fight. They buffed her a bit from my understanding. Our guild leader/pally tank was saying that his slow effect thing lasts a lot longer so it's up almost 100% of the time. They buffed Putricide as well. You can't force a second ooz to not spawn by pushing the boss into the 2nd phase anymore. If he starts the cast, the ooze comes out.

Yeah definitely grats on the Sindy kill. She's still a tough cookie. According to my DBM, I've wiped on her over 50 times.

Actually though, my last H-Sindy kill was one of my smoothest ever (10m, not 25). We decided to zerg it (1 heal 1 tank) and we pretty much one-shotted it. Sure, I might have blown up for over 100k a little before the fight ended, but solo healing it is hard (read: fun) as hell. At least I only took two tunnelers with me. Looking to keep the raid alive even longer next time.