st0rm

Members
  • Content Count

    60
  • Joined

  • Last visited

  • Days Won

    2

st0rm last won the day on July 10

st0rm had the most liked content!

Community Reputation

2 Neutral

About st0rm

  • Rank
    Member

Converted

  • Site
    http://namelessnoobs.com

Recent Profile Visitors

713 profile views
  1. @Airitech I ran my servers on windows 2016 server. I just gave up and got sick of people complaining about hit reg. The second I got them running on linux is the last time I heard of a complaint. The thing that gets me that sometimes it would be perfectly fine and then the next map it would be awful.
  2. Hey, So basically after a month of messing with stuff on windows and the hit detection. Sometimes it would be good and awful the other times. I gave up and just reinstalled my server to Linux and have no more hit detection issues. On a side note if you compile the server from GitHub master source now. A message will keep spamming in server chat that the server is out of date even tho I was using the newest source.
  3. Hey, Seems the url is down for people to download the files when the client can't auto install cod4x. https://cod4x.me/clupdate/
  4. Hey, I will be trying this over the weekend and report back. I have posted the compiled version if any other windows users want to help out. cod4x18_dedrun.exe
  5. Hey Fraggy, Does this fix also apply to us windows guys. Since I seen the commits were pointed to unix.
  6. Tired with g_antilag 0 and seems to be an issue still. As far as I know people started to complain after we switched from 2055 to 983. I have the server to automatically restart everyday to rule out that factor and it has not helped. At first I though it was hardware too. (i7 4790K, 16GB Ram and 256GB SDD). But I run other servers on the machine and it's only the cod4 that people complain about.
  7. Hey, I run 5 servers on a windows 2008 dedicated server. I have recently updated my servers to the new dev branch 983 from 2055. After the update players started complaining about the shots registration begin off on the server. Is there anything I can do to help debug the issue? Or has anyone had the same or similar issue after they updated? Thanks, st0rm
  8. st0rm

    Qconsole Spam

    Yeah its weird it only happened once.
  9. st0rm

    Qconsole Spam

    Seems like it is cause the reverse dns returns cod4master.cod4x.me But 963 build seems to be stable so will be moving all our servers to it.
  10. st0rm

    Qconsole Spam

    Hey, I updated one our servers to test 17.8 server branch. Seems the qconsole logs everything now. This might be a problem in the long run since the file will get pretty big. cmd 366: 1326850: d 0 \sv_maxclients\26\version\CoD4 X - win_mingw-x86 build 963 Mar 12 2019\shortversion\-\build\963\branch\dev_newarch\revision\abf470469e8ff24d65cc5d28ab804b8621d43c9e\_CoD4 X Site\http://cod4x.me\protocol\17\sv_privateClients\2\sv_hostname\^3NamelessNoobs ^7FFA High XP\sv_minPing\0\sv_maxPing\250\sv_disableClientConsole\0\sv_voice\0\g_mapStartTime\Sat Mar 16 14:26:45 2019\uptime\22 minutes\g_gametype\dm\mapname\mp_shipment\sv_maxRate\25000\sv_floodprotect\1\sv_pure\1\_Admin\st0rm\_Email\\_Website\www.namelessnoobs.com\_Location\USA!!!USA!!!\g_compassShowEnemies\0\gamename\Call of Duty 4 cmd 367: 1326950: I 5 750 cmd 368: 1326950: I 7 1250 cmd 369: 1330450: b 7 0 0 1 7 1375 34 3 0 11 0 2 1000 57 9 1 8 0 5 750 0 6 1 6 0 8 625 155 2 1 5 0 4 375 51 10 0 3 0 9 125 109 3 0 1 0 3 0 37 0 0 0 0 cmd 370: 1332900: N 2311 21238 cmd 371: 1332900: N 2314 65848 cmd 372: 1333850: a 91 cmd 373: 1333850: C 37 cmd 374: 1339900: N 2311 21246 cmd 375: 1339900: N 2314 65856 cmd 376: 1343150: N 2305 1492 cmd 377: 1343150: N 2315 1439 cmd 378: 1345850: d 1363 RU_1mc_uavrecon cmd 379: 1347900: N 2311 21254 cmd 380: 1347900: N 2314 65864 cmd 381: 1352200: a 91 cmd 382: 1352200: C 37 cmd 383: 1355750: N 2305 1493 cmd 384: 1355750: N 2315 1438 cmd 385: 1355900: N 2311 21262 cmd 386: 1355900: N 2314 65872 cmd 387: 1363900: N 2311 21270 cmd 388: 1363900: N 2314 65880 cmd 389: 1364800: a 91 cmd 390: 1364800: C 37 cmd 391: 1371900: N 2311 21278 cmd 392: 1371900: N 2314 65888 cmd 393: 1378400: d 1364 UK_1mc_ouruavonline cmd 394: 1379900: N 2311 21286 cmd 395: 1379900: N 2314 65896 cmd 396: 1382350: N 2305 1494 cmd 397: 1382350: N 2315 1437 cmd 398: 1387900: N 2311 21294 cmd 399: 1387900: N 2314 65904 cmd 400: 1389850: d 0 \sv_maxclients\26\version\CoD4 X - win_mingw-x86 build 963 Mar 12 2019\shortversion\-\build\963\branch\dev_newarch\revision\abf470469e8ff24d65cc5d28ab804b8621d43c9e\_CoD4 X Site\http://cod4x.me\protocol\17\sv_privateClients\2\sv_hostname\^3NamelessNoobs ^7FFA High XP\sv_minPing\0\sv_maxPing\250\sv_disableClientConsole\0\sv_voice\0\g_mapStartTime\Sat Mar 16 14:26:45 2019\uptime\23 minutes\g_gametype\dm\mapname\mp_shipment\sv_maxRate\25000\sv_floodprotect\1\sv_pure\1\_Admin\st0rm\_Email\\_Website\www.namelessnoobs.com\_Location\USA!!!USA!!!\g_compassShowEnemies\0\gamename\Call of Duty 4 cmd 401: 1390250: b 8 0 0 1 7 1875 32 7 1 15 0 2 1625 57 12 0 13 0 4 1125 52 14 0 9 0 8 875 143 7 0 7 0 5 750 999 9 1 6 0 9 625 107 6 0 5 0 6 500 61 3 1 4 0 3 0 37 0 0 0 0 cmd 402: 1391400: a 91 cmd 403: 1391400: C 37 cmd 404: 1395900: N 2311 21302 cmd 405: 1395900: N 2314 65912 cmd 406: 1399400: N 2305 1495 cmd 407: 1399400: N 2315 1436 cmd 408: 1403900: N 2311 21310 cmd 409: 1403900: N 2314 65920 cmd 410: 1408450: a 91 cmd 411: 1408450: C 37 cmd 412: 1410150: N 2305 1496 cmd 413: 1410150: N 2315 1435 cmd 414: 1411900: N 2311 21318 cmd 415: 1411900: N 2314 65928 cmd 416: 1412300: b 8 0 0 1 7 2125 34 9 1 17 0 2 2000 56 14 1 16 0 4 1625 53 15 0 13 0 8 1000 151 9 0 8 0 9 750 110 8 1 6 0 5 750 999 11 1 6 0 6 625 58 4 0 5 0 3 0 35 0 0 0 0 cmd 417: 1419200: a 91 cmd 418: 1419200: C 37 cmd 419: 1419900: N 2311 21326 cmd 420: 1419900: N 2314 65936 cmd 421: 1422450: N 2305 1497 cmd 422: 1422450: N 2315 1434 cmd 423: 1422650: K 2 cmd 424: 1425900: N 2311 21332 cmd 425: 1425900: N 2314 65942 cmd 426: 1430800: b 7 0 0 1 7 2375 34 9 0 19 0 4 1750 53 17 0 14 0 8 1125 155 10 0 9 0 6 875 60 5 1 7 0 9 750 107 9 0 6 0 5 750 999 12 1 6 0 3 0 36 0 0 0 0 cmd 427: 1431500: a 91 cmd 428: 1431500: C 37 cmd 429: 1432900: N 2311 21338 cmd 430: 1432900: N 2314 65948 cmd 431: 1439900: N 2311 21346 cmd 432: 1439900: N 2314 65956 cmd 433: 1442350: d 0 \sv_maxclients\26\version\CoD4 X - win_mingw-x86 build 963 Mar 12 2019\shortversion\-\build\963\branch\dev_newarch\revision\abf470469e8ff24d65cc5d28ab804b8621d43c9e\_CoD4 X Site\http://cod4x.me\protocol\17\sv_privateClients\2\sv_hostname\^3NamelessNoobs ^7FFA High XP\sv_minPing\0\sv_maxPing\250\sv_disableClientConsole\0\sv_voice\0\g_mapStartTime\Sat Mar 16 14:26:45 2019\uptime\24 minutes\g_gametype\dm\mapname\mp_shipment\sv_maxRate\25000\sv_floodprotect\1\sv_pure\1\_Admin\st0rm\_Email\\_Website\www.namelessnoobs.com\_Location\USA!!!USA!!!\g_compassShowEnemies\0\gamename\Call of Duty 4 cmd 434: 1442550: N 2305 1498 cmd 435: 1290900: N 2311 21196 cmd 436: 1442550: N 2315 1433 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 bad connectionless packet from 188.165.57.239:27953 Also get bad connectionless from the cod4x master.
  11. Seems to have fixed it. The only hitch warning I see now is when server gets registered on the master at server start up.👍
  12. Hey, Is there a fix for the b3hide since it uses it's own status command. Thanks.
  13. Add this to your startup command line +set sv_showasranked 1 +set modstats 0
  14. Oh cool good to know I might actually to update our server to the newest build again. Hopefully the random crashing will be gone.