A nice to have feature would be to support DNS-based servers for dynamic IPs.
Perhaps the server admin can specify it in the MOTD (no server-side binary change) or with a dedicated server-side flag (might require new server bin or a mutator/package).
Then, when the server gets added to favorites, the DNS name is used for the lookup when the client opens up the server browser's Favorites tab. This way, servers that switch IPs will still be reachable.
Alternatively, a GUID can be used, which the master server will "follow" when servers register, but that means that favorite resolutions go through the master server.
Will also require some input validation (and perhaps code that will ignore the DNS name if the resolution didn't match the connected IP when the user clicked "add to favorites", in which case the IP will be used again).
(This can also apply to UT99 and UT3)
A nice to have feature would be to support DNS-based servers for dynamic IPs.
Perhaps the server admin can specify it in the MOTD (no server-side binary change) or with a dedicated server-side flag (might require new server bin or a mutator/package).
Then, when the server gets added to favorites, the DNS name is used for the lookup when the client opens up the server browser's Favorites tab. This way, servers that switch IPs will still be reachable.
Alternatively, a GUID can be used, which the master server will "follow" when servers register, but that means that favorite resolutions go through the master server.
Will also require some input validation (and perhaps code that will ignore the DNS name if the resolution didn't match the connected IP when the user clicked "add to favorites", in which case the IP will be used again).
(This can also apply to UT99 and UT3)