-
Notifications
You must be signed in to change notification settings - Fork 0
Automation and Remote Access
The Import Bus actively pulls from the container on its arrow/front face. Its other faces connect to the network. Hoppers, pipes, and compatible automation can also insert through allowed passive-input faces.
Every 10 ticks, active import offers up to one item stack and supported bounded typed resources. It removes only what the Core can fully accept. If the Core is unavailable, conflicted, unloaded, or out of type capacity, the source remains unchanged.
The Export Bus pushes matching stored resources into the container on its front face. Other faces connect to the network but do not actively export.
Right-click with an item to set a filter; use an empty hand to clear it. Exact item properties matter. Every 10 ticks, Export offers up to one stack and removes only what the target accepted.
Use separate Export Buses for machine feeds or sorting routes. Point the front at the destination, configure filters, and test with a small amount first.
Bus configuration is server-owned and supports direction, side access, automation, Allow/Deny mode, and ordered exact filters. Cached capabilities become inert while disconnected or while rollback recovery is pending.
The Remote Terminal reaches one bound, loaded Core in the same dimension. It does not force chunks to load and does not follow a replacement Core placed at the same coordinates.