Misc Accessing Twilight Menu's 'saves' folder via Flashcard's kernel or accessing per-ROM saves via Twilight Menu.

[BirdWatcher69420]

In my particular example, the Flashcard in use is r4isdhc.hk 2023 that runs Ace3DS+ R4iLS Wood R4 1.62, from which I manually boot up Twilight Menu when I need nds-bootstrap.

Since Twilight Menu uses a dedicated 'saves' folder (Let's assume I keep all my ROMs in one folder, so the 'saves' one is affixed & stores all my saves), I have to move all of my .sav files from where the ROMs are at to the aforementioned dedicated folder, what makes it impossible to conveniently boot ROMs via Flashcard's kernel.

As known, one can move ROMs to different folders, and Flashcart's kernel should be able to boot them and assign a save per ROM to a respective folder where ROM is located, thus I think it has the possibility to access a different folder.
The question is, is there a way to make Twilight Menu access saves from the folder where the ROM is placed OR a way to make Flashcard's kernel look for a respective .sav in the 'saves' folder?

The only workaround I could imagine is to keep ROMs in the 'saves' folder to make .sav accessible by Flashcard's kernel AND have all the same ROMs placed elsewhere for Twilight Menu to make use of them.

 

[Wokann]

However, if you keep ROMs in the 'saves' folder and boot in twilightmenu++ , twilightmenu++ will create a new 'saves' folder in this path like this:
.\rom.nds
.\save\romfiles.sav
→
.\save\rom.nds
.\save\save\romfiles.sav
Maybe you can check the source code of nds-bootstrap in github, and edit the save path, then recomplie it to replace nds-bootstrap in your flashcart. To make save file saved to the respective folder where ROM is located.

 

[BirdWatcher69420]

... keep ROMs in the 'saves' folder and boot in twilightmenu++

I boot ROMs that I've put in the saves folder via flashcard's menu, and I boot ROMs I've put in the folder before saves with TM++, doubles the size taken by ROMs, but works as intended without creating separate folders thankfully. The only downsides are aforementioned doubled capacity needed and inability to sort ROMs by folder.

Regarding tinkering with nds-bootstrap's source code, - I can't due to my limited knowledge.