Fixing the script extender itself won’t take that long as it doesn’t need to hook that many functions (although depending on how much free time people have and whether there are any surprises, it could still take longer than most people expect). Fixing all the mods that depend on it will take much longer, as between them, they hook lots more functions than the script extender itself, and with this update, it’s not just a case of most functions being the same, but at a slightly different address (as was typical with creation club updates, which tools could help with), but instead lots of functions have changed slightly due to using an updated compiler, and lots of functions have been inlined differently (so instead of just existing once, they get copied into every function that uses them, and then optimised differently in each place based on the surrounding code).
So what I’m understanding from reading everyone’s outrage and input on this, is that Fallout London may or may not come out because of this, but more importantly, just wait a little while after the update to try out mods, just like every other Bethesda game update?
Little while could be a long while for some mods and maybe never for others. I wouldn’t be surprised if some mod developers don’t go back and fix it if they had moved on to other projects. These mods will be years old and anything that uses the script extender will have advanced features to it so they’re not a 3 minute quest mod using only existing assets found in the game itself.
Yeah this is the likely outcome. Happens all the time, tons of great old Cyberpunk mods broke with 2.0 and will probably never get updated for example.
This kind of mod is always a DLL of some kind, and typically, they’ll have you install the DLL to a location that the script extender will load DLLs from automatically (but sometimes they instead use the same name as a Windows DLL and go in the same directory as the game’s executable, as when the game tries to load the Windows DLL, it’ll try ones in its own directory before System32 and similar folders, then as long as the mod DLL in turn loads the real DLL, everything will still work). When the DLL’s loading, it’ll either overwrite bits of memory corresponding to functions with its own code, or if it needs to replace the whole function, will swap out the first few instructions with instructions to jump to a mod function instead.
Fixing the script extender itself won’t take that long as it doesn’t need to hook that many functions (although depending on how much free time people have and whether there are any surprises, it could still take longer than most people expect). Fixing all the mods that depend on it will take much longer, as between them, they hook lots more functions than the script extender itself, and with this update, it’s not just a case of most functions being the same, but at a slightly different address (as was typical with creation club updates, which tools could help with), but instead lots of functions have changed slightly due to using an updated compiler, and lots of functions have been inlined differently (so instead of just existing once, they get copied into every function that uses them, and then optimised differently in each place based on the surrounding code).
So what I’m understanding from reading everyone’s outrage and input on this, is that Fallout London may or may not come out because of this, but more importantly, just wait a little while after the update to try out mods, just like every other Bethesda game update?
Little while could be a long while for some mods and maybe never for others. I wouldn’t be surprised if some mod developers don’t go back and fix it if they had moved on to other projects. These mods will be years old and anything that uses the script extender will have advanced features to it so they’re not a 3 minute quest mod using only existing assets found in the game itself.
Yeah this is the likely outcome. Happens all the time, tons of great old Cyberpunk mods broke with 2.0 and will probably never get updated for example.
So how do they hook into the game, is it through the .DLL libraries?
This kind of mod is always a DLL of some kind, and typically, they’ll have you install the DLL to a location that the script extender will load DLLs from automatically (but sometimes they instead use the same name as a Windows DLL and go in the same directory as the game’s executable, as when the game tries to load the Windows DLL, it’ll try ones in its own directory before System32 and similar folders, then as long as the mod DLL in turn loads the real DLL, everything will still work). When the DLL’s loading, it’ll either overwrite bits of memory corresponding to functions with its own code, or if it needs to replace the whole function, will swap out the first few instructions with instructions to jump to a mod function instead.