Maze is dead~

[TerraSleet]

Isn't it a little inconsiderate that you released the map tiles of your village essentially leaving your village and nearby ones open to harassment?

I hope you asked for permission from your friends to post that.

[jorb]

I posted here.

[Garfy]

IF the computer was shutdown (doesn't matter if it's a real shutdown, hibernation or sleep mode) the connection between client and server should be severed, and session would be terminated. In this case server would logout this character IF it was possible. Maybe something else stopped the character from logging out, after player session was terminated. Like someone initiating combat or removing your permissions from pclaim / vclaim.

But was the PC really shutdown? Or maybe it stopped on a warning that there are still programs with unsaved data, but you left without seeing this?

In any case - it's always safer to log out with logout button.

It doesn't always work like this, especially in Haven and Hearth where it is possible for a character to be logged in without a player playing. What needs to happen is the client sends a message to the server saying "this character has logged out", then the server received this message and despawns the character from the world. Clearly this did not happen. Which means the client is at fault. Somehow the custom client he is using either didn't send the logout message, or incorrectly send it. Thus the server didn't log out the character.

Unless you were in combat, or on a claim you had no permission to be on, this is clearly an issue with the custom client being used. You should take it up with whoever is responsible for this client.

[Procne]

It doesn't always work like this, especially in Haven and Hearth where it is possible for a character to be logged in without a player playing. What needs to happen is the client sends a message to the server saying "this character has logged out", then the server received this message and despawns the character from the world. Clearly this did not happen. Which means the client is at fault. Somehow the custom client he is using either didn't send the logout message, or incorrectly send it. Thus the server didn't log out the character.

Unless you were in combat, or on a claim you had no permission to be on, this is clearly an issue with the custom client being used. You should take it up with whoever is responsible for this client.

Wait a minute - that would mean that if my net dies while playing haven then my character would never log out. I have hard time believing this is how it works. Player session cannot rely solely on such stateless "connection".

[lachlaan]

When the whole walljumping thing happened I was testing for possible exploits of my own walls with 2 characters, using amber client. Was possibly an older version than the one out now but it did correctly log my characters out on X-ing out.

Also, sorry for your loss Maze. Have to say that it's never pleasant seeing anyone die to bugs, even more so knowing that there's not going to be any reimbursal for such huge amounts of time invested in chars :\

Would be nice to have you guys poll the community on other options regarding the reimbursal stance.

Perhaps something along the lines of : all past characters cannot be revived , all deaths since the time of the new stance follow these rules (combined with a decent list of diagnostic logs to help determine actual death circumstances as often as possible)

1) If existing diagnostics prove bug death, revival.
2) If existing diagnostics don't prove bug death, add diagnostics that would've caught reported bug and similarly tough to diagnose bugs, say sorry to dead guy and move on, when next instance of bug happens - have diagnostics to sort it out better.

The way i see if it bugs continue to abound, the little drama that can be had over the loss of a 1 month char will be significantly harsher when year old chars start dropping like flies to bugs made possible by new content.

[Garfy]

Wait a minute - that would mean that if my net dies while playing haven then my character would never log out. I have hard time believing this is how it works. Player session cannot rely solely on such stateless "connection".

This happens.

I've had my internet go down. Try to login the next day to be met with the "already logged in" message.

[romovs]

this is clearly an issue with the custom client being used. You should take it up with whoever is responsible for this client.

Clearly
The aforementioned client operates identically to the default client when it comes to closing it.
Server logs out characters automatically if no message or message acknowledgement was received from the client within a 30 seconds span (or in that area. don't remember exactly). Which is what happens when the client is... closed.
There is *clearly* no way a character could have stayed logged in indefinitely when the client is closed unless something server side prevented the lgout.

[Garfy]

Clearly
The aforementioned client operates identically to the default client when it comes to closing it.
Server logs out characters automatically if no message or message acknowledgement was received from the client within a 30 seconds span (or in that area. don't remember exactly). Which is what happens when the client is... closed.
There is *clearly* no way a character could have stayed logged in indefinitely when the client is closed unless something server side prevented the lgout.

You can't fool me. You're just a notorious meta mass murderer.

[Kaios]

but i know most custom clients keep your chars logged in forever unless you properly log out. pressing "x" is the mistake here, im afraid. and in that case, this is not a bug to the best of my knowledge.

It has never worked this way for me, regardless of the client I'm using I've always just hit the X and it's been fine.

[Sevenless]

but i know most custom clients keep your chars logged in forever unless you properly log out. pressing "x" is the mistake here, im afraid. and in that case, this is not a bug to the best of my knowledge.

It has never worked this way for me, regardless of the client I'm using I've always just hit the X and it's been fine.

I believe the log out function has a specific check from the server that insures you managed to disconnect properly. Pressing the X does not check for logout. Usually speaking it's fine. But if the server hiccups for whatever reason, your client never bothers to verify that the server said everything's logged off properly.

Condolences maze. The kill bugs suck a lot, but I'm glad we aren't wading into revives. Sorry for what that means to you :/