When creating a stockpile for build management I use 'blueprint runs' as the way to specify the number of runs, especially when it is not equal to none.
When using BPC this works fine as stockpile tracks the sum of the runs of the bpc
When using a BPO - it seems to see the 'infinite' runs as zero, rather than present (or infinite) - is this a bug?
Feature request: when specifying blueprint runs (as count) and a BPO is present to satisfy it, rather than say surplus is infinite - just set surplus to zero, or +1, or text: BPO - whichever you feel is the most generic solution.
Feature request two: when including a BPO in a stockpile (specified as BPO) have the option to nullify the price aka price same as bpc (could be the 'item' setting - as you may have stockpiles where you want a BPO to be counted - to have an estimate of their total worth (although a standard asset filter is probably much faster!) - so maybe it could be a setting for 'all' stockpiles (eg, price BPO as same as BPC).
When creating a stockpile for build management I use 'blueprint runs' as the way to specify the number of runs, especially when it is not equal to none.
When using BPC this works fine as stockpile tracks the sum of the runs of the bpc
When using a BPO - it seems to see the 'infinite' runs as zero, rather than present (or infinite) - is this a bug?
Feature request: when specifying blueprint runs (as count) and a BPO is present to satisfy it, rather than say surplus is infinite - just set surplus to zero, or +1, or text: BPO - whichever you feel is the most generic solution.
Feature request two: when including a BPO in a stockpile (specified as BPO) have the option to nullify the price aka price same as bpc (could be the 'item' setting - as you may have stockpiles where you want a BPO to be counted - to have an estimate of their total worth (although a standard asset filter is probably much faster!) - so maybe it could be a setting for 'all' stockpiles (eg, price BPO as same as BPC).
Hope this helps! jEveAssets certainly does!!!