Jeoshua

True. And I touch on this, if your aim is to prevent people from being able to post it cross platform, as it is a very capable technique to add to the DRM module, and requires little more than adding a single F4SE command into the fragment script. This technique does not in any way preclude that, it merely gives you a vehicle in which to contain it.

I did make a slight modification. I do not mean to imply that this technique requires that you withhold all source for your mods from everyone, and I have edited the original post to better reflect that. The Holotape Fragment script is your key to all this, and that is the only source you need to withhold. Everything else is up the the discretion of the person implementing it. If you want to put a clause in there saying you're cool with people stealing it, and use this to provide a signature and legal way to prevent people who have reuploaded your mods from any legal repercussions, you can do that, too. Just make sure you upload that one with your signature on it first, no matter what way you take it.

What am I working on? The Solution. And I need your input, modders. Script kiddies, too. Try to tear it down, roll your own, just help us out. Link in signature.

Yes, we can only be aware of these problems in hindsight, after much dissection of the issues. In order to work (and TF2's hats and UE's community both prove it can), it has to be handled very carefully. It has to be done by a party which can foresee these issues, and the only way to do that is by learning from the past. I'm not sure that Zenimax would even allow it be handled correctly, tho. These are the same people who preemptively sued Notch when he tried to copyright the very word "Scrolls", tho... so maybe they do have foresight.

Awesome. If you come up with anything interesting or any modifications you made which you felt worked better, let me know so I can try and incorporate the best and most general ideas. I plan on updating this as people use it, and make it work as good as can be hoped. I have also updated the FAQ with the questions that I have been asked thus far and didn't simply anticipate, and hope they clear up some confusion over decompilation and the entire point of this technique.

Yes, they can, but not fully. This technique does not prevent people from removing the DRM module. That is why you upload your mod first. If the two mods contain the same code otherwise, and they took your DRM off or slapped their own DRM on, but yours is first, then you can prove standing. That's also why it's important to upload it even if you don't intend it to be used on that platform. That way your file with the same code is sitting on the same server, and its file date is earlier. Dates can be faked on a single computer, but anyone changing dates on Bethesda.net or Nexus.com upload times is in much deeper doo doo than stealing mods, to begin with. The thief can steal your code, but you can still prove it is yours, and there is no way that anyone else could. This is covered in the FAQ. And as far as not coding it right, literally the only part you have to get right is the signature. Everything else is fluff and just strengthening of the agreements that everyone is already legally being held to, whether or not the EULA is present in the game files. Also, other components to this DRM, such as a No-Console feature or XBox Only module could be crafted by third parties without ruining the integrity of the technique, just so long as you write some portion of it yourself, make sure you e-sign it, and don't share your final source.

