Page 1 of 1

[kovarex] [1.0.0] Right click on blueprint item doesn't close currently open blueprint

Posted: Sun Sep 13, 2020 3:50 pm
by ickputzdirwech
Steps to reproduce:
  • assign at least two blueprints, upgrade or deconstruction planners to your quickbar.
  • right-click on them after each other
  • press e or esc
The last opened blueprint will close, but the previous blueprint will open again. i would expect, that right-clicking on a different blueprint would close the previous one. The first issue with this is that you have to press e or esc several times. But it can also can result in a funny state with an empty blueprint.
empty blueprint.png
empty blueprint.png (183.3 KiB) Viewed 3287 times
As you can see it has no components. This happens when you take an empty blueprint, select some content for it and before saving it right-click on another blueprint in your quickbar and press e or esc once.

Re: [1.0.0] Right click on blueprint item doesn't close currently open blueprint

Posted: Sun Sep 13, 2020 4:21 pm
by ickputzdirwech
I played around with this a little more and now have the hand stuck in my inventory. Save attached. Here is how to reproduce it:
  • assign two blueprints to your quickbar. One with content and one empty.
  • take the empty blueprint and select some content for it.
  • before saving it, right-click on the other blueprint in your quickbar
  • click on "select new contents for this blueprint" and select new content
  • before saving it press e twice
You will end up with no item in your hand, but a hand in your inventory. You can't place anything in that slot.

Re: [1.0.0] Right click on blueprint item doesn't close currently open blueprint

Posted: Tue Sep 15, 2020 4:52 pm
by Rseding91
The behavior when opening subsequent blueprints is intended; it also works that way when opening books in books and such. The empty blueprint when re-selecting isn't.

Re: [kovarex] [1.0.0] Right click on blueprint item doesn't close currently open blueprint

Posted: Sat Oct 24, 2020 12:34 pm
by kovarex
Thanks for the report, it is now fixed for the next release.