Game Crashes, Help?

[ChronoDoor]

Running on the latest version Stellaris version, here's my Load order incase that matters

[coldheartzero]

So all those Exclamations "!",,,,,, remove those mods and see if the game runs.

 

Those "!" are telling you something is wrong.

[Narbon]

When you install a mod, look on date of upload or when was last update. All old mods are not support current versions. They all can cause some crashes.

[Armchair]

On 3/27/2023 at 6:16 PM, coldheartzero said:

So all those Exclamations "!",,,,,, remove those mods and see if the game runs.

 

Those "!" are telling you something is wrong.

Sometimes all that is "wrong" is that the mod hasn't been updated with the line where the author says that it is compatible with the current version of the game.  In many cases the mod is still compatible despite a lack of updates.  For example, many old portrait mods still work fine on the current build of the game despite not having been updated in years.

 

 

As for resolving the issue, the best way that I know how is to simply make a new mod list and start adding the mods back in one by one until you eventually encounter the problematic mod.  With a large modlist, maybe enable them in small batches at a time to see which batch causes a problem and then backtrack to investigate that batch.

[coldheartzero]

8 hours ago, Armchair said:

Sometimes all that is "wrong" is that the mod hasn't been updated with the line where the author says that it is compatible with the current version of the game.  In many cases the mod is still compatible despite a lack of updates.  For example, many old portrait mods still work fine on the current build of the game despite not having been updated in years.

 

 

As for resolving the issue, the best way that I know how is to simply make a new mod list and start adding the mods back in one by one until you eventually encounter the problematic mod.  With a large modlist, maybe enable them in small batches at a time to see which batch causes a problem and then backtrack to investigate that batch.

 

While that is true in SOME cases, it's not in most cases. And seeing that many errors screams of not knowing what you're doing.

[Armchair]

It depends on the type of mod and not the number of warnings.  70% of the mods in my current mod list throw those warnings.  The mods in question for me are things like portraits, name lists, and flags where the only thing "wrong" is that the *.mod file doesn't list the current version of the game.

 

Some of OP's mods are more in depth than that and change more than mere portraits.  The warnings are something worthy of consideration when trying to debug a mod list but aren't evidence on its own that the mod is bad.

 

Personally I suspect that some of the other LV related mods in the mod list might be causing the problem since Lustful Void looks like it is a more recent release while the later one in the list are older ones.  But as far as troubleshooting the problem I still recommend my original advice of turning off the mods and then start gradually turning them on again.  Starting with #1 in your mod list and working your way along the list.