anjenthedog Posted September 9, 2020 Share Posted September 9, 2020 That way, the minute your game doesn't start, you'll have a good idea why. And as a result of doing it sensibly instead of hastily, you only have to back track one or two saves instead of potentially losing entire levels of progress.... Link to comment Share on other sites More sharing options...
ZodiacBlack Posted September 10, 2020 Author Share Posted September 10, 2020 Alright, it was Wyre Bash turning stupid and the bashed patch got corrupted. I think I need to exclude a patch or something, but I'm not entirely sure on which patch is the culprit. Link to comment Share on other sites More sharing options...
righteousgoddoward Posted September 27, 2020 Share Posted September 27, 2020 What I do when getting crashing problems...is take off half my mods...test. If still crashing...take off a quarter more...test. etc etc Link to comment Share on other sites More sharing options...
ZodiacBlack Posted September 27, 2020 Author Share Posted September 27, 2020 Yea, I used to do that before... Until I began to maintain upwards of 1000+ mods at once. Now Iâm currently on SSEEdit and simply âcompactingâ all the references and conflicts together, manually. This way, I literally cannot get a crash from conflict, but probably from too many resources or scripts running at once. When I know thatâs the case, then I can actually start compacting the scripted mods as well to save space and remove unnecessary commands for some tiny, irrelevant events or stuff like that. Link to comment Share on other sites More sharing options...
righteousgoddoward Posted October 2, 2020 Share Posted October 2, 2020 That is such a long mod list. It lirerally put me to zzzzzzzzzzzzzzzzzz Link to comment Share on other sites More sharing options...
Recommended Posts