| 919 | 😟 | General | I'm having an issue with Behaviors, specifically the Request Item control. It seems that the Request Item control can both be used to request a target item or, in the case of an empty parameter, clear the request queue. There doesn't seem to be enough logic support to differentiate these two cases, so I'm running into a situation where my automation erroneously clears the request queue whenever it encounters an empty parameter.
Can you please split these two functions: have "Request Item" silently ignore an empty parameter, and create a separate "Cancel Orders" function explicitly to handle that task?
Example: I am creating a Behavior for a Storage Unit that's intended to request dependencies needed to create a target item. The Behavior takes a parameter (Target Item), inspects its dependencies, and then, after doing some math, (attempts to) creates (via Request Item) requests for each of the necessary dependencies to create that target. The issue I'm running into is that, in cases where there are less than 3 dependencies, the 2nd and/or 3rd dependency variables(/parameters) get stored as empty values. When those empty values make it to the Request Item, it clears the entire request queue on the unit. | | 2023-08-20 20:08:35 |