The consumable bundle feature has been released!
You can find the full issue of the development log here.
Alot of people are complaining that they donât like the fact that the packages dont open on their own, and I agree with your decision to not allow that to prevent unwanted opening. Because of this, I propose a solution; the posibility to âArmâ the packages, so that as soon as it needs to be opened, it will be opened, but they can also be put into an âunarmedâ state, where it wont open unless opened manually. I think this could be just a simple green/red toggle switch next to where the Unpack button already is on the item.
Apologies for my garbage drawing skills but I hope you see what I mean, green = armed, red = unarmed.
Just an idea, no idea how it would be to impliment this or if its even worth spending time on, but il just throw it out there. thanks 
1 Like
A decent alternative to âarmingâ the bundles would be an âauto-use bundlesâ checkbox in the new UPCK buffer (per bundle). Essentially, if you tick the checkbox, the bundles will be used one-by-one when required. When not ticked, it would keep bundles from being used automatically. This way makes it a one-click-and-forget type solution. Having to âarmâ bundles every time they arrive at your base may get a little annoying.
2 Likes
yeah thats what I mean, they shouldnt auto use, unless you tick the box.
This might make sense as an addition to the workforce consumables buffer as well or instead.
1 Like
What about adding a âunpack on arrivalâ setting that sits next to the âunload on arrivalâ setting?
A button âunpack on arrivalâ makes the assumption that the first stop the ship makes is where the bundle should be. While this works some of the time, there is a high chance that you want the bundle to go to the 2nd or 3rd stop. This means that you have to consider ticking or unticking this box upon sending every ship. This may get annoying in a similar way to âarmingâ bundles.
There could be a button in UPCK to automatically unload relevant bundles to the planets WF instead, but its the same issue. Its still very possible the user wanted that bundle on another planet and forgot to untick this feature. I canât see this working.