My mods broke so purged vortex and reinstalled. I Deleted fo76 reinstalled. From my Mod Download folder, I manually dragged and dropped each mod in the order I wanted. fallout76custom was correct and the game ran great. All mods are working, no conflicts.
Then the next day. I fired up Vortex and hit launch FO76. Some mods were broken. I had flesh-colored undies, with tits showing through..... among other things -.- Vortex had (through internal LOOT?) decided it knew better than me and reordered all the mods. (and the order it chose was so dumb) I noticed that most game profiles have a mod order or plugin tab under mods..... FO76 does not. How do I keep Vortex from messing up my mod load/ deployed order?
Is INI support possible? Without support for writing installed BA2s to the custom INI, it's pretty useless outside of update checking. FO76 can't read most loose files.
I have updated the extension for those who have problems modding the gamepass version, when listing the mods you downloaded to the ini in your documents, it qualifies according to the name of the gamepass documents (not fallout76custom.ini.project76custom.ini now) DOWNLOAD
Im experiencing an issue where vortex is no longer writing to the custom ini file (its not read only) I only started experiencing this after trying out another mod manager and switching back to vortex. Does anyone know how to fix this issue.
It will be late but let me answer. you probably used fallout 76 quick configuration. the first thing you need to do is delete the project76custom.ini or fallout76custom.ini file from documents and remove all mods from the mod manager. also enter the fallout 76 folder and found delete the folders created by the mods and verify the game. then start adding mods again. you will see that the mod names are written in the ini.
I don't think this is working? It's saying all the mods are activated and installed but not a single one is working :(. I can see them in the folder but they don't load.
It kind of works by adding the mod files (or rather symlinks to them) to Data folder. However it doesn't add them to Fallout76Custom.ini. So you have to manage your load order manually. While suboptimal, it's still easier, than doing everything manually. It kind of strange and confusing that this fact is not mentioned anywhere, so I wonder if it's broken or unfinished.
Is there any chance of adding support for the Gamepass version of Fallout 76?
It's fully able to be modded, but has a different .exe name from the Steam version. As a result when you try to manage the game in Vortex, it fails to detect. By default (and in the steam version) Vortex expects to find Fallout76.exe. In the gamepass version, the main executable is Project76_GamePass.exe. Beyond that the data subfolder structure and ini file location are the same, so it should just be a question of allowing a different executable name to be detected.
42 comments
From my Mod Download folder, I manually dragged and dropped each mod in the order I wanted.
fallout76custom was correct and the game ran great. All mods are working, no conflicts.
Then the next day. I fired up Vortex and hit launch FO76. Some mods were broken. I had flesh-colored undies, with tits showing through..... among other things -.-
Vortex had (through internal LOOT?) decided it knew better than me and reordered all the mods. (and the order it chose was so dumb)
I noticed that most game profiles have a mod order or plugin tab under mods..... FO76 does not.
How do I keep Vortex from messing up my mod load/ deployed order?
So you have to manage your load order manually. While suboptimal, it's still easier, than doing everything manually.
It kind of strange and confusing that this fact is not mentioned anywhere, so I wonder if it's broken or unfinished.
It's fully able to be modded, but has a different .exe name from the Steam version. As a result when you try to manage the game in Vortex, it fails to detect. By default (and in the steam version) Vortex expects to find Fallout76.exe. In the gamepass version, the main executable is Project76_GamePass.exe. Beyond that the data subfolder structure and ini file location are the same, so it should just be a question of allowing a different executable name to be detected.