Ownership of Formats and Description of Intent: Mod theft is a terrible thing. For this reason, I have collected postings describing a technology that can be implemented into any mod which will increase the professionalism of the mod, protect it from mod theft, provide legal standing with which to challenge pirates, and to provide ultimate piece of mind. First of all. I'm sorry. I love you Bethesda, but I really need to say something. I know it's not your fault. You wanted to give us a game that everyone could enjoy and that people on the console could finally enjoy the true depths of. Modding games on console is a revolution and you finally delivered. Unfortunately, your lawyers botched the job. They gave us such an unconscionable document that we needed to agree to, just in order to use your modding platform. I know. The lawyers made you do it. I know, you didn't know that there would be so many problems at launch. I know, you had no idea that since modding on consoles had been possible this whole time, it had attracted a crowd already that didn't care one fig about intellectual property. But many modders are afraid that their content is going to be stolen. This can fix that. Zenimax has made, and indeed can make, no claims on ownership of the PEX format, any more than they can make claims of ownership of the PA32+ format which the engine itself runs on. Files like these are code, running on a particular format, and don't immediately become the sole property of Zenimax unless created within the Creation Kit. Crucially in this case, F4SE mods must have their PEX created by a third party utility, and acted upon by another third party utility. The Script Extender's PA32+ binary format cannot be downloaded through Bethsoft.net, will not work on PS4, and is not allowed to be run on the XBone. And while you have to provide a PEX file for the engine to run, you don't need to provide a PSC file for the user to read. In fact, not providing the PSC file of this technology removes the possibility of anyone else claiming any ownership of your source code, because they never had it. This last fact is the key. Central Module: Create a holotape using a terminal script, containing a menu. This menu shall contain, but is not limited to: - A list of credits of people the modder wants to thank and/or damn. - A Digital Signature of the modder generated in whichever manner they see fit. - (Bonus module) A Public key half of a Public/Private key pair to be used with this digital signature, with the public in your original copy of the source code. Do not compile the private half into the code, and keep it separate from the source code entirely. Provides double security as even if they decompile your script, they do not have the rest of this key. Bonus points for using this key to encrypt something. - (Triple word score module) So named because console versions do not have the code words necessary to run it. Encode any command in an F4SE way, and you make this script only work on PC. Note that this does not require your mod to run F4SE code otherwise, and does not prevent usage on Bethsoft.net for mods which DO work on console. Name the holotape with an item tag of [DRM] before the name of your mod. You want people to see this because it lets the thieves know what they're getting themselves into, but it doesn't require that they even see it. ex: [DRM] Clean Deluxe And here is the most important bit. You don't need to provide this PEX in your main file. You don't even need to link to it. It literally just needs to be in your download. None of your other scripts need to be altered to use this technology, and it stands alone. Actually providing a working terminal script is required, but needing the user to run it is unnecessary. Non F4SE mods will not suddenly be forced to have the whole main file be reliant on external libraries, and those who need to assure that F4SE is installed for proper compatibility with scripts that DO have F4SE requirements can place the checks for their mods in this module file, which can later be disabled when it is not needed. The files remain in the original download and on the user's install, even if disabled on console. These files remain with the downloader of a Bethesda.net file downloader even if the mod they are taken from is pulled from the Nexus. Keep the source sacred: By withholding the source code used to create the PEX Fragment script which this holotape will display, you eliminate the possibility of there being anyone else who could have created this file. This provides you with legal standing to prove, beyond the shadow of a doubt, that you are the party who compiled that file. Do not share this file with anyone, excepting possible members of your modding company. Keep your source code off of the internet at all times, and do not share it with anyone for any reason. I'll state it one more time, just for good measure. I'll even bold it. Don't Share The Source. Don't use anyone else's either. The point is that it's supposed to be yours. To make this work, you have to write it. I'm sorry. I want to provide you with a working module, but by its very nature, you have to write this yourself. Other code can have its source shared, if you so wish. Nothing is preventing you from allowing people to view the source code of any other modules. The extent to which you want to have your mod be open source is completely in your hands, since you are the one creating this DRM. Outside of the actual Holotape itself, none of the other script matters to this scheme, and you can either share or withhold that as you deem fit. The same goes with any Blender or 3DSMax object files, Photoshop or GIMP files, Audacity files, or other source that you feel that you should or should not share with the general public. The only thing that matters is the holotape fragment script, and that is your key to all of this, along with the upload dates. More on that, later. Customization: Further modifications can be made to the DRM Holotape, such as mod settings (if you have them), change logs (please guys), shout outs (or damnations), instructions (definitely), jokes (if you're funny), cheats (if you need to git gud), or anything else that the user wants to put onto this holotape. It can be made a quest item so it cannot be dropped, you can use F4SE commands to ensure that it's PC only, and if you're really inventive you could make it as an ingestible if you can figure out a way to make it entirely in script (but seriously, why aren't more modders using the damned holotapes? I'm sick of eating my settings configurators! Bethesda gave you an integrated way to make menus on the Pip Boy, this time! USE IT!) Extra Modules: By implanting a private key of a private/public key pair for all to see in an in game menu, and keeping the public key privately held away from either the source code or the executable, you provide double strength protection against decompilation attacks. If the compiler never sees the private key, it cannot be extracted later on. Software capable of achieving this is easier to get than you think, and much easier to use. By linking one's mod into F4SE, using the debug code to turn something crucial on only if on PC, and not providing source code for that feature, you prevent the mod from being used solely through Bethesda.net. Anyone wanting to steal that mod would have to actually be a modder to understand what had been done and how to remove it. A decade of experience from the Nexus shows that modders can steal other modders work, but that it is highly unlikely and will be the source of much controversy and public outcry against the perpetrator, and rarely damages the reputation of the person who has been the victim. This is optional, and does not prevent Bethesda.net downloaders from installing your mod while on PC, as they can install the Script Extender like sane people too from its website, they just can't use Bethesda.net to install it for them any more than one used to be able to use the Nexus to do the same. Note that while this may break the menu on console, it will not break any other content, so can still be used to implant the digital signatures on your running mod. This content would not run on console but it would remain present in the files. You can also use the F4SE option to specifically encode your F4SE menu options, so there is your Triple Word Score. Upload widely: Armed with a mod that contains data only you could have created, you should upload this file as widely as possible. Your signature within the mod declares it to be yours, and the source in your hand proves it. Even if you do not intend your mod to be used on console, it is recommended to upload it there, as well, and set it to private. This ensures that your signature is distributed widely, and that anyone stealing your mod will not be able to claim that they got there first. Remember, you're not giving out your source, so you're not giving them the keys to your kingdom. Vaporware DRM: This technology is merely a technique, and due to its nature no running file or source code can be provided, and only examples given. A template could be created at some point, but the recommendation for proper usage is to create one's own, make it theirs, and never show anyone the exact source code they used to make it. This personal and unique ownership of the source code is both the point of this technology and it's mechanism. Make it your own. Note: This does not prevent mods from being stolen by capable modders who understand the technology and its use. A Decade of experience in the Bethesda modding community shows that these people will be dealt with swiftly and harshly upon discovery. It does however prevent anyone from being able to claim your work as their own in a convincing manner, whether that party is a mod thief, a console kiddie, an elite modder, Bethesda, or even Zenimax. No matter what rights you have to sign away to make your mod, this technique will provide legal standing to prove that you are the creator, because you have the key. Licensing and Copyleft: I hereby release this technology to the people of the Nexus, to all Bethsoft.net subscribers, to all Lovers, to all scripters, to all console peasants and PC doucebags, and to all modders everywhere, with love, in perpetuity, for ever and ever, Amen. Full rights are given for redistribution and modification of this technology without limitation and without credit, just so long as you're not a douche about it. You know who you are, just drop the bomb and back away. FAQ: Q: Will you be making this as a release in some form? A: No. The very nature of this technique absolutely precludes the possibility of anyone else making it for you. You can use a template of some form, but you must do the scripting and compilation yourself for this to work right. Q: But I don't know how to script! A: Learn. The scripting level required to create a basic, working example of this technique is extremely minor. You can learn it within a day, and do it without needing anything more than a text editor and the basic modding tools you already needed to create your mod in the first place. Q: What if my mod only changes game settings or weapon damage? Will this still work? A: You haven't changed anything that you can even set claim to. The only thing that you would be claiming is the DRM Holotape, itself. It still proves that you made that mod, but simple changes to the game settings aren't exactly representative of a huge amount of work on your part. You really don't need this technique, that's not your IP anyways. Q: I hate console kiddies. I want them to die. Will this technique help me achieve that? A: NO. It will not. You're a monster for asking. Seriously, put down the bomb. Q: This mod broke my game. A: No, you broke your game. Do you see the difference? Q: What if Zenimax tries to say the mod is theirs? I'm afraid my content will be stolen for another Bethsoft game. A: Then they won't be able to use your scripts, because that would mean they would have to include your name. Load your Holotape with something that you would need to get your mod working. Consider the source. They probably won't try to steal your content anyways, but they might get inspired by your ideas. Nothing will ever protect you from someone flattering you through imitation. Q: Can't this all just be removed? A: Yes, and that is why you need to make this yourself, keep the source code sacred, and upload the compiled holotape script to as many places as you can. This technique is all about providing you, the content creator, with legal standing to prove that your claim on being the creator is genuine, unique, and solid. Q: Should this thread be stickied? A: I think so, just so long as the comment section doesn't devolve into too much flaming. People aren't going to "like" this, but I hope enough people use it to make it worthwhile. If even one person uses this technique in a mod, I'll be happy. Q: What happens if a really capable modder comes along, and puts his own DRM module on? Does that mean he now has standing? A: No. You have the earlier file. If you have the source, and it's definitely older, and you can show that you made the mod first, and you have your standing. That said, anyone smart enough to do that would not be crazy enough to think it would work. Q: But why should I add a [DRM] tag? None of the mods which tag your items contain that tag! A: Not yet, anyway. Plus, this tag notifies any potential thieves of what you've done and why they should reconsider. Q: Couldn't someone just decompile the PEX file and then grab the original key? A: Yes they can decompile, no that doesn't give the same exact file. This would provide a way to remove your signature, but as long as you've uploaded this mod first, you still have proof that yours is the true claim. This isn't just a Holotape, it's a Holotape, the Source, and the date of upload that are the three key factors that ensure you have the ability to prove that your claim to the mod is the true one. Q: Does this go against the spirit of free exchange of information? A: The DRM can be as permissive or as restrictive as you want. You can even add an entry to the Holotape that declares what you would and would not like to happen with your mod. You can allow free distribution. You can allow modification. You could even claim that it's completely cool to steal your file and ask for donations from it without giving you any credit, if that's what you want. Anything you want to claim in that, you can. Depending upon what you claim, it may or may not be legally binding, but the entire point of this is to provide you with proof that something foul has occured, and therefore the means to do something about it. Q: Are the bonus modules necessary? A: No, but their usage is highly encouraged. Both are platform agnostic, can be used effectively on any platform, and in the case of the Public/Private key pair completely impregnable for the purposes of asserting Authorship over a file. You don't even need to share your mod to assert authorship if the private key and your copy of the source are kept safe enough. Q: This isn't FOSS friendly. A: I just linked you do a GNU product didn't I? What do I have to do, grow a neckbeard? Oh wait. I did. Q: Does this require any external files, mods, or products? A: No. You do not need to link your files to anything made by Bethesda, Valve, Zenimax, GNU, or ENB. You do not need to link to F4SE binaries unless attempting a PC-only build. You do not need to link any DLCs. If you use an external compiler, you don't even need to link to Fallout4.esm. You just need the DRM PEX file in your download, and to keep the source to it sacred. Q: Does this hurt Bethesda or the Bethesda.net mod community in any way? A: I sincerely hope not. In fact, it is my sincerest hope that Bethesda.net finds this technology useful in detecting and eliminating piracy and mod theft, and that the moderators of their download site find it useful in identifying and managing their mod collections.

