New version of Starfield means new problems with MO2

[Artemeissinin]

So there was recently a new version of Starfield which means a new version of SFSE.
Unfortunately there was not a new release of MO2Li, but that's fine.

Sorry if this all comes off as "new", but I'm basically brand new to Linux and just getting to this point has taken hours of "why won't you just ****ing work".

I tried modifying gamesinfo/starfield.sh (and also updated the external resource download to a new version while I was at it), but when I try to launch from MO2 (or directly from the exe), the game fails to launch due to the, now, old version of SFSE being bundled into the game redirecter.

If there was a way of manually maintaining the SE for games with active development such as Starfield, that might help in the future, but the reality is that most of the games that have vaguely active mod development communities have very inactive patch development teams, so it's like watching a meteor shower for the two to be happening at once.

[hughesjr]

There is a plugin called rootbuilder that can help .. but I have never been able to get it to work when using this script to install MO2 on Linux. MO2 plugins, like Rootbuilder, immediately crash MO2 for me if installed.

[Dark-Thoughts]

Since the other issue thread ended up being more of a general SF thread, here's the regular SFSE update steps after a SF update dropped:

• Delete the old _Starfield.exe that this installer created.
• Re-launch the MO2 installer, skip the fresh prefix & backup prompts.
• Confirm that it goes into the same folder path as before.
• Confirm to update it.
• After the MO2 installation, download the latest SFSE package and drop the updated SFSE files into the SF folder.
• Launch MO2 through Steam as usual.