by Blackcat12 » Fri Nov 26, 2021 12:29 pm
I think you are misunderstanding the issue. There is no issue with preserving the /inifile.
1. Open MM5 with a /inifile directive to a custom DB
2. Change something in MM5 that will prompt for a restart after the change, such as an addon update or change the skin.
3. When MM5 restarts, it is opening with the default DB instead of opening with reference to the original custom db that was initially opened.
I just did it again by changing the skin. I have to close MM5 and reopen again using the original shortcut or command line with reference to the inifile.
I think you are misunderstanding the issue. There is no issue with preserving the /inifile.
1. Open MM5 with a /inifile directive to a [b]custom DB[/b]
2. Change something in MM5 that will prompt for a restart after the change, such as an addon update or change the skin.
3. When MM5 restarts, it is opening with the default DB instead of opening with reference to the original custom db that was initially opened.
I just did it again by changing the skin. I have to close MM5 and reopen again using the original shortcut or command line with reference to the inifile.