Objection : Server rez "Rules"

[khandman]

The correct way to log out will be to sit and click on the Camp button. This is the safest and best way to go about doing it as for those 30 seconds you will be present to react to any danger that may pop up.

If you instead typed in /Q or /LD, then you are still vulnerable for the time it would take for a Camp to run it's course, and if you have chosen to perform a /Q or /LD in an unsafe spot, then what you have experienced will be a risk that could have been avoided.

Edit : /q isn't a log out mechanism, it's a client closure mechanism. No idea what exactly /ld would have originally been intended for, but the effects are very similar to the /q

[Fammaden]

Originally Posted by khandman [You must be logged in to view images. Log in or Register.]

The correct way to log out will be to sit and click on the Camp button. This is the safest and best way to go about doing it as for those 30 seconds you will be present to react to any danger that may pop up.

If you instead typed in /Q or /LD, then you are still vulnerable for the time it would take for a Camp to run it's course, and if you have chosen to perform a /Q or /LD in an unsafe spot, then what you have experienced will be a risk that could have been avoided.

Edit : /q isn't a log out mechanism, it's a client closure mechanism. No idea what exactly /ld would have originally been intended for, but the effects are very similar to the /q

Exactly this, you brought it on yourself with your impatience.

[Nexii]

No it hasn't happened to me. I wouldn't expect a rez from a guide or GM because I was too impatient to log out of character select.

[DeathsSilkyMist]

When you forceably disconnect a game client from a game server without telling the server you are doing so (/q, restart your computer, force close, etc.), the server doesn't know what happened because you didn't send it a message before you quit. Do not assume programs can always send out a message before they close.

That is why there is no information on the server side to determine what happened. The server simply noticed you are not sending back data packets, and it puts you into the linkdead state until you either start sending packets again, or the linkdead timeout occurs and the server kicks you. That is why /q or other forceable disconnects are dangerous, because you will still be logged into the server for the timeout period until it kicks you.

This is why /camp exists. When you camp and go back to character select, you send a message to the server telling it you are logging out. If you had camped alive and saw your character was dead later, that would be visible to the GMs, as they have the log of you camping due to the message being sent to the server (assuming they log that).

EDIT: For a bit more clarity, /q doesnt send a logout message to the server for gameplay balancing reasons. This is why camping takes 30 seconds. EQ would be too easy if you could log out at any time. This is because you could log out to prevent death, for example. Just pull mobs to a safe location, and logout right before you die. Then wait a few minutes for the mobs to path back. /q is mimicing a computer crash, force close, etc., so they file it under that same umbrella of a client disconnect that couldn't send a message, such as a computer reset.

[Twochain]

Originally Posted by Savazuul [You must be logged in to view images. Log in or Register.]

Please keep in mind that you're playing a 20 year old game on a set of servers that goes out of it's way to recreate the "classic experience" as a core tenet of it's mission. Even going as far as to recreate or "unfix" bugs in the EQEMU project to keep true to the Classic timeline.

Dying and xp loss to things beyond our control is part of that classic experience you're in this game for.

As far as what merits or does not merit a GM rez, also keep in mind that the reason we are so restrictive on what sort of events/incidents warrant a rez is because it's not always very clearly a server issue. Outside of server-wide lag spikes or crashes, it is incredibly difficult to determine what caused a death. Without some sort of definitive proof, we err on the side of that classic experience where the death penalty is harsh, and that's what we all knew going into playing a 20 year old game.

Yeah, OP keep in mind that at the very least, GM's here are VERY fast and VERY liberal about body/items recovery from rotted corpses.

"The customer service staff (GMs and Guides) will not assist players in any way in regards to this zone.
This includes help for issues such as unrecoverable corpses (see your local Necromancer),
or characters finding themselves stuck (see your local Magician), bugs, etc.
- Gordon "

Imagine them dropping the end game raid zone and our staff just saying "Do not contact us if you can't get your body for any reason"

[Pootle]

Originally Posted by completepts [You must be logged in to view images. Log in or Register.]

It would be clearly noted in logs what killed the LD level 60 char at the WC rings.

Why are you using /q at WC rings? just camp properly.

[Jontheripper]

Ctrl+s to sit
Ctrl+x to initiate camp
/ex to exit out of the client so you're not sitting in character select

Its the best of both worlds and really the only way to quit for the night imho

[strongNpretty]

Just get back to grinding man.. what's the problem here?

[Jimjam]

Originally Posted by DNRTFM

/quit - Immediately exits the game. However, when you exit in this manner, your character has not 'camped out' in the
proper fashion, and he or she will remain in the game world for a short period after you have quit. Your character will
be under the control of the server, and may very well die while you are not there to tell it what to do. So only use this
command when you are in a rush to leave the game or are in an in-game situation that you can't get out of with the standard
sit and camp method. The risk you take when using this shortcut to exit the game is all yours.

May I suggest using

/camp server

And

/camp desktop

They log your character out to server select and desktop. They are both good.

Originally Posted by Savazuul [You must be logged in to view images. Log in or Register.]

It would?

Problem number one, you're presuming facts with zero evidence.

Problem number two, when you /q out of the game, strange and unexplained stuff can occur. No one can know for sure what happened because you didn't camp out, and no one saw it.

All of the plausible explanations I discussed with you are related to the /q mechanism. All of which are classic, and none of which are bugs. You decided you didn't like this aspect of the game, and classified it as a bug on your own.

Next time, /camp. Problem solved.

In fairness, sometimes when you attempt to camp after the client finishes the count down it crashes and you are treated as link dead instead of being straight up removed from the game.

[Synphul]

Originally Posted by Jimjam [You must be logged in to view images. Log in or Register.]

In fairness, sometimes when you attempt to camp after the client finishes the count down it crashes and you are treated as link dead instead of being straight up removed from the game.

This happens to me occasionally, but it's pretty rare. The best is when I go to log in from the character select screen and instead of going into the game the client freezes, but it still puts me in the game linkdead so I have to wait for the active character timer. [You must be logged in to view images. Log in or Register.] I can't say it's ever gotten me killed, though.

I'm a /camp desktop person.