TL;DR
With the logistic groups announced, I think it's time to revisit this suggestion : Allow the engineer to create a logistic group in one operation by importing a blueprint item list.What ?
The core idea is we need some kind of interaction between blueprints and logistic requests, and the logistic groups are (were) one of the missing steps for that. Now that we can (will be able to with 2.0) group a set of individual logistic requests into a coherent whole, the last thing we need is use the contents of a blueprint to feed the logistic group. The things I will want to do at some point :1) I have a blueprint ([Edit] : Or a "Copy" selected) in hand, or I'm browsing my BP library, I want to :
- create a new logistic group with the items listed in the blueprint/blueprint book
- add to an existing logistic group the items listed in the blueprint/blueprint book
2) I am in my inventory preparing something, I want to be able to :
- Create a now logistic group by importing a blueprint/blueprint book from my library (or my inventory if blueprints in the inventory are still a thing in 2.0)
- Add to an existing logistic group the contents of a blueprint/blueprint book from my library
Cherry on top : QoL minor feature like pre-filling the new logistic group's name with the BP/BP book's name
Why ?
I think the why is pretty obvious, given it's one of the oldest feature requests regularly re-requested for 8 years.I'm aware having two paths to access the same core feature is twice the work, but I'm sure there are clever ways to do that to minimise the double work (like for example invoque the same interface from two starting points). I totally see myself using both, hence the suggestion to allow both.
[Edit] : In the 1) Blueprint in hand, I added a nuance : as soon as I have "Copied a zone on screen, even when there is no actual blueprint in hand, I want to be able tu use that feature.