I use MO2 and a stock game folder to launch from, but was having an issue where the tool was cleaning the plugins in Steam's Skyrim Special Edition folder. If you're having the same issue here are the steps I used to fix it:
Click the wrench icon at the top of MO2 Go to the plugins tab of the pop up Scroll down to find "Clean Plugins" Select "Clean Plugins" Change "explicit_data_path" to "true" I aslo changed "explicit_ini_path" to true (though I am not sure this is needed)
I should also note that I have an argument pointing SSEEdit to the stock game's data folder (in its executable settings, e.g. -D:"game path").
I'm not sure it's if it's actually working. It keeps launching sseedit, loads some stuff and then just closes sseedit, then launches to repeat the cycle all over again
Yes this is the intended behaviour, it's cleaning your plugins one by one against vanilla files, and to do that it needs to start and close Xedit over and over again for each one of your plugins.
I don't know why that didn't even cross my mind lol. I'm not sure that would work without some minor changes to the code. When I get home I'll play around with it and look into updating so it's completely separate from the original plugin, or if I can make it play nicer with managing multiple games
Currently working on it now. I've managed to get it to detect which game is being managed and look for xEdit based on the exe name for that game. Just need to implement that detection across the rest of the plugin and do some testing.
I uploaded a new version. It'll now detect the managed game and try to run the correct executable for it. e.g. If you're playing Skyrim SE, it'll try to launch an executable named SSEEdit and for Fallout 4, FO4Edit.
I'd have liked to make it check if the executable actually exists first, and if not try another name but the executable list isn't actually accessible to plugins and MO2 seems to have a bug making detecting a failed launch very difficult. The code to detect that from the original plugin doesn't seem to be functional either.
The python code isnt resolving paths properly for whatever reason. Have you tested the script on Windows and would it run out of the box? I put an absolute path to the .exe (2nd line of runClean function), used "native" windows (f****ng windows with its dumb \ ) paths instead though
I'm using Windows myself so it should run out of the box with Fallout 4 installed via Steam and FO4Edit added as an executable (with that name exactly). Do you get an error message?
All I'm getting from both startup options are BSA Packer and INI Editor. I can find both files in my plugins folder, so I know I put it in the right place (I think).
21 comments
Click the wrench icon at the top of MO2
Go to the plugins tab of the pop up
Scroll down to find "Clean Plugins"
Select "Clean Plugins"
Change "explicit_data_path" to "true"
I aslo changed "explicit_ini_path" to true (though I am not sure this is needed)
I should also note that I have an argument pointing SSEEdit to the stock game's data folder (in its executable settings, e.g. -D:"game path").
Is this the intended behavior?
I'm not sure that would work without some minor changes to the code.
When I get home I'll play around with it and look into updating so it's completely separate from the original plugin, or if I can make it play nicer with managing multiple games
Just need to implement that detection across the rest of the plugin and do some testing.
e.g. If you're playing Skyrim SE, it'll try to launch an executable named SSEEdit and for Fallout 4, FO4Edit.
I'd have liked to make it check if the executable actually exists first, and if not try another name but the executable list isn't actually accessible to plugins and MO2 seems to have a bug making detecting a failed launch very difficult. The code to detect that from the original plugin doesn't seem to be functional either.
Edit: i found out, it was a folder permission, ty anyway.
Damn, running flawless, great plugin, thanks! Endorsed.
I put an absolute path to the .exe (2nd line of runClean function), used "native" windows (f****ng windows with its dumb \ ) paths instead though
Do you get an error message?