The ones who must not be pinged
You have no clue what you are talking about and how any of this works.
I can confirm that there are bugs in the ice adapter that cause the weirdest kind of behavior. But I cannot tell you why, because it worked for years before that.
There is a case in Discord where a user confirms that the ice adapter causes internally 200mb/s traffic to the game.
Despite investigation we have no clue why.
What I can tell you for sure, that flaming at us is not going to help you or anybode else.
Don't expect a fix anytime soon. I spent multiple hours trying to fix it without success. Not motivated to do it again. Something is off with the directory structures in some of the new maps that breaks deployment.
The idea of the minimum username length is that users should have at least a meaningful syllable.
This requirement was introduced 7 years ago for the registration, so affecting new users. However, 100k+ accounts already existed back then.
We have 162 semi-active accounts with less than 3 characters, so this game change should be rolled back @Jip
Yes those are the character limits
There is no solution.
We don't know the cause. It could be a different individual problem on each pc. It could be something general with some network settings. It could be a bug in our software. There are multiple problems we noticed, but none of them explain the disconnect issue.
There is a slow progressing attempt to rewrite the ice adapter too be able to diagnose the problems better. But there's no ETA whenever I have time and motivation to progress there.
Why do I even need "yet another button" to enqueue? Why not automatically be enqueued as soon as you check any of the queues.
Probably something went wrong when deploying the files.
I need to look into it after my vacation.
Never, this likely just means the game can't write to the prefs file for some reason
warning: Unable to find file /mods/umt/modules/linq.lua
Looks like you are missing a file for a mod
Host candidates are all candidates "harvested" from your network interfaces - virtual or physical. So a 10.x.x.x address or 172.x.x.x appearing that you don't know could be a virtual machine network adapter or a docker network. Other ip addresses could stem from VPNs or other network services (Hamachi, ...)
Server relexive is the ip address a coturn server sees when you connect to it. If 73.157.8.80 is not your public ip, there indeed is a problem. Are you sitting in front of a proxy maybe? What does https://ifconfig.me show as IP?
Relayed candidates are basically the ip addresses of the Coturn servers that offer TURN traffic proxying,
And yes basically all our self-hosted coturn servers get DDoS hammered as soon as we publish the ip.
Global is a 3rd party service that cannot be ddosed.
