- Joined
- Sep 21, 2016
- Messages
- 357
- Reaction score
- 546
- First Language
- English
- Primarily Uses
- RMMV
Alrighty, so first off, I apologize if I'm posting this on the wrong board. I initially thought about posting this to the deployment board, but it's not an issue with deployment specifically. I also thought about posting in the support board, but I don't expect anyone to have any information on this problem, so my goal is to get as much attention on the issue as I can. Still, please move the thread if necessary.
With that out of the way: I currently have 6 commercial games, all of which are available on Steam and the Google Play Store. The Play Store's been a good source of income for me despite the issues I've had to resolve, mainly with performance and UI.
That said, there's one major issue I have no solution for involving save files. I'll start off by linking screenshots to three users who reported the problem:



The theme across these users is this: when I release an update for one game, the save files for all of my other games become seemingly unavailable.
The first idea to come to mind might be that updating one game overwrites the save files for my other games, but this doesn't seem to be the case. Updating a game whose save file was altered will seemingly restore the original save file (at the cost of all the others, of course). This shouldn't be possible if the save file was completely over-written or erased.
Two of my games (including Roguelite 2, my latest release) use Yanfly's Save Core, which grants the save files a different naming structure. Unfortunately this didn't solve the problem, as you can see with the 2nd screenshot above - after I released an update for Roguelite 2, that user lost their save data for all five of my other games.
I don't believe this happens on all devices. I happened to ask another user (different from the three pictured above) to check their save files after they downloaded an update. Their save files were thankfully unaffected. I would assume that, if every device had the same problem, I'd be flooded with email complaints and 1-star reviews, but I've only received three reports and a single 1-star review so far. (On an unrelated note: I am *very* thankful to the three above users, who were all much more understanding than I expected anyone to be after losing their save files. They all declined my offer to issue refunds.)
I spent an entire day trying to replicate the problem myself. I installed all of my games to one device and made save files for each one. After checking each game, the save files co-existed just fine. I then updated one of my games on the device. Each game was still unaffected. I tried a different device, trying different combinations of saving games to different slots, updating different games, etc. and had no luck replicating the issue.
This issue has been very frustrating for me--both because I have no idea how to solve it, and in a way, even if I did, I couldn't. This is because every update I release for a game (even one that could potentially fix that specific games' save files) runs the risk of altering the files for every other RPGMaker game installed on the same device.
And note that I said "any RPGMaker game" rather than just my games--because I assume that, unless every other RPGMaker game on Android uses a completely different save system, any update for those games could likely interfere with my games' save files, and vice versa.
I will add that, despite this long post, I'm not 100% sure that the problem is connected to game updates. Any number of things could alter a users' save files - uninstalling and reinstalling, backing up an older save to a different device, factory resets, who knows. The files for apps and programs on Android are completely hidden without rooting the device. I tried rooting four devices to find out exactly where the apps and saves are installed to, but was unsuccessful.
Though I hope anyone here with more knowledge than me knows about this issue and knows how to solve it, I've made this post more as a PSA to anyone deploying their games to the Google Play Store, specifically if you have more than one: releasing an update for one game *might* interfere with the save files for the other.
If you deploy your games before this issue is resolved, then it's likely too late to fix it, as I believe the case is for myself and my six games. I've been forced to discontinue updates for my games, and for my next release, will likely have to do extensive bug-testing on its Steam version before releasing it as-is, with no future updates ever, on the Play Store.
With that out of the way: I currently have 6 commercial games, all of which are available on Steam and the Google Play Store. The Play Store's been a good source of income for me despite the issues I've had to resolve, mainly with performance and UI.
That said, there's one major issue I have no solution for involving save files. I'll start off by linking screenshots to three users who reported the problem:



The theme across these users is this: when I release an update for one game, the save files for all of my other games become seemingly unavailable.
The first idea to come to mind might be that updating one game overwrites the save files for my other games, but this doesn't seem to be the case. Updating a game whose save file was altered will seemingly restore the original save file (at the cost of all the others, of course). This shouldn't be possible if the save file was completely over-written or erased.
Two of my games (including Roguelite 2, my latest release) use Yanfly's Save Core, which grants the save files a different naming structure. Unfortunately this didn't solve the problem, as you can see with the 2nd screenshot above - after I released an update for Roguelite 2, that user lost their save data for all five of my other games.
I don't believe this happens on all devices. I happened to ask another user (different from the three pictured above) to check their save files after they downloaded an update. Their save files were thankfully unaffected. I would assume that, if every device had the same problem, I'd be flooded with email complaints and 1-star reviews, but I've only received three reports and a single 1-star review so far. (On an unrelated note: I am *very* thankful to the three above users, who were all much more understanding than I expected anyone to be after losing their save files. They all declined my offer to issue refunds.)
I spent an entire day trying to replicate the problem myself. I installed all of my games to one device and made save files for each one. After checking each game, the save files co-existed just fine. I then updated one of my games on the device. Each game was still unaffected. I tried a different device, trying different combinations of saving games to different slots, updating different games, etc. and had no luck replicating the issue.
This issue has been very frustrating for me--both because I have no idea how to solve it, and in a way, even if I did, I couldn't. This is because every update I release for a game (even one that could potentially fix that specific games' save files) runs the risk of altering the files for every other RPGMaker game installed on the same device.
And note that I said "any RPGMaker game" rather than just my games--because I assume that, unless every other RPGMaker game on Android uses a completely different save system, any update for those games could likely interfere with my games' save files, and vice versa.
I will add that, despite this long post, I'm not 100% sure that the problem is connected to game updates. Any number of things could alter a users' save files - uninstalling and reinstalling, backing up an older save to a different device, factory resets, who knows. The files for apps and programs on Android are completely hidden without rooting the device. I tried rooting four devices to find out exactly where the apps and saves are installed to, but was unsuccessful.
Though I hope anyone here with more knowledge than me knows about this issue and knows how to solve it, I've made this post more as a PSA to anyone deploying their games to the Google Play Store, specifically if you have more than one: releasing an update for one game *might* interfere with the save files for the other.
If you deploy your games before this issue is resolved, then it's likely too late to fix it, as I believe the case is for myself and my six games. I've been forced to discontinue updates for my games, and for my next release, will likely have to do extensive bug-testing on its Steam version before releasing it as-is, with no future updates ever, on the Play Store.


