Silent connection failer (lag related)

[mvgulik]

Mmm. It seems to me the lag-spiking is (also) showing there is some character log-off bug.

Like:
Character not responding anymore. (client only features still work. so client has not effectively crashed. Which kinda explains the lack of any error output.)
Character not online anymore. (checked with secondary client and character.)

- Not sure if its a Ender client only thing, but I doubt it.

[borka]

yep - happened to me too 3 times, but as i have a mixture of my slow 3G Connection plus lag spike i thought it was more my connections fault.
I got 15 secs walk - 10 secs not responding - 20 sec walk - 20 secs not responding - for a while then it happened that i was logged out without Ender showing it... normally i have a constant upload from client and only the download to client is zero at lag spike - in that case ( walk - no response - walk) it was zero for both... (crosscheck with second client window showed that connection was ok)...so i assume it's just "inactivity log out" but without server being able to send the log out data to client cuz of a lag spike at that moment...

edit (reason follow up post) : this was happening to me the last 2 days only!

[Darthjew]

I've had thing like this for a half of the year (started nearly at 6th world launch), but it suddenly stopped like 2 months ago, to happen now again. But that was only me, now looks like not.

[mvgulik]

normally i have a constant upload from client

Just in case I get the urge. What do u use to see/check this?

[borka]

I use a tool from my internet provider that also shows it on the bottom of it's window, so i run Ender in a window, have the tool window in background and just the indicator shown below the Ender window. With that i also am able to recognize with what low transfer rate HnH is playable.

[mvgulik]

Just dropping in some more data.

In relation to the same (client connection failure) case, after a manual character(+user) log off.
- Either with 'Log out' in Options, or with 'lo' in console.
Logging of, while checking if the connection is ok. Seriously lowers the change on running into the losing connection problem. (success rate depends on the current HnH lag weather of course.)

Not sure if both cases, CQ: User initiated and Server initiated(if this is the case) 'log out', use the same method(communication wise), but they both could do with some sort of 'log out' checkup. Or else some unconditional 'drop to Log-in' screen' option for the client.

... Its kinda tiresome to have to restart the client, just because its assuming your still connected/loged_in. ...