Thanks for the report. This is now fixed for the next release.

What? There are tons of items that don't have a matching fluid of the same name. It's not a requirement of anything.

Thanks for the report however this is not a bug. The GUI is meant to let you input *some* values that are acceptable for most games. It's not an exhaustive input range.

Thanks for the report. This error indicates that you had some kind of system failure (CPU or RAM). Since on load it's failing to have a value in one of the electric networks that it validated on save was correct.

Do you know of any way to get a known good save file into this state?

I looked into it early on and it's functionally not possible. It's identical to asking for "Allow changing the name of an entity runtime". The only way to do it is destroy the old entity and create a new one with the new name.

The only way to change the quality of an entity runtime is to destroy ...

Thanks for the report however I don't believe we will be doing anything about this. Combat and combat related things were specifically never implemented in latency because there are too many moving parts to fake in the latency state.

Throwing capsules are done through the standard shooting logic ...

Thanks for the report. This is now fixed for the next release.

Thanks for the report however we won't be doing anything about this. The splitter you've placed inline, and the fact you're side-loading means the recursive "update the one in front of me first, so then I can move forward without leaving gaps" breaks down here.

Thanks for the report. This is now fixed for the next release.

Fascinating.

Thanks for the report however this is not a bug. If you want to remove the modules you can set a recipe and remove them, or simply pick up the entire machine which will also include the modules.

Thanks for the report. This is now fixed for the next release.

Inserters will put any spoiled items into the output of the biochamber. If the output is full then it will wait for the output to become empty - except in the case of the spawner - where the recipe runs just to keep the machine from dying - where it will put it into a 2nd slot next to the output ...

I see. I missed the part where you said 2.0.55. The linked bug report was fixed in version 2.0.56 which you aren't on and has not been released as stable yet.

Thanks for the report. The crash is fixed for the next release - it will simply shows a "corrupt map" error at the load screen.

The reason why the save is getting into that state seems to be a different bug which I'll forward to the fluids guy.

Thanks for the report. The error is that you left "log-stack-trace-on-non-critical-exception" enabled when you aren't supposed to. That, combined with something about your systems inability to generate a stack trace has crashed the game.

Simply disable that option.

Do you have a save from *before* it picked up the spoilage where when loaded it will pick it up and get stuck?

Sorry but I'm not seeing any inserter trying to put spoilage into a captured spawner in the save. I see one trying to put spoilage into a *wild* spawner - likely it had bioflux in its hand on the way to the spawner when it went wild and it has since spoiled.

Thanks for the report. The crashes are *all over the place*. That combined with the CPU you have makes me think your CPU is faulty and it's the 13th/14th gen CPU bug https://www.reddit.com/r/intel/comments/1egthzw/megathread_for_intel_core_13th_14th_gen_cpu/

Do you have the latest BIOS? If not, try ...

Thanks for the report however this is intended. The arrows draw above everything. If they didn’t they would be useless since the right side and bottom side of the screen almost always have GUI elements visible.