Lower the time a char stays in the game after disconnect

"

Toliman wrote:

"

vio wrote:

do you play on wireless? already tried to power off the router for 5 minutes so it resyncs with your provider?

dont get me started on this fucking thing
first, it goes to a local server before going to ISP, and the server ambushes me with lags 4-5 times a day
second, im on wireless and the wifi goes to a repeater before it goes to the router
third I've been resetting this router every few days for the last 8 years because it clogs up the connection without resets
and I'm not allowed to change router.

so that's how I play HC in this game

"

grepman wrote:

"

vio wrote:

the value for the timeout or the flag that enables some tech on the server to gradually lower the timeout to a certain base value if the connection is good would be transported like any other parameter that get's sent to the server (f.e. lockstep/predictive mode).

lockstep/predictive is transported through application layer and it pretty much only affects the client. before it used to predict if not receiving response fast. now, it will not do anything until the response.

disconnect detection often is built right on top of tcp/ip stack and is often built in connection libraries in such a way that it can change stack settings on host level (having permissions ofc).

for example, it is that way in enterprise software I work on. there is a proprietary [and optional] protocol on top of regular connection protocol JUST for disconnect detections. in my case, client side timeout IS configurable since we have multiple servers talking to each other inside the solution, but since its used on-premise its only for 'select few' and in cloud everything is pre-set and 'locked'.

no exposed end-user clients should be able to change anytyhing disconnect detection mechanism.