"Sort Saves into Folders by Content Directory" not working in Retroarch

[emperorbohe]

Hi!

I’ve enabled Retroarch Freedom Mode and was hoping to sort my game saves by content directory. This is mainly to keep continuity with my other devices and SyncThing, as different cores may be used on other devices.

I’ve turned on the “Sort Saves into Folders by Content Directory” option in my main Retroarch config file, and the setting does stay enabled. However, it seems that my saves are just going into the save/file directory and are not being put into any subfolders at all (despite the content directory option being enabled). Is there anyway to have them save into folders by content directory? I don’t want to sort by core (due to differences between devices), and I don’t want them all to save in a single directory (in-case there are games with identical names on different platforms).

Thanks!

[arctic-rocinante]

Something to be aware of is that changing those options won’t automatically move exiting saves (you need to do that manually). It only affects where new ones go.

So just to confirm, have you tried making a new save and seeing where it ends up? (vs. just looking at existing ones.)

[emperorbohe]

Yeah, new saves are being created in the general save/file folder and not in the folders named after the content directory

[icecode7]

I can confirm the same behavior on a fresh install of Loose Goose on the rg40xxv. The option to change this has three dots instead of a yes or no. Im going to try installing an older version of goose and updating instead.

[icecode7]

I want to say this is kind of an important feature as its how I used to sync my saves with a Batocera install on an RPi4 and my TV… Batocera is also locked down, and unfortunately uses different save path defaults. It used to be easier to edit MuOS and it seems this is a MuOS bug. No reason I should be able to edit this function. It wasnt three dots before…

[emperorbohe]

Forgot to mention that I am also using a RG40XXV

[xonglebongle]

Just because we do something differently from how you want to use it, then changing defaults and concluding it “must be a bug” is not a valid assumption.

MustardOS is intentionally more locked down than it used to be, and that is a deliberate design decision, not a regression.

Save paths, sync behaviour, and what is or isn’t user editable are defined to support consistency and stability across supported devices. We definitely don’t take into consideration other systems because we are our own thing.

Batocera using different defaults or being locked down in its own way does not imply what we are doing is incorrect or broken. If your current setup relies on modifying internal paths, that falls outside supported usage.

You are welcome to request a feature or explain a use case, but framing a design choice as a bug because it no longer matches a custom setup is inaccurate.