[Solved]What to do with "Unmanaged: Bashed Patch, 0"

[FuzzRocket9]

I see it's made redundant now that I made a new mod folder for my personal bashed patch, but I want to know if this has any other purpose?

 

Thank you.

Edited August 11, 2015 by FuzzRocket9

[Kesta]

This just means that you ran Wrye Bash not through MO, which led to a Bashed Patch being created directly in your data folder. Just deleted this bashed patch and make sure to always run WB through MO.

 

Note that "Bashed Patch, 0.esp" is always created if not already existing whenever launching WB, even if you didn't build it.

[hishutup]

It doesnt really matter where its located in MO because it doesnt have any assets. I leave mine at the top so I dont have to micro manage it.

[GrantSP]

I moved this because it isn't specifically to do with the STEP guide.

[FuzzRocket9]

Thanks guys. Something so simple, yet it would of bothered me if I ignored it, so I had to ask. Thanks as always :D

[GrantSP]

The bashed patch created with Wrye Flash is handled in a completely different manner to that for Skyrim.

For the patch to be created you must have either the blank patch in the Data folder, or in a mod of your creation, and that blank file is overwritten, not copied first then patched. Using WB in MO always places a new bashed patch in the 'overwrite' folder, with FO3 or FNV it doesn't.

This means it is much more fiddly to have multiple patches for multiple profiles.

 

When patching in the Fallout games, MO will log an error but still produce a working patch if the file is found in the Data folder. To get around this you should first copy a blank patch from the Wrye install and place it into a new user-created mod in MO.