Board Thread:Game Discussion/@comment-38518555-20200211235621/@comment-38518555-20200212222653

DrestinBlack wrote:

Here's an idea to pass along, in the broad strokes: game input is captured at 10hz. That means, 10 times per second, the game saves what the player is doing. That data is what's saved to produce replay files (along with car stats at start of race) plus the total race time; a value that can be hacked using a memory search&replace tool. We've seen that a race can report that it was run at 60 seconds but when we play back the Replay we witness a race that is, say, actually 90s long. That means that there are 900 inputs recorded, but there should only be 600. So, a sanity check could be performed against the replay data. Are there only as many inputs as expected for the recorded race time? If there are more, the data is invalid.

A 60 second race file should only contain 600 inputs. Any other number and there is a mismatch, reject the results. And that's how we stop that form of TT hacking. Sanity checks should also be performed to ensure the right track and only the right cars were used, too,

(Stat/fame/currency hacking: different topic) Not a coder, but this^ seems very reasonable, sensible and doable. All cheating will never be stopped in anything. ME7 points out the McLaren involvement in competitions. That is a major thing to protect. Cheats will never win that competition, simply because they know they will be exposed and embarrassed at how ordinary they are on a level playing field.

FM can automatically detect things about our accounts and our activity. But yet, still cannot detect changes being pushed into its own clients/servers? For hacked times to stick must mean some form of injection into servers/clients. Not a coder...just guessin'