this post was submitted on 16 May 2024
255 points (93.5% liked)
Games
16806 readers
907 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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...