Store Page
Space Engineers
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Space Engineers

Store Page
Space Engineers >  Workshop > taleden's Workshop > Taleden's Inventory Manager > Discussions
Taleden's Inventory Manager
Description Discussions88 Comments1793 Change Notes
Sakata 11 May, 2016 @ 11:09am
[edited for future searchers] Same/intra-block priorities
Hey there. Loving the script so far. I have a usage scenario I wanted to know how you'd handle: ships.
So far I've been using a welding drone with cargo that has [TIM Component:100] for all but one container. The last one is set to [TIM steelplate:1000 interiorplate:1000 construction:1000]
But some space is wasted, while other space isn't used up to capacity.

I basically want to be able to dock my drone, it gets filled with (optionally proportional by usage) components, then I can undock and do my thing.

Is there a correct way that I'm not seeing, to do this?
Last edited by Sakata; 17 May, 2016 @ 5:00pm
< >
Showing 1-3 of 3 comments
Vuelhering 17 May, 2016 @ 9:36am 
You can use priorities with numbers. I'm going from memory, so my syntax may be wrong, but you could do something like this:

Cargo 1 [TIM component:p1:100 steelplate:p2]
Cargo 2 [TIM steelplate:p1:1000 component:p2]

It should fill all quotas first (the 100 comps and 1000 steelplates), then the rest.

You might even be able to combine two in one cargo container, but not sure, like comp:p1:100 comp:p2. In fact, you can do this without priorities since quotas are first and non-quotas second priority automatically, but that makes it more obvious.
#1
Sakata 17 May, 2016 @ 4:51pm 
Ahh thanks I'll try that out. Nex to ask about nanity control factory issues :D Making a new thread for it though
#2
taleden  [developer] 21 May, 2016 @ 7:35pm 
It might not be super intuitive, but TIM will actually always fulfill any "limited" quotas first, before any "unlimited" quotas, so you don't even need the different priority numbers in the example above. Just having the ":100" and ":1000" will make TIM try to send at least that many to those containers first, and then send any extras to the container with the request with no amount limit.

So, for example, these four requests will be filled in this order from top-to-bottom, even though the "unlimited" priority numbers are ahead of the "limited" priority numbers:

[TIM Component:P3:100]
[TIM Component:P4:200]
[TIM Component:P1]
[TIM Component:P2]
Last edited by taleden; 21 May, 2016 @ 7:36pm
#3
< >
Showing 1-3 of 3 comments
Per page: 1530 50