[1.1.106] Blueprint with relative grid is about to be placed in absolute grid

[SWeini]

That's the blueprint I want to place, it has relative grid snapping enabled.

0eNql2+1u2kwQhuFz8W+omI/dAU7lVVSR4EZWwSDjvG1Uce41kEZVgtS97Z8O41mb4bnWQuRX9bh7qY9d0/bV+ld1ajfHeX+YP3fN9nL8s1ovZ9VrtbbFeVY1T4f2VK3/G+qa53azu1T0r8e6WldNX++rWdVu9pejb5sfh+dNPT/uNm2/6ZtDO99/X0h16dFu66GrnB9mVd32Td/Ut5bXg9ev7cv+se6Ggn82m1XHw6m5HL9dqd2udFikq5+a49/nXqovl3i6lL79sVrr4nyefVpZ31fuu017Oh66fv5Y7/rPC8aXdF1SvqRh0W0zLHt71e+0Ndx2UdLWcVsraZtwWy1pm9/bPr50bd3Nm/ZUd/3w0qe++a2vf+w79PjW7IZzvu4P22ur3ebp+6459dWdFYOvmD6uqGjFJX7rUslbt8JtvaStLMYGbTU1aCL4lqLolniCc1FfHuFVUV+e4WVR38Q/+yLTPvwyIuGymBZxCS52EdnCoyxFaMtqbOgkTd7eFvymirYM5XGWok1DR+zIRaQqD7QUoao+IgV5Wgp0TNpjWto18zewiFodEemivUGXY5OnMjl5fAuXIuhtRKSLdibjkdYiAI1HWsueso2nQHVa8mxE2tWmJc9GPKAXKW480lqkuMXo5MXU5BnfyLVoBzEeaS3aQZxHWotk9RGRLpLVdUQKltOS52PSvpqWPOdP61qErY+I9J3t4WFW9c3u7UuVD+ctbt8rnN8XGgK4He59d73Ru8VCipUUGyl2UpxIcSbFQYqXpHiFhsJGiGYoaIiCpihojILmKGiQgiYpaJSCZqlolsryiGapaJaKZqlolopmqWiWimaphbMUIqsQWYXIKkRWIbIKkVWIrEJkFSKrEFkFySpIVkGyCpJVkKyCZBUkqyBZBckqSFZBsgqSVZCsgmQVJKsgWQXJKkhWQbIKklWJrEpkVSKrElmVyKpEViWyKpFViaxKZFUkqyJZFcmqSFZFsiqSVZGsimRVJKsiWRXJqkhWRbIqklWRrIpkVSSrIlkVyapIViOyGpHViKxGZDUiqxFZjchqRFYjshqR1ZCshmQ1JKshWQ3JakhWQ7IaktWQrIZkNSSrIVkNyWpIVkOyGpLVkKyGZDUkqyFZncjqRFYnsjqR1YmsTmR1IqsTWZ3I6kRWR7I6ktWRrI5kdSSrI1kdyepIVkeyOpLVkayOZHUkqyNZHcnqSFZHsjqS1ZGsjmRNRNZEZE1E1kRkTUTWRGRNRNZEZE1E1kRkTUjWhGRNSNaEZE1I1oRkTUjWhGRNSNaEZE1I1oRkTUjWhGRNSNaEZE1I1oRkTUjWhGTNRNZMZM1E1kxkzUTWTGTNRNZMZM1E1kxkzUjWjGTNSNaMZM1I1oxkzUjWjGTNSNaMZM1I1oxkzUjWjGTNSNaMZM1I1oxkzUjWjGQNImsQWYPIGkTWILIGkTWIrEFkDSJrEFkDyRpI1kCyBpI1kKyBZA0kayBZA8kaSNZAsgaSNZCsgWQNJGsgWQPJGkjWQLLGCFnt7iwfbj8Pv/6c989/OM+q/+vudPvR71I8VhrLrB55eT7/BjVUnXU=

Copy blueprint

Now I want to place it, but it's stuck to absolute grid snapping (with the correct size, but the offset is not how I like it, there is a reason it is set to relative. the offset is also not "aligned" to my last placement in either direction). It worked hundreds of times before and suddenly was wrong.

The blueprint is stored in "My blueprints" and pinned to the hotbar from where I normally access it. I normally place the blueprint in the following way and did so just a few minutes before the buggy behavior:
1) selecting the blueprint from the hotbar
2) go into map mode
3) adjust position carefully using the mouse
4) click mouse and hold
5) press shift (I don't have radars yet, so I have to blueprint in the fog)
(4/5 sometimes swapped)
6) scroll down until I want to stop placing the blueprint
7) release shift and mouse button
8) walk down and let the companion drones build

Maybe I've done these actions in a slightly different order the last time. I also remember doing a single undo action because I placed the blueprint one time too often, but I believe I placed one more column of the blueprint afterwards correctly.

Canceling and selecting the blueprint again from the hotbar did not fix the issue.
Opening and closing the blueprint did not fix the issue.

Now while writing this bug report and trying it out again, the blueprint has fixed itself. I have opened the blueprint and exported as string. And I've opened the blueprint so many times that I can't say to never have "saved" instead of "closed" accidentally.

[Loewchen]

So you cannot reproduce the issue with the steps provided yourself?

[SWeini]

No, I did these steps hundreds of times and it only happened once. I still tried to describe my steps to the best of my knowledge. Because I know what I saw, and the blueprint was in the wrong snapping mode when being clicked. Sometimes a dev can see what's going wrong just by looking at the code.