Prism Launcher auto-import or use PrismLauncher instances

[Arelad1]

what would you like

A setting or a first time setup that either imports instances from PrismLauncher (if the underlying instance management system is the same, this is not an obligation), or uses the PrismLauncher instances path for detecting instances. This is not needed, but a clarification in the README about migration would be nice.

alternatives or workarounds

Maybe just a copy paste of the instances with a warning that they won't be synced, or using the PrismLauncher path alongside the rmcl path (I couldn't get rmcl to use the PrismLauncher path since the instance.cfg from Prism isn't the same as the instance.json)

additional context

rmcl does not need to be a tui version of PrismLauncher or MultiMC, in my opinion, but given migration from another launcher could be a nice feature, I'll continue trying to transfer and maybe (maybe) write a script for converting.

[objz]

rmcl supports the MultiMC format, so currently the way is exporting it from Prism as MultiMC and then importing it into rmcl. I know this is not a fancy way. I had that on my mind but forgot about it. I might introduce either a setup, as you said, or a menu in the TUI, I’m not sure yet

[Arelad1]

Oh, okay, I didn't know rmcl supported MultiMC instances. That's helpful information :). I'll try to understand how PrismLauncher exports and manages instances and if it can be converted into a bash or Rust tool (very basic knowledge of Rust), if I have the time. I guess I'll use rmcl only now (I was still using PrismLauncher for the instances I had not converted yet)

Thanks !

[objz]

Good Idea, lmk if you have a working script. I will eventually include this native into the launcher