Q: What logistics mods are supported?

A: Rift Rail currently features native integration with LTN (Logistic Train Network) and Cybersyn 2 (CS2). * CS2 support was re-introduced in v0.12 via the CS2 route plugin API. * Classic Cybersyn (v1): Support was removed in v0.10 due to architecture conflicts and will not be restored.

Q: Where is Cybersyn support?
A: Cybersyn 2 (CS2) is natively supported as of v0.12. See the CS2 setup section below.

Classic Cybersyn (v1) compatibility was permanently removed in v0.10.2 due to fundamental architecture conflicts and will not be restored.
If you strictly require classic Cybersyn integration, you must downgrade your mod version: * v0.10.1: Last version with N-to-M (Many-to-Many) Cybersyn support. * v0.8.2: Last version with 1-to-1 Cybersyn support.

⚠️ Warning: These are legacy versions. We DO NOT provide maintenance, bug fixes, or support for any Cybersyn-related issues on older versions. Use them entirely at your own risk.

Core Features: N-to-M Routing

Q: Can I connect one Entry portal to multiple Exits? (One-to-Many)
A: Yes! As of v0.10, you can connect an Entry portal to up to 5 Exit portals simultaneously.

Q: If an Entry is connected to multiple Exits, where does the train go?
A: The portal decides the destination based on the following priority:
1. Train Schedule Signal (Highest): If the train schedule includes riftrail-go-to-id = [ID] (the comparator does not affect routing; only the numeric value is read), and that ID points to a valid connected Exit, Rift Rail teleports to that Exit.
2. Entry Circuit Signal: If step 1 does not resolve to a valid Exit, Rift Rail reads riftrail-go-to-id from the Entry-side circuit network and tries to route to that Exit.
3. Default (Fallback): If neither signal resolves to a valid Exit, Rift Rail uses the configured default Exit; if unavailable, it teleports to the first available connected Exit.

Q: How do I find the "Unit Number ID" of a portal?
A: Open the GUI of any portal; the ID is usually displayed in the title bar or debug info.

Logistic Train Network (LTN) Setup

Q: How do I set up cross-surface LTN deliveries?
A: The setup logic has been updated in v0.10. To create a working route between Surface A and Surface B:

1. Requirement: Two-Way Path: The LTN dispatcher requires a return path to calculate the route validity.
   • Build Entry A -> Exit B (e.g., Nauvis to Vulcanus).
   • Build Entry C -> Exit D (e.g., Vulcanus to Nauvis).
2. Enable Switches: Open the GUI for all 4 portals involved and turn on the "LTN" switch.
3. Manual Activation: Unlike previous versions, the switch now only affects the specific building you clicked. You must ensure it is enabled on both the Entry and Exit sides.
4. Universal Network (ID -1): All Rift Rail portals are now permanently set to Network ID -1. They function as universal bridges for all LTN networks. The option to assign specific Network IDs to portals has been removed to simplify configuration.

Cybersyn 2 (CS2) Setup

Q: How do I set up cross-surface CS2 deliveries?
A: As of v0.12, Rift Rail natively supports Cybersyn 2. The setup is similar to LTN. To create a working route between Surface A and Surface B:

1. Requirement: Two-Way Path: The CS2 dispatcher needs a valid return path to dispatch trains. Build routes in both directions.
   • Build Entry A -> Exit B (e.g., Nauvis to Vulcanus).
   • Build Entry C -> Exit D (e.g., Vulcanus to Nauvis).
2. Enable Switches: Open the GUI for all 4 portals and turn on the "CS2" switch.
3. Manual Activation: Each switch only affects the specific building you clicked. You must enable it on both the Entry and Exit sides individually.
4. Automatic Route Selection: When multiple portals are available, Rift Rail automatically selects the globally optimal path by minimizing the combined distance of the train's approach to the entry and the exit's proximity to the destination stop. No manual configuration is needed.

⚠️ Tip: If you enable a CS2 switch but only a one-way route exists (e.g., A→B without a B→A return), the mod will warn you in chat. Build the return route to clear the warning.

问：目前支持哪些物流模组？

