Wavelink always using the node from NodePool which is connected first to Nodepool (Ignoring the specs and load of the lavalink server )

[munishkhatri720]

node : wavelink.Node = wavelink.Node(uri='https://eu-lavalink.lexnet.cc:443',password="lexn3tl@val!nk",secure=True,retries=3,id="LEXNET 1")

is connected first to Nodepool but it is a public node and worst quality (too much load on it )
but it still playing with this as u can see it is reconnecting again and again

[munishkhatri720]

wavelink Nodepool has to rearrange nodes by their loads

[chillymosh]

Hi,
The NodePool gets connected to lowest-use Node in the NodePool already, which is determined by how many Players your current Bot has running on it and not what the node has running on it. We do generally recommend running your own node.

Please make sure you are on the latest version, preferably the git version (2.6.1) as it has some minor fixes.

This may be subject to change in the future.

[munishkhatri720]

Hi, The NodePool gets connected to lowest-use Node in the NodePool already. Please make sure you are on the latest version, preferably the git version (2.6.1) as it has some minor fixes.

Do note that the load is determined by how many Players your current Bot has running on it and not what the public node has running on it.

but other bots are playing on a public node , it has to consider all, like javascript lavalink wrapper "erela.js" have