The changelog mentions "Identified severe incompat with Exotic Space Industries" without precising what the incompatibility is.

I'd like to disable the incompatibility on my side (fully accepting all risks involved, possibly even involving making a compat patch) and I would like to know exactly how this is going to impact my save.

I’m working on it, but as of right now, landing on Rubia with ESI enabled will straight up softlock you, as you will be stuck on Rubia unable to craft key buildings that you need to advance (because ESI changes those recipes). Rubia was also refusing to boot because ESI was changing key trigger tech requirements by default.

I spoke with Eliont. At this point, I mostly need time to make proper compatibility, to alter some recipes to make Rubia possible.

————
EDIT: I can make Rubia boot with ESI, and that compat is currently in my dev build. The rate limitting step is the part where I go through ESI’s recipes, and see how it impacts each part of Rubia to break all the softlocks. Some overhauls have unqiue mechanics that can interfere with things. K2SO had its special guns, and ESI does wacky things with technology costs. This takes longer than making the actual compat code, and I want to avoid a situation where I rush out a fix, and it just leads to another softlock 30 minutes later. I hope this gives you an idea.

I have updated Rubia to be compatible with ESI. However, it seems like there are some complications on the ESI side with respect to tech costs. You can now play with it enabled, but it may have some side effects until/unless Eliont changes ESI's tech cost system.

I understand, this was more in depth than I was aware of.

Thank you for your continued efforts!