Fraggy

Administrators
  • Content Count

    1052
  • Joined

  • Last visited

  • Days Won

    44

Fraggy last won the day on July 6

Fraggy had the most liked content!

Community Reputation

86 Excellent

About Fraggy

  • Rank
    CoD4X developer

Recent Profile Visitors

4096 profile views
  1. I will just use numbers here: #1: The client does acknowledge a snapshot which is already too old and discarded by the server because of its age. This means the server is not able to compare that old snapshot with the current gamestate. Server prints that message and sends a full snapshot instead just the differences to a older snapshot. (Reason is poor connection or client was frozen.) #2: Someone was sending junk to your server. A connection-less message server does not understand. #3: Was kept in from development/glitch hunting. Can be ignored. Just says how much bytes was received on reliable message channel. #4: I can only assume. Probably you are running out of space for constant config strings. Maybe too much script-menu or hud stuff. #5: Also I can only assume. Probably it is a hidden entity players don't see. So this message shows. No clue why a player can be non broadcasting. Is he dead? #6: Player has only CoD4 1.7 running which equals to protocol 6. Player needs the cod4x update. Then this message shows.
  2. If you manage to find or make a static code translator for all the asm code then you can do it maybe for ASM32 code. Otherwise there is no way beside decompiling everything remaining.
  3. Are you the only one with that issues on this specific servers? Servers you join must immediately request a screenshot. Maybe the logic is glitching when this happens in this way.
  4. +set sv_maxclients 32 into startup line
  5. I assume the server you played on has messed with your config before kicking you. Best thing is to reset your config. It is in %localappdata%\callofduty4mw\player Look in that folder for .cfg files and erase them. Otherwise you can try to make a new userprofile.
  6. You have to edit the default scripts.
  7. I think your rcontool is not supposed to generate files. No? Only file which can remember runtime settings is q3config_server.cfg but you have to exec it from command-line. And it will only remember stuff set with the "seta" command.
  8. But it is for single player only. Also I am not sure if we want support what is shown on the screenshots. Because you see too much from left and right side.
  9. I believe this is not the right forum.
  10. code_pre_gfx_mp.ff File does not exist in default cod4. No idea what is wrong
  11. He gets that error saying stats are reset?
  12. Then it has to come from your shared libraries. ld-linux or linux-gate or libc6 or whatever is probably broken on your system. So I assume you can not run any x86 programs.
  13. No idea then. But its weird indeed.