Why have you removed one of the game's most important features?

Work Around:

1) Open Nexus Mod Manager (you will need this!)
2) launch your game, wait in the launcher before starting the game.
3) Renable the mods using Nexus Mod Manager (you will notice launching disables them)
4) Hit play.
5) Play your game, you paid for your way!

This was reported in the patch beta. One theory was they took away support until the release of the creation kit.

Then they better release the CK fast, and by fast I mean like by lunchtime.

No, the theory is that they don't want mods to interfere with Beta patch testing. They likely just forgot to renable them for the live patch.

Probably February or around then. Use the NMM workaround til then. Or Wrye Bash if that's out yet for Fallout 4.

Edit

OP, that's a theory within a theory, because someone else suggested they removed it by mistake.

Either way we probs won't get official comment be great if we did though.

Bloody hell, you gotta be kidding me, it's like the 3 stooges are doing the patching. Ty for the heads-up OP.

My mods work. 1.2.37.0

Well as somebody already posted there is a workaround for the issiue but meh seriusly how the hell can you forget that in the patch from Beta,

Mine as well, just checked. But all, well the few I actually got, where manually installed. How about you jasper?

I had to use workaround otherwise most of them didnt work. Am not using many mods atm only a couple and 3 out of 4 dont work without the workaround.(all of them were NMM instaled)

Mine are deactivated too.

Another workaround : set the C:\Users\UserName\AppData\Local\Fallout4\plugins.txt file as read only. It stops the game resetting the file at startup, but you'll have to set it back to read/write for installing and uninstalling mods.

Note that some mods like texture mods that don't use esp files should not be affected by this problem

Also another thing to say about the patch while it is great they are fixing stuff they cud have fixed some of the bugged perks as well since those are basicly just wrong numbers put into the equation(like killshot perk etc..., took moders without proper tools few hours to find it and fix it so i am sure it wudnt take more than 5 mins for a developer with correct tools)

I'll send GStaff a PM.

Have Nexus Mod Manager running in the background.
After launching the Launcher, tick the mods back on.
Hit play.
This works for me, but it needs to be done every time you start up the launcher.

Thats the more permanent solution but youll still have to change it anytime you want to install new mods, or update your current ones.

Do they even test their patch ? They are aware than a lot of modders work now for mods to correct HUGE mistakes of game design, and the devs don't seem to allow this (auto moderation) ?

You must set to "read only" not even the plugins.txt but also all the profile's INI files (fallout4.ini and fallout4prefs.ini) and the default one in the game's directory fallout4 subdirectory (fallout4prefs.ini). If not, the launcher resets them also. Weird ...

I used NMM to install some of them. Others were installed manually.

Would be nice to hear something from them. Is this intentional? A mix-up? If so when are they planning to fix it?

I doubt its intentional probably just a leftover form Beta state which they overlooked and it can be circumvented relativly easy its just a hassle.

On a side note i also wish damn Steam wud allow an option of just notifying you when patches are released instead of auto applying them, since its not unknown that sometimes patches can cause issiues especially for people who use mods,.(so you might want to wait few days before instaling it for moders to make their creations compatible with latest releases)

I've asked him if it was intentional, and I'll post if he comes back to say it was a little mistake or something. Hopefully it's just an oversight. I'm sure he'll make a post/announcement about it, he may not have even known.

Thanks. I can't imagine that is was anything but unintentional, no need to rake them over the coals here. Just hope they speedily address the issue.

You manually set them to read-only? Because apart from being manually installed and rechecking the read-only box in the .ini file I didn't do anything else.

I really hope it's the case but ... Well, when you add the fact that your INIs are reset to default, it may be totally intentional, not a mistake.

And the patch didn't solve the problem (for a non QWERTY user) of personnalized key mapping.