Thanks for the info! Learned a lot. Plus the other ways to camp is very helpful.
To get critical of me demanding "proof" and "evidence" I died during a crash is ridiculous- why even ask me if you refused to help or educate me, up front? I learned for certain better than to petition again for this type of thing, no doubt. But to the ones who replied with all the helpful info, much appreciated!
Quote:
Originally Posted by DeathsSilkyMist
[You must be logged in to view images. Log in or Register.]
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.
|