Abyss Nexus & Fast-Travel Network
Activation, route verification and failure recovery for the evidence-supported Abyss Nexus network.
An Abyss Nexus is a travel node only after its activation and usable links are verified. The guide never invents a complete network from map proximity.
Patch 1.18.00 Abyss correction
Section titled “Patch 1.18.00 Abyss correction”A broken Abyss loop at Abyss Skyloop Bridge was corrected. If the loop reappears, confirm Version 2.00.02, preserve the nearest manual save and record the exact entry direction before retrying.
Source: Official Patch 1.18.00
Activation record
Section titled “Activation record”Phase 23 publishes the following record for every indexed Nexus:
- exact indexed label and region;
- nearest supported landmark or search zone;
- current-patch approach and activation signal;
- hazards, prerequisites and recovery;
- coordinate status;
- evidence and verification date.
Every current Nexus coordinate is marked unknown unless two independent current-patch sources reproduce the same numeric or normalised position. A source-map pin is useful search evidence, but it is not silently converted into a coordinate.
Network procedure
Section titled “Network procedure”- Open the current regional map and find the exact indexed label.
- Enter the white question-mark search area.
- Use Guiding Light to expose the blue glow.
- Create a manual save before a hazardous approach.
- Stand on the round floor plate until the map icon turns blue.
- Open the travel interface and record only visible destinations.
- Travel one link and verify the arrival node.
- Confirm the activation survives quit and reload.
Patch history
Section titled “Patch history”- Patch 1.02 added an Abyss Nexus in Pailune.
- Patch 1.03 allowed Nexus travel while mounted, falling, swimming or climbing.
- Patch 1.05 moved the Nexus near Zargan Tankworks to the cliff top while preserving prior activation.
- Patch 1.05 improved the Abyss map display for teleport paths.
Use the current node location, not an older screenshot.
No-route rule
Section titled “No-route rule”When no supported graph edge exists, report No verified link. Do not calculate a connection from region, distance, screenshot pixels or visual alignment.
Failure recovery
Section titled “Failure recovery”If a Nexus or link does not respond:
- record node, origin, destination and movement state;
- dismount and stand on stable ground;
- close and reopen the interface;
- leave the local interaction radius and return;
- reload the newest known-good save;
- check the current live Known Issues notice;
- preserve the failed route as blocked.
Expedition use
Section titled “Expedition use”Activate reliable nodes before:
- boss or rematch attempts;
- liberation operations;
- long trade routes;
- collectible sweeps;
- save-sensitive quest sequences.