TechAngel85

"Core" and "Baseline" are two different things in this case. Our "baseline" is typically 1K for exteriors and 2K for interiors...though that isn't 100%. As I mentioned, I'm only talking about getting rid of the dated "Performance" and "Extreme" nomenclature. Nothing more changes than deleting two lines of text. I only brought it up to the attention of everyone for simple discussion. I'm not talking about changing anything that is part of the Guide's structure. These two terms were simply never really implemented and changed when we shifted gears towards Packs. Those lines should probably have been deleted a long time ago.

I don't see why you would get rid of Baseline just because those two terms are no longer mentioned or used. That makes no sense to me. Baseline is still used often. I'm just talking about the nomenclature definitions being dropped. Nothing else.

I've added the STEP Patches into the nomenclature section since so many users ask about them and they are no longer an individual mod: https://wiki.step-project.com/STEP:2.10.0#Nomenclature I question whether or not "Performance STEP" and "Extreme STEP" should remain in the section. We haven't used these terms in quite some time in regards to...well, anything really. I think they can be removed without issue. Opinions?

A "patch" is something that make two or more mods work together without conflict. The STEP Patches are the same thing but allow for all the mods in the STEP Guide to work harmoniously together. Everyone should use the STEP Patches who are not creating their own custom patch; even then the STEP Patches can be used as a base for your custom patch. The STEP Patches are installed with the STEP Compilation. The STEP Compilation is a collection of mods which used to be individual mods within the Guide. We've simply combined them for ease of install.

I think that would make the compilation too large. The files from this mods are kind of big.

Install it normally and choose "aMidianBorn Book of Silence UNIQUE ITEMS" as the mod name. Choose "Merge" as the install option. You can just wait until you're done with the Guide to make your Bashed Patch.

If you're asking if you can reorder the INI parameters, then yes you can as long as they all stay under the correct heading. The headings can be reordered as well.

The CSS Extension will be going away with the upcoming wiki upgrade so removing your custom css will help you get a jump start.

If you haven't heard, there is a contest out there for modders: https://contests.nvidia.com/en-us/fallout4modcontest?mkt_tok=eyJpIjoiWXpJMllqSmpZemsyT0RSaiIsInQiOiIyVzZDcFJBNkMrUkxWVnZHUFNOYU1XSmw3RlBqTnRYQnNwWHE2OExnY2RPZDFqMFFyZWtEeWtVdzhPbHBIbldhVmt6NjhuMWxtWWZqQ0E1bGkySDFFUGNvTHdDaERMTWt5MytNeXhQRGVSRT0ifQ%3D%3D Basically create a mod, upload it to Bethesda.net, and then submit your entry using the link above. Top 20 modders will win some goodies!

I seen this the other day and it does look very, very nice! My only gripe is they removed the added weathers from VW and basically only kept the vanilla ones (tweaked). This was for "quality" reasons and the quality is very good, but one of the great features of VW is the expanded weathers.

You can usually just let LOOT sort them.

Better? I have no more firstborns or pie to give...

I was speaking more to the pre-loading of the plugins. The mod page is a bit value as to any benefits and "whys". Why would one need it? As for the memory fix, I'm not touching until I here some "vs" info between it Sheson's patch. If all is well, then this could potentially make it into the Fixes section of the STEP Guide.

I'm curious as to its benefits.

Yes, all lighting and weather mods are compatible.

@Kryptoyr Really a lot of this just went off topic due to our love for an intellectual debate around here (hence the maturity of our community to not go off like you see at Nexus). I will say this though, in reality a mod author has no more right to say "don't list my mod", than a large corporation has the right to tell the newspapers, "don't run that story". As long as no laws or rights are violated it's covered under freedom of speech/press laws in the country that the posting source resides. With that said, you're correct. It's so much about mutual respect in the modding community and that keeps it moving forward. Only a few tend to be on the zealous side of things and end up showing themselves as...donkeys. We all know a few...

I have read the majority of the links (the first one just takes you to the welcome page and not any specific content). I will simply agree that there is too much gray without discussing all this with Bethesda's lawyers. I'm not lawyer and hate the "jargon" used in the documents. It leaves too much open for interpretation by the layfolks. I will say that the Fallout 4 EULA has gotten a little more specific in regards to "Customized Game Materials". So perhaps Bethesda is aware of some of the confusion. I agree with Z, though. You'd be hard pressed to find any substantial mod that isn't to some degree a derivative work.

