Originally posted by Itek
Fixed ressurection timer that was counting down against the 3 hour limit when player was not logged in.
There's the current edition of the CS Reimbursement policy, which states (originally in bold and italics)
The Resurrection timer for any corpse is 3 hours of online time. Online time includes any time spent on any character on the account in question, any time spent on any character on the account in question, any time spent at the character select screen, or any time spent waiting in chat.
Another source, from the EQIM information page (which is undoubtedly out-of-date, but more recient than the 24hours online/7days offline rot timer example, which was removed Feb 13, 2002):
Regarding in-game side effects resulting from the use of the EQIM, EverQuest lead designer Rich Waters has this to say:
Being logged into EQ Instant Messenger does not count towards any resurrection timers, corpse timers, and the like. It connects you to the chat server, but isn't connecting you to the game world in any way that would affect your character at all.
Being logged into EQ Instant Messenger does not count towards any resurrection timers, corpse timers, and the like. It connects you to the chat server, but isn't connecting you to the game world in any way that would affect your character at all.
I don't know if there would've been anything a GM or outsource-mini-GM (since, as far as I know, there are no CS Guides anymore, only ingame-"GM event"-running Guides) could've done to rectify the situation, but it does seem like it was a legitimate bug and not simply a user error/misunderstanding. In my opinion at least, it feels a lot better to hear "Its a bug, but we can't do anything about it" than "Everything is working as it should, so nothing for us to do" (assuming the first is true, of course).
------------
On a side note, I've seen a thread or two about a player's horse reciently sticking around after they died. The horse never left, even when the player logged out, and the rez timer continued to decline (the player also had issues returning to the zone upon attempting to log back in) - maybe its something related?

Comment