GrantSP Posted June 6, 2016 Posted June 6, 2016 Have we tested the beta DDL 2.0 yet? If you mean DynDOLOD, then, yes. Tech and I got an early look at it and it is currently in active beta testing.
TechAngel85 Posted June 6, 2016 Author Posted June 6, 2016 The Beta is good to use for STEP. The new instructions are set up here: https://wiki.step-project.com/User:TechAngel85/Sandbox3 I was getting ready to ask Sheson when the beta will be fully released. That's when I was hoping to switch over to the new instruction set.
fbrafa Posted June 24, 2016 Posted June 24, 2016 Sorry if this isn't the place. I got somewhat confused by what I read in this thread and in the 'versioning' article. Specifically the '3.0 when Wrye Bash gets official support'. Does that mean you'll be dropping Mod Organizer in favor of Wrye Bash?
TechAngel85 Posted June 24, 2016 Author Posted June 24, 2016 No idea what you read, but 3.0 will not have anything to do with WB. STEP is staying with MO for the foreseeable future.
fbrafa Posted June 24, 2016 Posted June 24, 2016 No idea what you read, but 3.0 will not have anything to do with WB. STEP is staying with MO for the foreseeable future. Switch to official Wrye Bash support: 3.0.0 (major change resets minor/hotfix)I know it was under 'examples' but it spooked me a bit anyway Sorry.
Nebulous112 Posted June 24, 2016 Posted June 24, 2016 I know it was under 'examples' but it spooked me a bit anyway Sorry.I see what you meant. I was trying to figure out where this was being referred to, and you meant in the link to the versioning page. Yeah, no that is just an example of what would constitute enough of a change to be considered "major" and bump up the first number in the version schema.
TechAngel85 Posted June 24, 2016 Author Posted June 24, 2016 Oh, I can see where that might be confusing! No, it was just an example given which would cause a change to the that version digit. We're not changing back to WB.
fbrafa Posted June 30, 2016 Posted June 30, 2016 Has it been suggested already to mention TES5edit merged patches in the main STEP page? maybe for people who won't be using the STEP patches or people who intend to install additional mods after STEP. Maybe even provide official .modgroups for the STEP patches.
EssArrBee Posted June 30, 2016 Posted June 30, 2016 Has it been suggested already to mention TES5edit merged patches in the main STEP page? maybe for people who won't be using the STEP patches or people who intend to install additional mods after STEP. Maybe even provide official .modgroups for the STEP patches.We recommend using the bashed patcher from wrye bash because it does a lot more to combine the leveled lists.
fbrafa Posted July 1, 2016 Posted July 1, 2016 We recommend using the bashed patcher from wrye bash because it does a lot more to combine the leveled lists. Absolutely. But I meant for general conflicts other than leveled lists. A paragraph or two on the troubleshooting section. Just explaining basic automatic merged plugin creation and deleting the leveled lists prior to bashed patch. or even just linking to the TES5edit section of the wiki.
Nebulous112 Posted July 1, 2016 Posted July 1, 2016 Absolutely. But I meant for general conflicts other than leveled lists. A paragraph or two on the troubleshooting section. Just explaining basic automatic merged plugin creation and deleting the leveled lists prior to bashed patch. or even just linking to the TES5edit section of the wiki.Definitely good to let the Bashed Patch deal with leveled lists instead of a merged patch. However, personally, I create a custom xEdit patch for conflict resolution with other mods. I have found that Merged Patches cause more trouble than they are worth (by introducing errors and including things that you didn't want carried over), but that is just my personal opinion. I tried it once, I inspected it in xEdit, and I didn't like the result, lol. Edit: For people that do not know how to use xEdit, maybe the benefit is more than the downsides. I dunno. I think Ess would know more than I would about it.
fbrafa Posted July 1, 2016 Posted July 1, 2016 (edited) Definitely good to let the Bashed Patch deal with leveled lists instead of a merged patch. However, personally, I create a custom xEdit patch for conflict resolution with other mods. I have found that Merged Patches cause more trouble than they are worth (by introducing errors and including things that you didn't want carried over), but that is just my personal opinion. I tried it once, I inspected it in xEdit, and I didn't like the result, lol.I know what you mean. The automatic merge can be pretty dumb sometimes. and manual patch is too much hassle to put in the main guide, plus it's already covered in the xEdit guide. In this case the .modgroups would still be a good thing in my opinion and could be silently slipped along with the STEP patches. The user would be left with only post-STEP mod conflicts showing in red. Anyway, sorry about the rambling and if this should be posted elsewhere instead of here. Edited July 1, 2016 by fbrafa
Recommended Posts