Exactly! I hate when people keep saying Bethesda “screwed over” mod devs, as if making a free mod takes precedence over someone who actually works for the game studio being told by their boss to make this update happen.
There’s too much going on at the company for someone to try to track down mod authors to “get their permission”
It would be like you offering me a place to stay and asking if I’m okay with you doing housework. Like I have no say, it’s your house, you need to do regular maintenance.
LordWiggle@lemmy.world 5 days ago
Combining oblivion, morrowind and Skyrim into one game mod: Bethesda broke it. Fallout London: Bethesda broke it. Both very soon after release by an update which was specifically designed to break the mod. Yeah, they do actively break mods to screw too enthusiastic modders who will create more and better content using their platforms, which will show their failure, laziness and not-caring-at-all-about-their-customers-at-all, because they only think of money and how to get as much as much as possible by screwing their customers over again and again. Todd is an asshole and Bethesda is a rotten company which still profits and milks their old successes from the time they weren’t rotten.
BradleyUffner@lemmy.world 4 days ago
WTF are you smoking? It was not “specifically designed to break the mod”. It was specifically designed to coencide with the Fallout TV series on of Amazon prime.
Ledivin@lemmy.world 4 days ago
[Citation Needed]
Zahille7@lemmy.world 4 days ago
How are you even getting upvoted? You’re clearly just talking out of your ass.
Schadrach@lemmy.sdf.org 4 days ago
I’m now curious about this from a technical perspective - how did the update specifically break their mod in particular? Were they doing a bunch of custom DLL hooks or something?
I know with Skyrim SE modding it’s usually that any update breaks SKSE and a tiny handful of other mods that directly hook DLLs or the executable (these mods are usually scripting engine extensions and are a dependency for a variety of other mods), and depending on the update sometimes it takes longer than average to get a new version of those running (the AE update was one of those because they switched compiler version and that broke the method SKSE was using to find hooks). But in general that only breaks 1) mods using those (think SkyUI) until a new version comes out, after which most of those mods start working again without the individual mods needing an update and 2) mods that include their own plugin DLL, (think SkyClimb) which have to wait on an update and then compile a new version of the DLL for the new version of both the game and the other mod, because addresses and functions they are hooking may have changed. Mods not using SKSE or similar generally run just fine between versions of SSE (including AE).
Demdaru@lemmy.world 4 days ago
Full recompilation of exec from scratch - memory positions changed and basically f4se became extremely borked.
Schadrach@lemmy.sdf.org 4 days ago
So basically what happened with the AE release for Skyrim SE where Bethesda switched to a new compiler version and the tool the script extender team was using to find the correct offsets couldn’t handle it so they had to track down the offsets manually like before they’d written the tool, leading to a longer than usual time for the script extender to update than usual?
Which if it’s anything like SSE means that mods that didn’t use F4SE were basically unaffected, mods that use F4SE had to wait for it to update which took longer than usual after which they would mostly work unmodified, and mods that involved a plugin DLL for F4SE had to at the very least be recompiled against the new versions of the game and F4SE. Nothing about that specifically targets Fallout: London though from what it sounds like.