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

Thanks for the report. Issue here was that the underground building logic assumed that if belts between underground belt ends were straight they should get removed but that logic was slightly wrong as it could remove straight belts with side connections as well as showing what is reported here (on f...

Thanks for the report. I am considering this to be a Not a bug. If the grid position values would be required to be relative to the top left corner of all visible entities then if visible entities would change the grid position values would have to be adjusted. In this example when you selected blue...

Thanks for the report. I am not going to fix that issue in 1.1.x because pump logic is quite tricky to not cause performance problems. One of the operations in pump that is relatively expensive due to entity searches is search of fluid wagons so pump tries as much to not do those searches if not nec...

I am not considering this to be important to fix. Having this relative grid position be allowed to be out of core entity snapping would only have a cosmetic effect and tiny effects on the cursor position but it would not add any new behaviors or would not remove any existing behaviors. I will mark t...

Thanks for the report. Issue will be fixed in 2.0. Core of the issue is that blueprints in library are different objects than blueprints in inventory. When setting up that blueprint in library first a blueprint item is created but then it is cloned to blueprint record in the library. Common part of ...

Moving to translations.

Thanks for the report. I was able to reproduce the issue by watching the replay as well as reproduce it from scratch. It looks that replay considers first player as a local player so when first player left the game, blueprint library was disconnected from local player shelf and this caused another p...

Implemented for 1.1.106

This is implemented for 2.0 as LuaTransportLine::line_length.

How about 53-bit integers then? It's more than 32 so we get some benefit. We can't store 2 32-bit signals in one, but we can store 2 26-bit signals or 3 17-bit signals, which is both a benefit over being limited to e.g. 2 16-bit numbers when packing multiple values into a single signal type. How ab...

This is unlikely to happen unless we would update Lua to something newer than 5.2. If circuit network signals would have values based on 64 bit integers then scripts would have a hard time setting some values since all values in lua 5.2 are based on a `double` which cannot represent all 64 bit integ...

Thanks for the report however i cannot reproduce the issue you described. I was trying to place stone furnaces from ghost cursor and when stone furnace recipe finished crafting i was still placing stone furnace ghosts.

Do you have any mods enabled?

Thanks for the report. I see the issue was already fixed for 2.0.

Thanks for the report. The issue seems to be caused by the font we are using that is not supporting all possible glyphs from all languages. Moving to ideas and suggestions.

Thanks for the report. I fixed this for 2.0 by making --load-scenario not force map generator size to 50x50.

I am considering this to be a wont fix. Those checks are primarily for being compatible with map generator and we never assumed rails would be placable by map generator.

You are right, that is a desync. From a quick investigation it looks that when logistic container changes force, it destroys logistic point of that logistic container and since logistic point stores current filters they are simply lost. There is a code that is supposed to preserve filters when chang...

This is not relevant for 2.0 since we are trying to get rid of secondary collision box logic, however this function seems to be far more broken when considering rails given that rails have custom set of collision box orientations for each direction and this specific check directly takes bounding box...

I was running both saves for about an hour each and no crashes.