Unless you want to pay someone to write a custom action, I think you should give up on doing it all in one thing.
However, what about this for another solution:
State 1:
+ Int Compare VAR A to the minimum amount required.
- Equal = blank
- Over = blank
- Under = NOT ENOUGH transition
+ Int compare VAR B to the minimum amount required
- Equal = blank
- Over = blank
- Under = NOT ENOUGH transition
+ ETC for all INT variables
So in this system you are not checking if you have more than, you are seeing if you don't have enough. It will go down the line and check one by one and if it doesn't have enough for one, it transitions out to fail. If it has enough, it just moves on to the next one.
Now since you are looking for not enough, it will will reach the last int compare and just do nothing if there is enough. To have this final success transition, just do something like WAIT for 0.1, then transition to the success state. So just in case you don't get it, it will basically exit if it's not enough of anything (before the wait can take effect), or will otherwise time-out the wait because it did meet all the var minimums.
This doesn't work if you test for equal or over, because if you transition using that you will just do the first Var and skip the rest.... unless each one is placed in a different state that it flow through one by one.
