The problem
People lose blueprints sometimes. Some of them were familiar with older versions where blueprints were actually copied. Some of them just don't understand mechanics yet. So they move blueprints somewhere and then die/quit/whatever.Every of them blames moving and suggests to change default behaviour to copy.
Why this happens? Because it's not obvious that blueprints were moved. Well, you can guess that they work as any other item, and you can see that if you try. But it's still not obvious, there are no trigger that launches this mental process. And our brains are lazy.
How this can be solved? Look at the Microsoft Explorer. It shows a little hint under cursor when you drag the file: "moving" or "copying". Files are moved by default, like in Factorio, but you clearly see that file would be moved. And brain starts thinking in right direction.
The proposal
Proposal is quite simple: show a "MOVING" hint when non-empty(?) blueprint is hovered over some inventory.Bonus proposal: support Ctrl button that switches that hint to "COPYING" and does action of "Create copy of this" when blueprint is dropped.
