Starsector 0.97a is out! (02/02/24); New blog post: Save/Load UI, Autosave, Intel Map Markers, and More (04/10/24)
Alright, thanks. To confirm, you have the most recent version of Starship Legends installed?
If you DO use console commands to add a trait, does the crash occur? (if you don't even play with the Console Commands mod, you can disregard, but it would be a lot easier to test if you could replicate the crash with just commands.)
I'd be surprised if there was another mod besides KT and SL interacting here, but you can never be too sure.
Sorry to hear that - I'll see if I can replicate it. Can you post the crash report?
EDIT: I have attempted to recreate the bug, with the following method, and failed. There was no crash and everything seems to be working.Method- I spawned in an Ouroboros with console commands. I also spawned a Quetz and a Cathedral from SWP, just to check.
- I applied a trait to each of them the console command: addtrait good to capital_ship
This put a random trait on each ship I had spawned. Each gained the "notable" mod with that trait.
- I checked the refit screen and clicked on every clickable module. There was no crash.
- Just to check, I assigned an officer to each ship, then added a crew loyalty to each ship with: setloyalty 10 capital_ship
- Again, I checked the refit screen and modules. No crash.[close]
So, something else is happening. Either:
-the crash is caused only by traits added normally with battles, not console commands.
- the crash is caused by a specific trait, not just any trait. (What trait did your Ouro get?)
- you're running a noncurrent version of one of the mods.
- something else entirely.
Get back to me with some more info if you can.
EDIT2: I tried getting the trait "legit" (without console commands) and still, no crash.
Glad you got it working
Hotfix is up.
- Fixed crash caused by Ouroboros lacking some engines.
- Goon heavy fighter is now correctly labeled in the codex.
EDIT: lul ninja'd.
I'm guessing the problem is the Ouroboros head is missing 4 engines that were added to the Quetz head and are turned on when the body dies.
I have like 3 different logs, all of which are exceedingly long. I cannot tell which log it is, so I am going to try to recreate the crash after I delete all the current logs. I do have the Target Pip mod, but I didn't have it enabled when playing Vacuum. I only use Vacuum when playing it. As for the assault-style capital ship, yes speed over durability. Faster than normal, more fragile than normal and a mix between forward facing weapons. Maybe even a new weapon, or ship system, that draws the target closer to get more damage in with shorter range weaponry? It could be a built-in weapon, maybe one that is ship-specific and unobtainable through shops? Whatever you want, I just thought it sounded like a good idea for an assault capital.Quotedo you plan on adding more ships for the already existing factions and/or more factions?Yes, I definitely do! The Glaug have been pretty slow to get new ships, because those are originals by me, rather than kitbashes, but I was going to do an assault carrier in the Cruiser / Destroyer range (they desperately need a small carrier) this week, using some new methods I'm looking at for doing original ship art.
Anyhow, I can't promise you anything, but if the carrier experiment works out, I may very well do several new Glaug ships; what I'm going to try should shorten the production time a bit.
So, when you say "assault-style capital" what do you mean? Speed over durability?QuoteWhere are crash logs kept? I had a crash while in the middle of battle after updating to the new release. Not entirely sure what caused it, but I can only assume it had to do with the only mod I had installed. xDPlease let me know what you find- just copy-pasta the last bits of the log.
If the bug is with the Target Pip mod... yeah, it's buggy with Vacuum atm, dunno whether I'll fix it or not, but probably. I haven't ever tested with stuff like Omnifactory, tbh; I suspect it'd break five ways from Sunday, lol.