I have discussed this a bit with someone, and the thought occurs that the best thing you could put into this protected space and withhold the source code to would be a terminal entry or holotape of the EULA of the game, a list of credits and instructions, a change log, and further modifications to the terms and conditions that the modder expects the user to abide by, all accompanied by a digital signature. Depending upon what those modifications are, they may or may not be legally binding, but withholding the source that would have been required to make that document makes that e-signature valid anyways, and proves that you are the author of that mod. As a bonus, this does not require F4SE, can be used on mods actually intended for Console, and if for some reason you are one of the crazy mad multitude that DOES use F4SE, you can use it alongside any other checks for PC-only or to prevent its removal that you feel you need to put in there, should that be your intent. For more bonus points, give it an item tag of [DRM]. Boom.

You just hit what I've been trying to say this whole time. People keep taking Bethesda to task because it hasn't been made clear that this is all stuff that's coming down from Zenimax. These are the same people who preemptively sued Notch for trying to trademark the word "Scrolls".

I should also point out that making NMM require a verified install of the game not being a good idea, since NMM can operate on files which are not FOMM files. You would need to disallow that, and only be able to use those files. This would immediately break its compatibility with files from Other websites, and mean that NMM was no longer a general mod management solution, and just for the Nexus. That basically also means that one could not test that a mod install works properly without first making a FOMM file, instead of people being able to just zip up their loose file packages for quick and easy manipulation. And the biggest problem is that NMM isn't on the CONSOLE, so no matter what the Nexus does, it's not Bethsoft.net, it's not in the game proper, and it won't help stop the problems that have been occurring. Period.

