Well, it could have been worse. Fallout 4’s all-important script extender modding tool has taken less than 24 hours to be updated to work with the RPG’s freshly released anniversary update. It joins an ever-growing list of mods which have been categorised as updated over on Nexus Mods, while Bethesda are seemingly still looking into issues around the anniversary update’s extra creations stuff not showing up properly for Steam players.
As with last year’s Fallout 4 next-gen update, this re-release playing some degree of havok with mods was guaranteed going in, with Bethesda issuing a specific warning against ones which edit the game’s main menu. As modding platform Nexus Mods predicted, the list of mods requiring updates to work with the new version has been larger than just those.
The most important mod that’d need to be updated was Fallout 4’s script extender, which, like other games’ script extenders, serves as a key backbone of a lot of the game’s more complex mods. The good news is that the F4SE Team led by modder Ianpatt delved straight into analysing the new version as soon as it arrived and have already pushed live F4SE 0.7.4, which includes support for the anniversary update.
Beyond the script extender, 67 mods including the likes of Darker Nights, Better Companions – All In One, the Weapons of Fate ballistics overhaul, and a fix for the game’s infamous rusty face bug have also had their anniversary compatibility updates confirmed thus far. Munitions – Ammo Expansion Project and quest mod Attack of the Lobotomites are others among the updated mods I’d consider if I was starting to rebuild my load order right now.
Oh, and how can I forget the two most important Fallout 4 mods of all time?
Something also worth being aware of if you’re planning on buying Fallout 4 again for some reason is that Bethesda have been having some issues getting creation club stuff included in the anniversary update to show up as useable for those who’ve bought it. Based on the latest message on the topic in the studio’s Discord server, this looks to currently still be affecting some Steam users. If you run into it, following these instructions might help resolve things.
Personally, I’m not even contemplating a return to The Commonwealth until I know I can safely ride my Wolverine-clawed steed across the wastes again.
