WB not building new patch if previous patch is present

[Telessa]

For some reason my WB will not create a new updated patch if the previous patch is present.  Since the author of WB has made it abundantly clear that there will be NO support for those using MO    (seems odd since STEP requires we use it) I'm here seeking assistance.  

 

When I finished installing STEP Core 2.2.9, I ran WB for the first time and, as expected, the Bashed Patch, 0.esp was in the overwrite file along with the "Docs" folder containing the Bashed Patch, 0.txt and Bashed Patch, 0.html (I can't remember if they were present in previous builds or not seems it wasn't?). I then created the mod calling it "WB Output" and activated it. Everything was fine at this point.

 

Then I installed a couple of mods, ran LOOT and WryeBash again.  I clicked the "rebuild patch" and opened the overwrite file only to discover the "Docs" folder with the txt and html files inside but no new patch.  I thought maybe it glitched or something so I ran it all again.  The same thing happened.  But, to be on the safe side, I did another run and, once again, the same thing happened.  So, trying to discover what was happening, I opened the WB Output and under "Optional ESPs" I moved the original Bashed Patch, 0.esp from the lower pane to the upper pane.  I then ran WB again, and low and behold the Bashed Patch, 0.esp was in the overwrite file along with the Docs file.  

 

The only way I can get WB to create a new patch is if I move/delete the current patch prior to rebuilding the patch. Otherwise only the "Docs" file will be present in the overwrite file.  I've even tried adding a new mod, running LOOT and WB without moving/deleting the current patch then trying to run Skyrim but there is an instant CTD, as one would expect.  

 

Is this something new with WB?  It didn't used to be that way and I'm not sure if I've done something wrong or if WB has indeed changed and now is supposed to act this way.  Am I destined to have to delete the current patch before creating a new patch every time?  Seems silly to do things that way... help?

 

Thanks for reading and I'll check back later!

 

Ciao! 

 

[GrantSP]

Don't trust the timestamp as displayed by Windows Explorer. Open the bashed patch in TES5Edit and check the details in the header.

The file created by WB will overwrite the current one IF that file exists in the VFS, ie. if it is active in the mod list.

 

 

EDIT:

Ninja'd by Neovalen

Edited December 10, 2014 by GrantSP

[Nozzer66]

That's not surprising. When you make a mod and put the bashed patch in that mod folder, when you rebuild the patch the next time, it simply overwrites the one in the said mod folder.

 

To test this, check the date etc on the bashed_patch0.esp before and after you've run WB and check they've changed. If the date/time on the Bashed Patch has changed to the newer time, you're in business. It should have worked.

Edited December 10, 2014 by Nozzer66

[Telessa]

I have checked and it doesn't overwrite the previous .esp file.  I know it should have worked, the point is that it isn't working.  It doesn't update, it's not even in the overwrite in MO.

[Neovalen]

It does but the date doesn't change. Check the contents of the esp.

[Telessa]

I will take a look now!  Thanks!

 

BBS 

[Telessa]

Well by golly color me amazed!  Thanks everyone for helping me with that.  I had no idea there was a header checker or even a header! LOL  I can add the mods, I can run LOOT and I can run WB.  Beyond that I can come here and find out all the answers!  LOL  The last time I had things up and running there would always be the Bashed Patch, 0.esp in my overwrite file.  I had always done the drag and drop and replace with the overwrite file.

 

This is much betterl  Thanks again, I sure do appreciate ya'll.  I truly don't know what I'd do without all the knowledge that is so freely given here. Hats off to each of you!

 

Ciao! 

 

BTW, do I need to keep that Docs folder that is in the overwrite folder?  It contains the Bashed Patch,0.txt and .html.  

 

Thanks again! 

Edited December 11, 2014 by Telessa

[GrantSP]

Your choice, either delete them from the Overwrite or drag them into the Bashed Patch mod.

All they do is detail the changes that this patch contain, one in txt form the other a HTML.

 

I just drag mine into the folder. I am curious though why they don't automatically update. Maybe it's only certain file types that it works on.

 

hmm... investigation mode.

[Telessa]

*cheesy grin*  I'm glad I could give you something to investigate!  LOL

 

Ciao! 

[z929669]

Your choice, either delete them from the Overwrite or drag them into the Bashed Patch mod.

All they do is detail the changes that this patch contain, one in txt form the other a HTML.

 

I just drag mine into the folder. I am curious though why they don't automatically update. Maybe it's only certain file types that it works on.

 

hmm... investigation mode.

I am guessing because she never copied the doc files into "WB Output" in MO ... so they just kept updating Overwrite ;)

[GrantSP]

I am guessing because she never copied the doc files into "WB Output" in MO ... so they just kept updating Overwrite ;)

Actually, no, I'm facing a similar situation to her in that my WB reports don't automatically get updated as outlined here.

[z929669]

Yeah, I posted there ... weird behavior.