What I was trying to get across is that by using the formats and/or tools, you are agreeing to the part of the EULA which Z posted above. They own the formats and all references within. I didn't mean they owned the custom assets as I covered that already. But using those assets for the game you are agreeing to the EULA in which you are granting Bethesda the rights to "use, reproduce, modify, adapt, perform, display, distribute and otherwise exploit and/or dispose of the New Materials (or any part of the New Materials) in any way Bethesda Softworks, or its respective designee(s), sees fit". So even if the author still owns the assets, you're granting the rights to Bethesda to basically take your work and reproduce it and use it any way they deem fit. That is as close to giving up your rights to your assets that you can get. Imagine if Bethesda released a new DLC called "other lands" for Skyrim and they are basically an exact copy of Falskarr and other DLC sized mods. What can the authors do? Nothing. Even if the some of the assets in Falskarr are owned by the authors, Bethesda can come in, reproduce them, and release it for sale. It's right there in black and white that you're giving them the right to do this. With this in mind, I would question what actual "rights" the authors actually retain over the mods they produce for Bethesda games. This is all leading back to whether or not the authors have rights to "opt out" of having their mods call out by name on any site, not just Mod Picker and this includes STEP. In my opinion, they do not. Listing a name is freedom of speech/press. They have no say as long as it's not harmful to the mod in question. Basically, offering the "opt out" option is the same as STEP removing mods upon request. It's simply a "courtesy", not a "right" the authors have. Now this is different when discussing distribution, but it's been well established Mod Picker will not be distributing mods itself. Regardless of this intellectual debate on modder rights, Mod Picker will most likely be a great resource if it accomplishes what it's setting out to do.

It's take everything with a grain of salt at this point, until people like Sheson can verify his claims. It was Sheson that fixed the memory issues in Skyrim and that which the SKSE Team adopted so we all know it's good, sound stuff. This...reminds me of a mod a while back (can't recall the name) which as touting all this great stuff and when it was scrutinized it was found to be mainly complete nonsense. I'm not saying this is nonsense, but until we have some verification of the source code...I wouldn't drink the kool-aid.

You are correct. The EULA only covers mods created within the CK, but that includes ALL things created and produced using that tool and its formats. Sound files, textures, meshes, etc created outside of the CK are still owned by the original producer; however, in order for them to distribute or sell such assets they would have to be separated completely from any relation to the game including file formats. As soon as they're used in combination with the game, Bethesda EULA steps in....so as long as you don't associate them with the game, you're good to go to do whatever you want with the files. Where you are mistaken is in regards to the content within their file formats. It's their game and they have complete control what you do with it. That includes what files and content you add into it (CK created content or not). That part is crystal clear in the EULA. The ESP (Elder Scrolls Plugin), ESM, and BSA are all their file formats. By putting your content into their file formats you are agreeing to their EULA. So regardless if you're using xEdit or the CK to create your plugin, they still own it. Packing your assets into a BSA, you're agreeing to the EULA and they own it. At most, Bethesda would probably only issue a DCMA against the content, though, instead of taking outright legal action in court.

No, I don't think we need to do that. The other versions are not part of the baseline install which is what the instructions are laid out for. I do think we should reevaluate the newer versions though (for Extended).

I honestly don't see any authors going for the opt out option, though, since it simply creates more publicity for their mods. The only reason could be for incorrect information that is leading to support issues for them on their mod page. In which case two things will happen. One, the author will log into Mod Picker to correct the issue. Or, two, and this is more likely to happen, the author will opt out. I say the second option will happen more because at that point the author will be at a point of frustration and will likely act irrationally just to stop the misinformation and support issues it's causing. I know there will be things in place to help prevent misinformation, but this is reality and the internet we're talking about here. Misinformation is going to happen.

STEP would remove any mod that its author requested its removal. Such was the case for SRO. Starac did not support the torrents (but couldn't do anything about them). Since STEP used the torrent for this mod and it's author didn't support them, STEP removed SRO from the Guide (which was a major part of our texture replacers). So even in its current implementation, we could technically use Mod Picker. However, we will never do so for other reasons. This doesn't mean we wouldn't endorse it, though, once we have a handle it's ins and outs. Any "STEP Guides" which are posted on Mod Picker will not be official Guides done by our team. Those will only be available via our wiki. There is no other official source for our Guides.

A complete rewrite of the instructions are already complete for the 2.0 beta with new images included. This will be posted when the beta is no longer a beta. For now, the instructions in the page are still good...you just don't the reference images.

STEP:Core is meant to be a base for all modding to happen on top of it so it's meant to be installed as a whole; however, you can leave some out if you want. It's only a Guide, not a Bible. Be aware, though. If you're planning on using the STEP Patches installed with the STEP Compilation, then you are required to have certain mods in your load order.