packaging mods, contacting the author, rules

[Lord Valarian]

Hello. You properly reference all mods. Noting what's your changes and additions. Now about contacting the author, you have to get permission for each mod used in the package/mods? What if you can't get in contact with the author in reasonable period of time? What is the amount time you need wait?

 

 

For some, just packaging it with a omod conversion data written by me(couldn't find them). For example, Cyrodiil Transportation Network, I created a package:

 

CTN+v1.31 patch+omod conversion data + (proposed teleport location patch for 'frostcrag reborn').

[Thandal]

... Now about contacting the author, you have to get permission for each mod used in the package/mods? What if you can't get in contact with the author in reasonable period of time? What is the amount time you need wait?

In the US, the default copyright period for new works is "the life of the author +75 years."

 

While not trying to spark a debate about whether mods can be copyrighted, (see "derivative works") the principle is the same: If you didn't create it, and the author didn't give other explicit authorization, then you have to obtain permission before you can include/redistribute it.

 

These are The Rules here on the Nexus. :armscrossed:

 

(See the ToS, link in the top-right of every page.)

[Lord Valarian]

Most mods aren't, but I see your point. Some of require 3+ downloads. It's a real pain. Packaging all together in one file would be better. It's a long list of mods to contact. So, I'll private mail them and see what happens. I'll check the read me too. CTN is a great mod that would made better by packaging it. Here goes nothing....

 

Done.

[bben46]

From our Terms of Service

Do not upload compilations of other users work irrespective of whether the authors of the work you would like to compile together have agreed to your using their work in your compilation. For example: no "my favourite mods" lists or "best weapon" compilations.

 

Mod compilations are never a good idea. While on the surface it looks as if it would save a lot of time and hassle, it actually causes many more problems than it solves.

 

First, getting modders permissions. Many mod authors don't want their mods included in a compilation because they actually want real credit - in the form of downloads and endorsements for their mod which they will not get if it is in a compilation. The only one that gets any credit for a mod included in a compilation is the uploader of the compilation. Just saying I give credit to whoever does not give them any endorsements of their mod or credit for any downloads.

 

If you have more than a dozen or so mods in your compilation it can easily be so big that it boggs things down when trying to upload or download.

 

Just because the compilation works on your system that is no reason to expect it to work on someone elses system that may be quite different. This can be a serious problem if you have a very good system that is optimized for playing the game, and the person with a slow internet connection who just spent 3 hours on downloading a humongous compilation has a weak system that is not very well optimized for the game.

 

If any one mod in your compilation is updated by the original author, then the compilation is out of date and the compiler must redo it - that can take a couple of days that the users don't want to wait.

 

If any one mod has a game breaking bug, that renders the entire compilation useless untill that bug is fixed and the entire compilation is redone and reuploaded.

 

If any one mod in your compilation conflicts with any other mod not in the compilation that the user wants - they must uninstall the compilation, find and download each mod individually leaving out the conflicting one.

 

If the user doesn't want to use just one of the mods in the compilation for some reason, then they will have to uninstall the entire compilation and redownload each mod they do want individually.

 

If Beth or Steam update , there is a high probability that at least one mod in the compilation will cause a crash because of some incompatibility with the new version - making the compilation useless until fixed again.

 

If you ever decide to stop supporting your compilation with updates to fix all of these problems - around twice a week or more, then the people who use your compilation and depend on you to keep it up to date are SOL

[Lord Valarian]

Good points all. Hmm, i'll think about it. CTN is packaged neatly, one omod. I need fix the order using loadafter and patch the teleport bug. It's a hassle to put all those pieces together. At least I don't have to again. :)

 

There has to be a way have mod compilations without the downside. Users can group mods together that work well together. Not zips, but

 

UL170 is great, I have 10+ landscapes all together without problems. Not together as zip file, but downloads all files at once(or in sequence). I would never have gone through the hassle of downloading one at time and testing each one. ACK! It took downloading CTN+patch then writing the omod. Superlink: download group - CTN+patch+omod

 

Here's a good example. It took me a while to find all three. These oblivion crash preventers and OSR work well together:

 

Folder: Handy Oblivion additions

--Fastexit

--Oblivion Crash Prevention System

--Oblivion stutter remover

 

User recommended group of mods: A (superlink) and that downloads(and gives credit) all of them at once. Vs click mod-click download(3+ times). It also lists the links to normal view mod page. You now have all three at once(3 mod files) in one link. Mod owners get download credit and users get a time saving shortcut.

 

UL170, I had to patch it to make it work with frostcrag. UL170 superlink downloads all the mods in sequence, making a folder in process. Where you would download the massive zip file, the mod owners wouldn't get credit for the downloads. Here the mod owners get the download credit and users get the hassle free downloads. UL170 grouped together all the landscape mods downloaded you know play nice together.

 

If there is an omod to put together the package, it's added to the download list(by the user making the download link package).

 

The tech details would have worked out. Consider it... ;)

 

You still have to put it together at least once, but better anyway.