Compilation File

[KainsChylde]

I have an idea for something I want to do, but I figured I'd ask first so as to avoid stepping on any authors toes.

 

I have seen many requests/complaints here about how difficult it is to find all of the sexout mods and install them. People often ask for a compilation mod collecting everything into one package, and are usually responded to with the statement that individual plugins are updated too often and any compiled mod would be quickly out of date.

 

What if someone (namely me) were to volunteer to make and update such a compilation? I'd collect all the mods up, merge any data files (meshes, textures, menus, etc.) and package anything into one file for easy noob installation. I would NOT change any plugin in any way, only gather them together into one install. If anyone wishes their work left out of such a collection I would of course respect their wishes, and I would update my collection file once a week. I would only do a starter file, no incremental updates, and I would only maintain one or two legacy files for rollbacks. Updates would be the responsibility of the user, this would only be a starter package.

 

That was probably a little repetetive, but I wanted to be sure I was clear. What do you guys think?

 

SHORT VERSION: I'm not starting until I have at least the .esm creators' permissions. I'm not changing anything. I'm just collecting everything into one file for noob ease of use.

[ljacquard]

I am definitely voting for (EDIT: provided all the mod authors agree to it, of course. It might seem obvious, but prefer to add it, like you did )

 

Please let me know if I can help (mostly only during week-ends though, I prefer to be honest).

[astymma]

Even though SmallerTalk is not a Sexout plugin, feel free to add it to any Sexout compilation.

[KainsChylde]

Thank you astymma. I consider smallertalk an essential mod and would have asked had you not volunteered.

[Halstrom]

Thank you astymma. I consider smallertalk an essential mod and would have asked had you not volunteered.

I have no problems with you doing so for SCR and Pregnancy, I hope you can keep up

I'd leave Pregnancy out for a month or so till it gets out of beta.

[KainsChylde]

Halstrom, I plan on providing a disclaimer and links to each mods main page. My file will only be intended for beginning installers, they'll have to keep up with updates themselves. I'll keep it updated once weekly, unless a particular mod has a major overhaul and needs to be removed or redone.

[iron_jack]

One of the tricky bits is all the external stuff SCR uses. It requires gigs of external files that can't be included in any kind of compilation because a) authors are not necessarily LL members/even on the scene anymore, and it would render the AIO file waaaay too large for 32-bit FOMM to handle. It's possible to convert FOMM to 64-bit, but the target demographic (new/inexperienced mod users) would have no clue how to do that.

 

Wrye Flash can handle files of any size afaik, but again, not something new users tend to be familiar with.

[KainsChylde]

I do have a plan for that contingency, Iron_Jack. First of all, as I told Halstrom, I plan on providing links to the OP of all the mods I include. Second, there will be a header on my OP stating that it is only a collection and I am not the creator of any of the mods, and that the only materials included are those hosted on LoversLab or filesharing sites like mediafire.

 

I am an active user on Nexus, with mods of my own hosted there. As ban-happy as they are, they are still one of the best sources of mods and utilities and I have no intention of doing anything that will block my own access to those resources

[lindazana]

I don't quite think the required mods are -gigs- large...but perhaps they can be close. I myself would LOVE this to be done, as Try as I might, i cannot get my game just right. I got everything working right, no CTDs, body and most armors have bouncing breasts...but for all I try, my characters skin/texture is all messed up, and refuses to be corrected. So a noob friendly package like this would be amazing.

[KainsChylde]

I'm going to wait until June 17th for anyone to object to their plugins being included, then I'm going to assemble this package. The package will consist of all mods listed in this thread: http://www.loverslab.com/showthread.php?tid=8803

Edit: Any plugins listed as ALPHA/WORK IN PROGRESS will NOT be included until BETA ready. These plugins are usually updated multiple times daily, and with me only updating weekly it could end up majorly out of date in a mater of a day or two.

 

Due to Prideslayer's new FOMOD package, base sexoutNG will be a separate install. He put a lot of work into that, I don't know what mixing it into another package will do to the FOMOD scripts, and I don't want to break it.

 