Basically, I think that the entire community has committed a Type A Error in assuming that paid mods would be a bad thing. The problem with the Paid Mods Fiasco on Steam was not that people could charge money for mods. Rather, the entire situation was just poorly handled, and the only party who was set up to truly prosper in that situation was Valve. First, only a select few modders were allowed to post their mods as paid. These were just the early set of people, more Beta Testers, really, but but these slots were offered to the preeminent members in the community, and thus were immediately placed in an unfairly advantageous position. Second, the amount of money that was being paid out was grossly skewed in favor of Valve. Further there was no limitations placed on how much money could be asked for, and the modders were allowed to price their own goods. Those two factors led to prices far in excess of what the mods could have costed, as the mod authors priced their offerings many times higher than the money they wanted to receive, in hopes that since they were only receiving a small slice of the pie, the higher price would mean that they would be more correctly compensated for their efforts. A similar situation occurs in the Health industry, where the Insurance companies pay out only a fraction of what they are asked, leading to situations like having a simple checkup and being charged hundreds of dollars that the Insurance companies refuse to fully pay. Third, and finally, when these problems became apparent, they pulled out. They could have fixed these errors, as none of this is insurmountable or truly a problem inherent in the idea of people being able to sell things they make. This has been a list of errors, and this was the final one. Everyone in the community hated the way it had been set up, and their response was to throw out the baby with the bathwater, issue apologies, take their ball, and go home. That's the worst error, of all.