答： Rift Rail 目前与 LTN (Logistic Train Network) 和 Cybersyn 2 (CS2) 拥有原生集成。 * CS2 支持已于 v0.12 通过 CS2 的 route plugin 接口重新加入。 * 经典 Cybersyn (v1)： 由于架构冲突，v0.10 版本已移除支持，不会恢复。

问：Cybersyn 兼容功能去哪了？
答： Cybersyn 2 (CS2) 自 v0.12 起已获原生支持，请参阅下方 CS2 设置章节。

经典 Cybersyn (v1) 的兼容性已于 v0.10.2 因底层架构冲突被永久移除，不会恢复。
如果您必须使用经典 Cybersyn 集成，请降级模组版本： * v0.10.1： 支持 多对多 (N-to-M) Cybersyn 兼容的最后一个版本。 * v0.8.2： 支持 一对一 (1-to-1) Cybersyn 兼容的最后一个版本。

⚠️ 警告： 以上均为已停止维护的旧版本。作者绝对不会处理任何与 Cybersyn 相关的错误反馈，也不会对旧版本进行任何修复。请自行承担使用风险。

核心功能：多对多 (N-to-M) 路由

问：我可以将一个入口连接到多个出口吗？（一对多）
答： 可以！ 从 v0.10 开始，您可以将一个入口同时连接到最多 5 个出口传送门。

问：如果连了多个出口，火车会去哪一个？
答： 传送门会按照以下优先级决定去向：
1. 列车时刻表信号（最高优先级）： 如果列车时刻表中包含 riftrail-go-to-id = [数字]（比较符号不影响结果，只读取数值），且该 ID 对应已连接且有效的出口，列车将精准传送到该出口。
2. 入口电路信号： 如果步骤 1 未命中有效出口，系统会读取入口侧电路网络中的 riftrail-go-to-id 并尝试匹配出口。
3. 默认（保底）： 如果以上信号都未命中有效出口，系统会使用默认出口；若默认出口不可用，则传送到连接列表中的第一个可用出口。

问：我怎么知道传送门的“ID”是多少？
答： 打开任意传送门的 GUI，ID 通常会显示在标题栏或调试信息中。

LTN 物流网络设置

问：如何设置跨地表 LTN 运输？
答： v0.10 更新了设置逻辑。要建立地表 A 和地表 B 之间的 LTN 通路，您需要：

1. 硬性要求：双向往返。LTN 调度器需要计算回程路径才能成功派单。
   • 建立 入口 A -> 出口 B (例如：Nauvis 到 Vulcanus)。
   • 建立 入口 C -> 出口 D (例如：Vulcanus 到 Nauvis)。
2. 开启开关： 打开这 4 个建筑 的 GUI，全部开启 "LTN" 开关。
3. 手动激活： 与旧版本不同，现在的开关只影响您点击的那个建筑。您必须分别在入口侧和出口侧都手动开启。
4. 通用网络 (ID -1)： 所有 Rift Rail 传送门现在固定使用 网络 ID -1。它们充当所有 LTN 网络的通用桥梁。为了简化配置，自定义传送门网络 ID 的功能已被移除。

CS2 (Cybersyn 2) 跨地表设置

问：如何设置跨地表 CS2 运输？
答： 自 v0.12 起，Rift Rail 重新原生支持 Cybersyn 2。设置方式与 LTN 类似。要建立地表 A 和地表 B 之间的 CS2 通路：

1. 硬性要求：双向往返。CS2 调度器需要有效的往返路径才能派单。必须双向建立路线。
   • 建立 入口 A -> 出口 B（例如：Nauvis 到 Vulcanus）。
   • 建立 入口 C -> 出口 D（例如：Vulcanus 到 Nauvis）。
2. 开启开关： 打开这 4 个建筑 的 GUI，全部开启 "CS2" 开关。
3. 手动激活： 开关只影响您点击的那个建筑，入口侧和出口侧都必须分别手动开启。
4. 全局最优路由： 当存在多个可用传送门时，Rift Rail 会自动综合"列车到入口的距离"与"出口到目标站的距离"，选择全局最短路径，无需手动配置。

⚠️ 提示： 如果您开启 CS2 开关后只存在单向路径（例如 A→B 有，B→A 没有），模组会在聊天栏提醒您补建回程路线。