Place any rail with the type and orientation you want to change the other rails to adjacent to the Activation Module. To exchange rails, place an Activation Module and link it to all rails you want to change. This is often used to switch the direction of rails, and for advanced manipulation of docked entities. Using an Activation Module it is possible to replace or reorient rails. When the Rail Unload receives a high signal from any logic block that is linked to it, it will release the entity that is docked to it. It has no effect on "Always Allow", and "Never". If permission has already been given, the option will be displayed as " Disable current Dock pulling", and can be used to revoke the permission. It will give or revoke the one-time permission required by the settings "Always Ask", and "Always allow faction, ask for rest". If the parent entity is from a different faction or neutral, it will behave like "Always Ask". Will behave like "Always Allow" if docked to an entity aligned to the same faction, or if the pilot that docked the entity belongs to that faction, if the docked entity is neutral. Permission can also be given or revoked with the "Allow current Dock to pull/Disable current Dock pulling" options. If a player is inside the docked entity, they will be presented with a popup asking for this permission (when the next pull tick completes). This table lists and explains the available options:Ĭargo will not be transferred until a one-time permission is given. In order for cargo to be transferred from a docked entity to the parent entity, the docked entity must give the parent entity permission to pull items from its storage blocks.Ĭargo permissions can currently only be configured by entering the docked entity, opening the radial menu Tab, and navigating to the Load/Unload Rail Settings in the "Ship" section of the menu. There will be no interaction with Storage blocks that are not linked to the Rail Docker or Rail Unload. This will cause items to be transferred from the docked entity to the parent entity. (See the Cargo Permissions section below for details.) This can currently only be done by entering the docked entity, opening the radial menu Tab, and navigating to the Load/Unload Rail Settings in the "Ship" section of the menu, and there choose the desired setting. Third, the docked entity must give permission to have cargo transferred from it. Second, the linked storage on the parent entity must have its Auto-Pull active and defined items to pull. To transfer cargo, first both the Rail Unload and the Rail Docker that is docked to it must be linked to at least one Storage block on their entity. ![]() The Rail Unload will transfer cargo from the docked entity to the parent entity. The primary purpose of the Rail Unload is to allow for cargo transfer between docked entities. The arrows on the rail and docker indicate which way the docked entities will align. A Rail Docker can be attached to a Rail Unload by using the Rail Docker's docking beam on the rail it should dock to.
0 Comments
Leave a Reply. |