Well, there is only 1 version there FO4Edit 3.1.3 1dabbcd.
The XML requires the FO4Edit 3.1.3 bb242bc that is not there, also cant find it on Github apparently.
Unless, i was looking in the wrong place, but i dont think so.
Thanks for the XML update :)
Yeah, that's what I meant when I was talking about being frustrated with those projects that wipe out all traces of the old versions when they release a new version... before 1dabbcd was available, bb242bc was the only version of 3.1.3 that existed. Now it's only 1dabbcd. As it happens, this particular update justified exactly why I tend to require very specific versions of everything: in bb242bc, the exe file was named FO4Edit.exe, so I had to rename it to TES5Edit.exe during the extraction process. 1dabbcd changed it back to TES5Edit.exe, so it needed my intervention.
Update: Worked like a charm, thank you airbreather!
I am not new to step/MO (or SRLE or SRLE Extended) countless hours build setups with MO but this.. this just save so many tedious work, very nice tool.
Glad to hear everything's working out now.
I still have to test if everything is on the right place while in-game, but it booted up with no issues and up to Helgen had no misplaced textures or anything else.
There's a bit of a double-edged sword thing going on right about now. On the plus side, once StepperUpper runs through the whole process successfully, you can be sure that it didn't miss a checkbox on the 92nd step that's going to bite you after you get 21 hours into your game or something silly like that... it's very consistent, so if it's working for someone else, then it's going to work for you (assuming you use the exact same XML files and the exact same version of StepperUpper).
On the minus side, of course, if there's a bug, especially one that's StepperUpper-specific (like the one that's been the talk of the town for the last page or so), you can be pretty much 100% sure that this bug affects your setup as well. So you will need to do that one workaround if you want to get that juicy DLC content to work, it seems.
I still haven't had the opportunity to fix that bug yet.