Intelligent Logistic Slider / Logistics UI
Posted: Fri Jun 13, 2014 11:50 pm
To request a full chest, you have to put in higher numbers. For instance, 10K, 5K, 3K to get 9.6K, 4.8K and 2.4K.
The change from 0.10 towards "non-computer-numbers" is fine, but incomplete
, i.e. networked chests could get 50 slots.
Or any other number that makes sense, after thorough thinking. If 200 is the new 256, maybe 40 is more like it.
Furthermore, the request counts of chests should correlate with the item, so you could only request 40-50 [48] blueprints.
I welcome the move to a decimal system logic, but slots of 16, 32, 48 feel inconsistent, to me.
I realize, there is more to it, to end up with an easier system, than just getting rid of everything non dividable by ten.
Maybe there is a place for the 25 in this world, who knows...
Also, personal logistic slots should only request numbers according to item stack size and personal storage slots.
Based on the stack size, of the selected item, there could be a tweaked stepping system up to the maximum number.
thierry
The change from 0.10 towards "non-computer-numbers" is fine, but incomplete
![Uber Geek :ugeek:](./images/smilies/icon_e_ugeek.gif)
Or any other number that makes sense, after thorough thinking. If 200 is the new 256, maybe 40 is more like it.
Furthermore, the request counts of chests should correlate with the item, so you could only request 40-50 [48] blueprints.
I welcome the move to a decimal system logic, but slots of 16, 32, 48 feel inconsistent, to me.
I realize, there is more to it, to end up with an easier system, than just getting rid of everything non dividable by ten.
Maybe there is a place for the 25 in this world, who knows...
Also, personal logistic slots should only request numbers according to item stack size and personal storage slots.
Based on the stack size, of the selected item, there could be a tweaked stepping system up to the maximum number.
thierry