GeminiContractor Posted December 25, 2012 Share Posted December 25, 2012 I've been reading a lot of posts while searching through the internet that say TESVSnip and SkyEdit are broken(well the mods they edit become that way) So, if that's the case, is there any way to merge mods besides using the Creation Kit or Wrye Bash that is quick and won't break the mods? Link to comment Share on other sites More sharing options...
IsharaMeradin Posted December 25, 2012 Share Posted December 25, 2012 You could try TES5Edit. I believe it is possible to use it to do some merging. Link to comment Share on other sites More sharing options...
GeminiContractor Posted December 26, 2012 Author Share Posted December 26, 2012 You could try TES5Edit. I believe it is possible to use it to do some merging. Thanks for the recommendation and sorry for the late reply. How would you go about merging in TES5Edit? Can I just stuff all of my non-conflicting mods in and create a merged patch, and would I need to keep my other mods checked and in the folder? Link to comment Share on other sites More sharing options...
MShoap13 Posted December 26, 2012 Share Posted December 26, 2012 If it's non-conflicting mods, then using Wrye Bash's Bashed Patch is the way to go... Link to comment Share on other sites More sharing options...
ripple Posted December 26, 2012 Share Posted December 26, 2012 How would you go about merging in TES5Edit? Can I just stuff all of my non-conflicting mods in and create a merged patch, and would I need to keep my other mods checked and in the folder? I am assuming you want to merge esp's to cut down on the number of plugins in your load order, rather than, say, trying to make a compatibility patch to resolve conflicts. So, highlight the record you want to merge, right click and select 'copy as override into...', name your new merged plugin, repeat with the other mods you want to merge. Link to comment Share on other sites More sharing options...
blove Posted December 27, 2012 Share Posted December 27, 2012 "Copy as override into..." would still have the old file as a master. "Copy as new record into..." would be what you needed but you have to be careful to get and link all of the record dependencies as well. Link to comment Share on other sites More sharing options...
MShoap13 Posted December 27, 2012 Share Posted December 27, 2012 (edited) "Copy as override into..." would still have the old file as a master. "Copy as new record into..." would be what you needed but you have to be careful to get and link all of the record dependencies as well. No, just no. Copy as new record assigns a new FormID to any records you copy. This can wreak all kinds of havoc on your save games. IF you run into issues with master dependency, you're going to have to go through the copied records one by one and change the load order corrected prefix (the first two digits) of every FormID that points to the original plugin. These should be changed to match the new plugin's current load order in TES5Edit (If it's 04 in the tree on the left, all new FormIDs should point to 04, if it's 2A, then make them all 2A; any 00 prefixed plugins overwrite something from Skyrim.esm and should be left 00, same goes for DG/HF if your mod deals with their records). If it asks if you'd llike to make the changes to other records/subrecords in the plugin that reference that record, choose yes. Once you've completely gotten rid of FormIDs that point to the original plugin, right click on your new plugin and select "clean masters" this should remove the original plugin from the masters list of your new plugin (verify this in the new plugin's file header). This is one of the reasons why I said just use a bashed patch for non-conflicting plugins. Edited December 27, 2012 by MShoap13 Link to comment Share on other sites More sharing options...
blove Posted December 27, 2012 Share Posted December 27, 2012 Your "IF" is a must if done as an override and I will grant you that it is necessary for more complex merges done with xEdit. It is also a great way to create orphaned records. Simple merges should be done as new records in a new file. Link to comment Share on other sites More sharing options...
MShoap13 Posted December 27, 2012 Share Posted December 27, 2012 (edited) If you're dealing with a mod that only overrides things from one of the Master files (Skyrim.esm, Dawnguard.esm, or Hearthfires.esm) TES5Edit will not make your new plugin dependent upon the donor if you use copy as override. On top of that, if you copy these kinds of records as new records, they won't be overrides anymore. Your mod that gave Argonians talons won't give them talons anymore; instead, it will create a duplicate Argonian race with talons (and I'm pretty sure it wouldn't even be selectable in the changerace menu though I haven't tested it)... To avoid orphaned records just make sure you change records referenced in FormIDLists, etc. first and when TES5Edit catches that there's an internal subrecord (internal meaning contained within that plugin) that references the FormID you're changing and asks if you'd like to change it too, choose yes. If you have external records (from other plugins) referencing the FormIDs in your new merged plugin, you probably shouldn't be merging that particular plugin to begin with, but you'd have to alter the Master Files in the header of the subordinate plugin and change the subrecords by hand (you'd have to do this with Copy as New Record as well). To summarize:Bashed Patch Edited December 27, 2012 by MShoap13 Link to comment Share on other sites More sharing options...
blove Posted December 28, 2012 Share Posted December 28, 2012 Fear mongering about save game corruptions, using large fonts, and color really lends that extra support to something neither of us really know. What is the original poster merging? I am assuming that it is simple mods since novices should not jump in with both feet and simple merges should use simple solutions. Link to comment Share on other sites More sharing options...
Recommended Posts