This is just a happy thread really. After 30+ attempts over 4 nights we finally got Lurker down! And we did it in 11 minutes or so with only 2 deaths (me and 1 other). I got 1 shotted by an add after the tank forgot to pick it up.
Also, hit 985 dps on that fight and got my highest SB crit, 7.6k :D (trinketted and raid buffed had 1467 +shadow damage).
Next up: Hydross!!
- Forums
- World of Warcraft
- Class Discussion
- I'm officially raiding SSC :D
I'm officially raiding SSC :DFollow
Congratulations!
i think your average time on lurker is 6 minutes.
I hope your raid-dps is high enough to kill Hydross, cause he´s got an enragetimer.
Edited, Jan 18th 2008 2:48am by Oakenwrath
i think your average time on lurker is 6 minutes.
I hope your raid-dps is high enough to kill Hydross, cause he´s got an enragetimer.
Edited, Jan 18th 2008 2:48am by Oakenwrath
30+ attempts on Lurker? Grats on the kill, but I'm concerned. That's a lot of attempts for a boss like that.
grats ^^ also almost everyone takes their time when they first do bosses, heck i remember back in the days when there were no guides to SSC/TK/kara, we had to learn those encounters ourself, good fun doing it that way ^^ (anyone who didn't level up as TBC came out really missed out on alot of fun)
Quote:
30+ attempts on Lurker? Grats on the kill, but I'm concerned. That's a lot of attempts for a boss like that.
I was also concerned about it. And I exaggerate slightly. 4 or 5 nights and on some of those we were plagued by electricity cuts (Almost our whole guild lives in South Africa. So it was probably more like 20. Also, we had to weed out those who were not doing their job, not reading strats and dying early in the fight.
Our healers are excellent and our tanks are all prepared with the resist gear for Hydross so we should be ok.
Quote:
I hope your raid-dps is high enough to kill Hydross, cause he´s got an enragetimer.
I too am worried about the enrage timer :/ Unfortunately some of our dps is a little slack... Some are only putting out ~600 and falling quite short of the average damage.
south africa? which servers do you play on? EU or chinese? (or are there ones based there?) 'cos i could see 1 major issue for your dps being lag problems. try getting them all to use /stopcasting macros, should increase their dps considerably if you're all sitting at like 300+ms
Quote:
4 or 5 nights and on some of those we were plagued by electricity cuts
*shudder*
We play on US server.
300ms? I wish. I average around 750. I do use stopcasting Macros as do most of our ranged dps. I do realise that my dps is lower than it would be if I were to be in America or Europe. Probably could hit 1200. I often tend to lag to the extent that the next SB is 4 seconds later, not 2.5.
Edit: This country is in serious trouble. I can't work somedays because we have no electricity in some areas for 4-5 hour periods.
Edited, Jan 18th 2008 4:54am by AnotherSquirrel
300ms? I wish. I average around 750. I do use stopcasting Macros as do most of our ranged dps. I do realise that my dps is lower than it would be if I were to be in America or Europe. Probably could hit 1200. I often tend to lag to the extent that the next SB is 4 seconds later, not 2.5.
Edit: This country is in serious trouble. I can't work somedays because we have no electricity in some areas for 4-5 hour periods.
Edited, Jan 18th 2008 4:54am by AnotherSquirrel
i was hoping you wouldn't say US.... that' just the other side of the world o.0. you really should change to an EU server, the ping will be more aorund 300-400 :P
well i think south africa is just as far away, and you´ll probably have mor hubs in between africa an europe than africa and usa, but who knows what way our precious packets are routed.
I wouldn't use stopcasting, with the new Blizzard spell queue your spells will not only go off faster but you can't accidentally cancel them. Unless, of course, it interacts weird with latency like yours.
If you want a tip with Hydross with a low-DPS group, get 3-4 tanks, one on Hydross and 2-3 grabbing adds (including the other-phase Hydross tank). About 10 seconds into the phase, open up AoE on Hydross with all the adds stacked on top. Hell of a lot better than single-target, and you've got more damage on Hydross himself.
If you want a tip with Hydross with a low-DPS group, get 3-4 tanks, one on Hydross and 2-3 grabbing adds (including the other-phase Hydross tank). About 10 seconds into the phase, open up AoE on Hydross with all the adds stacked on top. Hell of a lot better than single-target, and you've got more damage on Hydross himself.
last i knew, blizzard disabled the spell queue thing 'cos it didn't work properly.. i tried not using /stopcasting when they made the change, pretty certain it lowered my dps, went back to using them again and tbh, i doubt i'll ever stop using them.
yes i think it is disabled
Huh, then I must have really missed something, because I can hit the key once about .2sec before my previous spell finishes and it still goes off. I can land Blast+Death within about .01sec of each other according to parses, something that just plain doesn't happen with /stopcasting, and I can fire Aimed+Arcane on my hunter so close to each other you can't tell there are two missiles. Last I heard, it acts weird with instant-casts though, something to do with not casting during the GCD and trying to queue another spell introduces your latency into the cast timer.
Edited, Jan 18th 2008 2:21pm by lsfreak
Edited, Jan 18th 2008 2:21pm by lsfreak
that's called lag due to a low FPS (most likely at least), i'm pretty certain they disabled the spell queuing
Possibly, I do have rather abysmal FPS, but tested on mages, especially, on ElitistJerks since 2.3 have brought up the spell queue, including how it doesn't work right with instant-casts but works perfectly with cast-time spells. When is it that it was supposedly disabled? 2.3.2? Because I *know* it was in place before that.
Loki the Sly wrote:
30+ attempts on Lurker? Grats on the kill, but I'm concerned. That's a lot of attempts for a boss like that.
we were somewhere around 50 attempts on kael before we got him down
no idea when. maybe they fixed it and reactivated it... but either way /stopcasting still works (which they supposedly disabled with the change) and tbh, /stopcasting >>>> relying on a broken blizzard system.
Except the Blizzard system isn't broken, considering human reaction time is ~.1sec or .15sec even with /stopcasting and you can regularly get .01-.05 with the Blizzard system :D
They never said anything about disabling /stopcasting, but that the server-side queue would eliminate the need for it. Which it has.
They never said anything about disabling /stopcasting, but that the server-side queue would eliminate the need for it. Which it has.
EvilShenanigans wrote:
Loki the Sly wrote:
30+ attempts on Lurker? Grats on the kill, but I'm concerned. That's a lot of attempts for a boss like that.
we were somewhere around 50 attempts on kael before we got him down
Kael is also pretty widely considered the much harder boss. If people can't get "hit the boss, jump in water when he's puking, and then hit adds" learning Kael is going to be like jabbing searing nails through your eyes.
Quote:
We play on US server.
300ms? I wish. I average around 750.
300ms? I wish. I average around 750.
Did you try the lagfix? Apparently it works wonders... guildie who plays from Chile on the US Servers and another from Sweden dropped from 450 and 700 MS to 150 and 195 respectively.
Quote:
Lag fix - Repost
I hesitated a lot before reposting it, but I didn't have any hate mail saying "omg you broke my computer !" the first time, so I'll assume it's fairly safe. (It's not like you'll be able to send a mail to complain if your computer isn't working anyway, right ?)
A few weeks ago I posted this fix from the ElitistJerks forums and it worked well for most of the people but it's not really safe and it was supposed to be fixed in 2.3.2, however it seems that the Nagle Algorythm fix in the 2.3.2 patch isn't as effective as expected for most of the players, and if you're in desperate need of a lower ping this is still the best way to go.
<><><> Read this first <><><>
1 - It might have side effects, like slowing down your download speed or affecting your performance on other softwares. (In most case, it doesn't change anything, but you've been warned)
2 - If you're not sure about what you're doing, just don't do it. I don't want to be responsible because you crashed your computer in some way because you made a huge error when editing the registry.
2.1 - Seriously, if you don't know what you're doing, don't do it.
3 - If you don't have the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\ directory, you can download and apply this file to your registry.
4 - Windows Vista users might want to check this post too.
Source - Elitistjerks.com
1 - TcpAckFrequency - NOTE if you are running Windows Vista this setting may not have any effect - a hotfix is needed which i'm tracking down. This works fine under Windows XP
Type "regedit" in windows "run.." dialog to bring up registry menu
Then find:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\
There will be multiple NIC interfaces listed in there, find the one you use to connect to the internet, there will be several interfaces listed (they have long names like {7DBA6DCA-FFE8-4002-A28F-4D2B57AE8383}. Click each one, the right one will have lots of settings in it and you will see your machines IP address listed there somewhere. Right-click in the right hand pane and add a new DWORD value, name it TcpAckFrequency, then right click the entry and click Modify and assign a value of 1.
You can change it back to 2 (default) at a later stage if it affects your other TCP application performance. it tells windows how many TCP packets to wait before sending ACK. if the value is 1, windows will send ACK every time it receives a TCP package.
2 - TCPNoDelay
This one is pretty simple (Discussed here)
Type "regedit" in windows "run.." dialog to bring up registry menu
Then find:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters
Right-click in the right hand pane and add a new DWORD value, name it TCPNoDelay, then right click the entry and click Modify and assign a value of 1.
Click Ok and close the registry editor, then reboot your PC.
Once you're done with the technical stuff (it probably won't take more than 1 minute if you're not too bad at it), you can finally get your reward.
Even if in this case, the fix was used to decrease a very high ping, it seems to work very well on low (~100ms) ping for some people (lowered to ~20 or ~30ms).
RPZip wrote:
Kael is also pretty widely considered the much harder boss. If people can't get "hit the boss, jump in water when he's puking, and then hit adds" learning Kael is going to be like jabbing searing nails through your eyes.
No kidding!
Not that Kael hard though.
Recent Visitors: 203
All times are in CST
Anonymous Guests (203)
- Forums
- World of Warcraft
- Class Discussion
- I'm officially raiding SSC :D
© 2024 Fanbyte LLC