Cannot reproduce. Could you provide an unmodded save file where the issue can be observed?

Given that those are directional pipe connections meaning there is a fluid flow happening on each plasma connection and given that fusion generators have fluid boxes with volume of 10 out of which only 5 participates in the fluid flow per tick, this works to be exactly 5/tick which equals 300/s ...

Thanks for the report. Issue is now fixed for 2.1.

Quick summary of the video is that DRAM needs refresh cycles and if a memory channel is currently being refreshed this causes memory access to be delayed until refresh finishes. Proposed solution in the video is that when you have more than 1 channel of memory then refresh cycles are usually not ...

No.

i am simplifying things here a lot because some details are not relevant. Each rail segment has 2 ends (front and back) and they know neighbor rail segments and if they are connected front-front, front-back, back-front or back-back. This is not relevant for the discussion. "east/west" was just a ...

In the picture below


I do not understand which game concepts nodes on your graph represent so i wont answer anything about it. I can only tell you that trains pathfinder is finding a path within a directed graph regardless of rails being bidirectional because there are separate nodes for travel ...

segments vs blocks is not relevant for this discussion. Quick glossary is provided in https://factorio.com/blog/post/fff-331 section `Trains Pathfinder changes`.

This situation does not create problems because pathfinder nodes are directional.

In the original picture that lists A, B, C, there ...

There are no easy solutions to make trains pathfinder not find paths that would cross themselves given certain train length (this would cause massive performance penalty and logic complexity due to all corner cases like repathing during travel to not collide with train, not even with positions train ...

Given the direction we went with display panel which for a brief moment supported LocalisedStrings but was downgraded to a regular string due to various problems (limit restriction bypasses, desyncs), i am not considering this to be an interesting direction to go, especially since this is a player ...

Welcome on forums. This is not a bug. `/evolution` uses data from `enemy` force while you are trying to read this data from `player` force.

Thanks for the report. Issue is now fixed for 2.1.

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

As a workaround, in game versions up to 2.0.76, do not pass `belt_stack_size_override` to create_entity, but instead set it in a separate instruction after loader was created using https://lua-api.factorio.com/2.0.76/classes/LuaEntity ...

I remember seeing something slightly similar (131263) but i am not sure i can decide if its the same issue or a different one.

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

Unfortunately there are no workarounds here, value of in_gui is simply unreliable up to 2.0.76 due to a bug.

From a quick look, "Server-30Levi" save file has only 6 migrations applied:
aquilo-tilesets.json (space-age)
biolab.json (space-age)
internal.json (space-age)
jelly-yum-rename.json (space-age)
shattered-planet.json (space-age)
tungsten-belt-rename.json (space-age)

while the "Server-31" save has ...

This looks like a memory bit flip, one byte had a value of "04" when it was expected to be "00" and as such one decorative had an incorrect value preventing save from loading. Attached is a fixed save file.

Thanks for the report. Issue is now fixed for 2.1.

I will make an executive decision here and claim this is Not a bug.

Rationale for this is that even if enemy forces would be required to not connect, there is a high expectation due to mods that rolling stocks of friendly forces would connect (some mods are abusing friendly forces for approving ...

Thanks for the report. I will consider this a duplicate of 131736 which is already fixed for 2.1. Reproduction is verified as fixed.