DrCube Posted October 20, 2018 Share Posted October 20, 2018 Reaching out to anyone who is the owner/maintainer of Project Nevada and Extra Options. I am assuming these are two different projects from two different teams but I have a merged version of Project Nevada and Extra Options that I would like to upload/return to the nexus. Who do I need to check with and get permission from to see if this can be done, or have such people scattered to the winds and moved on?I used the information helpful_visitor provided at the following link to resolve merge issues that affect MCM scripts:https://taleoftwowastelands.com/viewtopic.php?t=6027I made corrections to the following scripts (one if statement really)... PNxCMCMScriptPNxBMCMScript PNxRMCMScript ...took the following esm/esp files...Project Nevada - Core.esmProject Nevada - Cyberware.espProject Nevada - Equipment.esmProject Nevada - Rebalance.espProject Nevada - Extra Options.esmProject Nevada - Cyberware Additions.espProject Nevada - Rebalance Complete.espProject Nevada - All DLC.esp...and used mator's merge plugin standalone to combine them into a single PNMerged.esp file.Now this doesn't make everything all shiny and rosy because a lot of the compatibility patches I had downloaded for Project Nevada are toast. Also, in the following link, Roy and Mystical Panda call out other problems that can arise from merging...https://taleoftwowastelands.com/viewtopic.php?t=3872...but I didn't think I'd be able to get past the MCM menu problems. However, I've loaded up a new game with my PNMerged.esp file and all the MCM options seem to be functioning like normal. So far so good. Link to comment Share on other sites More sharing options...
dubiousintent Posted October 21, 2018 Share Posted October 21, 2018 Once you have checked the permissions allow you to make the changes you envision, you need to contact the "uploader" (link in the mod page) about any questions those permission statements leave in your mind. Those are indeed two separate (though related) mods by different authors and uploaders (not necessarily the same thing): PN is uploaded by schlangster, and PN-EO by Gribbleshnibit8. Both are still active on Nexus. "Merges" of separate files are neither "patches" nor "bug fixes"; so not explicitly covered in the standard permissions. Both mods do allow use of assets, so you could (IMHO: I'm not a moderator) post your own "mod" of the merge, giving due credit to the original authors. However, that is perilously close to a "compilation" which many authors object to as causing them lots of questions regarding something they had nothing to do with in the first place as well as quickly becoming outdated. Best to query the authors directly first, especially as they are available. Your compatibility patches are "toast" because when you merge using "Mator's Standalone Merge Plugin" it creates a new file with it's own record reference numbering sequence (the "merge down" technique). "Patches" require and expect the original records' references to perform their function (using the "merge up" technique). You would need to patch before creating the merge. Those would also need to be detailed and the permissions checked. While you have your own solution, you may find some articles of interest. The PN-MCM issue is discussed in the wiki "HUD-UI-Menu issues" article. The issue of combining patches prior to merging plugins is discussed in the wiki "Multiple file Merge-Up Procedure" article. -Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts