[Bug] Bungeesk disconnect automatique

[Lennord]

Describe the bug
When I do the code below and I use it in the game, it sometimes disconnects automatically and I have to restart the connection script for it to reconnect, no error (neither in the game nor in console).

on load:
	while client isn't connected:
		create new bungee connection:
			set address of connection to "127.0.0.1"
			set port of connection to 20000
			set password of connection to "password"
		start new connection with last created connection
		wait 30 seconds

To Reproduce

on join:
	delete global variable "test.settings.language.%player's uuid%"
	delete global variable "test.rank.name.%player's uuid%"
	delete global variable "test.rank.author.%player's uuid%"
	delete global variable "test.rank.date.%player's uuid%"
	delete global variable "test.firstjoin.%player's uuid%"
	wait 5 second
	set global variable "test.settings.language.%player's uuid%" to "EN"
	set global variable "test.rank.name.%player's uuid%" to "DEFAULT"
	set global variable "test.rank.author.%player's uuid%" to "CONSOLE"
	set global variable "test.rank.date.%player's uuid%" to "%now%"
	set global variable "test.firstjoin.%player's uuid%" to true

Expected behavior
Disconnecting from the server to the bungeecord should not be automatically disconnected unless the server in question is down.

Screenshots

Desktop:

• Paper version latest 1.18.2
• BungeeSK version latest build 2.0.0

[ZorgBtw]

here is a better code for connecting your client (beacuse it sometimes disconnect from the server)

function connect():
	while client is not connected:
		create new bungee connection:
			set address of connection to "127.0.0.1"
			set port of connection to 20000
			set password of connection to "s*eL/2N18dr5vTdZ"
		start new connection with connection
		wait 5 seconds

on load:
	connect()

on client disconnect:
        wait 5 seconds
        connect()

[Lennord]

I used your code, it optimizes better but it sometimes disconnects when it sends too much packet to the bungeecord.

[xibo1212]

I have the same problem with version 2.0.0, and sometimes I can't listen to the disconnection event, or the communication is not easy to use when the connection is not disconnected, which leads to the inability to reconnect in time, so I still use 1.1.0

[Lennord]

Hello, I would like to know when this will be fixed?

[NyuDev]

I'd like to know too, can't wait for the ver 2.0.0 ❤❤❤❤