iboomboom

This your client, just hit ok and play. You don't have to update your client.

That's just our mod being downloaded from the redirect server. You can try logging in to our regular server and see if that helps. You shouldn't need to download the mod if it's already downloaded.

Unfortunately nothing you can do individualy since it's a routing decision being made by the network in real time. I'll wait for our host to see what they come back with. Please keep sending me your IP and your tracecert output. In the interim though using a US VPN may help in this particular situation, that is something I would personally want to try if I were in that situation.

This is Arelion, they like to sometimes take the scenic route and go to Dallas from Chicago and then to NY before crossing the Atlantic.

I got word from NFO, so apparently the traffic to/from some of our European players toggles between Arelion and GTT depending on which is faster. Some times Arelion likes to take Detour to Dallas before it goes to Europe. This is what is causing the lag.

Good News folks, the server was stable for 2 days, sustained multiple games with up to 23 players in the server. The original server lockup issue is RESOLVED. Evident from today's logs. Towards the end of the day around 9:39pm EST, there was a subtle crash from the battle chatter (reloading, throwing grenade etc.) The server recovered in 10 seconds. I have patched this with a work around, the proper CoD4x compatible edits are in the works. Should be deployment ready by Sunday. You wouldn't know necessarily notice it unless you were aware of the change. Here are the remaining issues/complaints I hear from folks: My ping is high My ping jumps and goes higher I have lag, hit reg is not working For some players ping is high because they are physically farther from this server, Chicago, not that far from NY but still a little far. The caveat here is that in networking your traffic goes thru different routes. It just so happens that for some folk their traffic experiences too much of a spike when it reaches Chicago. This will indeed introduce some lag, and ping jumps. I can create a ticket with our host provider I am not certain what they will do, but it can be addressed. Often times, it resolves by itself in a few days or maybe a week. Please run the following commands in Windows Command Prompt and send me the results in TEXT format, not screenshots. CTRL+A, then CTRL+C and then CTRL+V on the forums or DM. I will forward the results to NFO and they can sort it out with the data center. tracert 74.91.119.86 (Current C4x server in CHG) tracert 74.91.116.124 (Previous C4x server in NY) By the way the NY server is running the same mod with the same fixes but it doesn't have auto recovery like the Chicago server, and that's why we don't play on it at the moment. Please continue to play on the Chicago server over the weekend. I can further harden the mod against any small lil leaks that may surface. For now it looks good. @Cheyenne @Dukoo @P1nh3ad @Roody @Kisses4You @Ruggerxi

From the very last crash I was able to capture the exact pattern that was causing the slow memory leak, which would cause the server to crash after 5-6 hours of intense gaming. I programmed some bots to hammer those exact player patterns (i.e. killstreaks, perks, connect/disconnect) for days. A few minor leaks were found as a result of this testing and fixes were applied throughout this period. It has been stable for 5 days of continuous bot warfare. Bot testing, however, still cannot capture the full scope of the Idiots playing on the server. Therefore, I would like request some volunteers to play on the COD4x Server (74.91.119.86:28960). The players who usually play around 12-3:00pm EST really stress the mod, something about their perks and killstreak selections. Please react to this post with "I have read this post" if you would like to help. I am thinking this coming Friday or Saturday, Friday is off for me, so I will be around to look at things if needed. As always should things go haywire, we always have our trusty old regular COD4 server. A few things to note. Server is fully automated, on crash or hang, it will auto restart Restart time for a normal restart is less than 5 seconds In case of a hang, the restart time is no more than 30 seconds COD4x server is custom built with latest changes from the COD4x community Steam Auth is disabled and the server behaves like regular COD4 server, this prevents Steam auth related crash (nothing to do with the mod) Server is registered with and listed on COD4x master server Server is located in Chicago, not by choice just what we got at the time of order For Europeans pings will be higher depending on their network routes I have applied the latest updates to the system and performed a full system wide reboot Thank you for your attention to this matter (IYKYK).

We haven't done anything to the shottys or the menus. We don't have the source code for it.

