We've all been there. You want to play some Conan and relax, you pick your favorite server, and then you're staring at this for the next 2 hours:

Absolute classic. Every big and popular server has had this issue. I've experienced it myself on all the servers I played on, and now our players have been experiencing it on Avardon as well.
We just took it as the harsh reality of playing Conan. That's how it is.
The only solution that seemed to be working for some people was a VPN, specifically a VPN to another continent. We had another solution with alternative IPs, proxy servers for the real game server. That also had varying degrees of success for different players. But even then, it was never a guarantee that you will connect to the server. Especially not if there's 80+ players.
I've spent countless hours in the past trying everything I could to resolve this issue, and so have many others. Different server configurations, reverse proxy solutions, investigating the logs, looking through UE4 source code and Wireshark captures to find an explanation, we tried it all.
So why was this happening in the first place and how did I fix it?
Let's remind ourselves three observations (because I now have the answers for each of them):
- The more players there are on a server, the more difficult it is to get in. At some point it's basically impossible to connect.
- When too many players try to join all at once (such as after server restart), the server cannot handle it and no one gets in.
- Somehow, VPNs to another continent help you get in easier, US players get into EU servers easier and vice versa. US players need EU VPNs to get into US based servers.
Remember these three observations, I'll reference them in the next part.
All of these were big question marks. No one understood why, it didn't make any sense at all. I studied networking and couldn't explain it either, until now.
Buckle up, the technical part begins. Don't worry, I'll try to avoid too many nerd words to make it easier to understand.
I've analyzed what's actually happening in the background and I was finally able to answer this mystery and pin point exact culprits.
Problem #1
Conan has a limited amount of data it can process per frame (you've probably seen the Server FPS number that goes down when there's a lot of people). Specifically 128 KB. Your movement, clicking of buttons, chat messages, approaching builds that have to load, or players with their Tot Custom accessories, all of that generates a lot of data sent through the server to other players. And believe it or not, accessories are huge contributor to that. Easy solution would be to limit them, but that wouldn't solve the real problem.
The more people there are on a server, the less frames it can process per second (typically 1 when there's 100+ players on a server), and at the same time, the more data it has to process. This is also what can cause red boxes. But more importantly, if the data doesn't fit within the limit set by the game, the lower priority packets (such as connection attempts) are refused, thrown away, ignored, so that people who are already connected don't get kicked out, they have the priority.
This explains the first observation - too many players = packets are ignored.
Problem #2
During my investigations, I've also found out that one singular connection attempt (be it through join button, direct connect button, or console command) actually creates about a 100 packets if they are not getting through. The client basically bombards the server trying to connect, which makes connections sometimes even heavier than actually being in the server.
This explains the second observation - players might not even be spamming the buttons, but Conan is spamming the connection packets and overflowing the server limit, making it difficult to connect when others are trying as well.
Problem #3
I've discovered that more often than not, your connection packets are not actually ignored because of the limit explained above. They go through, server actually responds and asks the client (your game) to confirm the connection, this is called a handshake. And during this handshake, the server actively decides to refuse your connection and client decides to show the timed out error anyway, even though it wasn't a time out.
The conversation goes something like this:
- "Hello client, I hear you, this is server, you can connect now, do you want to?"
- "You bet, I'm so ready to connect. I can't wait to play some Conan."
- "Hold up, cowboy, I'm not letting you in, you're some dangerous anomaly."
So why did this happen? It has a lot to do with the server being overloaded as well. During the handshake, server stamps its offer to join with the current time. The client has to connect within 40 seconds, but this requirement also has a lower limit of 0. If it took 0 milliseconds for the client to respond, then the server refuses it, as that simply doesn't make sense. Of course, naturally, nothing ever takes 0ms. Even if I was connecting from the same machine, the processing takes at least some tiny sliver of time.
The problem lies in the fact that the server updates its own time for this comparison once per frame, hence when server is slow under load of many players, it is suddenly considering anything faster than a frame (sometimes a second, sometimes half a second) as invalid connection that responded in unrealistic time of 0ms. That's why it's easier for US players to connect to servers hosted in EU and vice versa. Because it took enough time to get there, so that the server managed to process another frame in the meantime and updated its time. And so we need to use alternative IPs or VPNs to slow down our internet connection, because worse is better.
This explains the third observation - using VPNs helps but for the wrong reasons.
Funcom likely never observed these problems, because unmodded official servers likely run on enough Server FPS to never see this issue. And while I could send this all to Funcom and hope for the best, they are not updating Legacy version anymore and ignoring even more important emails.
I had to be creative and figure out a patch myself. First, I made a temporary solution with 96 lines of C++ that adjusts the size of the opened connection buffer, changes a number in memory of how many packets are accepted from connection attempt spam, and also removes the silly limit that prevented connections from going through if the handshake happened within one server frame. At least that's the simplified explanation. And it worked. We could now log in instantly.
With a fix made and tested, I got to work to get it ready for everyone. And so now, as of version 0.2.6 of Ratchet (Legacy), this patch is built into the script extender and can be used by any server.
To enable it, update your Ratchet installation, and add "netFixes": true into your config.
Players don't have to do anything, they can just log in and spend their time actually playing the game instead of staring at the dreaded "Connection timed out!" errors, that can now finally be forgotten, just like we forgot mod mismatch screens in the past with Conay. 😉
And the impact? Avardon had ~40% increase in average player count since I announced this fix. Over night, people who gave up on the game entirely are returning. We just wanted to play without having to stand on our heads to get into servers. And now we finally can.
Resolving this made me so happy, a flash of joy in otherwise lately depressing life.