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.
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.