I'm going to hop back to the zone for now, see you later commonwealth.

yeah those whining idiots will spend weeks on the forums instead of blocking the updates for thier lovely boobymodes forever

Originally posted by Xenophobe:

from the river of tears of those that again didn't protect their modded game from unwanted updates ... seek higher ground.

Ah yes, time to get my rubber dinghy.

i followed a guide to do it but its still wanting to update. big sad.

edit: nvm im dumb, it worked lmao

It feels great to block updates and safely preserve my mod list. It's very comfy in this update bunker. *plays wanderer on diamond city radio*

Very confusing how folks don't block updates.

Originally posted by Spagooty:

i followed a guide to do it but its still wanting to update. big sad.

Did you make the appmanifest file read only? That's the winning move.

Currently busy playing Palworld, obviously I will have to re-install Fallout 4 if I ever feel like playing the game again.

Saw this coming MONTHS ago after the Anniversary so I made a backup for all of my favorite mods on a separate thumbdrive, JUST IN CASE.

I now developed a habit to just use simple mods that did not rely on F4SE such as mods by Neeher.

In short, I'm now merely another spectator watching this... Flood, as the OP put it,

All I'm waiting for is to make sure that f4se still knows what it's doing, because frankly last time I fretted, turned out *everything works fine* what a surprise.

Honestly the update list looks *fantastic*. For EVERYONE. Mod makers, users, and console kiddos to boot.

Originally posted by Neo:

Originally posted by Spagooty:

i followed a guide to do it but its still wanting to update. big sad.

Did you make the appmanifest file read only? That's the winning move.

i did this and it still says "update queued", is it supposed to do that? what does making it read only actually do

im launching the game via MO2 running F4SE so i wont be affected but i dont actually know the reason behind making it read only

Originally posted by Mad Matt Dog:

Originally posted by Neo:

Did you make the appmanifest file read only? That's the winning move.

i did this and it still says "update queued", is it supposed to do that? what does making it read only actually do

im launching the game via MO2 running F4SE so i wont be affected but i dont actually know the reason behind making it read only

Because steam will balk at trying to change it if it's read-only. This IS the key to making sure that if you screw up (by hitting the PLAY button or trying to launch your modded game before launching steam) it'll still have trouble enough not to push the actual update on you.

Originally posted by Zekiran:

All I'm waiting for is to make sure that f4se still knows what it's doing, because frankly last time I fretted, turned out *everything works fine* what a surprise.

I really wish F4SE adds "current F4SE doesn't match actual game version. It may lead to bugs / corrupted saves. Are you willing to continue?" warning and allows to launch updated game. I presume CC updates has no impact on the gameplay, so artificial impediment should not take place.

Originally posted by 🎮 PalkoVvodets 🔑:

Originally posted by Zekiran:

All I'm waiting for is to make sure that f4se still knows what it's doing, because frankly last time I fretted, turned out *everything works fine* what a surprise.

I really wish F4SE adds "current F4SE doesn't match actual game version. It may lead to bugs / corrupted saves. Are you willing to continue?" warning and allows to launch updated game. I presume CC updates has no impact on the gameplay, so artificial impediment should not take place.

That might be something that should be suggested to them? It does seem like a good thing but the fact that it'll just outright crash or not start seems pretty clear when I tried it a while back.

Originally posted by Zekiran:

That might be something that should be suggested to them? It does seem like a good thing but the fact that it'll just outright crash or not start seems pretty clear when I tried it a while back.

Last time I've launched with outdated F4SE there was warning that F4SE doesn't correspond new version and the game didn't even launch. There were crashes back in the day? Hm, perhaps the mod operated specific part / signature of memory or something.

Originally posted by 🎮 PalkoVvodets 🔑:

Originally posted by Zekiran:

All I'm waiting for is to make sure that f4se still knows what it's doing, because frankly last time I fretted, turned out *everything works fine* what a surprise.

I really wish F4SE adds "current F4SE doesn't match actual game version. It may lead to bugs / corrupted saves. Are you willing to continue?" warning and allows to launch updated game. I presume CC updates has no impact on the gameplay, so artificial impediment should not take place.

If it was that easy they would have done it. But with how a SE works it will just crash the game every time.

Originally posted by Mad Matt Dog:

Originally posted by Neo:

Did you make the appmanifest file read only? That's the winning move.

i did this and it still says "update queued", is it supposed to do that? what does making it read only actually do

im launching the game via MO2 running F4SE so i wont be affected but i dont actually know the reason behind making it read only

the update will remain queued as long as the appmanifest_377160.acf file is not updated to the latest version ... I make a copy/paste backup of my Fallout 4 folder, let the game update in steam along with the appmanifest_377160.acf file, delete the Fallout 4 folder from steam and copy/paste the backup in it's place ... steam sees the updated appmanifest_377160.acf file, won't try to update it until the next update/Beth-bomb drops and the older version works as before (just don't verify game files).