On the subject of FOMODs. If anyone knows how to make a basic installer that allows a user to choose which options to install, I would greatly appreciate the assistance. Sexout has a LOT of plugins (with the list growing daily) and some players may not want everything.

 

Probably won't be available until around the 20th, due to testing of the package, making sure I don't break anything, etc. Once its up it will be updated weekly. Stay tuned!

[Fredfish]

THis would also be useful to those of us that like to tatally reinstall NV every so often ( I can never remember the proper installation order for everything and constantly changing and updating mods seems to make my game a little instable aftera while)

 

One mod to bring them all and in the darkness combine them!

[prideslayer]

You could use the fomod as is and just copy everything else into it. The script is not sexout specific and is in fact perfectly generic -- it just copies *everything* into the data directory.

 

If you do want it to be a fomod (or fomod ready) though, don't include the NVSE Extender. Both FOMM and Wrye will refuse to install it (FOMM silently, not sure about Wrye these days) because it is an executable (.dll) file. If it is included, the only way to install your download will be manually, which we all recommend against.

 

Good luck, and I hope you're not biting off more than you can chew! Once this is "out there", people are going to expect you to keep it updated. Not as regularly as we update all the mods, but still rather frequently, or else downloading it will be a little pointless.

[prideslayer]

THis would also be useful to those of us that like to tatally reinstall NV every so often ( I can never remember the proper installation order for everything and constantly changing and updating mods seems to make my game a little instable aftera while)

 

One mod to bring them all and in the darkness combine them!

 

There is no install order with sexout or sexout mods. None of the files conflict. It's your nude body, armors, etc that you'll want to make a custom installer for, if you've pieced that stuff together.

 

There isa lot of sexout stuff, sure, but it can all be installed in any order. Only the load order matters, and then only the ESMs : Sexout, SCR, Slavery, Legion.

[KainsChylde]

A question for you all. There are certain plugins/datapacks that need outside resources for full functionality (SCR, Maternity clothes) but will work without the outside files. Then there is Sexout Certified. SC requires Robco Certified to work. Its not optional, no "it'll still work just lose some functions", just have RobCo or don't have SC. Leave it out?

[Guest Loogie]

Sorry I didn't check this sooner.

 

Any plugin I've made is free game to add. Tryout started out as a community gift when Orangey gave it to us and it remains so, even if it only has a couple of original dialog lines left.

[KainsChylde]

So, a few notes.

 

I've got everything collected. I'm working on organising the files in a useable fashion for installing. I've made the decision to leave a few things out.

 

Prides NVSE extender. It needs to be installed manually, none of the mod manager programs available have any clue what to do with a .dll file.

 

Anything non-loverslab DEPENDENT. I.E. if it needs Willow, RobCo Certified, wsex.esm, etc. I can't include those mods, so I won't include anything dependent on those mods.

 

And while SCR and Maternity Clothes will be included, none of the files needed from Nexus will be. See above.

 

I'm almost ready to install and test it. I'll let you guys know how it goes.

[KainsChylde]

Well, with a few minor problems that I'm fairly certain are linked to specific plugins, my installer seems ready to go.

 

Only problem is, its too big. I keep getting a "filesize exceeds upload limit" error. I'm gonna try splitting it into a datapack and plugins set.

 

Before I try again, what is the upload size limit? I may have to break up the datapack, its freaking huge.

[prideslayer]

The maximum attachment size for the forums is 20MB. You can have up to 4 attachments per post.

[KainsChylde]

I may have a problem here. We's a prolific bunch here on LoversLab. All together, the total file size for everything sexout is 290 mb. Updating aside, this project may be too ambitious through sheer size. Any suggestions?

 

Edit: That 290mb? Thats compressed through standard settings with WinRAR. Uncompressed? The data files (not counting ESMs/ESPs) are 1.37 gb.

[prideslayer]

Nobody said it would be easy!

 

Can strip it down some.. there's not much need for sexout itself to be in there, the 'big' files in it almost never change, and it's an obvious requirement, but I don't think that would save you much space.

 

