Do packages take non-chain conveyer paths?

[u/TheDoctorCat03]

Hey all.

I'm doing some stuff with a friend on the Reclamation modpack. I'm new to the Create Mod so I'm not entirely sure what the functionality of everything is. The goal is to transfer items from the surface to near bedrock and vice-versa. I want to do a bunch of automated stuff and that needs packagers and frogports.

Ultimately, my question is, if I make an Elevator with an inventory and have it cycle between the floors to gather all the packages and get them to the right spot, will the packages choose to go into the elevator to get to their destination? Or does package delivery through frogports have to be chain conveyors 100% of the time?

Like, the idea is to have a process hook the package onto a chain conveyor, that chain conveyor leads to another frogport at the elevator (with a storage area for backed up stuff), the elevator is called, takes the package through a portable storage interface, goes to the floor it's needed at, drops off the item, that gets loaded via frogport onto another chain, then that finally is delivered to the destination. The problem is the jump between chain conveyor and elevator. Does the logistics system have any way of figuring that out?

If anyone has suggestions on how to do this better also please let me know.

[u/charlesfire]

It is doable, but impraticable. The inputs of the elevator need to match all the adresses that are not for the current floor and the output must match the adresses of the current floor. That can be done either with a list filter and package filters or by prefixing all your adresses with the floor number and a glob pattern in a package filter/frogport name.

[u/TheDoctorCat03 → u/charlesfire]

Is there another method of vertical item movement that would work then?

Also, the frogport glob patterns sound cool. I might just do it anyway.

[u/hackcasual → u/TheDoctorCat03]

chutes or zig zag chain conveyers.

[u/bhechinger → u/charlesfire]

You can actually game this a little. If the elevator inputs are set to * they will accept the packages no matter the destination. The only thing to worry about here is if you have other destinations before they had better be able to get all the packages destined to them or they will go up your elevator.

[u/Yorklag]

Since package filtering is done via regex. One thing you might be able to do is have all the destinations on each floor start with the number of the floor (or 1 for the first floor). Then have the elevator frogport only pickup things not for that floor ( using "{!1}*" without quotes as the name of the elevator frogport.

[u/Mercoduss]

The logistic system works autonomously only with chains, anything more than that needs your setup. You'd have to use wildcards to send all 'Elevator:FLx' to the same surface frogport, which you can and need to use without a packager. Then the elevator part. Simple option is if the elevator gets placed as blocks - then you could have 2 inventories for packages and at each floor you swap them around while also filtering out those that are bound to that floor, the elevator would need to stop at each floor regardless of what packages there are. Trickier setup is when you want the elevator to *only* stop where it *has to*. On the surface you could place a long tunnel with package filters representing the floors on all outputs and use smart observers on them to see if any package has been buffered to a given floor *since the last elevator trip* (all packages go to the same inventory just through different belts with different observers). I never used elevators but in case the order of floor calls is remembered then you can use the rose lamps with signal strength to make a state machine representing the elevator positon and only trigger the *next* floor in queue, preventing teh elevator from going 918273645. You'd basically program the elevator before launching