Dear Fellow Gamers, Rugger will send out a PM regarding this as well. After fighting the mod's compatibility issues with CoD4x server for roughly 2 weeks, we have decided to take it off public access. The mod was not written for the newer CoD4x server with stricter memory protections. Whenever the mod leaks memory, the protection unit kills the server. We got it to run stable for up to 6 hours on full load but its basically a ticking time bomb and any user event can be the detonator and cause a reboot. I want to thank you all for your patience and support. The new server brought many advantages and promises of further enhancements but the stability issue has rained on our parade. Therefore, for now the server is only for testing and fixing the stability issues. Sincerely, iBoomBoom

I am not on at the times you are. If you don't have the problems from your original complaint then I'll leave it at that and not waste any more resources.

@Dukoo I contacted our host. Can you run a tracert 74.91.119.86 command in windows shell and paste the results in text format. They said they'll investigate.

The color change is not because of the server by because of the client creating a new profile folder. I had a similar issue with amd gpus on windows 11. It's a client side game config setting. I'll post it here when i am on my PC. I can't say anything regards to the font maybe you can attach a screen shot?

FYI, this happened this morning. This happened because in that brief moment the server wasn't able to auth a client with Steam's network. I have since disabled steam authorization so we don't run in to these issues for the time being. Going from CS_FREE to CS_CONNECTED for BiggieUK>XI<ADM num 0 from: 82.7.234.148:28960<=>74.91.119.86:28960 This program has crashed with signal: Segmentation fault The current Gameversion is: CoD4 X - linux-i386-custom type 'e' build 1222 Jun 8 2026 File is cod4x18_dedrun Hash is: b2e575b23763e28cf28878d1fde59a7e0174eaa60c221b041598a41630f38ec4 ---------- Backtrace ---------- 20: cod4x18_dedrun(Sys_PrintBacktrace+0x31) [0x566fd32b] 19: cod4x18_dedrun(Sys_DumpCrash+0x9d) [0x566fd411] 18: cod4x18_dedrun(Sys_SigHandler+0x24) [0x566fd498] 17: linux-gate.so.1(__kernel_sigreturn+0) [0xf7240590] 16: ./steam_api.so(+0x1ff1e) [0xe120df1e] 15: ./steam_api.so(+0x202b2) [0xe120e2b2] 14: ./steam_api.so(+0x1ada0) [0xe1208da0] 13: ./steam_api.so(+0x1b578) [0xe1209578] 12: cod4x18_dedrun(SV_ConnectSApi+0x29) [0x567501dd] 11: cod4x18_dedrun(SV_SendClientGameState+0x61) [0x56760226] 10: cod4x18_dedrun(SV_ExecuteClientMessage+0x142) [0x567623a2] 9: cod4x18_dedrun(NET_UDPPacketEvent+0x66) [0x56725107] 8: cod4x18_dedrun(NET_Event+0x8c) [0x567799ec] 7: cod4x18_dedrun(NET_Sleep+0x1c9) [0x56779c09] 6: cod4x18_dedrun(SV_Frame+0x2f9) [

When the server hung twice today, I was ready to call it quits with getting this mod to stabilize on CoD4x server. After reviewing the console log from the first hang, I am hopeful this is the final leak in the bucket. I patched two files for the following bugs. - Slow drip leak due to long per player threads starting at every round switch. The more players on the server and the more rounds they play on a single map the leak becomes bigger. Certain maps can exacerbate this condition. It was originally not discovered because it wasn't the focus. - Extra 5th round bug. This happened due to a race condition. Multiple threads were touching the score limit check and on occasion would update the final score even though the score limit was reached. I have added safeguards to prevent this from happening. I run a watchdog service that monitors the game server and if it is hung, it will restart the server. I have enhanced this watchdog to perform deep process state captures before restarting. This way even if there is still some gremlin hiding somewhere bringing out its sneaky head, I will have the full trace of where to find it.

I have patched over 15 mod files with leaky buckets. I am running a stress test with bots. If you happen to see them, thank them for their untiring service. I do need real people to play and try to break it. We are 90% there, I just need some real crazy human gameplay to prove that its all done.