The game cannot assume that the API's behavior is fixed on WINE because anyone can change any of the functions to do something unexpected with a quick patch. Wine is a fully open implementation of Windows APIs on Linux. And aiming is something computers can do in their sleep. If you want to decide win/loss based on things computers can do easily, your game is probably bad. In the end, trusting the client is crazy. There's no wine, no virtualization, no additional software running. My computer is completely normal, down to the device descriptors on my mouse and monitor. Do game companies have MapReduce? I hope so.)Įxecuted well, the developer of the game could do nothing about it maybe I'm really good, or maybe I'm aimbotting. (You also don't want to make your mouse movements statistically different from anyone else's, or it's the server that will pick up on your cheating. I would introduce randomness, "input lag", jitter, and even some misses, so that people looking at the kill cam wouldn't immediately think "aimbot" as they are apt to do whenever they die. If I wanted to aimbot in an FPS, I would just analyze the HDMI output from my computer (via an FPGA) and have it directly create the necessary USB transactions to move my mouse to the target's head. All this anti-cheating stuff is mostly a scam to stop the dumbest of the dumb cheaters and probably collect information from your computer that's useful to advertisers/investors/law enforcement agencies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |