PerceptionRedemption

A glutton has stolen the sausage and has eaten it.

I am aware of this. The issue is about my ability to fetch the servers list and to broadcast my server and it did that whatever my setup was. I had talked a bit about my connection issues that had or still have sudden appeared on at least another topic. So, I am limited to direct connect for both and this might be a real slowdown for nothing. I just came here to talk about the status and my intents about it. The server is officially closed because I cannot fetch and broadcast. I was unable to get to the MP-Gaming's Server neither when I saw people in.

For anyone who might care at least a single bit only... for the others, there are other more important topics for you. You might have waited for long because the server has stopped to be there for quite a while. This information is now outdated and there is now a complete absence of this server on the list and direct connect. I originally intended to release the commands so it could be useful for the other server owners. I have chosen to delete them and anything Renegade-related, except the music and the screenshots. It would have been weird and harder to get many players to come by connecting directly when some are certainly unaware of such possibilities. They'd rather connect with the help of the frontend provided with the Renegade-X mod. I was unable to connect to the servers list server, either as a player or as a server host. So, the players would see my server absent from the servers list.

I had the server ready before the new year. However, it is not broadcastable.

Hi Milkey and welcome to the forums, I would join them now if I were you . I didn't expect a ban of the clan from Jelly. I will probably check why...

You have my encouragements. Have a good success in this project.

If only the players that never see the forums would get the files... There has been a decrease of the number of players because they don't seem to know what to do. It is sad. It looks like the solution is to bake them an update...

Happy New Year to you all!

Hahaha!

The only IP and its port I could get by opening the frontend is 66.90.85.23:7779.

My logs didn't obtain 64.191.3.217 as it was supposed to be.

stun.xten.com has been successfully pinged and not successfully tracerouted. It blocks at Amazon-peering.net.bell.ca [67.69.246.10]

I have a clean installation of the client and the server now, with a failsafe server copy, without the Renegade-X mod. I have uninstalled my firewall and reinstalled it with the latest version available. I cannot get the server list. The firewall's information about the connection reports a connection to the port 7799 with the IP 66.90.85.23 with the Renegade-X frontend. I have no problem accessing anything else online. For 66.90.85.23 : I have executed a traceroute and I have pinged and it blocks at comcast02.fdcservers.net [75.149.229.82] I am able to both ping and tracert for stunserver.org and sc.renegade-x.com.

Thank you for your answer. Two different people so far have confirmed the problem. It worked fine until today here. I will recheck my settings on my end.

Is the server list down right now? My server reports that the connection attempt has not been completed. I looked at the frontend and I get the same and it says that I cannot get the list. I also checked if I could update my Renegade-X installation. The updater says that Renegade-X failed to update.