Also on AOL
- Autos
- Technology
- Lifestyle
- Gaming
- Finance
- Entertainment on AOL
- Lifestyle on AOL
- Sports on AOL
- Travel on AOL
- More on AOL
Featured Galleries
Joystiq
© 2013 AOL Inc. All rights Reserved. Privacy Policy | Terms of Use | Trademarks | AOL A-Z HELP | About Our Ads

Reader Comments (Page 1 of 1)
1-12-2010 @ 12:53PM
Malchon said...
Hooray! More raid content fixed! Woo-hoo! But Test at Sea and various other GAME BREAKING bugs remain unfixed going on 1 + months now! YAY! WOOT!
Reply
1-12-2010 @ 1:02PM
Eudeyrn said...
Test at Sea is technically still completable, but the workaround is a pain (and requires cold weather flying). You have to fly up to the Argent Tournament grounds, and go north into the new "Sea Reaver's Run" zone, then use the quest item while you are there. Then, fly back down to the ships with the quest mobs on it, without touching the right mouse button (using INS and DEL to pitch up/down). The green targeting reticle should remain visible during your entire flight back. Land on one of the ships, then aggro all the mobs in a pile, and then right click to use the quest item. You'll hit ~10 of them, which means you can do the quest in 2 runs.
1-12-2010 @ 1:04PM
Eudeyrn said...
The Slumbering King is still broken in Howling Fjord, though, as the quest mob never spawns. Some people have had success opening a ticket and having a GM manually reset the mob. Unfortunately, response times are on the order of days now, so good luck being on when it actually gets reset.
1-12-2010 @ 1:07PM
Malchon said...
@Eudeyrn
Yeah I tried that yesterday, and got 7 of them, and on my way back on the 3rd trip up there, I got dismounted while flying through Grizzly Hills. Nothing attacked me, I didn't hit any keys on my keyboard, one moment I was in the air, the next I was dead on the ground. A pain? You're damn right it is, and it's unacceptable that this has been the only way to complete this quest going on for a month now. I understand from looking at various topics that it's going to take a patch to fix this (and numerous other bugs that have sprung up since 3.3 hit), and if that's the case, what's the hold up on the patch?