Jump to content

Question

Posted

I use a bashed patch for skyrim. I noticed that certain plugins would have green text, but when building the bashed patch, these mods would not be included in the merged patches list. Is there any way to force these mods to be merged, or is there a good reason why they should not be? This is working under the assumption that all plugins that have green text are ok for merging.

 

Similar to this is that BOSS reports that certain plugins have Delev and Relev bash tags. WB applies some of these tags automatically, but on other mods the tags are not added even though BOSS says they should be, so i end up manually adding these tags. However, even with these tags, some of these plugins are not automatically added to the leveled lists when rebuilding the bashed patch. Should i manually add these plugins to the leveled lists when rebuilding the bashed patch, or only include those that are automatically added?

 

I understand that bashed patches and skyrim are still new territory, so maybe WB has issues with skyrim plugins and so maybe i really shouldn't be using a bashed patch yet. However, i remember from oblivion that bashed patches made life much simpler for me by reducing compatibility issues, so would be nice to start building it already :)

 

Thanks for the help!

9 answers to this question

Recommended Posts

  • 0
Posted

The bashed patch still very much a WIP, some types of data are completely decoded and implemented in Bash and others have not even been looked at yet. It will not cause problems unless you try to force stuff that hasn't been worked on yet. Keep everything on automatic and make sure you are running in Skyrim mode and you'll be fine.

  • 0
Posted

Thanks for the quick reply frihyland. I will keep everything on automatic. Just to clarify, when you wrote "running in skyrim mode" do you mean using the Bashed Patch, Skyrim.esp over the oblivion one? Both come with WB SVN 260, and im using the skyrim one as per z929669's WB guide instructions.

  • 0
Posted

No you can delete oblivion bashed patch, along with the oblivion ini edits and the archiveinvalidation and also make sure lock load order is turned off, all those things are from oblivion and irrelevant to skyrim at best and confusing and annoying at worst.

 

skyrim mode I mean settings > game > skyrim

 

I should check the bash guide and make sure that stuff made it in.

  • 0
Posted

skyrim mode I mean settings > game > skyrim

 

I should check the bash guide and make sure that stuff made it in.

 

 

If you install WB for Skyrim, this will already be configured.

  • 0
Posted

But dont we need to install SVN version now so that works with BOSS 2.0. Which then requires deleting oblivion stuff?

 

Should a section be added to the guide for configuring SVN version as I expect SVN may be needed again in future! I have no idea if this is a few lines or much longer :) Perhaps as a seperate wiki page so as not to complicate main page

 

Just installed standalone python and then SVN version last night. Tonight will try to actually use it on some test mods with a view to switching over from MO with new STEP.

 

As an aside that likely belongs in the other topic on the ini file - In terms of bash.ini and changing /oblivion to /skyrim is there only about 2 or 3 of these? The rest seemed to be for paths to oblivion tools that I had not heard of so I left those as \oblivion

  • 0
Posted

But dont we need to install SVN version now so that works with BOSS 2.0. Which then requires deleting oblivion stuff?

 

Should a section be added to the guide for configuring SVN version as I expect SVN may be needed again in future! I have no idea if this is a few lines or much longer :) Perhaps as a seperate wiki page so as not to complicate main page

 

Just installed standalone python and then SVN version last night. Tonight will try to actually use it on some test mods with a view to switching over from MO with new STEP.

 

As an aside that likely belongs in the other topic on the ini file - In terms of bash.ini and changing /oblivion to /skyrim is there only about 2 or 3 of these? The rest seemed to be for paths to oblivion tools that I had not heard of so I left those as \oblivion

 

 

On the SVN: I am waiting for the "final" WB release that incorporates the "fully functional" BOSS API. SVN will likely have other issues that I cannot address, and the next stable WB release is likely to have some other features that are more Skyrim friendly.

 

RE bash. ini edits... they do belong here, as these are explicitly related to WB behavior... yes, only 3 entries for changing \oblivion to \skyrim

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.