Doctor Archive

No notes about it or anything.. but now we apparantly have a time limit in which we have to res somebody. If we can't get there in time.. say a few minutes.. then we can NOT res that person.. we get the message "Your target has been dead for too long. There is no hope for ressing."

*cries* Why'd they do this to us? Were the devs not giving us enough hate so they had to screw something up with us? ugh..... this is lame...

THAT is the way it was planned to be, but that is just from what i've heard. they may have really reduced the time though which stinks

Actually there is an auto clone feature in the game which cloned a player if you did not reach them in time. Perhaps now game tells you.

Okay.. apparanly this is a bug...

Another one of my friends died in front of me.. Literally 2 seconds after they died I tried to res them and it gave me the same message that they'd been dead too long and that i couldn't res them. Even tho I tried ressing them right after they died.

So its a bug... another one....

Zarlor If you could please throw this up on the correspondant board as a bad doctor bug. We'd all appreciate it.

A little more info too.. This happened to 2 seperate people.. and during the time we were fighting a couple others died too.. but I was able to res them without any problems. So it seems to be happening randomly at this moment.

i havent ran into this problem yet, but i know a few other doctors on eclipse who have.

Zalor i would really like to see this make the list, and im sure others would too.

After hearing about this 'rez' issue all day, I finally tested it tonight.

I had a friend I incapped and DBed in a duel several times using poison. Here are the results:

30 Seconds: Rez Successful

45 Seconds: Rez Successful

1 Minute: Rez Successful

5 Minutes: Rez Successful

Not once did I get that message that others have gotten.

At this point I gave up because, quite frankly, if in the midst of battle I DON'T rez someone within 5 minutes it's because A) They either cloned or auto-cloned or B) I died as well.

I don't know what this rez timer is set at, but it isn't so low as to hinder my group hunts.

Well i think what I ran into was a bug that caused the timer to be 0 at death.. so you can't res the person no matter how fast you try ressing them right after they die..

It doesn't sound like the timer is set really low... its just a bug.

I had that cant rez message today. group got wiped out 2250m from the nearest cloning center, i released, hit burst run and ran back, got to the 1st one, rezed them, tried to get the second one and got the message. I'd say it took 7-10 minutes to make the run. thats a guess though.

"Actually there is an auto clone feature in the game which cloned a player if you did not reach them in time. Perhaps now game tells you."

I seriously doubt it. I have overnight macro sampled nearly every night since the game was released. Some times my fighter character gets killed during the night. Never have I found myself at a clone center afterwards and every time my fighter char got killed I just had my Doc rezz him. This could be anywhere from minutes to hours after death.

An interesting test would be to have the person who timed out log out and then back in and see if you can rezz them. I'm guessing the timer isn't tied to your character so this would reset the timer. Probably would have to wait the 5 or so minutes to completely log out however.

I died in the Warren tonight and my group dragged me around for 5-10 minutes to find another doctor to rez me. That short time was enough to get the "corpse too old" dialog and I had to clone. The other doctor couldn't rez me despite having consent.

yeah, in the 30 mins I got to play last night before my computer bit the big one on me I tested this on a bunch of guildmates. an overwhelming majority rezed normally while dead from times ranging from 5 seconds to 10 minutes, but 2 instances I got the no rez message. first one was when my target had been dead 10 seconds, and the second at 8 minutes. as reported, this seems to be an entirely random occurrance which sucks, cause its going to take forever for them to track down now...

Well, this was first reported like yesterday afternoon. They did ask us to gather the bugs we are seeing into a thread on teh COrre forum, so reast assured that anything from here I got until I stopped reading the furms last night was already posted over there.

A couple of sperate requests at 1:30 in the morning, my time... sorry guys, I was asleep.