Talk:2019 Spring Update/@comment-36912561-20190604172957/@comment-34918040-20190606070658

@ SunnyTomato:

This has nothing to do with iOS. GL will not tell you the exact reason why you were put on the cheaterboard. They know very well that their algorithm cannot be perfect (already by definition), but CC is instructed to not provide any information about it. If they did, this would mean a flood of mails and they would have to admit that their programming is (at best) sub-optimal. And as the CC's only job is to keep customers away, things are like they are.

Here's some more reasons for an algorithm to assume that you cheat:
 * Your internet connection can have hiccups which causes MP race logs to lack some parts of your race. The result is a an improbable race time or race path.
 * As every OS tends to self-destruct after a certain time (yes, iOS, too), some files of the game can be corrupted, resulting in false checksums. False checksums indicate that files have been tampered with, and the almighty algorithm says: You cheater!
 * Some apps (like the ES File Exlorer for Android) log each and every accessed file of the system. While this is meant to be a good control feature, it causes time lags when Asphalt wants to access important game files. Time lags mean that a third-party app interferes with Asphalt which causes the Almighty Spaghetti Monster to let a flood of Carbonara rain down on you. By the way, CarBonara is the actual correct word for CB, not cheaterboard.
 * many more reasons which the limited imagination of CC agents is unable to seize (please remember, their imagination is limited by order of GL, not by nature).

See what I'm aiming at? Detection algorithms are almost surely imperfect. Always. GL just don't want to admit it to keep trouble (and work) away. Getting a new ride CAN cause some irregularities because of incorrect programming, but it's easier to call customers cheaters than to work on better programming.