Permissions regarding Modpacks

[murrrph]

Hi!

 

I got into skyrim modding recently, and after spending about two days downloading every single dependency for every mod in my 'i want this, ooh, and that'-list, figuring out load orders, i have kindof come to realize that its a bit plagued by 'dependency hell' .

 

So i figured I would start working on a modpack, and i have started the slow process of gently spamming mod creators.

 

But i have a couple of questions for the community .

 

1) Do you know of any addons that have clearly labled permissions?

2) What do you think would be the best way to package a modpack?

3) Do you have any suggestions for mods that you would really like to see in a modpack?

4) If you are a mod developer, and you read this, would you give your permission to redistribute your mod, providing nothing is changed? <3. If not, why not? Any suggestions? Anything that would sway your mind, even if it would take a lot of work?

5) Is there anything like this already out there? Am i being a sillybutt?

[pepertje]

A little disclaimer beforehand: I'm not a moderator and I don't know all the in's and out's of LoversLab rules. This is all based on my personal experience and the overall impression I have of the community.

 

In my experience, most authors create mods for the community on LoversLab. I'm busy in the New Vegas scene myself, and mostly it's okay so long as you properly credit the original author, should you use their assets. I'm not too much into the Skyrim scene as an author, but I think it's the same principle: so long as you properly credit the original author, they won't make a huge deal out of it, aside from the fact that a lot of mods are under constant development. If they don't mention that they don't want their mod used, they'd likely mention it on the main page of their file.

As for packaging, be careful what you're doing. Like I said, a lot of mods are actively being developed and it's highly unlikely a large mod you're using (such as sexlab) would go unchanged for more than a couple of months. If I recall it right, it is discouraged to package mods together, since this could cause conflicts. If it's all mods that aren't being developed anymore, I think it could be safe enough, but do know WHY it is no longer being developed, some mods die off because they've become game-breaking.

As for mods in a mod pack, I couldn't really tell, I've got a large folder of LL mods for Skyrim, some of which are the usual requirements and others are just so diverse...

As for redistributing, I don't think NV mods would be of any use to you hehe. In the hypothetical case, sure, so long as you refer to the original page (in case there's been updates, it's mostly a precaution). But personally, I would like to receive at least a notice, that way I'd know someone else is using my assets as intended. This is purely personal, though.

To sum everything up: there are some modpacks, but those are usually from the same author. The reasons are, as beforementioned, that the mods on LoversLab are usually being developed constantly. If you were to package everything together, it could be that a month later, the versions you're using are already outdated. So if you're going to make a modpack, make sure you keep a close watch over the mods you're using and update the ones in your own pack.

 

I can't stress this enough: I'm no moderator, so I could be mistaken somewhere in here.

[murrrph]

A little disclaimer beforehand: I'm not a moderator and I don't know all the in's and out's of LoversLab rules. This is all based on my personal experience and the overall impression I have of the community.

 

In my experience, most authors create mods for the community on LoversLab. I'm busy in the New Vegas scene myself, and mostly it's okay so long as you properly credit the original author, should you use their assets. I'm not too much into the Skyrim scene as an author, but I think it's the same principle: so long as you properly credit the original author, they won't make a huge deal out of it, aside from the fact that a lot of mods are under constant development. If they don't mention that they don't want their mod used, they'd likely mention it on the main page of their file.

As for packaging, be careful what you're doing. Like I said, a lot of mods are actively being developed and it's highly unlikely a large mod you're using (such as sexlab) would go unchanged for more than a couple of months. If I recall it right, it is discouraged to package mods together, since this could cause conflicts. If it's all mods that aren't being developed anymore, I think it could be safe enough, but do know WHY it is no longer being developed, some mods die off because they've become game-breaking.

As for mods in a mod pack, I couldn't really tell, I've got a large folder of LL mods for Skyrim, some of which are the usual requirements and others are just so diverse...

As for redistributing, I don't think NV mods would be of any use to you hehe. In the hypothetical case, sure, so long as you refer to the original page (in case there's been updates, it's mostly a precaution). But personally, I would like to receive at least a notice, that way I'd know someone else is using my assets as intended. This is purely personal, though.

To sum everything up: there are some modpacks, but those are usually from the same author. The reasons are, as beforementioned, that the mods on LoversLab are usually being developed constantly. If you were to package everything together, it could be that a month later, the versions you're using are already outdated. So if you're going to make a modpack, make sure you keep a close watch over the mods you're using and update the ones in your own pack.

 

I can't stress this enough: I'm no moderator, so I could be mistaken somewhere in here.

 

Thats some pretty darn good points right there. Hmm.

Not going to redistribute any mods without the authors explicit permission (The mod developers can't really tell if i am a disrespectfull arse that uses their hard work without asking, or if i am trying to raise them up, so I certainly feel like asking first might be a good thing )

 

But keeping the pack updated, yes, i can see how that would be extremely important. Should probably set up a watchlist for threads, and also invite the developers to have the opportunity of doing something like, say, a pull request on github or similar.

 

Also links to all of the official sources in some obvious way, along with thank-thank-you-notes.. Yes. Hmm. Maybe an updater if i get my thumb out of my arse. That could be usefull .

[yatol]

1) Do you know of any addons that have clearly labled permissions?

2) What do you think would be the best way to package a modpack?

3) Do you have any suggestions for mods that you would really like to see in a modpack?

4) If you are a mod developer, and you read this, would you give your permission to redistribute your mod, providing nothing is changed? <3. If not, why not? Any suggestions? Anything that would sway your mind, even if it would take a lot of work?

5) Is there anything like this already out there? Am i being a sillybutt?

 

1) eveything is a copy paste of something else, so... nothing really have that permission thing from the original author^^

2) loose file, if modpak have mod x version 1.4 in bsa, and dumbass that don't bother reading have mod x version 1.2 in loose file, dumbass will whine about it, dumbass 2 will do the same, dumbass 3 will do the same... and it never end

3) don't waste your time doing something you don't intend to use

4) you only heard about the ones that want their name on everything that use something from on of their mods, but few really care about that

5) there's some here and there, but few bother uploading that, as it's only problems

 

[Kendo 2]

4) If you are a mod developer, and you read this, would you give your permission to redistribute your mod, providing nothing is changed? <3. If not, why not? Any suggestions? Anything that would sway your mind, even if it would take a lot of work?

There is no reason to repackage someone's entire mod.  Make it a required file instead.  That removes the need for permissions other than contacting the original author as more of a courtesy than anything else.

Not repacking mods also keeps your download size smaller, prevents more load on Ashal's servers and allows the original author to enjoy the fruits of their labor.  It also absolves you of any problems that might be associated with said mod.  Conflicts, scripts not working and other issues are not yours to deal with.  And even if they were, would you know the answers to people's questions and trouble shoot a mod you didn't author?  Why would you want to?

 

And you have to remember the fan base you're dealing with.  People do not read install instructions, they are smarter than anyone else (or so their mommy's have them thinking) and they are entitled to what they want when they want it.  Do yourself a favor and avoid repacking mods you didn't make, even if the original author gives you permission.

[Nergui]

Remember to write a "readme.txt" and add that to your archive, even if most people won't read it. Some of us do read them and are disappointed when one isn't available.

 

Basically, what the mod does, how to install, how to uninstall, your permissions and most importantly credits.