Exactly! This is a very good solution. It might be less satisfying than using a failed F4SE check to insult the user and destroy their game for some people, but it is far more effective in the long run, and way less shady. It wouldn't work as well for people who aren't making mods that actually add any new resources, but the actual true ownership of such mods is a bit murky anyways. They require no external tools, and operate entirely on material that is certainly owned by Zenimax in its entirety. The stuff you make is the stuff you can own. Modifications of works owned by others is only covered under Fair Use.

Holy crap! Interestingly enough, this is phenomenal for people who don't want their mods to be on XBox, but it requires they upload them FOR XBox. Bear with me, here. For some reason, you don't want your mod appearing on XBox. So what you do is you upload it for XBox, but set it to private. Crucially, if you have any external files, do not provide the source for these. Keep all model files, photoshop sources, uncompiled Papyrus source code, and any other file that you used to create your game resources out of the upload. Now, when someone uploads a version of your mod without your consent, you have an example to point to and say "See? This is the same file! I have the source for the mod right here, and they don't! That's my mod! Take that down, now!" And you will have the standing to be able to do so.

This. Zenimax has made, and indeed can make, no claims on ownership of the PEX format, any more than they can make claims of ownership of the PA32+ format which the engine itself runs on. Files like these are code, running on a particular format, and don't immediately become the sole property of Zenimax unless created within the Creation Kit. Crucially in this case, F4SE mods must have their PEX created by a third party utility, and acted upon by another third party utility. The Script Extender's PA32+ binary format cannot be downloaded through Bethsoft.net, will not work on PS4, and is not allowed to be run on the XBone. And while you have to provide a PEX file for the engine to run, you don't need to provide a PSC file for the user to read. In fact, not providing the PSC file to Bethesda.net removes the possibility of anyone else claiming any ownership of your source code, because they never had it. So by linking one's mod into F4SE, using the debug code to turn something crucial on only if on PC, and not providing source code for that feature, you prevent the mod from being used solely through Bethesda.net. Anyone wanting to steal that mod would have to actually be a modder to understand what had been done and how to remove it. A decade of experience from the Nexus shows that modders can steal other modders work, but that it is highly unlikely and will be the source of much controversy and public outcry against the perpetrator, and rarely damages the reputation of the person who has been the victim. Using that technique, you could even add a fail state that says that this mod is only supported on PC, or if you're a douchy modder you can lambaste people for downloading a pirated version. As it stands, if any random from the internet can steal a mod and upload it and ask for donations, that sets a low bar for the kind of people we're going to have to deal with stealing our mods. Using the above technique at least assures that any villains that we still get are at least Moriarty level, so at least more interesting.

