When importing mods / DLLs, the records in the database have hard-coded paths to the user profile that imported the mods
After copying over the "AppData\Local\Metis Mod Launcher" folder to use the configured profile on a new user account, all records still use the prior user account's profile path
Potential Solutions
Replace "C:\users\" with "%UserProfile%" in DB file paths, then expand the ENV variable when needed
Provide an "Update Profile Paths" button to update any file paths that don't match the current user's profile
Provide a command-line argument to configure the "App Profile" location, so it can be redirected to a path that's consistent regardless of user profile
Use Case
I share my desktop with my gf, who uses her own Windows/Steam user account so she can play online with friends from her steam list. She and I also use the same mods, so usually I'll import, then test them out. But there are quite a few mods that we are using, and it gets a bit unwieldy to do the import/export dance while trying to keep all the DLL paths in the right spots.
It would be far easier if I could just copy the entire AppData folder to her user profile and reset the permissions.
Alternatively, if there were command-line options for resetting/configuring the app's data path, I could then redirect it to something like "C:\ProgramData\Shared\Metis Mod Launcher" so both user accounts can get to it.
Problem Statement
Potential Solutions
Use Case I share my desktop with my gf, who uses her own Windows/Steam user account so she can play online with friends from her steam list. She and I also use the same mods, so usually I'll import, then test them out. But there are quite a few mods that we are using, and it gets a bit unwieldy to do the import/export dance while trying to keep all the DLL paths in the right spots.
It would be far easier if I could just copy the entire AppData folder to her user profile and reset the permissions.
Alternatively, if there were command-line options for resetting/configuring the app's data path, I could then redirect it to something like "C:\ProgramData\Shared\Metis Mod Launcher" so both user accounts can get to it.