The general pratice in the console space for anti cheat was to rely on the consoles inability to run modified code via DRM. A game on the PC could be over run b

The general pratice in the console space for anti cheat was to rely on the consoles inability to run modified code via DRM. A game on the PC could be over run by cheaters but have very few issues on console, until the console is broken. These days crossplay removes that secuirty blanket (After all, thats all it was, a secuirty blanket). The 360 is a nice example, until the DVD-Rom firmware mod was out there things were pretty peaceful in the online gaming space (Excluding people using external manipulation such as network manipulation or exploiting bugs in the code allowing them to get into out-of-bounds areas. Things like aim bots just wasn't a thing). Once the DRM was bypassed starting with the DVD-Rom mod people quickly found that often the only file that was checked for modifications was the .xex file that the console executed. Many games would just have their configs in scripts that could just be easily edited, burnt onto a fresh disk and the game would just happily use those edited configs because the games were pretty much client authoritative esp thanks to the peer to peer nature most games used. To get around Tilte Updates / Server side game configs people would use scripts which were still loaded off disk to change the TU/server side loaded config values back to what ever they wanted after the game had loaded/fetched them. The JTAG & Reset glitch hacks gave cheats more freedom as a) they didn't have to burn a new DVD with every change they wanted to make b) gave them even more freedom on the system to change things as they were basically "root". My point being that many console games at the time used the consoles DRM as their anti-cheat, once one was broken, so was the other.