And you're not going to find those on nexusmods.com. You're not going to find them on twitter and you're not going to find them on the bethsoft.net forums or the bethesda.net mod archives. And you're not going to find them because any Bethsoft employees you find cannot make legally binding statements about a Bethesda game. And Bethesda cannot make make comments on something that the lawyers at Zenimax made for them. And Zenimax doesn't come to any of those sites. And any employee that talks out of turn would be fired. We're dealing with three companies in a large corporate edifice, here, and not all of them have a legal department. That's why we've seem Bethesda employees issues statements telling us that DMCA takedowns are our only option for definite removal of mods. They've seen what Zenimax made them agree to. They probably think it's bonkers, and want to see a third party challenge it.

I don't think this would be able to work. NMM already only downloads games through its download system for games which you have, however, you can always download the file through standard means manually, even for games which you do not have. I can, for example, go download stuff for any of those star wars games, put them on my hard drive, open the file up, play with it, but of course cannot actually use the mod as intended because I own exactly 0 star wars game titles. Something which would work is if the CK were able to actually upload a placeholder block. When one published their mods through the CK, if you were able to select "This is for PC only" and to upload only a tiny placeholder to Bethsoft.net for XBox and PS4, saying that this mod is not supported on these platforms.

I'm just saying... PC vs Console wars on the internet. We could all have forseen this. It's not like the best and brightest from both camps are somehow exclusively allowed to play this game. Anyone with an internet connection has the ability to get into this particular rally. If they don't even need to download to downrate a mod, that means they don't even need to actually have an opinion on the mod. They could just be a random from the internet with an axe to grind because "XBox Rulz, PC Droolz", or "Console peasants are scum". And you know I'm not making this up because there are actually concrete examples of all of that happening as we speak, all over this forum.

