There is some precedent for this method of detection. This is the most likely way Relic caught the people it banned.
Commands can be scanned server-side and these telltales can be detected. Things like setting a specific bit in a command that otherwise wouldn't be set, or detecting an injection or addition to a command instruction that would never come from a clean player's game client. What it can likely detect, however, are telltale modifications to the game data that a maphack would create. That would require client-side anti-cheat, which almost certainly doesn't exist in CoH2.
#Company of heroes 2 cheat skin
What this means is the anti-cheat has no way of detecting the use of third-party programs, such as AutoHotkey, or local third-party modifications, such as sound or skin packs, that only modify local data for one player and don't interact with the core gameplay information that is being sent to the servers. It's simply processing the data received from players. This isn't VAC or Punkbuster, it doesn't look at the processes running on your machine. This means the information they're detecting is information that has to be sent to the battle servers. Of course, nothing I say can be verified, and Relic is likely not going to speak publicly about the details of their anti-cheat solution, but we can make some basic assumptions from what they announced.įirst of all, this is a server-side anti-cheat solution. Just want to clarify a few things, because there are a lot of misconceptions flying around on COH2.ORG.