The stack-size logic only updates once per swing operation Could you please elaborate how this relates to the very first swing reading the stack size off a different tick than all subsequent swings? I don't really see the connection between these two statements. This inconsistency between the first...

Oftentimes, you have blueprints that should only be tileable in one dimension. You can already achieve this effect currently by using some large grid size for the dimension which you don't want to be tileable. However, using large grid sizes such as 10^6 or 10^9 seems to cause some tremendous lag, a...

Regarding my feature request for allowing a grid size of 0, should I post that again in the suggestions subforum?

Regarding the bug itself, values >= 2147483648 and <= 0 are already disallowed. Would it make sense to further restrict the upper bound to 2^30 or something for the time being?

When using very large grid sizes such as 2147483647=2^31-1, placing blueprints at y=-1 or -2 causes jitter and places the blueprints incorrectly. The same does not happen for positive y-values or y-values that are further away from 0. Slightly smaller grid sizes such as 2147483645 cause the gaps to ...

I think that is already pretty much implemented with cut&paste and undo. Simply press ctrl-x, select the area and place the blueprint somewhere else. If you made a mistake press ctrl-z. If you do it fast enough before any construction bots come along it will just cancel the deconstruction plan....