Wow. not being terribly proficient with modding I found this a nightmare to understand and install. Evrything else is installed automatically and now I have to search through 6 Tb of drives to install this? Thanks for not making an autoinstaller and wasting a couple of hours for me. Don#t know how good it is, as I gave up in the end, Ain't mobody got time for that shit.
This is like... the lowest bar of installing a mod, man. What could you not follow here? Most of this is just basic computing skills, not even modder stuff.
Lol if this was a nightmare to install I'd stay away from modding if I where you. This is prob one of the easiest installations when it comes to modding.
If you are having trouble like I was, just go to your Steam, Right Click on Fallout 4, Properties, Local Files and Browse. It will take you directly to the Fallout 4 Directory and then just drag and drop and you should be good to go.
Don't listen to those dudes telling you you should stay away from modding. The script extender is a verry specific modding tool you need, not many mods require it, so you can still mod other stuff, like simple mesh and texture mods, through the nexus mod auto installer, you don't even have to manually extract the files , the software lets you download enable and disable mods as you please. Cheers.
From the FAQ: "[ FAQ ] * Console version? - No. Not possible due to policy restrictions put in place by the console manufacturers." Sorry bud, ain't gonna happen thanks to copyright.
if you want "real Mods" don't play on console, what is provided half the time is a striped version of what runs on PC. Just save the money and build a pc if you wanna mod my dude
I've installed F4SE with the Nexus Mods Manager, but AAF will not work or open at all, and a message flashes up every time I load saying $NO_F4SE or similar, soo for some reason it won't recognise that it's been installed. Any ideas?
For anyone experiencing the issue of F4SE plugins not loading when using MO2 v2.2.0, go to Executables>Edit and select Fallout4.exe. There is a new function called Force Load Libraries, mark the checkbox and click on "Configure Libraries". Add a new row and select Fallout4.exe as the process and f4se_1_*_*.dll as the library to load. From now on you can select Fallout4 to run the game instead of F4SE since MO2 will force it to load the F4SE dll. All the f4se plugins installed via MO2 should now work ingame.
Nevermind, I got creative. I simply right clicked after selecting all and just moved it to the folder in which my F4 directory is held along with my other games, and then I dragged each file into my fallout 4 directory.
I have now encountered a new issue. When typing the "getf4seversion" prompt into the command prompt bar I do not receive the message "F4SE version: 0.1.1. release idx 1. runtime 010101E0". Instead, I receive "command prompt unrecognized". I would really appreciate any tips or tricks or advice!
Give Feedback
106 comments
What could you not follow here? Most of this is just basic computing skills, not even modder stuff.
"[ FAQ ]
* Console version?
- No. Not possible due to policy restrictions put in place by the console manufacturers."
Sorry bud, ain't gonna happen thanks to copyright.
All the f4se plugins installed via MO2 should now work ingame.
Did as you said, but still nothing changed.