Fraggy

What is the "ExecClientCommand" trick? I don't know about it. Only such stuff I have seen is sharing rcon passwords with clients. Well I assume exec() sends the input to Cbuf_AddText() - everything else would be too risky. And that command text gets executed when server calls next time Cbuf_Execute(), which is after Virtual machine is done with current frame and before next frame Virtual Machine gets called. Should be obvious it does not work as you expect. waittill endframe is inevitable.

You need the base game. The base game needs to be updated to version 1.7. You have to install the updates 1.6 and 1.7. When cod4 1.7 is working you can install cod4x

How are you reading a config? I believe it is something you can not do in cod4 1.7

There is no such feature. Just leave them alone when they think they need to play CoD4 on electronic waste. Would be, annoying to have a server which does limit the fps below the monitor update rate.

Well we need to blacklist the knownduplicated playerids. Your insight will probably not help us too much. The authsystem is flawed. And I was aware about it from the start when I implemented it. I don't have any better solution. A better solution would require a device driver every player has to install. I doubt many are happy to do that, just to get identified on a gameserver. Also I don't wanna bother with creating device drivers either plus I would not get it signed anyway. So I have no proper solution regarding using the computers hardware to identify someone. Having to deal with duplicated serial numbers makes the whole shit even harder.

Yes seems like that. But it is just derived from the playerid. It is discouraged to use the playerid for anything else than onto the banlist. About server owners still doing that we can not help. Can you please go in game, open console, enter $ministatus and make a screenshot you send us? In case $ministatus is blocked then visit another server.

Update: It won't be on this weekend.

You have also restarted your PC? You are also really logged in into Steam?

Your operating system is?

+set dedicated 1 As a commandline option. In case this doesn't work file a bug report.

@Hajas, I have created a brand new profile in CoD4 X and connected to this server: cod4://187.99.241.102:28960 I did not had any issue by connecting and joining. So what should I do now?

Be aware that update to version 19.0 is coming soon, could be at the upcoming weekend, and will be mandatory to all server owners. The upcoming client will probably not be able to connect to older servers due to an incompatibility in the newer Steam authorization procedure. Server's Steam Appid will default to 7940 from now on (has been before 42750) and clients will use the same when a license is available. Server will accept Steam client authorization requests still for appid 42750. However older servers aren't able to accept connections for appid 7940. The pure server requirement will maybe going to be ditched for now or even forever. Make sure your server works with version 18.1.

Well you are lucky enough Valve is not checking and validating every shit on their steam backend servers.

He will be maybe happy with next update. But that requires that no old servers are active anymore, or it will throw steam auth errors.

Screenshot taking failed.

It isn't fixed yet. Just on my PC it is - maybe - fixed.

I can only assume here. I believe this is random and can happen to everyone in theory. I hope this problem will be gone with next update 18.6/19.0 but I am not really sure about this issue (why it happens). Bug should be there in cod4x for years now.

I doubt a reinstall makes it any faster. I know it is annoying. When I implemented it, it did hitch only for 1 second on my old PC. I already considered that as disrupting. Your case seems extreme. Auto-screenshoting like it is done on some servers was not my intention and is not provided by cod4x server by default. But it is in control of the admins and not in my control how they use or misuse this facility.

Reserved

With the update 19.0 there is a significant change rolling in. We will allow only the listing of pure servers ("set sv_pure 1") servers on the masterserver. Now you might think: sv_pure is enabled already! Well this is not really the case. Although the dvar does exist, it does nothing anymore at all since CoD4X17a servers came up. The verification code was just not implemented in them since people bypassed it anyway with an "sv_pure" exploit. However this has led to a state where around ~40% of players play nowadays with tampered .IWD files, because nobody cares, possible due to CoD4X17a's complete removal of this check. But anyway since I see it as important that all players on a server play with the same set of gamefiles and not with "Mario" player textures, I will put that validation back into gameserver with next major version. After some checking of checksums of players on my server, I have noticed some players using unofficial iwd files but they seem to be used by many players however. To lower the impact on players, I would like to know if there are very very popular alternative sets of iwd files players could have downloaded with the CoD4 game from shady sources. (possible they have single player stripped assets or whatever). If there is an alternative set of files, I consider to possible add some files after review to the allowed list - required the assets inside are not changed. In order to prevent that pure servers will lack players (players will usually just join another impure server instead of fixing their game), having a pure server will be a requirement to be listed onto the masterserver. If you know something about matter (edited iwd files) then give your input here please.

There is nothing we can do about it. I can only recommend in general, play onto a server where you don't get screenshoted all the time. I assume his hardware/driver is extremely slow at the procedure which is ongoing on screen capture while other GPUs aren't that slow even when they are older. It does not make a difference when you take a screenshot every 20 minutes or every 3 minutes, just that last variant is more annoying for the players.

In most cases it doesn't need any adjustments.

But this is for sure not how to solve their problem. They can just shutdown the server until their problem is fixed. But instead they fuck up every player's settings. (What is probably not even helping)

Wasn't that error suppressed? Are you at an older build I never released?

What error do you receive when compiling it?