-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passing a round after DoubleCashMode is true resets the save #17
Comments
on second thought i should try this with a non steam account save brb |
This issue is outside of the scope of this project, the save file packing works; this is not a problem with monke. Closing. |
Yeah, BTD6 automatically revert to a previous version of the saves whenever you edit stuff with the unpacker/packer. |
Does it do this if you don’t edit the save file at all when repacking? I’m thinking there must be some extra protection on micro transaction stuff…. I haven’t had this issue. |
naw i just tried with a non ninja kiwi account, theres no extra protection its just cloud saves lol Did what MGJerry mentioned, I now have double cash mode without paying a dime on my main account. I'm not even flagged lol. |
Did this accidentally a few times, most of the time they stay the same size as when they are repacked (meaning the game assume nothing is out of the ordinary), while very rarely they are reverted to cloud saves. And from what I've seen, saves are only reverted when they are linked to a ninjakiwi account, sometimes follow by a flag to the accounts after that. And the save usually only get revert if you add too much monkey money, xp & user rank,... There's probably a limit/threshold to how much a resource you can gain between checks, a lot of online game have this to prevent hacking in stuff (ex. from my past: The Battle Cats) And like @Xioverze mentions above, non-ninjakiwi linked saves doesn't even get reverted, you can just use the save you just repacked and it works fine. |
The video that shows what im experiencing
https://streamable.com/sa1il5
The text was updated successfully, but these errors were encountered: