JediStudley Posted March 4, 2021 Share Posted March 4, 2021 I was going to share an ESL (esp) that patched the differences between two other mods that I didn't write. I don't use any assets from either mod, just the ESL to resolve the conflicts. In conflict resolution, configuration values are copied from each of the mods to make the patch. Even though I'm fairly certain the configuration values are ok to use, I still wanted to ask the community first. Link to comment Share on other sites More sharing options...
IsharaMeradin Posted March 4, 2021 Share Posted March 4, 2021 Personally, if the patch is strictly a plugin that requires the original mods to be installed and active, I see no harm in sharing it. Yet, there are others that see the entire created work as copywritten and that unless explicit permission is granted then even a patch is a no go. You are wise to ask for clarification before publishing. Do you have links to the mods in question that you have patched? Reading their permission statements (if any) would go a long way in answering your question. Link to comment Share on other sites More sharing options...
JediStudley Posted March 4, 2021 Author Share Posted March 4, 2021 Thanks for your response! https://www.nexusmods.com/skyrimspecialedition/mods/21654 AI Overhaul ... indicates no using resources, but does allow for modify files with credit (which I always do anyway)https://www.nexusmods.com/skyrimspecialedition/mods/18665 SVOM ... this is completely locked down and requires permission to make even modifications. I've emailed the creator of SVOM, just in case. I think AI Overhaul is ok, from the permission settings. Patching that just affects the ESL/ESP is really a grey area for me to make a call. Link to comment Share on other sites More sharing options...
IsharaMeradin Posted March 4, 2021 Share Posted March 4, 2021 Based on the perms in that mod, it would probably be best to get permission from the author of SVOM before proceeding, just to play it safe. AI Overhaul should be okay, but it doesn't hurt to send a message to that author either. Better there be a record of effort in reaching out if an author takes offence with a patch rather than no effort at all. Link to comment Share on other sites More sharing options...
JediStudley Posted March 4, 2021 Author Share Posted March 4, 2021 a good point. thank you for the feedback! I wasn't sure about permissions and ESP files themselves, but it is better to be sure of even those. :cool: Link to comment Share on other sites More sharing options...
JediStudley Posted March 5, 2021 Author Share Posted March 5, 2021 In case anyone else is looking in the future, the ESP/ESL contains a lot of information (configurations for packages, NPC, locations, etc.) Where things are grey is determining when something is trivial and when it isn't. For example, changing an NPC's hair color and duplicating that is hard to argue should need permissions. On the other hand, if that same ESP file contains the definition of a new quest, that is easy to argue it should need permissions. The mods in question here change a lot of NPC's with references to custom packages and scripts (note the packages & scripts were not being copied for the patch). From these two mods (AIO & SVOM) the copied portions are configuration of NPC's. Arguably this doesn't need permissions, but it is safer and good etiquette when things are in the 'grey'. Link to comment Share on other sites More sharing options...
Recommended Posts