main()įile 'bash ash.py', line 310, in main ret = bush. Input encoding: None output encoding: None locale: ( 'en_US', 'cp1252')įilesystem encoding: mbcs Searching for game to manage:įile 'Wrye Bash Launcher.pyw', line 88, in bash. If things still aren't working as intended, take a look at your Smashed or Bashed Patch on FO4Edit.Wrye Bash starting Using Wrye Bash Version 307.0.

If your conflicts are mostly leveled list related, go for Bash. If you know you have a lot of conflicts unpatched, go for Smash. I wouldn't recommend using both Bash and Smash in the same load order.

It's also useful for very small conflict patching, as well as merging tweaks together without having to go through merging. That being said, neither is safe from error, and you might have to tweak a thing or two every now and again - and for that, you're going to need FO4Edit. It's also much easier to visualize missing masters and plugins loading before their masters, as everything is color coded. Bash has funcionalities such as changing masters on a file's header, and from what I've seen can compact formIDs for esl flagging. Bashed Patches will consolidate your Leveled Lists but not much else Smash is far more comprehensive when it comes to solving conflicts. Personally, I just sort my load order manually, by categories, and solving conflicts if they appear.įO4Edit, Bash and Smash all do different things. This might be outdated news, so take it with a grain of salt. Well, from what I know, LOOT is not as reliable for Fallout 4 as it is for Skyrim.

Wrye bash fallout 4 save game cleaner