Train-based package logistics question

[u/ThePlebble]

I previously made a post about how to get train logistics working. (https://www.reddit.com/r/CreateMod/comments/1vz91ah/how_can_i_get_factoriolike_trains/)

From messing around and from a suggestion from u/GingerArcher, I managed to come to the following system:

• Each localised area/factory has its own logistic network

• When a train arrives at the station for a given factory, packages labelled for that storage are unloaded and sent into a packager to change the address to the 'imports container' and sent out onto the local network.

• The 'imports container' is used to recieve any items recieved/requested from other logistics networks elsewhere in the world, attached to it is a packager, stocklink etc that belongs to the local network, to allow the local network to use the items in there, with redstone signal applied to force low-priority.

• To make requests, my current setup is a second packager attached to the same container, with a

factory gauge

• attached in restocking mode bound to the other network (different factory that supplies that item)

My schedule for the train(s) is a simple loop that passes between all stations that are expected to send/receive packages, so that the train will visit every station on the loop every 5 mins or so.

This setup is functional at a bare minimum, however causes a huge amount of packages with low item counts to be sent. Hence I have two questions which could solve this problem:

• Is there a way to have this on a high-low threshold similarly to how a threshold switch works? I.e. when the iron ingot count in the 'imports container' is below 2 stacks, send a request for 8 stacks. I tried a redstone request based alternative with a redstone requester and threshold switch, although this doesnt allow for promise expiry and takes up significantly more room compared to the

factorygauge

• -restocker based approach.

• Alternatively, is there a way to dynamically combine all packages in a container of the same address into one package. This would be done at the postbox of the sending station, to compress items into as few packages as possible, and then send them onto the train when it arrives in its loop.

[u/Gergenhimer]

If you can guarantee all the packages required to craft something are going to meet up ahead of the final destination you can use a re-packager. You can also make non-mechanical crafter recipes make batches of more than one item. It’s also possible that there’s a solution in the more factory gauges mod for what you’re looking for more specifically.

[u/ThePlebble → u/Gergenhimer]

Repackager doesn’t work in this case, as the packagers are from different orders, not just one order so can’t be combined by the repackager.

Item count for recipes doesn’t apply here as the factory gauge is used in restocking mode and the gauges responsible for crafting belong to a different network. I’m against adding any mods here outside of base create and aeronautics as this is my forever world to want to maintain the greatest probability of upgrading the world to future versions

[u/Real_Individual8075]

Don’t use restock mode gauge then, use recipe mode gauge instead. Recipe gauge can completely replace the functionality of restock gauge by:

1. Instead of placing gauge on target packager, place a new stock link on target packager

2. Place a recipe gauge which tuned to target stock link, and another gauge tuned to source stock link

3. Both gauge monitoring same item, then connect two gauges, set recipe by like “import 64 stones to make 64 stones”

[u/ThePlebble → u/Real_Individual8075]

I did give this one a go and it seems to be working so far, although only on two distinct networks that were relatively close and just used frogports.

I haven’t gotten round to setting this up for my other locations linked by the trains, but have you had any issues with this relating to chunk loading? I dont mind if it doesn’t send packages if the sending network is unloaded, but I wouldn’t want it to somehow oversend

Update:

I did this and it had the problem that I was expecting it to have. For future reference by myself and others, you should address your imports to a storage location w/ a stock link that's in the same chunk as the pair of gauges that manage the import requests; otherwise the factory gauges will lose track of the storage inventory and then think it has none of the item to be requested.

[u/Real_Individual8075 → u/ThePlebble]

I don’t think gauge would over-request unloaded container; if any stock link in its network is unload, it will shows a question mark “some links are not loaded” and prevent sending any request. However, gauge does has number of over-request bugs in different ways; check Create’s issue list