PDA

View Full Version : Epic quests shut down for the weekend by the Friday afternoon update?


Glenolas
02-10-2008, 12:53 AM
<p>1.  Pre friday's update, I got the key to drop to start the Illusionist quest.   Found the door it opens,  in about 5 mins the halfling spawns,  we go talk,  I fail his test.   Somehow in years past I'd gotten only 4 of the fun type illusions, he wanted the one I didn't have as part of his test.   I know he worked, however, and knew where he was.    </p><p>Okay, back to Qeynos to get illusion,  didn't resume with the quest until Sat a.m.     Went back to door,  opened it, no halfling, so settled in to wait.     150 minutes later, still no halfling.  The key is in bags,  door opens, just no NPC.  </p><p>It's easy for me to do a prolonged test, as with 3 computers, I do real life web work on one,  camp and watch something on another.    Nobody else nearyby, no one else came and got  it.  The NPC simply never showed.     I came back 3 more times during the day,  waited 30 mins each time, no halfling.   Key is in bags,  just no NPC.  </p><p>2.  Prior to the Friday Afternoon Update, I'd finished Fury epic thru the rhinos, including killing the ^^ that closes the quest just before the update happened.   Came back 2 hours later, after update was done, and went to find the scribe.   Camped the location all the furies said (cage in Eastern Pens),  also ran around both buildings in eastern pens checking all cages, but NO SCRIBE.   Brought guildie scout out who  checked track for him by name, no joy.   2 hours continuous, never losing track of the cage, but checking all the other frogs also...NO JOY.   Nobody else got there and grabbed it, etc.   It just never spawned.    </p><p>3.  Helped a guildie fury with the chokodai Saturday afternoon.  Seems the group of 3 needed to call to her would not spawn.   75 minutes later, they were still not seen.   Throughout the day a loose network of Furies on the server talked in chat, and nobody on the quest got the chokodai group of 3.  </p><p>So where did the NPC's go?   Did anyone get any of the the above updates on Saturday?</p><p>Any other missing NPC's need adding to the list?</p><p>Glenolas</p><p>Level 80 Wizard, Fury, Illusionist</p><p>Guk</p>

Syth
02-10-2008, 02:15 AM
Any NPC or mob that despawns automatically, rather than being killed, doesn't spawn again until a server reset or second instance is made. This includes the Illusionist epic quest starter NPC, the Bouncer for Stein HQ that runs around for a while then despawns, and 2 of the NPCs needed for the last step of the Illu epic quest. It looks like yours are the same, assume it'll be fixed Monday/Tuesday.

Allisia
02-11-2008, 12:55 PM
Bouncer Prud does respawn. My wife chased him til he despawned while waiting for me to catch up. A few hours later that night we got him. This doesn't directly address the original poster's issue. It seems this problem is being felt by many and it affects a lot more than just the epic quests.

Tarl28
04-14-2008, 01:10 AM
<p>I started my Fury Epic yesterday.  I was able to complete up to the Rhinos.  When you lead the young rhino's through Traitors Pass, it will not update once you get them to the other heard.</p><p>I petitioned and waited, went to bed, got back up, still logged in, with my 4 rhino's in tow.</p><p>Went back to bed (I work nights).  Got up this afternoon, it seems the Rhino Mask doesn't work with the named, the name killed me and the 4 rhino's.</p><p>Fury epic is broken in more than one spot?</p>

missdoomcookie
04-14-2008, 09:38 PM
<cite>Tarl28 wrote:</cite><blockquote><p>I started my Fury Epic yesterday.  I was able to complete up to the Rhinos.  When you lead the young rhino's through Traitors Pass, it will not update once you get them to the other heard.</p><p>I petitioned and waited, went to bed, got back up, still logged in, with my 4 rhino's in tow.</p><p>Went back to bed (I work nights).  Got up this afternoon, it seems the Rhino Mask doesn't work with the named, the name killed me and the 4 rhino's.</p><p>Fury epic is broken in more than one spot?</p></blockquote>We have this issue identified and a fix in the works.