I already responded back to you on discord, but the short version is many thanks for the detailed report. It should be fixed now :)

A sorta copypaste of the more detailed explanation I typed on discord (because stuff on discord is not always easy to find) regarding this issue:
So what apparently happened is that I had set the blocked travel cells to block off crew from travelling below a certain line of cells. But the cells below the blocked ones were still traversable, but just not accessible.
This never caused any issues...until the thruster was set on fire below this line of blocked travel cells and a crewmember was trying to take a fire extinguiser and find a way to that particular cell.

What I didn't realize was that apparently blocked travel cells are also impossible to set on fire. So once one of the cells below this line was hit, it could still catch fire and when it did a crewmember would attempt to put the flames out.
Since it couldn't get to its calculated destination (because I blocked the cells leading up to the cell that was on fire), it would cause the pathfinding crash.

(Link to the Discord thread in question https://discord.com/channels/314103695568666625/1207030366699921448 )

The main reason I didn't want to do a process of elimination with enabling just a few mods is the load time. Cosmoteer spends quite a lot of time loading mods if there is any changes to the mod load list or any mod updates.

Thinking back on it I could have tried to make a minimal setup in creative with only this mod enabled, will consider doing so if the fix doesn't work.

Will be doing a test of the fix in a bit. Fingers crossed.

Curious, still getting the same error. Checked the workshop folder and I do have the update. Time to see if I can make a minimum example of this or if it is some cross-mod shenanigans.

Hmm, one reason the save is still broken could be due to the fire already beeing in the inaccessible area. Tried replicating it but no success so far.

Lucklicy there is an autosave from before the paradox fire, so I will just be resuming from there.

Originally posted by WarrantyVoid:

(Link to the Discord thread in question https://discord.com/channels/314103695568666625/1207030366699921448 )

The main reason I didn't want to do a process of elimination with enabling just a few mods is the load time. Cosmoteer spends quite a lot of time loading mods if there is any changes to the mod load list or any mod updates.

Thinking back on it I could have tried to make a minimal setup in creative with only this mod enabled, will consider doing so if the fix doesn't work.

Will be doing a test of the fix in a bit. Fingers crossed.

Yes, the load times increase dramatically with even the most minute changes (which is rather unfortunate for modders like me as this can make testing and tweaking quite time consuming).

Interesting thing you say about your save still being broken due to the fire already preexisting. This indicates that the blocked travel cell doesn't actually prevent it being on fire. It just prevents it from being set on fire.

But I'm glad this is now solved and you pointed me into the right direction, nicely done :)

Locking this since this issue has since been fixed.