That's not how it works for Retail RetroArch. It updates like a regular Xbox game (assuming the current listing is still up, this gets delisted periodically all the time.) so the LocalState folder is left intact. Only ways it can be deleted is if you manually uninstall RetroArch, manually delete the folder, or factory reset. (either option, doesn't matter if you keep games and apps.)
so if a new update is released, update instead of uninstalling, then installing the new version?
If an update is released, then let it update like a regular game that received a patch. If the app is delisted, then you will have to install the newer listing (if you want to be up to date at least) and manually transfer your files from an app to the other. It might be RetroArch still, but in that scenario you're technically dealing with two different apps, so the LocalState folders aren't shared.
That's what I figured. What would happen if you out the Retroarch files in a folder on the root of Q or S? I mean it's like 40,000 files, so it takes over an hour to update.
The root of the S Folder is completely inaccessible in Retail, so that's impossible. As for the root of the Q Drive, it's not a good idea since unless you are using a NTFS formatted drive with the correct permissions, the files won't even be allowed to be placed outside of the folder and still work correctly. Even if you change the directories in RetroArch itself. You need a USB drive for that to be viable, and even then not everything can be stored outside of the LocalState folder or the S Folder. retroarch.cfg is stuck to LocalState, while cores don't work outside of the default S Drive directory period.
Reboot the system and see if an update pops up. Also, RetroArch on Retail (Gamr13's version anyway) is based on nightly builds, so stable builds really aren't relevant here.
It's already happened a lot mate. This post really isn't changing anything because Retail RetroArch has been a thing for two years now. It's always taken down after around two weeks and re-uploaded, it's a game of cat and mouse that has lasted a long time. Unless Gamr13 decides to stop uploading builds, that really won't change.
The apps are usually re-uploaded a few hours after a take down. When it's re-uploaded, you just download it as if it were the first time you downloaded it.
maybe the new name is to fool microsoft. it also has a different developer name. it is the new update, I guess nightly build. I'm uploading the files now. right now, I have both that and the original retroarch installed. I tried to do a cut and paste from both directories, but there's no way to cut the content, only copy it.
I dunno, name changes really haven't done anything to combat what is mostly an automated process in the past. And a different developer name just means that this type of takedown was that Microsoft banned the developer account that hosted the apps. So, a new dummy account is made. The other type of takedown is simply delisting the apps and nothing more.
No, that's a common misconception and a source of misinformation. So I want to be very clear about this: THE USER IS NEVER AT RISK OF BEING BANNED FOR SIMPLY DOWNLOADING AND USING THESE APPS. The only one at risk is the developer account hosting said apps since they are the ones who are breaking the Store's ToS. That's why there hasn't been a single banned user for using this in 2 years. Incidentally, the developer account is a Partner Center account, which is not related to an Xbox Live account in the slightest.
The location inside the Q Drive where the other LocalState folders for the apps are located. If you're using Durango FTP, this translates to LOCALFOLDER.
Local state is the only location we can ftp to? I updated my Durango ftp as well, so it will have to be something that's permanent.
