This would definitely be a useful option for subscribers. When using auto-connect, landing on a congested free server can affect speed and consistency, which defeats the purpose of paying for priority infrastructure.
From a performance perspective, it’s very similar to how system optimization works in other areas, if one limited resource gets used accidentally, the whole system slows down. Identifying and avoiding those constraints early usually leads to a much smoother experience. I’ve seen the same concept explained well in tools like https://thebottleneckcalculator.com/ , where the idea is to detect which component is actually limiting performance instead of guessing.
An option to exclude free servers would basically remove that potential bottleneck and make auto-connect much more reliable for paid users.
This would definitely be a useful option for subscribers. When using auto-connect, landing on a congested free server can affect speed and consistency, which defeats the purpose of paying for priority infrastructure.
From a performance perspective, it’s very similar to how system optimization works in other areas, if one limited resource gets used accidentally, the whole system slows down. Identifying and avoiding those constraints early usually leads to a much smoother experience. I’ve seen the same concept explained well in tools like https://thebottleneckcalculator.com/
, where the idea is to detect which component is actually limiting performance instead of guessing.
An option to exclude free servers would basically remove that potential bottleneck and make auto-connect much more reliable for paid users.