Hey everyone. Let's take a look back at NewestCoServer and ConquerSx.
The base is the problem.
Here's a little history lesson. NewestCoServer was Tanel's project. During testing, he discovered that the source crashed around 40 players. He quickly realized that the source was a huge mess and that the way he handled characters (as well as multiple other things) was wrong. It required a lot more time and math to do simple things such as spawning.
He gave the source to Arco to 'develop'. He released it here on Elitepvpers and started the "Official 5165 Questions" Thread in the release section. Then, after people got their hands on it, ConquerSX paid an unknown person to add MySql to the source. After getting the source back, he added "fixes" to it (most which damaged the source immensely). He released his work and started marketing it as the best source in the world.. "completely bugless"... which we all know by now is complete crap (hopefully).
That's the history. Why do people think it's a socket problem? Well, when I was a noob- Arco started saying false shit about how the socket system is fucked beyond repair, and the only way to fix it was to replace it. That is incorrect. Arco hasn't improved much since then- and I believed it until recently when Tanel told me to look at the socket system for the first time. The socket system is fine. It's not the best, but it's not the problem. Here's why...
Assigning clients and logging in takes up a lot of CPU for the server. Each person takes up to 7 CPU (logged in), normally between 2 and 4 CPU when idle. Logging into the server takes 50 to 70 more CPU, which is very bad. Once the server maxes out the computer's CPU, it becomes unstable and things start to fall apart as it all lags behind. So if 4 people log into the server at the same time as 30 people are attacking things, the characters will start to notice NPCs spawning late. They walk and jump around to see what's happening and the server becomes FLOODED with spawn requests and movement. Since the server has no queue to protect itself, the packets have no where to go and get held on the socket connection. Finally, the packet handler crashes the socket system. An exception is thrown when the connection maxes out.
The socket system actually survives the crash. There is actual proof that it's not the socket system because you can see the clients stay connected with your own eyes. The console freezes but the connection is still there.
That's the problem.
That's why I don't want people using it.
That's why I hate ConquerSX.
If you have to use this source... use NewestCoServer.
Sincerely,
Fang
The base is the problem.
Here's a little history lesson. NewestCoServer was Tanel's project. During testing, he discovered that the source crashed around 40 players. He quickly realized that the source was a huge mess and that the way he handled characters (as well as multiple other things) was wrong. It required a lot more time and math to do simple things such as spawning.
He gave the source to Arco to 'develop'. He released it here on Elitepvpers and started the "Official 5165 Questions" Thread in the release section. Then, after people got their hands on it, ConquerSX paid an unknown person to add MySql to the source. After getting the source back, he added "fixes" to it (most which damaged the source immensely). He released his work and started marketing it as the best source in the world.. "completely bugless"... which we all know by now is complete crap (hopefully).
That's the history. Why do people think it's a socket problem? Well, when I was a noob- Arco started saying false shit about how the socket system is fucked beyond repair, and the only way to fix it was to replace it. That is incorrect. Arco hasn't improved much since then- and I believed it until recently when Tanel told me to look at the socket system for the first time. The socket system is fine. It's not the best, but it's not the problem. Here's why...
Assigning clients and logging in takes up a lot of CPU for the server. Each person takes up to 7 CPU (logged in), normally between 2 and 4 CPU when idle. Logging into the server takes 50 to 70 more CPU, which is very bad. Once the server maxes out the computer's CPU, it becomes unstable and things start to fall apart as it all lags behind. So if 4 people log into the server at the same time as 30 people are attacking things, the characters will start to notice NPCs spawning late. They walk and jump around to see what's happening and the server becomes FLOODED with spawn requests and movement. Since the server has no queue to protect itself, the packets have no where to go and get held on the socket connection. Finally, the packet handler crashes the socket system. An exception is thrown when the connection maxes out.
The socket system actually survives the crash. There is actual proof that it's not the socket system because you can see the clients stay connected with your own eyes. The console freezes but the connection is still there.
That's the problem.
That's why I don't want people using it.
That's why I hate ConquerSX.
If you have to use this source... use NewestCoServer.
Sincerely,
Fang
