Is there a plan to make the launcher so it says what mods are and aren't compatible/updated for the current patch like the old launcher? It would help keep the game stable
So it would seem that mod load order is now determined by ther order in which you enable mods. I did a test on a compatibility patch:
--Test Case 1--
1. Enabled compatibility patch
2. Enabled mod
Moad load order ended up being in (dlc_load): .."compatibility_patch_mod.mod","mod.mod"
Result: Compatibility patch mod was not applied
--Test Case 2---
Did the opposite thing:
1. Enabled mod
2. Enabled compatibility patch
Moad load order ended up being in (dlc_load): .."mod.mod","compatibility_patch_mod.mod"
Result: Compatibility patch mod was applied
--Test Case 3---
Using enable mods function seems to randomize mods in dlc_load as well. I didn't even bother trying to figure out the logic behind there.
What would be an expectation of the behavior:
The dlc_load should respect the order in which the mods are actually ordered in the mod selection screen. This will cause lots of false reports to mod authors, it will break backwards compatibility...
Your mod launcher is not production ready guys.
Slightly off-topic, but if there's an espionage expansion in the future it should actually literally be called "Stellaris: Redacted".Stand by for the big reveal of <redacted>
So it would seem that mod load order is now determined by ther order in which you enable mods. I did a test on a compatibility patch:
--Test Case 1--
1. Enabled compatibility patch
2. Enabled mod
Moad load order ended up being in (dlc_load): .."compatibility_patch_mod.mod","mod.mod"
Result: Compatibility patch mod was not applied
--Test Case 2---
Did the opposite thing:
1. Enabled mod
2. Enabled compatibility patch
Moad load order ended up being in (dlc_load): .."mod.mod","compatibility_patch_mod.mod"
Result: Compatibility patch mod was applied
--Test Case 3---
Using enable mods function seems to randomize mods in dlc_load as well. I didn't even bother trying to figure out the logic behind there.
What would be an expectation of the behavior:
The dlc_load should respect the order in which the mods are actually ordered in the mod selection screen. This will cause lots of false reports to mod authors, it will break backwards compatibility...
Your mod launcher is not production ready guys.
We are, in fact, working on a search feature at the moment - Btw, the order you see is the load order of the mods; you can drag-n-drop the mods.
Are you some sort of mind reader? It's in the works.
Please, don't take this the wrong way, but I'm very much curious as to why "release it when it's actually done" is such an alien concept to the company?Indeed - We are looking at several usability improvements when it comes to heavy mod usage. It'll take us a few weeks to implement and QA, but this is one of our primary focus areas.
Yes, maybe it will. Can we please get it WHEN it is there, or at least better than what we already had? I'm not sure I can stomach another placeholder with a roadmap without bursting into tears and throwing stones at the moon.The second big reason for the move is that this new launcher will become
That is part of an issue with steam handling mods and modders updating instead of versioning ( as they don't want to lose people's interest)I really hate that you cant see what mods are technically out dated.
I was hoping to just play 2.3.3 and ride it out until all this was worked out.... but now i cant do that since core mods have been updated and dont show up/work in the old launcher now. Thanks for making it impossible to play past modded games.
That is part of an issue with steam handling mods and modders updating instead of versioning ( as they don't want to lose people's interest)I really hate that you cant see what mods are technically out dated.
I was hoping to just play 2.3.3 and ride it out until all this was worked out.... but now i cant do that since core mods have been updated and dont show up/work in the old launcher now. Thanks for making it impossible to play past modded games.