iboomboom

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.

I used bots to cover the scenarios that could potentially create the leaks. It withstood the beating for 1 hour then we had people play for 3 hours. It crashed once early morning when people started joining in then quickly self recovered. I was able to use that to patch the new leak source. Synthetic testing can only do so much, real life in-game interactions brings out previously undiscovered behaviors.

It's patched...

Thanks for reporting. There's a hole that needs to be plugged, I discovered it this morning but I had to leave for work. Will patch the mod when I get home. cod4x doesn't tolerate leaky mods so it just bitches about it.

On a related note, those who have IPv6 enabled. If your ISP has separate routes for IPv6, cod4x support IPv6. I had our host provision an IP6 address. Try it. # >XI< MW2 Freezetag C4x IPv6 address # Type this line in your game console /connect [2605:6ac0:2b:0:216:3eff:fe6b:9344]:28960

Folks, Here's an update. After a very long Sunday, I'd like to say that I fixed the mod induced instability on the CoD4x server. It was caused by the use of poison perk, repeated freeze/unfreeze, the resources were not freed when round switched and it kept corrupting the memory. It was our mod that had to be made CoD4x compatible in the end. This is a weakness, in my opinion, of CoD4x's revised memory management that it cannot handle bad mod scripting hence forth crashing the server. For the technically inclined. After 4 hours of running, and folks playing on the server. I dumped the process core, looked at the memory area that was getting corrupted had AI perform 2 audits of the allocators and their status, its CLEAN. It's FREAKING CLEAN now. Please play on the new COD4x server [ 74.91.119.86:28960 ] . If it hangs for some reason, I want it to stay in that state until I get to it. Therefore, should that happen proceed to the regular cod server. The most exciting thing of it all is that, the server is listed on COD4x master servers and we are getting new visitors. It would be pretty amazing to see the server grow.

When I logged in to your computer, you had multiple installations. Your levels your hours are still there. You need to backup all the profile folders. Then delete all the installation and copies of the game. then try each saved profile folder at a time. Once you have what you had. Install Cod4xclient again. it will restore it.

Folks, I applied some fixes to the mod. Here's what will help determine if these fixes worked. - Equip the venom perk and get poison KILLS, the victim has to bleed out from the poison, not heal. - Freeze/defrost + map rotation

Not entirely sure but I suspect its their subdomain where you fetch the servers list from their master server?

Once we've sorted the memory bug. We will focus on scaling the concurrent players supported by the mod.

Yeah, I don't know why they flag it. Maybe it's the weird domain extension. 4 years ago when someone suggested I try cod 4x I also stopped to to think and didn't. Then a little later I did and well we are here now.

You made me spin a new server build. All because you had network issues. I am not mad. I just want to have some space from you.

Folks, On Sunday 06/07 play primarily on the regular COD4 server. I am going to be doing some maintenance work on the server. You are welcome to stop to help test stuff. I will be in TS and in the server when I am doing stuff. Thank you for your support.

Excellent this confirms my suspicion. Your route to NewYork servers gives you 90'ish ping. Your route to Chicago server gives you almost double the ping. It's not a mod issue. It's your ISP's route to that specific data center. These two are cod4x servers and your ping to .86 (current c4x server) is almost double. Can you run a route trace now to all 3 servers?

Can you run this on your windows machine and send me your results. # Run all 3 one by one and press Control-C to stop ping -t 74.91.119.86 ping -t 74.91.116.124 ping -t 162.248.95.178 @Icequeen you too, also, you are on WiFi? You play on WiFi?

old server is in NY, new server is in chicago.

@Dukoo What's your ping and how bad is your lag if you connect to this server ? This was the first C4x server we put that we started having hard hang issues with. This has the exact same code as the other one and if you don't have issues with this but the other one. Then the problem is the network not the servers. In fact, its a big clue to some people having weird pings.

If for whatever reason his ISP is routing his ( @Dukoo's) traffic through LA that would explain the lag only he's experiencing. @Icequeen might also have the same thing happening. Can you specify custom DNS server in your router? Try Google's 8.8.8.8 or Cloudfare's 1.1.1.1

I had to delete one of my maps because it was crashing my game. Can you delete this map from your local game folder? i ran thru this entire rotation last night to make sure no maps crashed the server. I found one and removed it.