I've run through the STEP:Core procedure, and finally got to the bashed patch part of 2.N (2.10.0).
I've run through the process here: http://wiki.step-pro...Recommendations, ensuring I ran LOOT, and did the meta rules.
Part 8 of the bashed patch process itself is giving me issues.
When complete, a browser window pops up, but it's a 404. No OK button. I close that window, get another popup with the checkmark to activate the bashed patch. I click the checkmark and close.
Checking the Overwrite area, there is only a Docs folder, with Bashed Patch, 0.txt and Bashed Patch, 0.html in it. NO bashed patch, 0.esp.
I saw elsewhere that this could be because Wrye Bash had been run outside of LOOT previously, but there is NO "bashed patch*" anywhere on the system, especially in the Data folder of SKYRIM as expected in this scenario. There IS a bashed patch, 0.esp on the right pane of MO, at the bottom of the Plugins Tab list.
I've reinstalled Wrye and reran from MO to no effect.
EDIT: I noticed in the MO log:
DEBUG (00:03:05.0109): createfile w: C:\SKYRIM\steamapps\common\Skyrim\Data\Bashed Patch, 0.esp -> C:\SKYRIM\APPS\ModOrganizer\mods\Cleaned Update ESM\Bashed Patch, 0.esp (80000000 - 3) = 00000774 (0) [god I hate win10 - a full drive search didn't turn this up]
the bashed esp is in the cleaned update folder but the modified date is 2 hours ago, the first time I ran Wrye. Can I use this esp file? Where would I move it to? I assume there's some kind of settings I can reset to stop this weird folder placement behaviour?
Edited by kleshas, 05 September 2017 - 02:09 AM.