Because if F4SE is demanding you update something, it means that the version numbers aren't correct. This isn't a texture replacer, it's not going to be compatible with the wrong version. File offsets change when you update an exe file, and f4se will break. Honestly it's a godsend that they added in something that can send out that error message. What you need to realize is that 1.5.205+ are all beta files. They aren't finalized, and they are subject to change. They are not finished products. 1.5.157, on the other hand, is the last stable release that works. All the beta files are a work in progress to get Bethesda.net up and running, they're not tweaks or features or even truly required to run this game on PC (unless you use Bethesda.net (and you're here on the F4SE page on the Nexus, so probably not your primary mod source, neh?)). You need to have the right version of F4SE that matches up with your Fallout 4. Period. There is no way around it. Nobody is forcing you do do anything except keep a matching set of things together. Why is that challenging? You feel forced tho. Did you opt into the beta feature on Steam? Because if so, that's why it keeps breaking; you told Steam that you were okay with this kind of thing, and preferred to have the latest files without regard for stability. Turn that off and stick with the Stable release, from now on.

Look up the console commands. gr quality -1 gr off If it's the aliasing you're trying to remove: gr quality 4 You're welcome.

Then you wont ever download a mod of mine ever again. <snip> You're right. Not when you're literally advocating cyberterrorism. Seriously. Just wow. So yeah. I'm bowing out of this discussion from now on. This has become too toxic, and you're apparently perfectly capable of hanging yourself in a legally binding manner without anyone's assistance.

Ok so to be clear it's stated here: Well that's not the language I recall from the Skyrim CK. If that's the case, then Zenimax's lawyers are pretty stupid. They cannot legally claim ownership of things that their program did not create. Any attempt to claim that simply because the Editor packaged those files for consumption by others means that now they own them is bunk, and would not hold up in any court of law (besides some Texas circuit courts frequented by Patent Trolls, because they hate us for our freedoms, apparently). That would be like someone claiming that The Nexus owns the full copyright to all images linked to in their forums, because the underlying process of linking a mesh file or a texture file to a record in an esp file is mechanically about the same thing. Now, if the esp file links only to cut content, or vanilla meshes distributed with the game, that mod would be the sole asset of Zenimax no matter how it was distributed or packaged, but that's not really what's going on here for 90% of DDProduction83's mods.

You didn't include the definition of terms. What is "Your Game Mods" defined as? Pay attention.

I suppose it would. Just refernce some kind of PC specific record and the mod will infinite load screen when on console. But that seems like a Bad Ideatm. Likely there are not these kind of records anywhere to be had, and it's definitely on grey legal grounds. Not to mention that I, for one, would not download anything knowing that someone put a landmine in there, no matter if the landmine recognized me as a friendly

Read the EULA of the Editor carefully. It only mentions things created with the Editor, which the document defines as the Creation Kit. Any Meshes, Textures, and other files of the kind cannot be created in the Editor, and are merely referred to by the ESP files. Bethesda retains some rights over these ESP files, but makes no legal claim on anything not created in the Editor. Furthermore, archiving a file does not change the copyright holder, as if I were to zip up some of my files, they do not become the property of 7Zip Inc, rather, they retain my copyright. That means that these files, which contain an ESP/ESM and a BA2, contain within them the copyrighted work of Bethesda AND of DDProductions83, and thus should be subject to the laws of copyright infringement if done without the consent or approval of the author. If Bethesda has a problem with that, and they wanted to keep the file up for some reason, they would only legally be entitled to keep the ESP file, which would be useless without the supporting files.

There's a key point that everyone seems to miss here. These people uploading the work of others didn't create anything at all. They merely used these tools to convert them. Additionally, NIFs, DDSs, and any other file-types other than ESP, VIS, and possibly a couple of others that I am forgetting, cannot be created with Bethesda's provided tools. The copyrights of those remain with whatever creator, and there is legal precident to treat these as separate from the plugin. Does anyone else remember the Mass Effect resources issue? When people were taking files wholesale from Mass Effect and porting them to Fallout 3, they were considered to be stolen. They had to have passed through the editor in order to be in the game, but legally speaking they were not at that point the possession of Bethesda. Those mods were taken down for copyright infringement. Thus, the Copyright of any file not created wholly inside of the Editor lies with the original copyright holder of that file, and editing of any file similarly does not change the holder of the Copyright, and at all times this Copyright remains the sole possession of whoever originally created that file and claimed it. Thus, the process of uploading a file does not change its copyright, all files retain their initial copyright through any editing process, and the files uploaded without permission of DDProductions83 retain his original copyright due to the extra file contents that they must contain in order to work. The only acceptable console port of the work of DDProductions83, legally, would be if someone removed any meshes, textures, and likewise any work done by DDProductions83, and uploaded only an ESP file that was created wholly by a third party. In other words, the only acceptable port is a work inspired by his mods, and would be a new mod in and of itself. I rest my case.