If possible, it might help to simplify your tags, such as reducing the number of different priority levels that are in use. It might also help to try to further specialize your storage; for example instead of 20 containers all tagged for "Component" so that every subtype of component is divided among them, you could reserve one just for "Steel Plate", another just for "Construction Component", etc. By having fewer stacks of items to distribute, TIM will have to take fewer steps on each run.

I'd eventually like to extend the cycle feature so that it has no upper limit, but that would be somewhat difficult and especially hard to cram into Keen's arbitrary code length limit. If they ever raise that limit though, I'll definitely look into it.

I had several Oxygene generators ( just for fun, my ship has only hydrogene engines) After 20 same priority parameters, TIM crashed. I just changed priorities to ammount, so TIM just loads 10k full .

I ended up just taking some of the containers and removing the TIM tags from them to remove them from consideration (they were full anyway...) Guess I'll offload them to a second base/grid eventually.

Thanks for the reply and of course, Taleden, thanks for making TIM.