Andrew Steinborn cb261c6513 Better handle not failing over on a read timeout ... The existing Velocity logic was pretty optimistic, hoping the player connection would stay alive long enough to accept a connection to another server. Now, if we notice a read timeout on the server end, we'll treat the disconnect as "unsafe" and disconnect the player immediately. I've added a configuration option to solve the issue in the way BungeeCord does it. This could cause issues with servers that extensively modify the server pipeline and could degrade the user experience, though. Let's try this more conservative and see if it helps,		2020-07-20 21:55:33 -04:00
..
src	Better handle not failing over on a read timeout	2020-07-20 21:55:33 -04:00
build.gradle	Merge branch 'dev/1.1.0' into adventure-api	2020-07-12 01:49:08 -04:00