Could host it elsewhere.. mediafire or something I guess?

[KainsChylde]

That may work. The main culprits here, it appears, are maternity clothes and something with the file name AR4SCR20120301, containing st.esp.

 

Maternity is 142 mb compressed, 848 uncompressed. And thats just evil and user's files, not included their recomended downloads from nexus.

 

The other one is 39.9 mb compressed, 138 mb uncompressed. Looks like its the resources for sex toys.

 

You may (or may not) be happy to know, pride, that your fomod comes in 3rd at22.8 mb compressed, 65.7 mb uncompressed.

 

.rar blows. I now know why .7z is the archive of choice. Still gotta split it into 2 files before I can use mediafire.

[KainsChylde]

And now I understand why everyone said it'd be too much work to make a compilation installer. You people work too damn fast!!

 

But, back on topic. I now know the installer will work. Thanks to Prideslayers new Sexout fomod, including that makes mine a fomod too. So tomorrow evening I will go through, get all the most current files to update mine with, and we go live! And then it'll be out of date an hour later

[prideslayer]

Make sure you use the fomod dir from CORE and not DATA, then edit it to suit. The script in that one will activate sexout and put it in the right place. You'll want to modify it to do the same with SCR, Legion, and Slavery ESMs as well of course.

 

And yes.. we all update a few times a week when active, though I try to keep non-beta releases down to a weekly schedule. With all the mods going into this, you'll have to update as often as all of us combined..

[KainsChylde]

I was originally thinking once a week. I may update that to twice weekly. This is only intended as a starter pack, after all. Its up to the user, once its up and running, to keep their files up to date.

 

On the subject of fomods, I was thinking of doing a customizable install. I've seen fomods where you can choose which features you want, and it checks what you already have for things like dependent files, patches, expansions, etc. How hard is one of those to make?

 

Because, for example, I personally don't like SexoutSex. Being able to walk up to anyone, say basically "Hey, lets fuck", and be guaranteed a yes just seems wrong to me. So I'd like to be able to make a fomod where I can chose to leave out that sort of thing if I want.

 

Or then theres Sexout Certified. I'm currently leaving that and Sexout Lobos out, because they require RobCo Certified. And then there's Hard Prison Time. I believe that is dependent on Powder Gangers Tryout. Then theres Sexout Breeder, which is dependent on Pregnancy. I could go on, but I think you get my point.

 

How do I make it so people can install only what they want, don't accidentally install things they don't have the requirements for, and make sure its all in the right order? (I know, I'm getting ahead of myself. I do that.)

[prideslayer]

I was originally thinking once a week. I may update that to twice weekly. This is only intended as a starter pack' date=' after all. Its up to the user, once its up and running, to keep their files up to date.

[/quote']

Works for me. I *try* to keep my official releases to once a week or less often. Betas happen more frequently.

 

On the subject of fomods, I was thinking of doing a customizable install. I've seen fomods where you can choose which features you want, and it checks what you already have for things like dependent files, patches, expansions, etc. How hard is one of those to make?

 

It's not difficult to make them at all, you'll have to learn a little C# scripting. It does make it more difficult for users to manually install, or to use Wrye/Bain to do their installs, if you're not careful. This is why I haven't done it with Sexout itself yet.

 

How do I make it so people can install only what they want, don't accidentally install things they don't have the requirements for, and make sure its all in the right order? (I know, I'm getting ahead of myself. I do that.)

 

You modify the "script.cs" file in the fomod directory. Look online for examples. I've found the one from project nevada to use a *lot* of options, be reasonably well commented, and fairly feature complete as far as what you'd commonly want to do.

 

At the end of the day, the files is simply a full blown C# program being run in the context of FOMM. If you're a programmer, there is basically no limit at all to what the script can do. One of the things I intend to have it do for Sexout, eventually, is connect here to LL to see if you're installing the latest version or not, as a for example.

 

It can also fetch and install the extender if it's missing, getting around the FOMM restriction on executable files in FOMODs.