It says in the thread, they already fixed it by having the madserver.net server reject connections.
Previously Microsoft parked it by having it handshake and send empty replies, which worked for other madserver-seeking games but choked these two.
Since switching to TCP rejects cleared the issue, a custom DNS entry was probably a viable workaround before the upstream fix.
It says in the thread, they already fixed it by having the madserver.net server reject connections.
Previously Microsoft parked it by having it handshake and send empty replies, which worked for other madserver-seeking games but choked these two.
Since switching to TCP rejects cleared the issue, a custom DNS entry was probably a viable workaround before the upstream fix.