Board Thread:Game Discussion/@comment-37632463-20190814072548/@comment-34556626-20190904063800

DrestinBlack wrote: MatteoPRR3 wrote: HULK7WG wrote: SeedSpeed wrote: User MatteoPRR3 is using a game function of cloud and save as given within the game. I don't think it's fair to accuse and point as exploiter just out of the bag like this. 3 words mate. "not as intended" No. If it was so, then Drives would not be restored. Restoring Drives on Cloud Restore is not a glitch, nor something the programmers simply forgot: it is a precise choice. If it was not, then there would also be no point in keeping Drives recharge timer alive: also recharge timer should be "restored" (down to zero, for example) when cloud restoring. It is kept going on, instead. Therefore restoring Drives must be a choice, and then there is no exploitation in my behaviour. Think about it: if you can avoid the limitations of drive just by doing cloud restores - why bother with it at all. What is the purpose of drive if you can just ignore it? Do you think they create something, something that costs money to early recharage, something with a count down to restore function, omething so important it's on the main screen - that no one cares about whatsoever because it does absolutely nothing. Drive becomes an utter waste of time and space and programming because you can just ignore it. THAT is what you believe their precise choice was? Let's make something that can effortlessly be worked around and therefore does absolutely nothing. ... rrriiiggghhhtttt.... Matt has explicitly stated on Reddit that using Cloud Save to restore Drive is not using the function as it is meant to be used. He said Cloud Save is only for transferring saves from one device to another. So yes, using Cloud Save to restore Drive is an exploit and you can be banned for it. Just that they haven't banned anyone until now. But it doesn't mean you are correct in using the exploit.