Originally Posted by
__Xen0
Are you really that fucking stupid? Not only your bad english makes me sick but also the bullshit you write on MPGH. Some people are trying to learn here and you just keep posting your wrong shit.
"Forzen: 4": I am not sure what you mean by that, but I assume it means frozen (Correct me if I am wrong). 4 is the flag for what is called "NoTarget".
"Noclip: 1-2(Diffrent noclip mode)": They are not different no clip modes. 1 is actual no clip and 2 is UFO mode, which is kinda weird in MW2 and not like the UFO mode most people know.
But now to the most stupid part of your post. "You can get player state from before timer ends and after it ends."
before timer ends and after it ends lol. Sorry, back on topic:
That is not the player state. There is an actual struct called player state (playerState_s). The value that gives a player no spread is a flag in the glient_s structure. Have you ever used IDA before? You should check it out. ent->client->flags (with ent being a gentity_s, client a gclient_s and flags an int) is what determines if a player has noclip or whatever.
Now to clear up the confusion about why no clip is given to a "random" player when you are in multiplayer I will explain why that happens.
The address found by that one guy is for the player with client number 0. When you are hosting your own private match you will most likely be client 0 (or even always?) and thus it will work just fine. But in multiplayer, somebody else might be client 0, even if you are the host. The fix for this would be finding out your client id, then getting your gentity_s, then your gclient_s and then changing your flags. The bad way, which still works would be finding the addresses for all clients with cheat engine. If anyone is interested in it let me know, I dug around in IDA for a while and found the struct offset for the client pointer and the offset of the flags.
Also, the your joke at the end with "replayed" was funny, thanks for the good laugh!