31
Mods / Re: [0.9.1a] Secrets of the Frontier (Prerelease 7) - indev campaign mod
« on: February 23, 2020, 06:57:19 PM »
Yeah , sorry .
Archean Order is it .
Archean Order is it .
Starsector 0.97a is out! (02/02/24); In-development patch notes for Starsector 0.98a (2/8/25)
Dunno about the zip version bug but when applying the Hotfix jar to the beta branch, the save game seems to stop loading as it says its incompatible or outdated mods, yet without it the save does work fine with the mod updated
I'm practically using all mods and Nex mostly affects faction mods and nothing else besides Vayra yes?
Granted a new save start would be fine but I did found a good Nebula system to colonize, and got lucky for once in having several Terran worlds close to each other, excluding the one at the very fringe of the galaxy
Is the jar file supposed to fix it or is the fix already included and up to date and Im just using an outdated one?
hi
nice mod, really enjoying it.
just a small issue. i've been getting CTDs recently, its probably mod conflicts for sure but i'm mentioning it here in hopes of finding a solution or work around.
i'm getting a CTD regarding a fatal slot id (ws 015) not found on hull (dominator_luddic).
i've checked the file and there is a weapon slot there, not sure why it wont notice it. any ideas?
i've been having this issue with another mod, the Archean Order, with their mule and buffalo ships.
maybe these two mods don't play nice?
anyways, thanks for any insight you can provide.
Archean Order replaces a lot of vanilla files with its own, and many of those files have significant changes to the slot ids. The mule is particularly likely to cause crashes, because it looks like the author not only edited every single hardpoint but also renamed them from the format "WS 001" to "WS001", so any other mod that makes a mule variant is going to crash with it.
If you get stuck on any crashes that look sort of like "Slot id [WS 010] not found on hull [aurora_ix]," it probably means that some mod created a variant, "aurora_ix" of the vanilla ship "aurora", but archean order deleted the weapon slot [WS 010] in the original file.
So for Archean Order, you can fix this by going into "Starsector\starsector-core\data\hulls", finding the relevant .ship file, opening with a text editor, finding "WS 010" in that file, copying the entire section between (and including) curly brackets, and then pasting it into the same place in the file of the same name in "Starsector\mods\Archean Order TC v1.3.4e\data\hulls". That section is structured as a comma separated list of bracket-enclosed hardpoint definitions, so you need to make sure that each item has a comma after it except the last one.
I've been resolving most of the incompatibilities with Archean Order this way as they come up. It's a really hacky way of fixing it, but it keeps it from crashing, and I haven't had to restart my play through.
hi
nice mod, really enjoying it.
just a small issue. i've been getting CTDs recently, its probably mod conflicts for sure but i'm mentioning it here in hopes of finding a solution or work around.
i'm getting a CTD regarding a fatal slot id (ws 015) not found on hull (dominator_luddic).
i've checked the file and there is a weapon slot there, not sure why it wont notice it. any ideas?
i've been having this issue with another mod, the Archean Order, with their mule and buffalo ships.
maybe these two mods don't play nice?
anyways, thanks for any insight you can provide.
Archean Order replaces a lot of vanilla files with its own, and many of those files have significant changes to the slot ids. The mule is particularly likely to cause crashes, because it looks like the author not only edited every single hardpoint but also renamed them from the format "WS 001" to "WS001", so any other mod that makes a mule variant is going to crash with it.
If you get stuck on any crashes that look sort of like "Slot id [WS 010] not found on hull [aurora_ix]," it probably means that some mod created a variant, "aurora_ix" of the vanilla ship "aurora", but archean order deleted the weapon slot [WS 010] in the original file.
So for Archean Order, you can fix this by going into "Starsector\starsector-core\data\hulls", finding the relevant .ship file, opening with a text editor, finding "WS 010" in that file, copying the entire section between (and including) curly brackets, and then pasting it into the same place in the file of the same name in "Starsector\mods\Archean Order TC v1.3.4e\data\hulls". That section is structured as a comma separated list of bracket-enclosed hardpoint definitions, so you need to make sure that each item has a comma after it except the last one.
I've been resolving most of the incompatibilities with Archean Order this way as they come up. It's a really hacky way of fixing it, but it keeps it from crashing, and I haven't had to restart my play through.