Hurmu Gate Network: Difference between revisions

From MicrasWiki
Jump to navigationJump to search
mNo edit summary
Line 3: Line 3:
The Hurmu Gate Network has been developed by the [[Hurmu Gate Institute]] and the [[Hurmu Gate Company]].
The Hurmu Gate Network has been developed by the [[Hurmu Gate Institute]] and the [[Hurmu Gate Company]].


All trips through the Gate Network were put on hold from 2.VII.1703 onwards, due to the death of [[Kir Azariah Vidar]] during a solo transit from [[Huyenkula Gate|Huyenkula]] to [[Walstadt Gate|Walstadt]]. An investigation is underway.
All trips through the Gate Network were briefly put on hold from 2.VII.1703 for three months, due to the death of [[Kir Azariah Vidar]] during a solo transit from [[Huyenkula Gate|Huyenkula]] to [[Walstadt Gate|Walstadt]]. An investigation identified breaches of standard operating procedures by a malcontented member of the hub control staff as the primary cause of the fractional gate misalignment incident. The gate resumed essential operations in support of the [[Hurmu Peace Corps]] during the [[Barikalus-Hurmu war]] thereafter.


== Network ==
== Network ==

Revision as of 11:45, 17 January 2022

The Hurmu Gate Network refers to the network of gates that allow for instantaneous transport between two gates through displacement of space-time.

The Hurmu Gate Network has been developed by the Hurmu Gate Institute and the Hurmu Gate Company.

All trips through the Gate Network were briefly put on hold from 2.VII.1703 for three months, due to the death of Kir Azariah Vidar during a solo transit from Huyenkula to Walstadt. An investigation identified breaches of standard operating procedures by a malcontented member of the hub control staff as the primary cause of the fractional gate misalignment incident. The gate resumed essential operations in support of the Hurmu Peace Corps during the Barikalus-Hurmu war thereafter.

Network

The network can only accommodate up to 25 gates. Currently, 7 are operational, and 6 are being built, allowing for future planning of 12 gates.

In order to travel between two gates, for example between Kaupang and Ghawlama, the Hub will arrange for opening the network between these gates at a given time. Then each gate must make it available for travel from the other.

Three sets of codes are thus entered into the system:

  • In the Hub: "H1K2G" (read as Hub opens the route from Kaupang to Ghawlama)
  • In Kaupang: "K1K2G" (read as Kaupang opens the route from Kaupang to Ghawlama)
  • In Ghawlama: "G1K2G" (read as Ghawlama opens the route from Kaupang to Ghawlama)

Then Kaupang enters its initiation code, "K!K2G" (read as Kaupang initiates travel from Kaupang to Ghawlama).

Once travel is complete, the closing codes must be entered:

  • In the Hub: "H0K2G" (read as Hub closes the route from Kaupang to Ghawlama)
  • In Kaupang: "K0K2G" (read as Kaupang closes the route from Kaupang to Ghawlama)
  • In Ghawlama: "G0K2G" (read as Ghawlama closes the route from Kaupang to Ghawlama)

The Hub cannot open a gate remotely (for security reasons), but can close a gate remotely if it does not close on its own. Similarly, the Hub can block a gate from accessing the network this way.

A B C D E F G H I J K L M N O P Q R S T U W X Y Z

Operational gates

Planned gates