270
Fallout 4 mods are broken again following update
(www.eurogamer.net)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 May 2024
270 points (100.0% liked)
Games
16630 readers
522 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
The mods that weren't backwards compatible were primarily the ones that depended on the script extender. This was an unsupported executable that expanded on the commands available to the scripts in the mods.
Not to say unsupported is bad, but everyone was well aware that if they depended on the script extender, they would break if the game updated at all. The biggest mods avoided that dependency for exactly this reason, and really didn't have any trouble. (Sim Settlements still worked the entire time, for example)
And like usual, the community stepped up and updated their unsupported extension quickly, ready for this outcome.
If you made a mod that depends on the script extender and then quit playing the game or supporting your mod, that was a choice you made as a modder. Meanwhile there's mods that haven't seen an update in 8 years that continue to work without issue.
People act like mods breaking after an update is new. Bethesda (and every other dev team) has been doing it since Morrowind (and long before that) The MWSE and everything else were fine back then, too.
I mean, the issue is that the updates fix nothing of value and break mods in this decade old game. Passable update for console, “why did you even try?” on pc.
Yeah, Minecraft updates break mods all the time but there it is just something the community accepts as normal and lives with. The huge update rage is something I only see with Bethesda game modding.
Because Bethesda games are exclusively single player and offer absolutely no way to decline updates. If they had the old version available as a "beta" or (even better) if Valve stopped dying on the "every game must be updated before launching it even single player games because fuck you" hill there wouldn't be any outrage.
Turn automatic updating off for the game in question in Steam, and then set the download rate for Steam to 0 so it can't update when you start up the game.
So you say that you want the gog.com version of the game then?
Without having to re-buy the game, yes. I'd even be willing to pay GOG a bit of money for the cost of hosting the files etc, but I'm not paying Bethesda twice. That's just rewarding bad behaviour.
People have whined about this for twenty years. Yawn
Then perhaps it is an issue that should be remedied?
They've got top men working on it as we speak.
Top. Men.
I prefer my men bottom.
Right, that's really more of a Steam issue than a Bethesda issue. I get why Valve and Bethesda don't want to provide customer support for old versions, but they don't have to. People have been figuring out their own problems when using obsolete systems or software for a long time.
I have no issue with Steam pushing the updates and encouraging you to take them, but giving no way to decline is a pretty poor user experience. Especially when we already know they keep old versions on their servers, as people have made guides on how to downgrade with Steam
Technical question - does the script extender use signature/pattern scanning at all?
It sounds to me that it may have broken because it doesn't use it.
You could say "oh they recompiled it so the registers changed" but I highly doubt they changed the code that much or touched optimization flags.
The next gen update used a completely different compiler, and that created a highly different executable, that's why the update for script extender took so long and that's why the script extender for next gen edition is unable to load "old" script extender mods.
It is the same that happened with Skyrim Anniversary Edition.
Oh this is the "next gen" update? That would explain things.
Oh well...
They actually do fuck up the memory registers. It's essentially the same problem DFHack has whenever Dwarf Fortress gets an update.