Core configuration is a little tricky to keep updated, especially if you’re having trouble settling on a aesthetically pleasing directory hierarchy. AFAIK, the configuration is in /run/muos/storage/info/core, so the second you move your ROMs, the “link” disappears and you have to pick a core for that directory.
I suggest a feature that allows for “suggested defaults” in the form of a .core.cfg and .core.gov (or similar), dropped anywhere in the ROMs structure. Any manual changes would override this, and clearing the core configuration would effectively fall back to the suggested defaults in ROMs.
Side note: For this to work, the “directory style” core and gov configs should be inherited in the directory hierarchy.
This is a very interesting idea however muOS does not, and will not, store extra data inside the content / ROMS folder. This is a deliberate and permanent design choice. The folder structure is meant to remain clean and portable, and the friendly folder system is how we balance that with automatic core / system assignment.
Yes, it may come with some quirks, but that’s the trade off we’ve chosen over implementing a static or metadata driven directory system that some folk might be used to with other systems.
So while we do see where you are coming from, this particular feature, including the idea of .core.cfg or .core.gov files in the ROMs structure, is not something we’ll be pursuing hope you understand.
Gotcha! Just to make it absolutely clear, the .core.* files dropped in the ROM directories were NOT supposed to written by muOS, but created/copied over along with the ROM files. Anyway, I see your point
