I can't install mods (Starfield)

[helgafinken]

SFBG5004esm and Shattered Space are showing up in red in MO2. I can't install mods. Things don't work! And I get the message that sTestFile entries are present and You have plugin management enabled but you still have sTestFile settings in your StarfieldCustom.ini. These must be removed or the game will not read the plugins.txt file. Management is still disabled.
I am trying to figure it out - but after hours of trying things - nothing works. Help please!

[craigsters]

the shattered space esm is not being managed or recognised properly by Loot and MO2 and you may need to constantly add a asterisk symbol (*) in front of ShatteredSpace.esm in the Plugins text located in C:\Users\16137\AppData\Local\Starfield , I'm having to do this myself too

The ShatteredSpace.esm loses it's asterisk symbol (*) upon game exit and needs to be re-added to the Plugins text, don't forget to save the changes in the text each time you re-add the asterisk symbol (*) in front of the ShatteredSpace.esm

[Avrie]

Originally posted by helgafinken:

SFBG5004esm and Shattered Space are showing up in red in MO2. I can't install mods. Things don't work! And I get the message that sTestFile entries are present and You have plugin management enabled but you still have sTestFile settings in your StarfieldCustom.ini. These must be removed or the game will not read the plugins.txt file. Management is still disabled.
I am trying to figure it out - but after hours of trying things - nothing works. Help please!

What version of MO2 are you using? The current full version (2.5.2) does not support the buggy or Shattered space. You need to update to the latest alpha from the discord.

Here is the current invite https://discord.gg/BtpRD2GR

You're looking for 2.5.3 - Dev Build 2 on the dev build channel. Silarn and holt are on top of things, but to use MO2 for Starfield you'll need to stay current with the alpha builds. They work fine. I'm currently in Shattered space with just over 100 mods installed and working perfectly.

Also you still have some of the workarounds from before plugin management. Time for you to do a 'new' clean MO2 installation.

[Avrie]

Originally posted by craigsters:

Thanks Craigster, but that's mostly a Vortex thing, and LOOT is not needed

[helgafinken]

I haven't been able to do this. Perhaps I'll try Vortex? I don't really care about using LOOT - but I like MO2. Thank you for your reply!

[Avrie]

Originally posted by helgafinken:

I haven't been able to do this. Perhaps I'll try Vortex? I don't really care about using LOOT - but I like MO2. Thank you for your reply!

which version are you using?

[AuddieD]

Temporarily rename StarfieldCustom.ini, making so MO2 thinks there isn't one. You most likely have automatic archive invalidation set in MO2, so let MO2 recreate one on launch then exit the game after it loads. See if you can enable the mods. If there are no problems, check your renamed file line by line to ensure that nothing is actually in there that interferes. If you have Plugins.txt mod, it's not needed any more. These are all just guesses though. I moved Starfield from Vortex to MO2 so I had to do this by default.

[helgafinken]

Originally posted by Avrie:

Originally posted by helgafinken:

I haven't been able to do this. Perhaps I'll try Vortex? I don't really care about using LOOT - but I like MO2. Thank you for your reply!

which version are you using?

I have the latest version now. Thank you for your help!

[helgafinken]

Originally posted by AuddieD:

Temporarily rename StarfieldCustom.ini, making so MO2 thinks there isn't one. You most likely have automatic archive invalidation set in MO2, so let MO2 recreate one on launch then exit the game after it loads. See if you can enable the mods. If there are no problems, check your renamed file line by line to ensure that nothing is actually in there that interferes. If you have Plugins.txt mod, it's not needed any more. These are all just guesses though. I moved Starfield from Vortex to MO2 so I had to do this by default.

Thank you for your reply. I think, somehow I managed to do something - and it seems to work now. I will try to remember your tip about the archive invalidation!