Custom.ini changes crashes game on start up

[RedBoxHero]

So I'm trying to mod the game and I'm putting the correct changes in archive under customs.ini in my docs. But when I alter it the game won't go past a black loading screen.

[Rabidnid]

Originally posted by swfcris:

So I'm trying to mod the game and I'm putting the correct changes in archive under customs.ini in my docs. But when I alter it the game won't go past a black loading screen.

I would go back to where you got the change from and ask there. I've not modded 4, but NV and 3 pretty much do the same thing if the ini is changed.

[Jonny Sparta]

you can definitly get away with warping the INI's in all sorts of ways but any errors in how you write it might cause something like that idk, just make sure you've got it written in perfectly.

double check you plugins to make sure you've got all your required master files as well, i know missing masters can cause issues before you even get into game, though i think it'll usually just crash

Originally posted by Rabidnid:

I would go back to where you got the change from and ask there. I've not modded 4, but NV and 3 pretty much do the same thing if the ini is changed.

don't listen to this guy, you can get tons of modding assistance here

[Licensed To Thrill]

I want to help you dude, but you have to be more clear than that.

"customs.ini" -- make sure it's under Fallout4Custom.ini

You, "made the changes" -- please list the changes verbatim! so I can determine if they were done correctly.

-------

Here are the proper changes for anyone else reading this.

On Windows, go to your Documents folder. I won't tell you how to find that. LOL

Open up the folder inside of that called My Games.

Inside of My Games is a folder called Fallout4. Open that.

Inside of Fallout4 there is a file called Fallout4Custom.ini. Open that.

If Fallout4Custom.ini does not exist, follow these steps in this order:

1. a. Run the game. Past the "Play/Options/Exit" menu.
1. b. That means your game should start ALL the way up the point where it says, "New Game", "Load", or possibly "Continue". Actual game, not the small rectangle splash menu.

2. a. Go back to the folder I mentioned above and look for Fallout4Custom.ini
2. b. If it's there, then good! Skip the next step.
2. c. If it's NOT there, go to the next step.

3. a. Create a text file. (Right-Click -> New -> Text Document). Name it anything.

3. b. Inside of Windows Explorer (Windows explorer is the yellow folder icon / program that let's you browse your files and folders. No, it's not called "My Computer" but people call it that anyway.) -- Make sure Windows Explorer folder options have the option UNchecked that says, "Hide file extensions for known file types." If you don't know how to do this, you are probably going to fail at modding your game. But if you want to learn! Google, "Windows folder options" or "Windows show file extensions".

3. c. Left-Click the text document that you just created in step 3. a. so that it is highlighted. Press F2, and it will let you rename it. Rename the ENTIRE name (including .txt) to "Fallout4Custom.ini" - no quotations, obviously. Fallout4Custom.ini. I repeat. No quotations.

-------------------------------------------
----- Back to the Tutorial ! -------

Open Fallout4Custom.ini

Do you see the section headers? Those are the things labeled like, [Display]. These denote the TITLE (heading) of the section, and surrounds them with brackets [ ]. So all Display settings are under [DISPLAY] or [Display]. Duh.

Is your file blank? No worries! Keep following.

Do you see a section that says, [Archive] or [ARCHIVE]?

If not, add one to the end! Make sure you add a double-enter (double line break) to the end of the file so that an empty line is ABOVE [Archive] and BELOW the final line of the file.

Now we will add a line underneath [Archive] to add a setting to that section. Two settings, actually.
Or, if they are already there, then we will CHANGE those settings.
This is the part that "makes it work".

If you have these lines, change them. If not, add them. Always keep a blank line before any [SectionHeaders]. If that sentence was confusing to you, then you have not been paying attention, or you are so deeply confused by computers that you SHOULD NOT be doing this.

Okay, here are the lines to ADD or MATCH (with a change). Matching these lines may include DELETING words and symbols. This is normal!

Your Archive section should MATCH this, however you achieve that.

[Archive]
bInvalidateOlderFiles=1
sResourceDataDirsFinal=

Yes, there is literalliy NOTHING after sResourceDataDirsFinal. The = symbol has nothing behind it. This is correct.

There you go, you did it, champ! Give yourself a belly rub or whatever humans do and go conquer the Commonwealth. I mean, err... help restore the Commonwealth. Not that conquering stuff. Don't tell the humans we do that. The tasty humans won't trust us if we tell them.

[ronr42]

It's Not the 3 lines you added to the Fallout4Custom.ini that is causing the crashing. It's the Conflicting mods you installed that became active once you added those 3 lines.

[RedBoxHero]

Originally posted by Jonny Sparta:

you can definitly get away with warping the INI's in all sorts of ways but any errors in how you write it might cause something like that idk, just make sure you've got it written in perfectly.

double check you plugins to make sure you've got all your required master files as well, i know missing masters can cause issues before you even get into game, though i think it'll usually just crash

Originally posted by Rabidnid:

I would go back to where you got the change from and ask there. I've not modded 4, but NV and 3 pretty much do the same thing if the ini is changed.

don't listen to this guy, you can get tons of modding assistance here

I found the issue. I read somewhere the adding STRINGS/ to sResourceDataDirsFinal= in the custom ini file fixes the issue. Everything seems to be working fine now.

[RedBoxHero]

Originally posted by Jonny Sparta:

you can definitly get away with warping the INI's in all sorts of ways but any errors in how you write it might cause something like that idk, just make sure you've got it written in perfectly.

double check you plugins to make sure you've got all your required master files as well, i know missing masters can cause issues before you even get into game, though i think it'll usually just crash

Originally posted by Rabidnid:

I would go back to where you got the change from and ask there. I've not modded 4, but NV and 3 pretty much do the same thing if the ini is changed.

don't listen to this guy, you can get tons of modding assistance here

I found the issue. I read somewhere the adding STRINGS/ to a part of the custom ini file fixes the issue. Everything seems to be working fine now.