What is the line playlist_cores = for in the retroarch.cfg?

So im doing some house cleaning, and part of that was removing all core associations and setting a default core to my manually created playlists from way back when.

I ended up having some trouble with the recorder wanting to default to an old path that didnt exist anymore when looking for my custom.cfg for that.

I notepad++'d the path and found the relevant entry, but I also came across the playlist_cores = entry which was ultimately chock full of DETECT;DETECT;DETECT and somewhere in the list, the absolute path I’m referring to that was incorrect.

I first changed the path to what it is now, then i realized if the rest are DETECT, theres no reason for that one not to be, so I went to change it.

Then i began counting the “DETECT” entries and there were less than I have playlists to begin with.

So I backed up my cfg and deleted the entire line expecting it to be recreated. It wasnt.

I then removed all the DETECT entries so it was just blank playlist_cores = "" and retroarch removed that itself upon startup.

So i tried adding back a single DETECT to it. Retroarch did not remove it at that point.

Ultimately im trying to find out what created this line, and if i need it, before i purge the backed up retroarch.cfg and move on with my life :stuck_out_tongue:

while we’re at it playlist_names = too. Deprecated? Found a commit from twinaphex from like 4 years ago that says “start adding playlist names and playlist cores to cfg file” but that doesnt seem to be the case any longer?

at least best i can tell deleting both these lines and they dont get recreated…

I don’t see either of those grepping through the source. So, dunno. Probably safe to lose them.

thank you hunterk. i assume theyre from prior to newer versions of the playlists.lpl files that contain data regarding core names etc maybe.

retroarch has evolved substantially since then for sure. Nobody would probably bother with it, but it would sure be cool if deprecated lines were removed from the cfg files when no longer used.

Similar to an uninstaller cleaning up after itself. Otherwise your faced with; in time a incredibly large, confusing, hard to navigate cfg file, or restarting your cfg.

neither are very appealing :stuck_out_tongue: