This ingame mod bulls*** has to stop

[BeingShotAt]

Can we like, seriously petition to have this horse s*** removed from Fallout 4?

I have to re-enable EVERY SINGLE ONE OF MY MODS, EVERY SINGLE TIME I TRY TO PLAY THE GAME, as shown below, reenabling all of my esps and esms for the 1000th time in a f***ing row(and this is after I've done the whole sign-up process that would allegedly prevent this from happening)

 

http://i1255.photobucket.com/albums/hh638/BeingShotAt/thisbullshithastostop_zps9numso5s.png

Modding was so simple and easy before hand, just boot up Nexus Mod Manager, turn on what mods you want, make sure they're compatible, and use LOOT to sort them.

Done

So easy, so simple, what's painful most of all is this is obviously an attempt of Bethesda to gain more control over the modding scene, but all it's doing is making me wish I could refund fallout 4 and get my money back, the hassle is such a pain in the ass.|

I assume this goes on for everyone, I really want to start a petition to inform Bethesda that PC gamer's DO NOT WANT THIS, it's all well and good for console gamers, but for those of us on the PC, Bethesda darlin, please piss off.

The Steam Workshop worked great for Skyrim, and Nexus does too, why not have the same system for this? We do not need this ingame mod bulls*** that further clutters up the modding process with another additional layer of needless complexity that is f***ed as all hell to boot and nowhere near as easy or user-friendly as NMM is.

So tell me, what do you all think?

Edited May 8, 2016 by BeingShotAt

[Reneer]

I've had exactly 0 problems with Fallout 4 disabling my mods. So I have to assume you're doing something "incorrectly" on your end to make that happen.

[Arthmoor]

So tell me, what do you all think?

I think you should find your plugins.txt file and make sure it's not still marked read-only.

 

And then make sure you update NMM to the latest version since that issue was taken care of. Or, one hopes it was.

 

Either way, this isn't the game's fault so there's no reason to remove something that works perfectly fine.

[JetSteele]

I haven't had any disabling issues either on my end.

[dainsgames]

Can we like, seriously petition to have this horse s*** removed from Fallout 4?

 

I have to re-enable EVERY SINGLE ONE OF MY MODS, EVERY SINGLE TIME I TRY TO PLAY THE GAME, as shown below, reenabling all of my esps and esms for the 1000th time in a f***ing row(and this is after I've done the whole sign-up process that would allegedly prevent this from happening)

 

 

 

Modding was so simple and easy before hand, just boot up Nexus Mod Manager, turn on what mods you want, make sure they're compatible, and use LOOT to sort them.

 

Done

 

So easy, so simple, what's painful most of all is this is obviously an attempt of Bethesda to gain more control over the modding scene, but all it's doing is making me wish I could refund fallout 4 and get my money back, the hassle is such a pain in the ass.|

 

I assume this goes on for everyone, I really want to start a petition to inform Bethesda that PC gamer's DO NOT WANT THIS, it's all well and good for console gamers, but for those of us on the PC, Bethesda darlin, please piss off.

 

The Steam Workshop worked great for Skyrim, and Nexus does too, why not have the same system for this? We do not need this ingame mod bulls*** that further clutters up the modding process with another additional layer of needless complexity that is f***ed as all hell to boot and nowhere near as easy or user-friendly as NMM is.

 

So tell me, what do you all think?

 

If their 1.5 patch had retained my game's ability to be played, I would have an opinion. Since it didn't, after a couple of hours of following troubleshooting directions and fixing things, I uninstalled and am now playing a game which works every time I start it.

 

When these ridiculous problems are fixed, I'll try again. In the meantime, I will be happy to support your contention that since Bethesda has had official mod management in their games for much of a decade, and has officially added the same to this game, any problems with running a mod setup which formerly worked is 100% on them.

[Reneer]

If their 1.5 patch had retained my game's ability to be played, I would have an opinion. Since it didn't, after a couple of hours of following troubleshooting directions and fixing things, I uninstalled and am now playing a game which works every time I start it.

 

When these ridiculous problems are fixed, I'll try again. In the meantime, I will be happy to support your contention that since Bethesda has had official mod management in their games for much of a decade, and has officially added the same to this game, any problems with running a mod setup which formerly worked is 100% on them.

So you're blaming Bethesda because an update they made to their game broke the mods you were using and those mods caused your game to crash. Tell me again why this is Bethesda's fault?

 

Bethesda can't possibly be expected to determine if every mod setup in existence will work with their game, just as every mod author can't be expected to test if their mod works with every other mod out there.

Edited May 8, 2016 by Reneer

[gamefever]

 

If their 1.5 patch had retained my game's ability to be played, I would have an opinion. Since it didn't, after a couple of hours of following troubleshooting directions and fixing things, I uninstalled and am now playing a game which works every time I start it.

 

When these ridiculous problems are fixed, I'll try again. In the meantime, I will be happy to support your contention that since Bethesda has had official mod management in their games for much of a decade, and has officially added the same to this game, any problems with running a mod setup which formerly worked is 100% on them.

So you're blaming Bethesda because an update they made to their game broke the mods you were using and those mods caused your game to crash. Tell me again why this is Bethesda's fault?

 

Bethesda can't possibly be expected to determine if every mod setup in existence will work with their game, just as every mod author can't be expected to test if their mod works with every other mod out there.

 

 

Nah your wrong Reneer as long as there are more cry babies than actual mod authors the masses are always right...Rule of the Mob an all.

 

But otherwise I agree with you 100% its sad how these guys think.

 

Anyways

 

I have not had any problems with modding Fo4.

 

Not one bit.

 

Guess some ppl are newbs.

[bionicbadger]

While I don't like Bethesda interfering with the way I want to play my games, and don't buy the argument that as paying customers we're not within our rights to criticize their decision, I think this may be an issue with your installation, not with Bethesda's game.

 

As mentioned above, please check whether your plugins.txt at C:\Users\<username>\AppData\Local\Fallout4 is set to read-only. Next, open it up and place an asterisk before each ESP and ESM except for the main Fallout4.esm, e.g.:

# This file is used by Fallout4 to keep track of your downloaded content.
# Please do not modify this file.
Fallout4.esm
*AwesomeMod.esm
*AnotherAwesomeMod.esp

The mods should load up with no problem for you now.

[Yansai]

Don´t you use NMM?

I use the latest version which fixes these problems and I don´t have to re enable the plugins every time.

[laowai68]

I'm using 61.22 version of NMM and I still need to re-enable everything every time. I will try to disable and re-enable every mod I use, (all settlement/clothing/weapon mods, about 12 to 14 in total) in NMM, but honestly, at this point I'd rather get drunk and watch cat videos on youtube.

 

edit: I found my plugins.txt file, removed the read only flag, and added the *s.

 

I would see if it works, but now I'm drunk and watching cat videos.

 

Thanks Bethesda for making a great game/franchise less fun than substance abuse + mindless entertainment.

Edited May 8, 2016 by laowai68