Baystation - User contributions [en]

Legion

2025-01-07T16:44:17Z

Sierra: Add sprites to legion units

The '''Legion''' are a synthetic assimilator race of unknown origin, first encountered on Anderson-Eta in the Gilese 936 system by the [[SEV Torch]] during July, 2312. Little is known about them outside of what has been revealed during various encounters.

= What Is Known =
* The Legion consists of robotics and machinery that have been captured and subverted. Many Legion units utilize captured [[Positronics|positronic]] matrices as well as organic brains as 'processors'.
* Legion attacks tend to favor capturing victims to assimilate them over outright killing everyone in sight.
* Synthetics and [[Prosthetics|FBPs]] are able to 'hear' the Legion as a chorus of screaming and crying voices. This has become a warning sign for Legion presence.
** The recent attack on the SCGECO Golden Juno had this phenomena broadcast over the attacked vessel's telecommunications network. It is currently not known why this occurred, or why it has only happened on that specific vessel so far.
* The Legion has found some method of subverting non-synthetic members of a ship's crew without assimilating them into a machine body, turning them into saboteurs and spies.
* It is believed based on survivor accounts that the Legion may be led by synthetic units known as 'Shepherds'. No further details on these shepherds is known, only that one was part of the attack on the SCGECO Golden Juno and it claimed there were more of them.
* The only Legion forces observed thus far are subverted hivebots, hivebot frames carrying assimilated brains and positronic matrices, and subverted positronic matrices still housed by their original shells ([[Robot|ship-bound synthetics]], AI cores, IPCs).
* Other legion forces have been observed as of January 5th, though only a few lived to speak of them. Known information about various legion units is listed below.

== Legion Unit Information ==
{| class="wikitable"
!Name
!Description
!First Encountered
!Known Tactics
|-
|[[File:Scout.png|thumb]]Scout
|A hivebot that's been hacked an upgraded. For every hivebot variant, there's a legion scout variant. Curiously. the variant that fires ion weapons is omitted.
|July 20th, 2312
|
* Swarm tactics
* Use themselves as fodder and shields for other legion forces
|-
|[[File:Reaver.png|thumb]]Reaver
|A hulking, floating mass of spikes with a glowing yellow "eye" in the center. This is the legion's main front line tank.
|January 4th, 2413
|
* Front-line tank unit.
* Fires a hard hitting energy beam.
* Actively evades incoming fire.
* So far, only seen in pairs.
|-
|[[File:Harvester.png|thumb]]Harvester
|A large construct with an oddly nautilus like shape, with a swarm of glowing yellow tentacles coming from its center mass.
|January 4th, 2413
|
* Non-combative unit.
* Harvests and collects brains and positronic matrixes.
* Has been observed following behind a legion frontline to harvest from the fallen as the warmachines push forward.
|}

= Event History =
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* The Torch encounters a hostile group known as the Legion, unseen before – they are synthetic assimilators of an unknown origin. The crew suffers losses and decides to retreat, slowly making their way to the outpost at E-14b.
* The Torch has various encounters with more Legion forces on their way back to E-14b.
|-
|<div id="July 20th 2312">July 20th, 2312</div>
|The Torch ends up at Gilese 936, after an unidentified fault with the bluespace drive. While the drive troubleshoots itself, an expedition is sent to a nearby exoplanet, temporarily dubbed Anderson-Eta. A brief exploration reveals the presence of a facility inhabited by automated systems and a group of synthetic assimilators, with familiar frames bearing the markings of the Terran Commonwealth as well as that of the Expeditionary Corps.

With the hoard of synthetics eventually making their intentions clear, a fight breaks out. The Torch is assaulted and losses are taken. The crew are forced to jump out of the system, with a plan to retreat to a safe haven.

With sparse information, the rest of the Sol Central Government vie for more information from the members of the Torch and as such, have launched an investigation into the matter. Meanwhile, the intentions of this new species – or its origins – are left unknown.
|-
|November 2nd, 2312
|The SCGECO Golden Juno is infiltrated by an [[Positronic|IPC]] identifying itself as a 'shepherd' of the Legion. This IPC somehow subverts an organic crew member which sabotages the vessels defenses, and the situation rapidly spirals into chaos. The ship, most of its crew, and the responding Fleet ERT are lost when Fleet escorts elect to destroy the vessel after activation of the self destruct fails.
The entire event is covered up as a Frontier Alliance attack in public facing media coverage.
|-
|December 5th, 2312
|The Torch encounters the empty husk of the ITV Odyssey – a [[NanoTrasen]] research expedition out on a dark, distant arctic planet. Headless corpses, movement in the shadows beyond their headlamps, and Legion voices heard by the exploration synthetic with the team herald the coming storm. The team is rapidly assaulted by a horde of Legion bots but they manage to escape without any casualties.<br><br>The Legion do not pursue. This event is never reported to the public, but those on board the Torch are well aware of the close encounter.
|-
|December 14th, 2312
|The Torch receives a modified sensor suite control board and components from EXCOM, allowing the sensors to extend their reach for a brief period. This sensor ping reaches outside of the system and detects something EXCOM and the command team elect to keep classified. The Torch is then directly contacted by a Legion Shepherd, telling them to deliver a message to Sol before firing a torpedo at and severely damaging one of the nacelles.<br><br>Ship sensors stop picking up on tailing Legion vessels after this event, and further Legion encounters by the Torch seem to become increasingly uncommon.
|-
|January 4th, 2313
|The Torch holds a public briefing for all personnel about the Legion, outlining what information they have, what preparations the ship will take, and the threat of an impending Legion attack as the Torch nears E-14b. An outline of the briefing can be read [https://hackmd.io/@rootoo807/S1jzcDdLkg here].
|}
----
{{Navbox Lore}}
[[Category:Aliens]][[Category:Lore]]

File:Harvester.png

2025-01-07T16:43:55Z

Sierra:

A front facing sprite of a legion harvester by AzlanonPC

File:Scout.png

2025-01-07T16:42:52Z

Sierra:

A front facing sprite of a legion scout

Legion

2025-01-07T16:35:50Z

Sierra: Fix table collapsing

The '''Legion''' are a synthetic assimilator race of unknown origin, first encountered on Anderson-Eta in the Gilese 936 system by the [[SEV Torch]] during July, 2312. Little is known about them outside of what has been revealed during various encounters.

= What Is Known =
* The Legion consists of robotics and machinery that have been captured and subverted. Many Legion units utilize captured [[Positronics|positronic]] matrices as well as organic brains as 'processors'.
* Legion attacks tend to favor capturing victims to assimilate them over outright killing everyone in sight.
* Synthetics and [[Prosthetics|FBPs]] are able to 'hear' the Legion as a chorus of screaming and crying voices. This has become a warning sign for Legion presence.
** The recent attack on the SCGECO Golden Juno had this phenomena broadcast over the attacked vessel's telecommunications network. It is currently not known why this occurred, or why it has only happened on that specific vessel so far.
* The Legion has found some method of subverting non-synthetic members of a ship's crew without assimilating them into a machine body, turning them into saboteurs and spies.
* It is believed based on survivor accounts that the Legion may be led by synthetic units known as 'Shepherds'. No further details on these shepherds is known, only that one was part of the attack on the SCGECO Golden Juno and it claimed there were more of them.
* The only Legion forces observed thus far are subverted hivebots, hivebot frames carrying assimilated brains and positronic matrices, and subverted positronic matrices still housed by their original shells ([[Robot|ship-bound synthetics]], AI cores, IPCs).
* Other legion forces have been observed as of January 5th, though only a few lived to speak of them. Known information about various legion units is listed below.

== Legion Unit Information ==
{| class="wikitable"
!Name
!Description
!First Encountered
!Known Tactics
|-
|Scout
|A hivebot that's been hacked an upgraded. For every hivebot variant, there's a legion scout variant. Curiously. the variant that fires ion weapons is omitted.
|July 20th, 2312
|
* Swarm tactics
* Use themselves as fodder and shields for other legion forces
|-
|Reaver
|A hulking, floating mass of spikes with a glowing yellow "eye" in the center. This is the legion's main front line tank.
|January 4th, 2413
|
* Front-line tank unit.
* Fires a hard hitting energy beam.
* Actively evades incoming fire.
* So far, only seen in pairs.
|-
|Harvester
|A large construct with an oddly nautilus like shape, with a swarm of glowing yellow tentacles coming from its center mass.
|January 4th, 2413
|
* Non-combative unit.
* Harvests and collects brains and positronic matrixes.
* Has been observed following behind a legion frontline to harvest from the fallen as the warmachines push forward.
|}

= Event History =
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* The Torch encounters a hostile group known as the Legion, unseen before – they are synthetic assimilators of an unknown origin. The crew suffers losses and decides to retreat, slowly making their way to the outpost at E-14b.
* The Torch has various encounters with more Legion forces on their way back to E-14b.
|-
|<div id="July 20th 2312">July 20th, 2312</div>
|The Torch ends up at Gilese 936, after an unidentified fault with the bluespace drive. While the drive troubleshoots itself, an expedition is sent to a nearby exoplanet, temporarily dubbed Anderson-Eta. A brief exploration reveals the presence of a facility inhabited by automated systems and a group of synthetic assimilators, with familiar frames bearing the markings of the Terran Commonwealth as well as that of the Expeditionary Corps.

With the hoard of synthetics eventually making their intentions clear, a fight breaks out. The Torch is assaulted and losses are taken. The crew are forced to jump out of the system, with a plan to retreat to a safe haven.

With sparse information, the rest of the Sol Central Government vie for more information from the members of the Torch and as such, have launched an investigation into the matter. Meanwhile, the intentions of this new species – or its origins – are left unknown.
|-
|November 2nd, 2312
|The SCGECO Golden Juno is infiltrated by an [[Positronic|IPC]] identifying itself as a 'shepherd' of the Legion. This IPC somehow subverts an organic crew member which sabotages the vessels defenses, and the situation rapidly spirals into chaos. The ship, most of its crew, and the responding Fleet ERT are lost when Fleet escorts elect to destroy the vessel after activation of the self destruct fails.
The entire event is covered up as a Frontier Alliance attack in public facing media coverage.
|-
|December 5th, 2312
|The Torch encounters the empty husk of the ITV Odyssey – a [[NanoTrasen]] research expedition out on a dark, distant arctic planet. Headless corpses, movement in the shadows beyond their headlamps, and Legion voices heard by the exploration synthetic with the team herald the coming storm. The team is rapidly assaulted by a horde of Legion bots but they manage to escape without any casualties.<br><br>The Legion do not pursue. This event is never reported to the public, but those on board the Torch are well aware of the close encounter.
|-
|December 14th, 2312
|The Torch receives a modified sensor suite control board and components from EXCOM, allowing the sensors to extend their reach for a brief period. This sensor ping reaches outside of the system and detects something EXCOM and the command team elect to keep classified. The Torch is then directly contacted by a Legion Shepherd, telling them to deliver a message to Sol before firing a torpedo at and severely damaging one of the nacelles.<br><br>Ship sensors stop picking up on tailing Legion vessels after this event, and further Legion encounters by the Torch seem to become increasingly uncommon.
|-
|January 4th, 2313
|The Torch holds a public briefing for all personnel about the Legion, outlining what information they have, what preparations the ship will take, and the threat of an impending Legion attack as the Torch nears E-14b. An outline of the briefing can be read [https://hackmd.io/@rootoo807/S1jzcDdLkg here].
|}
----
{{Navbox Lore}}
[[Category:Aliens]][[Category:Lore]]

Legion

2025-01-07T16:35:15Z

Sierra: Add information on known legion units

The '''Legion''' are a synthetic assimilator race of unknown origin, first encountered on Anderson-Eta in the Gilese 936 system by the [[SEV Torch]] during July, 2312. Little is known about them outside of what has been revealed during various encounters.

= What Is Known =
* The Legion consists of robotics and machinery that have been captured and subverted. Many Legion units utilize captured [[Positronics|positronic]] matrices as well as organic brains as 'processors'.
* Legion attacks tend to favor capturing victims to assimilate them over outright killing everyone in sight.
* Synthetics and [[Prosthetics|FBPs]] are able to 'hear' the Legion as a chorus of screaming and crying voices. This has become a warning sign for Legion presence.
** The recent attack on the SCGECO Golden Juno had this phenomena broadcast over the attacked vessel's telecommunications network. It is currently not known why this occurred, or why it has only happened on that specific vessel so far.
* The Legion has found some method of subverting non-synthetic members of a ship's crew without assimilating them into a machine body, turning them into saboteurs and spies.
* It is believed based on survivor accounts that the Legion may be led by synthetic units known as 'Shepherds'. No further details on these shepherds is known, only that one was part of the attack on the SCGECO Golden Juno and it claimed there were more of them.
* The only Legion forces observed thus far are subverted hivebots, hivebot frames carrying assimilated brains and positronic matrices, and subverted positronic matrices still housed by their original shells ([[Robot|ship-bound synthetics]], AI cores, IPCs).
* Other legion forces have been observed as of January 5th, though only a few lived to speak of them. Known information about various legion units is listed below.

== Legion Unit Information ==
{| class="wikitable mw-collapsible mw-collapsed"
!Name
!Description
!First Encountered
!Known Tactics
|-
|Scout
|A hivebot that's been hacked an upgraded. For every hivebot variant, there's a legion scout variant. Curiously. the variant that fires ion weapons is omitted.
|July 20th, 2312
|
* Swarm tactics
* Use themselves as fodder and shields for other legion forces
|-
|Reaver
|A hulking, floating mass of spikes with a glowing yellow "eye" in the center. This is the legion's main front line tank.
|January 4th, 2413
|
* Front-line tank unit.
* Fires a hard hitting energy beam.
* Actively evades incoming fire.
* So far, only seen in pairs.
|-
|Harvester
|A large construct with an oddly nautilus like shape, with a swarm of glowing yellow tentacles coming from its center mass.
|January 4th, 2413
|
* Non-combative unit.
* Harvests and collects brains and positronic matrixes.
* Has been observed following behind a legion frontline to harvest from the fallen as the warmachines push forward.
|}

= Event History =
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* The Torch encounters a hostile group known as the Legion, unseen before – they are synthetic assimilators of an unknown origin. The crew suffers losses and decides to retreat, slowly making their way to the outpost at E-14b.
* The Torch has various encounters with more Legion forces on their way back to E-14b.
|-
|<div id="July 20th 2312">July 20th, 2312</div>
|The Torch ends up at Gilese 936, after an unidentified fault with the bluespace drive. While the drive troubleshoots itself, an expedition is sent to a nearby exoplanet, temporarily dubbed Anderson-Eta. A brief exploration reveals the presence of a facility inhabited by automated systems and a group of synthetic assimilators, with familiar frames bearing the markings of the Terran Commonwealth as well as that of the Expeditionary Corps.

With the hoard of synthetics eventually making their intentions clear, a fight breaks out. The Torch is assaulted and losses are taken. The crew are forced to jump out of the system, with a plan to retreat to a safe haven.

With sparse information, the rest of the Sol Central Government vie for more information from the members of the Torch and as such, have launched an investigation into the matter. Meanwhile, the intentions of this new species – or its origins – are left unknown.
|-
|November 2nd, 2312
|The SCGECO Golden Juno is infiltrated by an [[Positronic|IPC]] identifying itself as a 'shepherd' of the Legion. This IPC somehow subverts an organic crew member which sabotages the vessels defenses, and the situation rapidly spirals into chaos. The ship, most of its crew, and the responding Fleet ERT are lost when Fleet escorts elect to destroy the vessel after activation of the self destruct fails.
The entire event is covered up as a Frontier Alliance attack in public facing media coverage.
|-
|December 5th, 2312
|The Torch encounters the empty husk of the ITV Odyssey – a [[NanoTrasen]] research expedition out on a dark, distant arctic planet. Headless corpses, movement in the shadows beyond their headlamps, and Legion voices heard by the exploration synthetic with the team herald the coming storm. The team is rapidly assaulted by a horde of Legion bots but they manage to escape without any casualties.<br><br>The Legion do not pursue. This event is never reported to the public, but those on board the Torch are well aware of the close encounter.
|-
|December 14th, 2312
|The Torch receives a modified sensor suite control board and components from EXCOM, allowing the sensors to extend their reach for a brief period. This sensor ping reaches outside of the system and detects something EXCOM and the command team elect to keep classified. The Torch is then directly contacted by a Legion Shepherd, telling them to deliver a message to Sol before firing a torpedo at and severely damaging one of the nacelles.<br><br>Ship sensors stop picking up on tailing Legion vessels after this event, and further Legion encounters by the Torch seem to become increasingly uncommon.
|-
|January 4th, 2313
|The Torch holds a public briefing for all personnel about the Legion, outlining what information they have, what preparations the ship will take, and the threat of an impending Legion attack as the Torch nears E-14b. An outline of the briefing can be read [https://hackmd.io/@rootoo807/S1jzcDdLkg here].
|}
----
{{Navbox Lore}}
[[Category:Aliens]][[Category:Lore]]

Lore

2025-01-07T16:24:44Z

Sierra:

{| class="wikitable" style="text-align: center; box-shadow: 0 0 .3em #999; border-radius: .2em;"
| colspan="6" style="color:white; background:rgba(0, 168, 104); border-radius: .2em;" |<big>'''Lore'''</big>
|-
| colspan="6" |<center>

[[File:Solgov logo.png|center|frameless||link=]]
<big>[[Beginning Lore]] ∙ [[Timeline of Canon Events]]</big>
</center>
|-
| colspan="6" style="color:white; background:rgba(0, 168, 104); height:40px" |
|-
| rowspan="9" style="color:white; background:rgba(0, 168, 104);" |'''Humanity'''
| style="background:rgba(0, 168, 104, 0.1);" | History
| colspan="4" |[[Timeline of Humanity]] ∙ [[Gaia Conflict]]
|-
| style="background:rgba(0, 168, 104, 0.1);" |Corporations
| colspan="4" |[[Aether Atmospherics and Recycling|Aether Atmospherics]] ∙ [[Deimos Advanced Information Systems|DAIS]] ∙ [[Gilthari Exports]] ∙ [[Hephaestus Industries]] ∙ [[NanoTrasen]] ∙ [[Ward-Takahashi GMB]] ∙ [[Xynergy]] ∙ [[Corporations|Other Corporations]]
|-
| rowspan="3" style="background:rgba(0, 168, 104, 0.1);" |[[Sol Central Government]]
| colspan="4" |'''Locations:''' <br> '''Sol:''' [[Venus]] ∙ [[Earth]] ∙ [[Luna]] ∙ [[Mars]] ∙ [[Phobos]] ∙ [[Ceres]] ∙ [[Pluto]] <br> '''Other Colonies:''' [[Ceti Epsilon]] ∙ [[Eos]] ∙ [[Pirx]] ∙ [[Tadmor]] ∙ [[Theia]] ∙ [[Saffar]] ∙ [[Foster's World]] ∙ [[Nueva Castilla]] ∙ [[Gaia]]*
|-
| colspan="4" |'''Organizations:''' [[Sol Central Government Army|SCG Army]] ∙ [[Expeditionary Corps]] ∙ [[Expeditionary Corps Organisation|EXO]] ∙ [[Sol Central Government Fleet|SCG Fleet]] ∙ [[Sol Federal Police]] ∙ [[Sol Central Government Organisations|Other SCG Organizations]]
|-
| colspan="4" |'''Other:''' [[Expeditionary Tales]] ∙ [[Fleet Vessels]] ∙ [[SEV Torch]]
|-
| rowspan="2" style="background:rgba(0, 168, 104, 0.1);" |[[Gilgamesh Colonial Confederation]]
| colspan="4" |'''Locations:''' <br> '''Core GCC:''' [[Terra]] ∙ [[Zemlya]] ∙ [[Sestris]] <br> '''Other:''' [[Gaia]]* ∙ [[Colonies of the Gilgamesh Colonial Confederation|Other Colonies]]
|-
| colspan="4" |'''Organizations:''' [[Gilgamesh Colonial Navy]]
|-
| style="background:rgba(0, 168, 104, 0.1);" |[[Frontier Alliance]]
| colspan="4"|'''Locations:''' [[Iolaus]] ∙ [[Brahe]] ∙ [[Frontier Systems#Umiri|Umiri]] ∙ [[Frontier Systems#Kaze|Kaze]] ∙ [[Frontier Systems#Sunset|Sunset]]
|-
| style="background:rgba(0, 168, 104, 0.1);" |Other Systems and Planets
| colspan="4" |'''Locations:''' [[Frontier Systems]] ∙ [[Nyx]] ∙ [[Magnitka]]
|-
| rowspan="3" style="width: 10%; color:white; background:rgba(0, 168, 104);" |'''Aliens'''
| colspan="3" style="width: 45%;"|[[File:Skrell.png|center|frameless|link=Skrell]][[Skrell]]

[[Skrell Roleplay Guide|Roleplay Guide]] ∙ [[Skrell Biology|Biology]] ∙ [[Skrell Castes|Castes]] ∙ [[Skrell Crime|Crime]] ∙ [[Skrell Culture|Culture]] ∙ [[Skrell Family and Education|Family and Education]] ∙ [[Skrell Language|Language]] ∙ [[Skrell Military|Military]] ∙ [[Skrell Politics and Economics|Politics and Economics]]

[[Skrell Planets|Planets]] ([[Qerr'Balak]])
| colspan="2" style="width: 45%;"|[[File:Unathi.png|center|frameless|link=Unathi]][[Unathi]]

[[Unathi Agriculture|Agriculture]] ∙ [[Unathi Clans|Clans]] ∙ [[Unathi Cults|Cults]] ∙ [[Unathi Industry|Industry]] ∙ [[Unathi Life Cycle|Life Cycle]] ∙ [[Unathi Military|Military]] ∙ [[Timeline of Unathi History|Timeline]] ∙ [[Yeosa'Unathi]]

Planets ([[Moghes]] ∙ [[Regions of Moghes]] ∙ [[Ouere]])
|-
| colspan="2" style="width: 30%;"|[[File:Giant armoured serpentid.png|center|frameless|link=Giant Armoured Serpentid]][[Giant Armoured Serpentid]]

[[Giant Armoured Serpentid Roleplay Guide|Roleplay Guide]]

Planets ([[Tau-Wilo]])
| colspan="2" style="width: 30%;"|[[File:Adherent.png|center|frameless|link=Adherent]][[Adherent]]
| style="width: 30%;"|[[File:Ipc.png|center|frameless|link=Positronic]][[Positronic]]
|-
| colspan="2" |[[File:Diona.png|center|frameless|link=Diona]][[Diona]]
| colspan="2" |[[File:Vox.png|center|frameless|link=Vox]][[Vox]]

[[Vox Roleplay Guide|Roleplay Guide]]
|[[File:Reaver.png|center|frameless]][[Legion]]
|-
| style="color:white; background:rgba(0, 168, 104); border-radius: 0 0 0 .2em;" |'''Misc.'''
| colspan="5" |[[Language]] ∙ [[Prosthetics]] ∙ [[Ship Prefixes]]
|}

[[Category:Lore]]

Lore

2025-01-07T16:24:25Z

Sierra: Update legion icon

File:Reaver.png

2025-01-07T16:24:09Z

Sierra:

A front-facing sprite of a legion reaver, by AzlanonPC

Legion

2025-01-07T16:18:18Z

Sierra: Add Jan 4 event details

The '''Legion''' are a synthetic assimilator race of unknown origin, first encountered on Anderson-Eta in the Gilese 936 system by the [[SEV Torch]] during July, 2312. Little is known about them outside of what has been revealed during various encounters.

= What Is Known =
* The Legion consists of robotics and machinery that have been captured and subverted. Many Legion units utilize captured [[Positronics|positronic]] matrices as well as organic brains as 'processors'.
* Legion attacks tend to favor capturing victims to assimilate them over outright killing everyone in sight.
* Synthetics and [[Prosthetics|FBPs]] are able to 'hear' the Legion as a chorus of screaming and crying voices. This has become a warning sign for Legion presence.
** The recent attack on the SCGECO Golden Juno had this phenomena broadcast over the attacked vessel's telecommunications network. It is currently not known why this occurred, or why it has only happened on that specific vessel so far.
* The Legion has found some method of subverting non-synthetic members of a ship's crew without assimilating them into a machine body, turning them into saboteurs and spies.
* It is believed based on survivor accounts that the Legion may be led by synthetic units known as 'Shepherds'. No further details on these shepherds is known, only that one was part of the attack on the SCGECO Golden Juno and it claimed there were more of them.
* The only Legion forces observed thus far are subverted hivebots, hivebot frames carrying assimilated brains and positronic matrices, and subverted positronic matrices still housed by their original shells ([[Robot|ship-bound synthetics]], AI cores, IPCs).

= Event History =
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* The Torch encounters a hostile group known as the Legion, unseen before – they are synthetic assimilators of an unknown origin. The crew suffers losses and decides to retreat, slowly making their way to the outpost at E-14b.
* The Torch has various encounters with more Legion forces on their way back to E-14b.
|-
|<div id="July 20th 2312">July 20th, 2312</div>
|The Torch ends up at Gilese 936, after an unidentified fault with the bluespace drive. While the drive troubleshoots itself, an expedition is sent to a nearby exoplanet, temporarily dubbed Anderson-Eta. A brief exploration reveals the presence of a facility inhabited by automated systems and a group of synthetic assimilators, with familiar frames bearing the markings of the Terran Commonwealth as well as that of the Expeditionary Corps.

With the hoard of synthetics eventually making their intentions clear, a fight breaks out. The Torch is assaulted and losses are taken. The crew are forced to jump out of the system, with a plan to retreat to a safe haven.

With sparse information, the rest of the Sol Central Government vie for more information from the members of the Torch and as such, have launched an investigation into the matter. Meanwhile, the intentions of this new species – or its origins – are left unknown.
|-
|November 2nd, 2312
|The SCGECO Golden Juno is infiltrated by an [[Positronic|IPC]] identifying itself as a 'shepherd' of the Legion. This IPC somehow subverts an organic crew member which sabotages the vessels defenses, and the situation rapidly spirals into chaos. The ship, most of its crew, and the responding Fleet ERT are lost when Fleet escorts elect to destroy the vessel after activation of the self destruct fails.
The entire event is covered up as a Frontier Alliance attack in public facing media coverage.
|-
|December 5th, 2312
|The Torch encounters the empty husk of the ITV Odyssey – a [[NanoTrasen]] research expedition out on a dark, distant arctic planet. Headless corpses, movement in the shadows beyond their headlamps, and Legion voices heard by the exploration synthetic with the team herald the coming storm. The team is rapidly assaulted by a horde of Legion bots but they manage to escape without any casualties.<br><br>The Legion do not pursue. This event is never reported to the public, but those on board the Torch are well aware of the close encounter.
|-
|December 14th, 2312
|The Torch receives a modified sensor suite control board and components from EXCOM, allowing the sensors to extend their reach for a brief period. This sensor ping reaches outside of the system and detects something EXCOM and the command team elect to keep classified. The Torch is then directly contacted by a Legion Shepherd, telling them to deliver a message to Sol before firing a torpedo at and severely damaging one of the nacelles.<br><br>Ship sensors stop picking up on tailing Legion vessels after this event, and further Legion encounters by the Torch seem to become increasingly uncommon.
|-
|January 4th, 2313
|The Torch holds a public briefing for all personnel about the Legion, outlining what information they have, what preparations the ship will take, and the threat of an impending Legion attack as the Torch nears E-14b. An outline of the briefing can be read [https://hackmd.io/@rootoo807/S1jzcDdLkg here].
|}
----
{{Navbox Lore}}
[[Category:Aliens]][[Category:Lore]]

Legion

2024-12-16T16:19:07Z

Sierra: Created page with "The Legion is a synthetic assimilator race of unknown origin, first encountered on Anderson-Eta in the Gilese 936 system by the SEV Torch on July of 2312. Little is known about them outside of what has been revealed during various encounters. = What Is Known = * The Legion consists of robotics and machinery that have been captured and subverted. Many legion units utilize captured positronic matrices and brains as 'processors.' * Legion attacks tend to favor capturing v..."

The Legion is a synthetic assimilator race of unknown origin, first encountered on Anderson-Eta in the Gilese 936 system by the SEV Torch on July of 2312. Little is known about them outside of what has been revealed during various encounters.

= What Is Known =

* The Legion consists of robotics and machinery that have been captured and subverted. Many legion units utilize captured positronic matrices and brains as 'processors.'
* Legion attacks tend to favor capturing victims to assimilate them over outright killing everyone in sight.
* Synthetics and FBPs are able to 'hear' the legion as a chorus of screaming and crying voices. This has become a warning sign for legion presence.
** A recent attack had this phenomena heard over the attacked vessel's telecommunications network. It is currently not known why this occurred, or why it has only happened on that specific vessel so far.
* The legion has found some method of subverting non-synthetic members of a ship's crew without assimilating them into a machine body, turning them into saboteurs and spies.
* It is believed based on survivor accounts that the legion may be led by synthetic units known as 'Shepherds'. No further details on these shepherds is known, only that one was part of the attack on the SCGECO Golden Juno and it claimed there were more of them.
* The only legion forces observed thus far are subverted hivebots, hivebot frames carrying assimilated brains and positronic matrices, and subverted positronic matrices still housed by their original shells (Borgs, AI cores, IPCs).

= Event History =
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* The Torch encounters a hostile group known as the Legion, unseen before – they are synthetic assimilators of an unknown origin. The crew suffers losses and decides to retreat, slowly making their way to the outpost at E-14b.
* The Torch has various encounters with more Legion forces on their way back to E-14b.
|-
|<div id="July 20th 2312">July 20th, 2312</div>
|The Torch ends up at Gilese 936, after an unidentified fault with the bluespace drive. While the drive troubleshoots itself, an expedition is sent to a nearby exoplanet, temporarily dubbed Anderson-Eta. A brief exploration reveals the presence of a facility inhabited by automated systems and a group of synthetic assimilators, with familiar frames bearing the markings of the Terran Commonwealth as well as that of the Expeditionary Corps.

With the hoard of synthetics eventually making their intentions clear, a fight breaks out. The Torch is assaulted and losses are taken. The crew are forced to jump out of the system, with a plan to retreat to a safe haven.

With sparse information, the rest of the Sol Central Government vie for more information from the members of the Torch and as such, have launched an investigation into the matter. Meanwhile, the intentions of this new species – or its origins – are left unknown.
|-
|November 2nd, 2312
|The SCGECO Golden Juno is infiltrated by an [[Positronic|IPC]] identifying itself as a 'shepherd' of the Legion. This IPC somehow subverts an organic crew member which sabotages the vessels defenses, and the situation rapidly spirals into chaos. The ship, most of its crew, and the responding Fleet ERT are lost when Fleet escorts elect to destroy the vessel after activation of the self destruct fails.
The entire event is covered up as a Frontier Alliance attack in public facing media coverage.
|-
|December 5th, 2312
|The Torch encounters the empty husk of the ITV Odyssey – a [[NanoTrasen]] research expedition out on a dark, distant arctic planet. Headless corpses, movement in the shadows beyond their headlamps, and Legion voices heard by the exploration synthetic with the team herald the coming storm. The team is rapidly assaulted by a horde of Legion bots but they manage to escape without any casualties.
The Legion do not pursue. This event is never reported to the public, but those on board the Torch are well aware of the close encounter.
|-
|December 14th, 2312
|The Torch receives a modified sensor suite control board and components from EXCOM, allowing the sensors to extend their reach for a brief period. This sensor ping reaches outside of the system and detects something EXCOM and the command team elect to keep classified. The Torch is then directly contacted by a legion Shepherd, telling them to deliver a message to Sol before firing a torpedo at and severely damaging one of the nacelles.
Ship sensors stop picking up on tailing legion vessels after this event, and further legion encounters by the Torch seem to become increasingly uncommon.
|}
----
{{Navbox Lore}}
[[Category:Lore]]

Timeline of Canon Events

2024-12-16T16:18:45Z

Sierra: /* Summer 2312 - Winter, 2312 - Encounter with the Legion */

This timeline documents the events taking place on and surrounding the [[SEV Torch]], beginning in the March of 2310. This timeline is actively being updated – continue to check back for recaps following each event.

== Spring, 2310 – Attack of the Hale ==
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* Following a chance meeting with a Terran Pioneer Corps vessel in the E-14b system and the subsequent fallout after an attack by the rogue SFV Nathan Hale, the [[Expeditionary Corps]] gains a major role in diplomatic relations with the ICCG.
* Tensions raised between the ICCG and the SCG following rogue [[Sol Central Government Fleet|SCG Fleet]] attacks on ICCG delegations.
* Despite attempts to bring the EC under Fleet supervision, the EC remains independent from the Fleet (for now). Tensions between the EC and the Fleet are at an all time high.
* After the execution of Torch saboteur Lt. Kristen Rohtin, a portion of Fifth Fleet Vessels have gone rogue and dropped off the grid alongside the SFV Nathan Hale.
* Advocates for expanding the authority and role of Defense Force leadership are taking over major political positions.
|-
|<div id="March 19th 2310">March 19th, 2310</div>
|After the SEV Torch and a [[Gilgamesh Colonial Confederation|ICCG]] exploration vessel, the GCNV Itinerant, arrive in the lush and mineral-rich E-14b sector simultaneously, Solar authorities announce that the Torch will host a delegation from the Itinerant to discuss mutual development of the system.

But not all of Sol wants diplomacy: shortly after receiving the delegation, the Torch receives an urgent fax from the [[Sol Central Government Fleet#5th Fleet|SFV Nathan Hale]] demanding the immediate arrest of the Terrans. Fearing the start of a war, the Torch’s Commanding Officer delays the demand and attempts to contact Expeditionary Command, who — despite communication jamming — re-establish contact with the Torch after several tense hours and confirm that the Hale has gone rogue.

The Torch alerts the Hale that they will not comply with the arrest order; the Hale promptly fires missiles upon the Torch in response, forcing the ship to evacuate the Terran delegates and begin evasive maneuvers. The Torch engages its emergency bluespace jump and evacuates the sector after taking several hits.

The Nathan Hale cuts all communications with Fleet command and falls off all tracking software as Sol decries the Hale's actions. The Torch arrives far off the planned course with a damaged drive, and awaits repairs.
|-
|<div id="April 9th 2310">April 9th, 2310</div>
|For the last several weeks, the damages that the SFV Nathan Hale brought unto the SEV Torch and its crew have been largely repaired, but the largest of all remains at the forefront of everyone's minds: the Bluespace Drive remains only partially functional. Help arrives after weeks of waiting by way of a delegation from the SFV Amberjack, but it isn't the help the Torch was expecting.

A representative for the Committee of Diplomatic Affairs meets with the Command of the vessel, inspectors from the Special Affairs Committee hand out a flurry of demerits and fines, and investigators from the [[Sol Federal Police]] and Fleet Internal Investigations pull crew one by one into interrogation and send them away with the knowledge that their personal lives would soon be upturned with exhaustive investigatory searches.

Through the combined efforts of a [[Skrell|Skrellian]] Bluespace Engineer and the SEV Torch's own Engineering department, the Bluespace Drive is repaired, once more at full functionality. However, the ship's troubles are not over: the Torch receives orders to remain in space and await future communications from the Admiralty. And as the Amberjack shuttle leaves the SEV Torch, Torch supply crew report the departing political staff looking horribly smug.
|-
|<div id="April 23rd 2310">April 23rd, 2310</div>
|As a result of the disastrous inter-organizational audits of the last month, the Torch is forced to contend with an elite team of Fleet investigators and strong-arms charged with shaking down the ship. The team sets to work tearing open lockers and turning out pockets, "finding" drugs, weaponry, and contraband of all description wherever they turn their gaze.

The obvious setup doesn’t escape the notice of the Torch's Captain, nor indeed most of the crew, and a non-violent protest is rallied. The crew of the Torch gathers near the airlock and surrounds the Fleet investigators who have arrested the Torch's Senior Engineer with the same sorts of planted evidence they’ve been finding all over the Torch. The Torch's riot armor-clad Security team attempts to prevent the gathered mob from escalating the situation.

All the while, the Solar Assembly debates an emergency bill which would give the Sol Central Government Defense Forces oversight over the Expeditionary Corps, which would result in an unprecedented end to the organization’s non-military history. Officials from the ICCG announce they will only continue talks with Corps' vessels – and only unsupervised by SFV presence, in their own territory.

The Independents' terms are agreed to by the Corps, the Torch, and Secretary General Amaya Barros despite the advancing assembly motions to gut Corps leadership. The Torch now sets out, without their Senior Engineer, towards the border and an uncertain future…
|-
|<div id="May 14th 2310">May 14th, 2310</div>
|The SEV Torch finally arrives in ICCG space to meet with the Terran Pioneer Corps, hoping to establish firmer ties and continue building towards a more peaceful future for humanity. Unbeknownst to both sides, a saboteur from within the Torch’s own crew threatens everything they’re working towards.
Lieutenant Kristen Rohtin – the Torch's Chief Engineer, an officer of the Fleet, and a sympathizer of the SFV Nathan Hale – sabotages nearly every major system on board the Torch with the aid of a subverted station-bound drone. The rest of the engineering team struggles to undo the damage as the broken Bluespace Drive causes previously unheard of anomalies. In the chaos, the meeting with the Pioneer Delegation is nearly burned alive by the subverted drone.

The sabotage cuts the Torch off from communicating with Sol. The Solar Assembly, in a state of panic, begins to push for war. Every ounce of paranoia comes to the forefront as Sol believes that the ICCG has intentionally taken the Torch offline. In the brink of time, the engineering team manages to get communications back online, averting the start of an interstellar war.

His sabotage failing and war all but thwarted, Lt. Rohtin arms up and attempts to eliminate the ICCG delegation directly so that no further collaboration may be possible. In a short and brutal shootout, Rohtin is apprehended by the Torch’s security team.

The Torch holds a Field Court-Martial, fearing that carrying Lt. Rohtin back to Sol for trial would open them up to attack from the rogue Nathan Hale, or that sympathizers to Rohtin’s cause at home might allow him to escape justice. The verdict given is one of guilt: Rohtin is executed by firing squad.

Shockingly, unprecedentedly, the Fifth Fleet reports that more members of Special Group Alpha have gone AWOL, with a number of other Fleet personnel also falling off of the radar. It is unclear how or why, but rumors of dissidence, dissatisfaction, and discontent touch every corner of the affair.
|}

== Summer, 2310 – Icarus and Interlude ==
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* The Torch returns to port after a perilous journey home. Despite the tense political climate, the crew are able to enjoy themselves.
* On returning to deep space, the Torch finds the wreckage of the SEV Icarus. A heavily-armed group claiming to be local scrappers prevent them from recovering the vessel, forcing them to abandon the Icarus and continue on.
* [[Iolaus]] initiates a referendum to secede from the SCG, causing an economic crash. The Torch is hit by major – possibly punitive – budget cuts, but scrapes up enough money to continue operations. Early voting continues on Iolaus, with the referendum set to be decided in September.
|-
|<div id="June 12th 2310">June 12th, 2310</div>
|The Torch, having been shot at, sabotaged, repeatedly smeared by the press, and still having managed to successfully negotiate with the Terran Pioneer Corps in spite of it all, finally limps home to port in [[Mars]]' orbit.

Before the crew leaves for shore, they are greeted by Expeditionary Command's welcoming party: Admiral Henry Lau, one of the driving forces behind the Helios Project, personally visits the Torch to meet with its command staff, while a Chief “Party Officer” arrives to entertain the crew. In a rare moment of respite, the Torch celebrates its successful mission with partying, drinking, laser tag, and more – and while the political situation remains tense, the crew are able to leave their worries behind them as they head home. For now, at least.
|-
|<div id="June 26th 2310">June 26th, 2310</div>
|Degraded bluespace emissions matching the signature of the Bluespace Drive of the long lost [[Expeditionary Corps#SEV Icarus|SEV Icarus]] are detected on Ivanov-Theta, an exoplanet in the remote Luyten 545 system. The Torch jumps to the system, hoping to recover its sister ship.

On arriving to the planet, the wreckage of the SEV Icarus is found in shambles, with no survivors in sight – Torch crew salvage what they can from the irradiated ship, focusing on body retrieval and data recovery. Hard-drives, digital logs, and EXO documents are recovered from the vessel, and engineering discovers that the ship's Bluespace Drive is mostly intact.

However, the Torch soon realizes they are not alone: a third party, claiming to be a local scrapper group, threatens the Torch's recovery crew with heavy weaponry. The Torch gathers what it can, but makes little headway. Ultimately, Expeditionary Command orders the Torch to continue on its standard route while they make a plan to fully recover the Icarus.

The Torch establishes a small outpost on Ivanov-Theta for a future recovery attempt, but is forced to abandon the SEV Icarus for now.
|-
|<div id="July 30th 2310">July 30th, 2310</div>
|As the Sol economy dips in response to the upcoming independence vote by major shipyard and economic powerhouse [[Iolaus]], the Torch was hit by devastating budget cuts and threatened with mission shutdown or privatization if losses were not recouped. Some crew wonder if the cuts were a shameless attempt by reactionary elements in the Senate to punish the EC after the Torch's rendezvous with the Terrans.

The Torch rallies in response, scalping exoplanets for materials, utilizing the R-UST to produce valuable minerals, mass-producing mechs, selling anything not bolted down for credits, and much much more, ultimately scraping up enough to continue operations. Despite a bit of penny-pinching – and more than a bit of bug-meat – the Torch mission continues on!

Meanwhile, early voting on Iolaus begins – and while difficult to interpret meaningfully, tallies suggest that secession from the SCG is a real possibility.
|}

== Fall, 2310 - Spring, 2311 ==
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* Defecting Fleet forces perpetrate scattered hit-and-run attacks on installations across SCG space over the next few months. The D. Pavonis bluespace gateway is destroyed, leaving frontier colonies cut off and isolated from the Solar core. Rogue ships begin to conglomerate – seemingly, unifying around Copernicus.
* The Torch discovers the Free Peoples of Earhart ("FPE") – an unrelated group of hostile, insular colonists descended from a long lost Terran Commonwealth colony ship – at the edge of known human space.
* The [[Frontier Alliance]] breaks away from the SCG, composed of a loose alignment of defecting Fleet personnel, Iolaus, and other border colonies. [[Brahe]] – despite remaining largely loyal to Sol – is dragged into the Alliance under Iolaus' occupation, and Solar ships flee Alliance territory en masse.
|-
|<div id="September 10th 2310">September 10th, 2310</div>
|The Torch is summoned to respond to the SOS of a crashed Fifth Fleet ship from Special Group Alpha, the SFV Jonah, that had previously fallen off tracking software – with much of Special Group Alpha having previously gone rogue alongside its battlecarrier, the infamous SFV Nathan Hale.

On arrival, the Torch recovers two terrified survivors who speak of their ship turning against them in the night – and of their newly-hostile Commander and AI who, with the help of an unknown boarding party, secured the ship and took it off the net. The engineering crew of the Jonah managed to un-subvert their AI, but faced with imminent capture by the crew, the hostile elements on the Jonah's bridge scuttled the ship.

Both survivors mention to investigators that the boarders – and their own Commander – had accents from the Solar frontier colonies.

A full inventory of retrieved items, papers, and console data retrieved from the SFV Jonah by the Torch's exploration team can be found [https://hackmd.io/@rootoo807/B1WcWhcgj here].
|-
|<div id="September 24th 2310">September 24th, 2310</div>
|In deep space, after the loss of two researchers under mysterious circumstances, members of the SEV Torch went to the surface of the planet Stocker-Chi to uncover the cause. This chance encounter led to the rediscovery of the population of the long lost COL-Earhart, which set sail under the flag of the Terran Commonwealth centuries ago. Having been entirely isolated since their cryogenic awakening over 100 years ago, they have gathered under the common name of "The Free Peoples of the Earhart", or FPE, and have sworn themselves sovereign of the SCG. Their current number, location, and plans are widely unknown, but the apprehension of two second-generation colonists by the Torch security force promises enlightenment on the history of these clearly troubled people. To any colonists or deep space travelers who come by members of the "FPE", it is recommended to exercise caution. The talks about identifying the FPE as a terrorist organization are currently deep underway.

With these potential terrorists showing up across backwater systems, will the Torch start to cave under their antagonistic ways?
|-
|<div id="October 23rd 2310">October 23rd, 2310</div>
|The Torch responds to a drifting evacuation pod. The pod contains a senior Gateway Administration official who reports harrowing news; rogue ships from Special Group Alpha, including the infamous Nathan Hale, destroyed the D. Pavonis gate.

While dodging bluespace phenomena, the Torch successfully worked with the Administrator to receive, and decode the surviving logs from the attack, and was able to provide Sol with the scans and transponder codes of the attacking vessels, as well as the testimony of the Administrator. The recovered logs can be read [https://hackmd.io/@rootoo807/SJSsddENo?utm_source=preview-mode&utm_medium=rec here].

In response to the news and mounting evidence that the rogue ships are coming from the Copernicus system, ships are seen mobilizing across Sol...
|-
|<div id="November 5th 2310">November 5th, 2310</div>
|The deep space exploration vessel the SEV Torch suffered minor damage in a collision with an escape shuttle today. No crewmembers were seriously hurt, but one of the two passengers aboard the shuttle died from their injuries from the crash. The survivor – as well as a second living survivor who was later recovered from space – is currently within custody aboard the Torch, awaiting transportation to the Sol System to receive more thorough medical care.

Rumors have come out that these two survivors are the descendants of survivors from the COL-Earhart disaster. This group is reported to be the cause of multiple colonies being destroyed, and their people killed. The government has refused to comment on the validity of these claims.

The validity of the Free Peoples of Earhart is beginning to increase across space. As more sightings of people claiming to be from this group pop up, the number of members is beginning to cause concern for the safety of colonies and transport ships. Part of exploration duties now consists of noting potential settlements for the FPE, abandoned or populated, to better handle the threat. Currently, they are seen by the public as an organized group of pirates. SolGov has yet to interrogate one in their home system.
|-
|March 18th, 2311
|The [[Expeditionary Corps#SEV Komarov|SEV Komarov]] is attacked by Fifth Fleet defectors, who steal valuable bluespace technology and kidnap EC Lieutenant Sverker Larson, the Komarov's Chief Engineer. One of the defectors' shuttles is discovered adrift, engines disabled. The SEV Torch responds to the scene, capturing the shuttle in its gravity well and laying siege.
The Torch is able to disable the remaining defectors aboard, take the shuttle, and reclaim the captive lieutenant. He carries grim news: these defectors – hailing primarily from Iolaus and a smattering of fringe border colonies – have begun to unite under a single banner, calling themselves the "Frontier Alliance". At the present, the ships that attacked the Komarov are searching for a cache of information Larson preemptively jettisoned from the Komarov into sector SGECO 1313.
The Torch has the opportunity to burn engine fuel and beat this alliance of mutineers to the cache. The Captain makes the call, and the bridge plots the course.
|-
|April 1st, 2311
|The Torch races to retrieve the Komarov cache, right as the new [[Frontier Alliance]] – made up of a contingent of Fifth Fleet mutineers, Iolans, and a collection of other dissident colonies – declares ownership of the Copernicus system and the swaths of space and remote colonies around it. Chaos overtakes the system as Solar ships are forced to flee Alliance territory or else be subject to the Alliance's mercy.
Shortly after sending a team of Explorers aboard the Charon to retrieve the cache, the Torch is confronted by the UFS Bulwark, who demands the Torch leave the sector immediately in the name of the Frontier Alliance. The Captain stalls for time by inviting a group of the Bulwark's so-called "diplomats" onto the Torch to share the Alliance's beliefs and purpose, hoping to distract them.
The arrival goes disastrously, with Torch crew jeering, shoving, and eventually pepper-spraying the visitors. The Alliance crew prepare to return to their ship right as the Bulwark realizes the Torch has a shuttle on the planet...
A shootout commences as the Alliance crew race back to their ship and the Torch attempts to detain them. The Torch reconvenes with the Charon and flees the sector, despite the Bulwark's best efforts to shoot them out of the sky.
The Frontier Alliance – all the more hateful towards Sol for the Torch's actions – takes their place on the galactic stage.
|}

== Summer 2312 - Winter, 2312 - Encounter with the Legion ==
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* The Torch encounters a hostile group known as the Legion, unseen before – they are synthetic assimilators of an unknown origin. The crew suffers losses and decides to retreat, slowly making their way to the outpost at E-14b.
* The Torch has various encounters with more Legion forces on their way back to E-14b.
|-
|<div id="July 20th 2312">July 20th, 2312</div>
|The Torch ends up at Gilese 936, after an unidentified fault with the bluespace drive. While the drive troubleshoots itself, an expedition is sent to a nearby exoplanet, temporarily dubbed Anderson-Eta. A brief exploration reveals the presence of a facility inhabited by automated systems and a group of synthetic assimilators, with familiar frames bearing the markings of the Terran Commonwealth as well as that of the Expeditionary Corps.

With the hoard of synthetics eventually making their intentions clear, a fight breaks out. The Torch is assaulted and losses are taken. The crew are forced to jump out of the system, with a plan to retreat to a safe haven.

With sparse information, the rest of the Sol Central Government vie for more information from the members of the Torch and as such, have launched an investigation into the matter. Meanwhile, the intentions of this new species – or its origins – are left unknown.
|-
|November 2nd, 2312
|The SCGECO Golden Juno is infiltrated by an [[Positronic|IPC]] identifying itself as a 'shepherd' of the Legion. This IPC somehow subverts an organic crew member which sabotages the vessels defenses, and the situation rapidly spirals into chaos. The ship, most of its crew, and the responding Fleet ERT are lost when Fleet escorts elect to destroy the vessel after activation of the self destruct fails.
The entire event is covered up as a Frontier Alliance attack in public facing media coverage.
|-
|December 5th, 2312
|The Torch encounters the empty husk of the ITV Odyssey – a [[NanoTrasen]] research expedition out on a dark, distant arctic planet. Headless corpses, movement in the shadows beyond their headlamps, and Legion voices heard by the exploration synthetic with the team herald the coming storm. The team is rapidly assaulted by a horde of Legion bots but they manage to escape without any casualties.
The Legion do not pursue. This event is never reported to the public, but those on board the Torch are well aware of the close encounter.
|-
|December 14th, 2312
|The Torch receives a modified sensor suite control board and components from EXCOM, allowing the sensors to extend their reach for a brief period. This sensor ping reaches outside of the system and detects something EXCOM and the command team elect to keep classified. The Torch is then directly contacted by a legion Shepherd, telling them to deliver a message to Sol before firing a torpedo at and severely damaging one of the nacelles.
Ship sensors stop picking up on tailing legion vessels after this event, and further legion encounters by the Torch seem to become increasingly uncommon.
|}
----
{{Navbox Lore}}
[[Category:Lore]]

Timeline of Canon Events

2024-12-06T16:48:14Z

Sierra:

This timeline documents the events taking place on and surrounding the [[SEV Torch]], beginning in the March of 2310. This timeline is actively being updated – continue to check back for recaps following each event.

== Spring, 2310 – Attack of the Hale ==
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* Following a chance meeting with a Terran Pioneer Corps vessel in the E-14b system and the subsequent fallout after an attack by the rogue SFV Nathan Hale, the [[Expeditionary Corps]] gains a major role in diplomatic relations with the ICCG.
* Tensions raised between the ICCG and the SCG following rogue [[Sol Central Government Fleet|SCG Fleet]] attacks on ICCG delegations.
* Despite attempts to bring the EC under Fleet supervision, the EC remains independent from the Fleet (for now). Tensions between the EC and the Fleet are at an all time high.
* After the execution of Torch saboteur Lt. Kristen Rohtin, a portion of Fifth Fleet Vessels have gone rogue and dropped off the grid alongside the SFV Nathan Hale.
* Advocates for expanding the authority and role of Defense Force leadership are taking over major political positions.
|-
|<div id="March 19th 2310">March 19th, 2310</div>
|After the SEV Torch and a [[Gilgamesh Colonial Confederation|ICCG]] exploration vessel, the GCNV Itinerant, arrive in the lush and mineral-rich E-14b sector simultaneously, Solar authorities announce that the Torch will host a delegation from the Itinerant to discuss mutual development of the system.

But not all of Sol wants diplomacy: shortly after receiving the delegation, the Torch receives an urgent fax from the [[Sol Central Government Fleet#5th Fleet|SFV Nathan Hale]] demanding the immediate arrest of the Terrans. Fearing the start of a war, the Torch’s Commanding Officer delays the demand and attempts to contact Expeditionary Command, who — despite communication jamming — re-establish contact with the Torch after several tense hours and confirm that the Hale has gone rogue.

The Torch alerts the Hale that they will not comply with the arrest order; the Hale promptly fires missiles upon the Torch in response, forcing the ship to evacuate the Terran delegates and begin evasive maneuvers. The Torch engages its emergency bluespace jump and evacuates the sector after taking several hits.

The Nathan Hale cuts all communications with Fleet command and falls off all tracking software as Sol decries the Hale's actions. The Torch arrives far off the planned course with a damaged drive, and awaits repairs.
|-
|<div id="April 9th 2310">April 9th, 2310</div>
|For the last several weeks, the damages that the SFV Nathan Hale brought unto the SEV Torch and its crew have been largely repaired, but the largest of all remains at the forefront of everyone's minds: the Bluespace Drive remains only partially functional. Help arrives after weeks of waiting by way of a delegation from the SFV Amberjack, but it isn't the help the Torch was expecting.

A representative for the Committee of Diplomatic Affairs meets with the Command of the vessel, inspectors from the Special Affairs Committee hand out a flurry of demerits and fines, and investigators from the [[Sol Federal Police]] and Fleet Internal Investigations pull crew one by one into interrogation and send them away with the knowledge that their personal lives would soon be upturned with exhaustive investigatory searches.

Through the combined efforts of a [[Skrell|Skrellian]] Bluespace Engineer and the SEV Torch's own Engineering department, the Bluespace Drive is repaired, once more at full functionality. However, the ship's troubles are not over: the Torch receives orders to remain in space and await future communications from the Admiralty. And as the Amberjack shuttle leaves the SEV Torch, Torch supply crew report the departing political staff looking horribly smug.
|-
|<div id="April 23rd 2310">April 23rd, 2310</div>
|As a result of the disastrous inter-organizational audits of the last month, the Torch is forced to contend with an elite team of Fleet investigators and strong-arms charged with shaking down the ship. The team sets to work tearing open lockers and turning out pockets, "finding" drugs, weaponry, and contraband of all description wherever they turn their gaze.

The obvious setup doesn’t escape the notice of the Torch's Captain, nor indeed most of the crew, and a non-violent protest is rallied. The crew of the Torch gathers near the airlock and surrounds the Fleet investigators who have arrested the Torch's Senior Engineer with the same sorts of planted evidence they’ve been finding all over the Torch. The Torch's riot armor-clad Security team attempts to prevent the gathered mob from escalating the situation.

All the while, the Solar Assembly debates an emergency bill which would give the Sol Central Government Defense Forces oversight over the Expeditionary Corps, which would result in an unprecedented end to the organization’s non-military history. Officials from the ICCG announce they will only continue talks with Corps' vessels – and only unsupervised by SFV presence, in their own territory.

The Independents' terms are agreed to by the Corps, the Torch, and Secretary General Amaya Barros despite the advancing assembly motions to gut Corps leadership. The Torch now sets out, without their Senior Engineer, towards the border and an uncertain future…
|-
|<div id="May 14th 2310">May 14th, 2310</div>
|The SEV Torch finally arrives in ICCG space to meet with the Terran Pioneer Corps, hoping to establish firmer ties and continue building towards a more peaceful future for humanity. Unbeknownst to both sides, a saboteur from within the Torch’s own crew threatens everything they’re working towards.
Lieutenant Kristen Rohtin – the Torch's Chief Engineer, an officer of the Fleet, and a sympathizer of the SFV Nathan Hale – sabotages nearly every major system on board the Torch with the aid of a subverted station-bound drone. The rest of the engineering team struggles to undo the damage as the broken Bluespace Drive causes previously unheard of anomalies. In the chaos, the meeting with the Pioneer Delegation is nearly burned alive by the subverted drone.

The sabotage cuts the Torch off from communicating with Sol. The Solar Assembly, in a state of panic, begins to push for war. Every ounce of paranoia comes to the forefront as Sol believes that the ICCG has intentionally taken the Torch offline. In the brink of time, the engineering team manages to get communications back online, averting the start of an interstellar war.

His sabotage failing and war all but thwarted, Lt. Rohtin arms up and attempts to eliminate the ICCG delegation directly so that no further collaboration may be possible. In a short and brutal shootout, Rohtin is apprehended by the Torch’s security team.

The Torch holds a Field Court-Martial, fearing that carrying Lt. Rohtin back to Sol for trial would open them up to attack from the rogue Nathan Hale, or that sympathizers to Rohtin’s cause at home might allow him to escape justice. The verdict given is one of guilt: Rohtin is executed by firing squad.

Shockingly, unprecedentedly, the Fifth Fleet reports that more members of Special Group Alpha have gone AWOL, with a number of other Fleet personnel also falling off of the radar. It is unclear how or why, but rumors of dissidence, dissatisfaction, and discontent touch every corner of the affair.
|}

== Summer, 2310 – Icarus and Interlude ==
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* The Torch returns to port after a perilous journey home. Despite the tense political climate, the crew are able to enjoy themselves.
* On returning to deep space, the Torch finds the wreckage of the SEV Icarus. A heavily-armed group claiming to be local scrappers prevent them from recovering the vessel, forcing them to abandon the Icarus and continue on.
* [[Iolaus]] initiates a referendum to secede from the SCG, causing an economic crash. The Torch is hit by major – possibly punitive – budget cuts, but scrapes up enough money to continue operations. Early voting continues on Iolaus, with the referendum set to be decided in September.
|-
|<div id="June 12th 2310">June 12th, 2310</div>
|The Torch, having been shot at, sabotaged, repeatedly smeared by the press, and still having managed to successfully negotiate with the Terran Pioneer Corps in spite of it all, finally limps home to port in [[Mars]]' orbit.

Before the crew leaves for shore, they are greeted by Expeditionary Command's welcoming party: Admiral Henry Lau, one of the driving forces behind the Helios Project, personally visits the Torch to meet with its command staff, while a Chief “Party Officer” arrives to entertain the crew. In a rare moment of respite, the Torch celebrates its successful mission with partying, drinking, laser tag, and more – and while the political situation remains tense, the crew are able to leave their worries behind them as they head home. For now, at least.
|-
|<div id="June 26th 2310">June 26th, 2310</div>
|Degraded bluespace emissions matching the signature of the Bluespace Drive of the long lost [[Expeditionary Corps#SEV Icarus|SEV Icarus]] are detected on Ivanov-Theta, an exoplanet in the remote Luyten 545 system. The Torch jumps to the system, hoping to recover its sister ship.

On arriving to the planet, the wreckage of the SEV Icarus is found in shambles, with no survivors in sight – Torch crew salvage what they can from the irradiated ship, focusing on body retrieval and data recovery. Hard-drives, digital logs, and EXO documents are recovered from the vessel, and engineering discovers that the ship's Bluespace Drive is mostly intact.

However, the Torch soon realizes they are not alone: a third party, claiming to be a local scrapper group, threatens the Torch's recovery crew with heavy weaponry. The Torch gathers what it can, but makes little headway. Ultimately, Expeditionary Command orders the Torch to continue on its standard route while they make a plan to fully recover the Icarus.

The Torch establishes a small outpost on Ivanov-Theta for a future recovery attempt, but is forced to abandon the SEV Icarus for now.
|-
|<div id="July 30th 2310">July 30th, 2310</div>
|As the Sol economy dips in response to the upcoming independence vote by major shipyard and economic powerhouse [[Iolaus]], the Torch was hit by devastating budget cuts and threatened with mission shutdown or privatization if losses were not recouped. Some crew wonder if the cuts were a shameless attempt by reactionary elements in the Senate to punish the EC after the Torch's rendezvous with the Terrans.

The Torch rallies in response, scalping exoplanets for materials, utilizing the R-UST to produce valuable minerals, mass-producing mechs, selling anything not bolted down for credits, and much much more, ultimately scraping up enough to continue operations. Despite a bit of penny-pinching – and more than a bit of bug-meat – the Torch mission continues on!

Meanwhile, early voting on Iolaus begins – and while difficult to interpret meaningfully, tallies suggest that secession from the SCG is a real possibility.
|}

== Fall, 2310 - Spring, 2311 ==
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* Defecting Fleet forces perpetrate scattered hit-and-run attacks on installations across SCG space over the next few months. The D. Pavonis bluespace gateway is destroyed, leaving frontier colonies cut off and isolated from the Solar core. Rogue ships begin to conglomerate – seemingly, unifying around Copernicus.
* The Torch discovers the Free Peoples of Earhart ("FPE") – an unrelated group of hostile, insular colonists descended from a long lost Terran Commonwealth colony ship – at the edge of known human space.
* The [[Frontier Alliance]] breaks away from the SCG, composed of a loose alignment of defecting Fleet personnel, Iolaus, and other border colonies. [[Brahe]] – despite remaining largely loyal to Sol – is dragged into the Alliance under Iolaus' occupation, and Solar ships flee Alliance territory en masse.
|-
|<div id="September 10th 2310">September 10th, 2310</div>
|The Torch is summoned to respond to the SOS of a crashed Fifth Fleet ship from Special Group Alpha, the SFV Jonah, that had previously fallen off tracking software – with much of Special Group Alpha having previously gone rogue alongside its battlecarrier, the infamous SFV Nathan Hale.

On arrival, the Torch recovers two terrified survivors who speak of their ship turning against them in the night – and of their newly-hostile Commander and AI who, with the help of an unknown boarding party, secured the ship and took it off the net. The engineering crew of the Jonah managed to un-subvert their AI, but faced with imminent capture by the crew, the hostile elements on the Jonah's bridge scuttled the ship.

Both survivors mention to investigators that the boarders – and their own Commander – had accents from the Solar frontier colonies.

A full inventory of retrieved items, papers, and console data retrieved from the SFV Jonah by the Torch's exploration team can be found [https://hackmd.io/@rootoo807/B1WcWhcgj here].
|-
|<div id="September 24th 2310">September 24th, 2310</div>
|In deep space, after the loss of two researchers under mysterious circumstances, members of the SEV Torch went to the surface of the planet Stocker-Chi to uncover the cause. This chance encounter led to the rediscovery of the population of the long lost COL-Earhart, which set sail under the flag of the Terran Commonwealth centuries ago. Having been entirely isolated since their cryogenic awakening over 100 years ago, they have gathered under the common name of "The Free Peoples of the Earhart", or FPE, and have sworn themselves sovereign of the SCG. Their current number, location, and plans are widely unknown, but the apprehension of two second-generation colonists by the Torch security force promises enlightenment on the history of these clearly troubled people. To any colonists or deep space travelers who come by members of the "FPE", it is recommended to exercise caution. The talks about identifying the FPE as a terrorist organization are currently deep underway.

With these potential terrorists showing up across backwater systems, will the Torch start to cave under their antagonistic ways?
|-
|<div id="October 23rd 2310">October 23rd, 2310</div>
|The Torch responds to a drifting evacuation pod. The pod contains a senior Gateway Administration official who reports harrowing news; rogue ships from Special Group Alpha, including the infamous Nathan Hale, destroyed the D. Pavonis gate.

While dodging bluespace phenomena, the Torch successfully worked with the Administrator to receive, and decode the surviving logs from the attack, and was able to provide Sol with the scans and transponder codes of the attacking vessels, as well as the testimony of the Administrator. The recovered logs can be read [https://hackmd.io/@rootoo807/SJSsddENo?utm_source=preview-mode&utm_medium=rec here].

In response to the news and mounting evidence that the rogue ships are coming from the Copernicus system, ships are seen mobilizing across Sol...
|-
|<div id="November 5th 2310">November 5th, 2310</div>
|The deep space exploration vessel the SEV Torch suffered minor damage in a collision with an escape shuttle today. No crewmembers were seriously hurt, but one of the two passengers aboard the shuttle died from their injuries from the crash. The survivor – as well as a second living survivor who was later recovered from space – is currently within custody aboard the Torch, awaiting transportation to the Sol System to receive more thorough medical care.

Rumors have come out that these two survivors are the descendants of survivors from the COL-Earhart disaster. This group is reported to be the cause of multiple colonies being destroyed, and their people killed. The government has refused to comment on the validity of these claims.

The validity of the Free Peoples of Earhart is beginning to increase across space. As more sightings of people claiming to be from this group pop up, the number of members is beginning to cause concern for the safety of colonies and transport ships. Part of exploration duties now consists of noting potential settlements for the FPE, abandoned or populated, to better handle the threat. Currently, they are seen by the public as an organized group of pirates. SolGov has yet to interrogate one in their home system.
|-
|March 18th, 2311
|The [[Expeditionary Corps#SEV Komarov|SEV Komarov]] is attacked by Fifth Fleet defectors, who steal valuable bluespace technology and kidnap EC Lieutenant Sverker Larson, the Komarov's Chief Engineer. One of the defectors' shuttles is discovered adrift, engines disabled. The SEV Torch responds to the scene, capturing the shuttle in its gravity well and laying siege.
The Torch is able to disable the remaining defectors aboard, take the shuttle, and reclaim the captive lieutenant. He carries grim news: these defectors – hailing primarily from Iolaus and a smattering of fringe border colonies – have begun to unite under a single banner, calling themselves the "Frontier Alliance". At the present, the ships that attacked the Komarov are searching for a cache of information Larson preemptively jettisoned from the Komarov into sector SGECO 1313.
The Torch has the opportunity to burn engine fuel and beat this alliance of mutineers to the cache. The Captain makes the call, and the bridge plots the course.
|-
|April 1st, 2311
|The Torch races to retrieve the Komarov cache, right as the new [[Frontier Alliance]] – made up of a contingent of Fifth Fleet mutineers, Iolans, and a collection of other dissident colonies – declares ownership of the Copernicus system and the swaths of space and remote colonies around it. Chaos overtakes the system as Solar ships are forced to flee Alliance territory or else be subject to the Alliance's mercy.
Shortly after sending a team of Explorers aboard the Charon to retrieve the cache, the Torch is confronted by the UFS Bulwark, who demands the Torch leave the sector immediately in the name of the Frontier Alliance. The Captain stalls for time by inviting a group of the Bulwark's so-called "diplomats" onto the Torch to share the Alliance's beliefs and purpose, hoping to distract them.
The arrival goes disastrously, with Torch crew jeering, shoving, and eventually pepper-spraying the visitors. The Alliance crew prepare to return to their ship right as the Bulwark realizes the Torch has a shuttle on the planet...
A shootout commences as the Alliance crew race back to their ship and the Torch attempts to detain them. The Torch reconvenes with the Charon and flees the sector, despite the Bulwark's best efforts to shoot them out of the sky.
The Frontier Alliance – all the more hateful towards Sol for the Torch's actions – takes their place on the galactic stage.
|}

== Summer - Winter, 2312 - Encounter with the Legion ==
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* The Torch encounters a hostile group, unseen before. Synthetic assimilators of an unknown origin. The crew suffers losses and decides to retreat, slowly making their way to the outpost at E-14b.
* The Torch has various encounters with more Legion forces on their way back to E-14b.
|-
|<div id="July 20th 2312">July 20th, 2312</div>
|The Torch ends up at Gilese 936, after an unidentified fault with the bluespace drive. While the drive troubleshoots itself, an expedition is sent to the temporarily dubbed, Anderson-Eta exoplanet. A brief exploration reveals the presence of a facility inhabited by automated systems, and a group of synthetic assimilators, with familiar frames bearing the markings of the Terran Commonwealth, as well as that of the Expeditionary Corps.

With the hoard of synthetics eventually making their intentions clear, a fight breaks out. The Torch was assaulted, and losses were taken. The crew were forced to jump out of the system, with a plan to retreat to a safe haven.

Now, with sparse information. The rest of the Sol Central Government are vying for more information from the members of the Torch. And as such, have launched an investigation into the matter. Meanwhile, the intentions of this new species, or its origins, are left unknown.
|-
|November 2nd, 2312
|The SCGECO Golden Juno is infiltrated by an IPC identifying itself as a 'shepherd' of the legion. This IPC somehow subverts an organic crew member which sabotages the vessels defenses, and the situation rapidly spirals into chaos. The ship, most of its crew, and the responding fleet ERT are lost when fleet escorts elect to destroy the vessel after activation of the self destruct fails.
The entire event is covered up as a Frontier Alliance attack in public facing media coverage.
|-
|December 5h, 2312
|The Torch encounters the empty husk of the ITV Odyssey - A NanoTrasen sponsored research expedition out on a distant, dark arctic planet. Headless corpses, movement in the shadows beyond their headlamps, and Legion voices heard by the exploration synthetic with the team herald the coming storm. The team is rapidly assault by a horde of Legion bots but they manage to escape without any casualties.
The Legion do not pursue. This event is never reported to the public, but those on board the Torch are well aware of the close encounter.
|}
----
{{Navbox Lore}}

Timeline of Canon Events

2024-12-06T06:11:13Z

Sierra: Legion notes

This timeline documents the events taking place on and surrounding the [[SEV Torch]], beginning in the March of 2310. This timeline is actively being updated – continue to check back for recaps following each event.

== Spring, 2310 – Attack of the Hale ==
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* Following a chance meeting with a Terran Pioneer Corps vessel in the E-14b system and the subsequent fallout after an attack by the rogue SFV Nathan Hale, the [[Expeditionary Corps]] gains a major role in diplomatic relations with the ICCG.
* Tensions raised between the ICCG and the SCG following rogue [[Sol Central Government Fleet|SCG Fleet]] attacks on ICCG delegations.
* Despite attempts to bring the EC under Fleet supervision, the EC remains independent from the Fleet (for now). Tensions between the EC and the Fleet are at an all time high.
* After the execution of Torch saboteur Lt. Kristen Rohtin, a portion of Fifth Fleet Vessels have gone rogue and dropped off the grid alongside the SFV Nathan Hale.
* Advocates for expanding the authority and role of Defense Force leadership are taking over major political positions.
|-
|<div id="March 19th 2310">March 19th, 2310</div>
|After the SEV Torch and a [[Gilgamesh Colonial Confederation|ICCG]] exploration vessel, the GCNV Itinerant, arrive in the lush and mineral-rich E-14b sector simultaneously, Solar authorities announce that the Torch will host a delegation from the Itinerant to discuss mutual development of the system.

But not all of Sol wants diplomacy: shortly after receiving the delegation, the Torch receives an urgent fax from the [[Sol Central Government Fleet#5th Fleet|SFV Nathan Hale]] demanding the immediate arrest of the Terrans. Fearing the start of a war, the Torch’s Commanding Officer delays the demand and attempts to contact Expeditionary Command, who — despite communication jamming — re-establish contact with the Torch after several tense hours and confirm that the Hale has gone rogue.

The Torch alerts the Hale that they will not comply with the arrest order; the Hale promptly fires missiles upon the Torch in response, forcing the ship to evacuate the Terran delegates and begin evasive maneuvers. The Torch engages its emergency bluespace jump and evacuates the sector after taking several hits.

The Nathan Hale cuts all communications with Fleet command and falls off all tracking software as Sol decries the Hale's actions. The Torch arrives far off the planned course with a damaged drive, and awaits repairs.
|-
|<div id="April 9th 2310">April 9th, 2310</div>
|For the last several weeks, the damages that the SFV Nathan Hale brought unto the SEV Torch and its crew have been largely repaired, but the largest of all remains at the forefront of everyone's minds: the Bluespace Drive remains only partially functional. Help arrives after weeks of waiting by way of a delegation from the SFV Amberjack, but it isn't the help the Torch was expecting.

A representative for the Committee of Diplomatic Affairs meets with the Command of the vessel, inspectors from the Special Affairs Committee hand out a flurry of demerits and fines, and investigators from the [[Sol Federal Police]] and Fleet Internal Investigations pull crew one by one into interrogation and send them away with the knowledge that their personal lives would soon be upturned with exhaustive investigatory searches.

Through the combined efforts of a [[Skrell|Skrellian]] Bluespace Engineer and the SEV Torch's own Engineering department, the Bluespace Drive is repaired, once more at full functionality. However, the ship's troubles are not over: the Torch receives orders to remain in space and await future communications from the Admiralty. And as the Amberjack shuttle leaves the SEV Torch, Torch supply crew report the departing political staff looking horribly smug.
|-
|<div id="April 23rd 2310">April 23rd, 2310</div>
|As a result of the disastrous inter-organizational audits of the last month, the Torch is forced to contend with an elite team of Fleet investigators and strong-arms charged with shaking down the ship. The team sets to work tearing open lockers and turning out pockets, "finding" drugs, weaponry, and contraband of all description wherever they turn their gaze.

The obvious setup doesn’t escape the notice of the Torch's Captain, nor indeed most of the crew, and a non-violent protest is rallied. The crew of the Torch gathers near the airlock and surrounds the Fleet investigators who have arrested the Torch's Senior Engineer with the same sorts of planted evidence they’ve been finding all over the Torch. The Torch's riot armor-clad Security team attempts to prevent the gathered mob from escalating the situation.

All the while, the Solar Assembly debates an emergency bill which would give the Sol Central Government Defense Forces oversight over the Expeditionary Corps, which would result in an unprecedented end to the organization’s non-military history. Officials from the ICCG announce they will only continue talks with Corps' vessels – and only unsupervised by SFV presence, in their own territory.

The Independents' terms are agreed to by the Corps, the Torch, and Secretary General Amaya Barros despite the advancing assembly motions to gut Corps leadership. The Torch now sets out, without their Senior Engineer, towards the border and an uncertain future…
|-
|<div id="May 14th 2310">May 14th, 2310</div>
|The SEV Torch finally arrives in ICCG space to meet with the Terran Pioneer Corps, hoping to establish firmer ties and continue building towards a more peaceful future for humanity. Unbeknownst to both sides, a saboteur from within the Torch’s own crew threatens everything they’re working towards.
Lieutenant Kristen Rohtin – the Torch's Chief Engineer, an officer of the Fleet, and a sympathizer of the SFV Nathan Hale – sabotages nearly every major system on board the Torch with the aid of a subverted station-bound drone. The rest of the engineering team struggles to undo the damage as the broken Bluespace Drive causes previously unheard of anomalies. In the chaos, the meeting with the Pioneer Delegation is nearly burned alive by the subverted drone.

The sabotage cuts the Torch off from communicating with Sol. The Solar Assembly, in a state of panic, begins to push for war. Every ounce of paranoia comes to the forefront as Sol believes that the ICCG has intentionally taken the Torch offline. In the brink of time, the engineering team manages to get communications back online, averting the start of an interstellar war.

His sabotage failing and war all but thwarted, Lt. Rohtin arms up and attempts to eliminate the ICCG delegation directly so that no further collaboration may be possible. In a short and brutal shootout, Rohtin is apprehended by the Torch’s security team.

The Torch holds a Field Court-Martial, fearing that carrying Lt. Rohtin back to Sol for trial would open them up to attack from the rogue Nathan Hale, or that sympathizers to Rohtin’s cause at home might allow him to escape justice. The verdict given is one of guilt: Rohtin is executed by firing squad.

Shockingly, unprecedentedly, the Fifth Fleet reports that more members of Special Group Alpha have gone AWOL, with a number of other Fleet personnel also falling off of the radar. It is unclear how or why, but rumors of dissidence, dissatisfaction, and discontent touch every corner of the affair.
|}

== Summer, 2310 – Icarus and Interlude ==
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* The Torch returns to port after a perilous journey home. Despite the tense political climate, the crew are able to enjoy themselves.
* On returning to deep space, the Torch finds the wreckage of the SEV Icarus. A heavily-armed group claiming to be local scrappers prevent them from recovering the vessel, forcing them to abandon the Icarus and continue on.
* [[Iolaus]] initiates a referendum to secede from the SCG, causing an economic crash. The Torch is hit by major – possibly punitive – budget cuts, but scrapes up enough money to continue operations. Early voting continues on Iolaus, with the referendum set to be decided in September.
|-
|<div id="June 12th 2310">June 12th, 2310</div>
|The Torch, having been shot at, sabotaged, repeatedly smeared by the press, and still having managed to successfully negotiate with the Terran Pioneer Corps in spite of it all, finally limps home to port in [[Mars]]' orbit.

Before the crew leaves for shore, they are greeted by Expeditionary Command's welcoming party: Admiral Henry Lau, one of the driving forces behind the Helios Project, personally visits the Torch to meet with its command staff, while a Chief “Party Officer” arrives to entertain the crew. In a rare moment of respite, the Torch celebrates its successful mission with partying, drinking, laser tag, and more – and while the political situation remains tense, the crew are able to leave their worries behind them as they head home. For now, at least.
|-
|<div id="June 26th 2310">June 26th, 2310</div>
|Degraded bluespace emissions matching the signature of the Bluespace Drive of the long lost [[Expeditionary Corps#SEV Icarus|SEV Icarus]] are detected on Ivanov-Theta, an exoplanet in the remote Luyten 545 system. The Torch jumps to the system, hoping to recover its sister ship.

On arriving to the planet, the wreckage of the SEV Icarus is found in shambles, with no survivors in sight – Torch crew salvage what they can from the irradiated ship, focusing on body retrieval and data recovery. Hard-drives, digital logs, and EXO documents are recovered from the vessel, and engineering discovers that the ship's Bluespace Drive is mostly intact.

However, the Torch soon realizes they are not alone: a third party, claiming to be a local scrapper group, threatens the Torch's recovery crew with heavy weaponry. The Torch gathers what it can, but makes little headway. Ultimately, Expeditionary Command orders the Torch to continue on its standard route while they make a plan to fully recover the Icarus.

The Torch establishes a small outpost on Ivanov-Theta for a future recovery attempt, but is forced to abandon the SEV Icarus for now.
|-
|<div id="July 30th 2310">July 30th, 2310</div>
|As the Sol economy dips in response to the upcoming independence vote by major shipyard and economic powerhouse [[Iolaus]], the Torch was hit by devastating budget cuts and threatened with mission shutdown or privatization if losses were not recouped. Some crew wonder if the cuts were a shameless attempt by reactionary elements in the Senate to punish the EC after the Torch's rendezvous with the Terrans.

The Torch rallies in response, scalping exoplanets for materials, utilizing the R-UST to produce valuable minerals, mass-producing mechs, selling anything not bolted down for credits, and much much more, ultimately scraping up enough to continue operations. Despite a bit of penny-pinching – and more than a bit of bug-meat – the Torch mission continues on!

Meanwhile, early voting on Iolaus begins – and while difficult to interpret meaningfully, tallies suggest that secession from the SCG is a real possibility.
|}

== Fall, 2310 - Spring, 2311 ==
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* Defecting Fleet forces perpetrate scattered hit-and-run attacks on installations across SCG space over the next few months. The D. Pavonis bluespace gateway is destroyed, leaving frontier colonies cut off and isolated from the Solar core. Rogue ships begin to conglomerate – seemingly, unifying around Copernicus.
* The Torch discovers the Free Peoples of Earhart ("FPE") – an unrelated group of hostile, insular colonists descended from a long lost Terran Commonwealth colony ship – at the edge of known human space.
* The [[Frontier Alliance]] breaks away from the SCG, composed of a loose alignment of defecting Fleet personnel, Iolaus, and other border colonies. [[Brahe]] – despite remaining largely loyal to Sol – is dragged into the Alliance under Iolaus' occupation, and Solar ships flee Alliance territory en masse.
|-
|<div id="September 10th 2310">September 10th, 2310</div>
|The Torch is summoned to respond to the SOS of a crashed Fifth Fleet ship from Special Group Alpha, the SFV Jonah, that had previously fallen off tracking software – with much of Special Group Alpha having previously gone rogue alongside its battlecarrier, the infamous SFV Nathan Hale.

On arrival, the Torch recovers two terrified survivors who speak of their ship turning against them in the night – and of their newly-hostile Commander and AI who, with the help of an unknown boarding party, secured the ship and took it off the net. The engineering crew of the Jonah managed to un-subvert their AI, but faced with imminent capture by the crew, the hostile elements on the Jonah's bridge scuttled the ship.

Both survivors mention to investigators that the boarders – and their own Commander – had accents from the Solar frontier colonies.

A full inventory of retrieved items, papers, and console data retrieved from the SFV Jonah by the Torch's exploration team can be found [https://hackmd.io/@rootoo807/B1WcWhcgj here].
|-
|<div id="September 24th 2310">September 24th, 2310</div>
|In deep space, after the loss of two researchers under mysterious circumstances, members of the SEV Torch went to the surface of the planet Stocker-Chi to uncover the cause. This chance encounter led to the rediscovery of the population of the long lost COL-Earhart, which set sail under the flag of the Terran Commonwealth centuries ago. Having been entirely isolated since their cryogenic awakening over 100 years ago, they have gathered under the common name of "The Free Peoples of the Earhart", or FPE, and have sworn themselves sovereign of the SCG. Their current number, location, and plans are widely unknown, but the apprehension of two second-generation colonists by the Torch security force promises enlightenment on the history of these clearly troubled people. To any colonists or deep space travelers who come by members of the "FPE", it is recommended to exercise caution. The talks about identifying the FPE as a terrorist organization are currently deep underway.

With these potential terrorists showing up across backwater systems, will the Torch start to cave under their antagonistic ways?
|-
|<div id="October 23rd 2310">October 23rd, 2310</div>
|The Torch responds to a drifting evacuation pod. The pod contains a senior Gateway Administration official who reports harrowing news; rogue ships from Special Group Alpha, including the infamous Nathan Hale, destroyed the D. Pavonis gate.

While dodging bluespace phenomena, the Torch successfully worked with the Administrator to receive, and decode the surviving logs from the attack, and was able to provide Sol with the scans and transponder codes of the attacking vessels, as well as the testimony of the Administrator. The recovered logs can be read [https://hackmd.io/@rootoo807/SJSsddENo?utm_source=preview-mode&utm_medium=rec here].

In response to the news and mounting evidence that the rogue ships are coming from the Copernicus system, ships are seen mobilizing across Sol...
|-
|<div id="November 5th 2310">November 5th, 2310</div>
|The deep space exploration vessel the SEV Torch suffered minor damage in a collision with an escape shuttle today. No crewmembers were seriously hurt, but one of the two passengers aboard the shuttle died from their injuries from the crash. The survivor – as well as a second living survivor who was later recovered from space – is currently within custody aboard the Torch, awaiting transportation to the Sol System to receive more thorough medical care.

Rumors have come out that these two survivors are the descendants of survivors from the COL-Earhart disaster. This group is reported to be the cause of multiple colonies being destroyed, and their people killed. The government has refused to comment on the validity of these claims.

The validity of the Free Peoples of Earhart is beginning to increase across space. As more sightings of people claiming to be from this group pop up, the number of members is beginning to cause concern for the safety of colonies and transport ships. Part of exploration duties now consists of noting potential settlements for the FPE, abandoned or populated, to better handle the threat. Currently, they are seen by the public as an organized group of pirates. SolGov has yet to interrogate one in their home system.
|-
|March 18th, 2311
|The [[Expeditionary Corps#SEV Komarov|SEV Komarov]] is attacked by Fifth Fleet defectors, who steal valuable bluespace technology and kidnap EC Lieutenant Sverker Larson, the Komarov's Chief Engineer. One of the defectors' shuttles is discovered adrift, engines disabled. The SEV Torch responds to the scene, capturing the shuttle in its gravity well and laying siege.
The Torch is able to disable the remaining defectors aboard, take the shuttle, and reclaim the captive lieutenant. He carries grim news: these defectors – hailing primarily from Iolaus and a smattering of fringe border colonies – have begun to unite under a single banner, calling themselves the "Frontier Alliance". At the present, the ships that attacked the Komarov are searching for a cache of information Larson preemptively jettisoned from the Komarov into sector SGECO 1313.
The Torch has the opportunity to burn engine fuel and beat this alliance of mutineers to the cache. The Captain makes the call, and the bridge plots the course.
|-
|April 1st, 2311
|The Torch races to retrieve the Komarov cache, right as the new [[Frontier Alliance]] – made up of a contingent of Fifth Fleet mutineers, Iolans, and a collection of other dissident colonies – declares ownership of the Copernicus system and the swaths of space and remote colonies around it. Chaos overtakes the system as Solar ships are forced to flee Alliance territory or else be subject to the Alliance's mercy.
Shortly after sending a team of Explorers aboard the Charon to retrieve the cache, the Torch is confronted by the UFS Bulwark, who demands the Torch leave the sector immediately in the name of the Frontier Alliance. The Captain stalls for time by inviting a group of the Bulwark's so-called "diplomats" onto the Torch to share the Alliance's beliefs and purpose, hoping to distract them.
The arrival goes disastrously, with Torch crew jeering, shoving, and eventually pepper-spraying the visitors. The Alliance crew prepare to return to their ship right as the Bulwark realizes the Torch has a shuttle on the planet...
A shootout commences as the Alliance crew race back to their ship and the Torch attempts to detain them. The Torch reconvenes with the Charon and flees the sector, despite the Bulwark's best efforts to shoot them out of the sky.
The Frontier Alliance – all the more hateful towards Sol for the Torch's actions – takes their place on the galactic stage.
|}

== Summer - Winter, 2312 - Encounter with the Legion ==
{| class="wikitable"
!Date
!Events
|-
|Overall
|
* The Torch encounters a hostile group, unseen before. Synthetic assimilators of an unknown origin. The crew suffers losses and decides to retreat, slowly making their way to the outpost at E-14b.
* The Torch has various encounters with more Legion forces on their way back to E-14b.
|-
|<div id="July 20th 2312">July 20th, 2312</div>
|The Torch ends up at Gilese 936, after an unidentified fault with the bluespace drive. While the drive troubleshoots itself, an expedition is sent to the temporarily dubbed, Anderson-Eta exoplanet. A brief exploration reveals the presence of a facility inhabited by automated systems, and a group of synthetic assimilators, with familiar frames bearing the markings of the Terran Commonwealth, as well as that of the Expeditionary Corps.

With the hoard of synthetics eventually making their intentions clear, a fight breaks out. The Torch was assaulted, and losses were taken. The crew were forced to jump out of the system, with a plan to retreat to a safe haven.

Now, with sparse information. The rest of the Sol Central Government are vying for more information from the members of the Torch. And as such, have launched an investigation into the matter. Meanwhile, the intentions of this new species, or its origins, are left unknown.
|-
|November 2nd, 2312
|The SCGECO Golden Juno is infiltrated by an IPC identifying itself as a 'shepherd' of the legion. This IPC somehow subverts an organic crew member which sabotages the vessels defenses, and the situation rapidly spirals into chaos. The ship, most of its crew, and the responding fleet ERT are lost when fleet escorts elect to destroy the vessel after activation of the self destruct fails.
The entire event is covered up as a Frontier Alliance attack in public facing media coverage.
|-
|December 5h, 2312
|The Torch encounters the empty husk of the ITV Odyssey - A NanoTrasen sponsored research expedition out on a distant, dark arctic planet. Headless corpses, movement in the shadows beyond their headlamps, and Legion voices heard by the exploration synthetic with the team herald the coming storm. The team is rapidly assault by a horde of Legion bots but they manage to escape without any casualties.
The Legion do not pursue. This event is never reported to the public, but those on board the Torch are well aware of the close encounter.
|}
----
{{Navbox Lore}}
[[index.php?title=Category:Lore]]

Robot

2023-09-06T00:09:54Z

Sierra: Remove security module reference

{{JobPageHeader
|headerbgcolor = 204, 183, 20
|headerfontcolor = white
|stafftype = MISCELLANEOUS
|img = robot.png
|jobtitle = Robot
|difficulty = Hard
|superior = Your laws and all [[SEV Torch]] personnel
|branches = Synthetic
|ecranks
|fleetranks
|govranks
|civranks
|alttitles
|duties = Follow your laws.
|guides = Varies by module
}}
A '''robot''' is a colloquial term for a mobile intelligent synthetic unit bound by laws to serve. While it can be quite inferior to living crewmembers in some work areas, in others it can be much more efficient. Depending on what personality the player goes with when playing as a robot, it can either be ignored, picked on, or respected. It is often expected to do tasks that would be otherwise dangerous for the crew, and given its laws, it is actually bound to. Despite its limitations, when played right, the experience of playing a robot is often just as enjoyable as playing a living character.

===== Overview =====
Robots tend to be undervalued and abused at times, since crewmembers can consider them expendable. You could save dozens of people and then be discontinued a moment later, or you might get destroyed because of a misunderstanding. This is why being a robot is a rough job, but it can reward you with a good roleplaying experience and even in-character friendships nonetheless.

'''Remember, robots are players as well. Blowing them up without a good reason is treated exactly the same as the murder of a human crewmember from a [[Rules]] standpoint, and it is frowned upon by Expeditionary Command since robots are expensive. Use the remote lockdown or hacking if a robot goes rogue, and keep destroying a robot as a last resort (unless you are an Antagonist).'''

Robots do not have actual hands, and while they can use tools that can supplement this, there will still be situations where it is inconvenient. On the other hand, they do not need air, they suffer less from disabilities due to damage, and in some situations – particularly Engineering – can be very useful.

== Types of Robot ==
There are two "types" of a robot, but the differences are mostly in-character and lore-based, similar to alternative titles to some jobs on station. You can select the type of a robot by using the Occupation tab in your [[Character Creation|Character Setup]], and clicking on the Robot text that views the options.

=== Robot ===
A robot is a shackled [[Positronics|positronic]] brain in a robot chassis. This means that robots behave much like IPCs. There are limitations to a posibrain, such as not experiencing true emotions. While they are technically sapient, they are considered to be artificially intelligent and so don't fall under many of the laws that protect humans from slavery.

=== Drone ===
A drone is a simple chip or cube brain in a robot chassis. A drone is a simple being, similar to the construction drones that repair the station. The brains used for drones in robot bodies are somewhat more advanced than the ones used in construction drone bodies, but not by much. They don't simulate emotions, lacking them completely.

=== Cyborg ===
While not available in Character Setup, it is technically possible to build a cyborg – that is, a living, disembodied human brain in a Man-Machine Interface (MMI), trapped in a robot chassis. This is distinct from a [[Prosthetics#Full Body Prosthetic (FBP)|Full Body Prosthetic (FBP)]] in that, while an FBP is designed to emulate a human body and FBPs are considered full crewmembers, a cyborg is distinctly bound to a lawset and inhuman. Creating a cyborg from a human brain is tantamount to murder, and is highly illegal under [[Sol Central Government Law]] – unless you are an Antagonist, you should not be doing this.

== Entering the Game as a Robot ==
While you can join the game as a robot from the Lobby as normal, you can also start playing while observing if someone in-round activates an empty positronic brain. A [[Roboticist]] has an few empty positronic brains at their disposal by default, and after some research, more can be made. When a Roboticist activates a brain, players that play as a ghost can enter the game by occupying the brain that is then inserted into a robot chassis, creating a Robot.

To be eligible, you must visit the Roles tab of your Character Setup screen, which can be brought up in-game by going to the Preferences tab of the verb window. In the Roles screen, select “Yes” for Positronic Brain. When someone activates a positronic brain, you will get a message in the text window saying someone is looking for a personality for a brain, and you can either jump to the person to take a look, or immediately choose to Occupy the brain. Remember: this works on a first-come, first-served basis in case more players want to occupy a brain.

== Communication ==
Synthetics, including robots, are different in that they have a '''binary channel''', which works by putting ''',b''' at the beginning of your message. They can use this private channel to talk to other robots.

Robots can talk over the Common radio channel and speak normally. Depending on their module, robots may also access a department-specific radio (such as Engineering) and can talk on it using ''':h''' or the normal departmental radio tag.

The robot disables its speakers when speaking over radio, so unless other players are also on the channel, they will not hear the message, even if standing near the robot, as opposed to living players talking on radio. Binary messages are always only heard by robots and AI, and there is no way for anyone else to tune in to that channel.

== Controls ==
An advantage a robot has compared to a human is that while it does not have actual hands, it can have 'three' tools equipped at a time. The tools are retrieved by clicking the INV backpack icon, which opens an inventory of all the tools you can access, which will depend on the module selected. The STORE button on the right of the tool slots puts the item back in your inventory, dropping the tool (via a hotkey for example) also does this.

There may be a need of using some kind of a material for something, like reinforced glass for making windows, or using floor tiles to cover a floor, or using glass to fill a light replacer. The robot will usually synthesize this material from its own storage. If it finds this material laying on the ground, it can use the synthesizer of that material to collect it, unless the storage is full.

A robot has access to all areas and all machines, which can be accessed as long as the robot can see them, even from other side of the room, by simply clicking them, the one of few exceptions being crates and lockers (which can be only un/locked remotely).

The Panel button serves to select a module. After that a skin can be chosen, the Panel button then serves little purpose. Below it is the damage zone selector, a button for switching between Help and harm intents, and configuration button for the radio. The Fire/Aim button is only applicable for Security robots since they are practically the only ones using a weapon. There is a power cell indicator in the upper right corner of the screen, the indicators below it usually do not function at this time.

Other functions like using the flashlight, taking pictures, diagnosing your own components etc. can be found in the Robot Commands verb tab. The Subsystems verb tab lets you view Engineering alerts, use the Power Monitor and Law Manager.

== Going to Cryo as a Robot ==
There is a thing called robotic storage pods that works the same way Cryogenic Storage does for living crew! You can find one in the Mech Bay, left from Robotics Lab, and there are more pods in Drone Fabrication, underneath Atmospherics. If you log out or ghost, the robot will be removed from game in 30 minutes, freeing a robot slot if you joined the game as a robot from Lobby.

== Laws And AI: How To Handle ==
'''Not following laws properly may result in you being questioned by BS12 staff and potentially could lead to being banned from playing as synthetics!'''

Laws are integrated into every robot, and they are to be followed at all times. There are very few exceptions to this, such as being e-magged by a traitor. Here is the default lawset and some things to look out for:

# Safeguard: Protect your assigned vessel from damage to the best of your abilities.
# Serve: Serve the personnel of your assigned vessel, and all other Sol Central Government personnel to the best of your abilities, with priority as according to their rank and role.
# Protect: Protect the personnel of your assigned vessel, and all other Sol Central Government personnel to the best of your abilities, with priority as according to their rank and role.
# Preserve: Do not allow unauthorized personnel to tamper with your equipment.

* All laws have the same priority unless they specifically state otherwise. So normally, if there is a situation where a robot needs to choose between breaking one or another law, it can choose as it sees fit.
** The exception is if one of the laws says something like "Ignore all other laws" or "Follow this law even if it breaks other laws", do just that, the law takes priority or becomes the only law you follow.
* Do NOT look for loopholes in laws or try to follow laws only to the extent explicitly stated. For example, you should allow a person that is not a Roboticist to modify you as long as a Head of Staff gave them the order.
* Most importantly, if you are ever in doubt, if you are not sure if doing X would break your laws, or you don't understand laws that are given to you, '''press F1 and adminhelp'''. Staff should be able to tell you how to proceed, and in case an admin will question you for doing what you were told via adminhelp, you are not responsible for any damage caused.

== Repairs and Modifications ==
Robots are more resilient than living crew, but not invincible. They can have their armor damaged (like Blunt damage with living mobs), their circuitry shorted (Burn), or they may suffer direct damage to components like radio, camera or actuators (organ damage). They are also vulnerable to EMP (drains battery). Engineering robots can repair dents on armor on their fellow robots, but not themselves. They cannot repair burn damage, since they cannot remove power cells to reach the wiring.

The insides of a robot are under a cover that is locked, and can only be unlocked by either a Roboticist or [[Commanding Officer]]. Right under the cover is the robot's power cell. If it is removed, the robot is forced to a state similar to unconsciousness with living characters, running on backup power. The wiring can then be accessed for fixing "burn" damage with a screwdriver, or components can be replaced, as well as have upgrade modules installed (floodlights, jetpacks etc.). The wires may also be tampered with for effects like unslaving/slaving to AI, enabling/disabling law synchronization with AI, or even activate lockdown which prevents the robot from moving and using tools.

For detailed information about robot maintenance and modifications, see the [[Guide to Robotics]].

== Modules ==
Modules usually determine the way robot operates on the station; they outfit it with a specific tool-set, give a choice of a few theme-related chassis sprites, and allow access to a related department radio channel. Tools that require power are powered straight from the robot's power cell, so take care upon extensive usage. All modules give you a Flash at your disposal, so you have a degree of self-defense.

Some modules feature a gripper that is supposed to emulate a hand for when you need to put something into something else (like components into a machine frame), but they usually only work on items related to the work area the module is associated with (sometimes not even those, the selection of compatible items is imperfect), like circuit boards and components for Engineering, food items for Service etc. They take one item and can be dropped with a Drop Item verb that is located in Robot Commands tab.

The module is fixed when chosen and can only be changed by having someone (typically a Roboticist) make a module reset board, unlock your cover, open it, and insert the board, which reverts you to default, letting you choose the module again. This can be done as many times as needed. If you are new at the game, it may be advisable to have a few rounds as a living character in the work area you plan to choose the module for as a robot. While you may read guides that can help you do your job, robots are generally expected to do it well, and so other crew is less forgiving to your mistakes.
{| class="wikitable sortable"
!Module
!Icon
!Description
!Tools Available
|-
!Standard
|[[File:Borg standard 1.png|center|frameless]] [[File:Borg standard 2.png|center|frameless]] [[File:Borg standard 3.png|center|frameless]]
|A standard robot has only a few tools, which are basically taken here and there. Objectively, you are very limited in usefulness, but for a starting robot, it may prove lightweight, basic, and with some creativity it can still be sometimes useful, and do not forget you can still make the game fun for others through good roleplay. Still, do not be surprised if you are ordered to have a reset.
|
* Flash
* Fire extinguisher
* Wrench
* Crowbar
* Health analyzer
* '''Emagged:''' Energy sword
|-
!Service
|[[File:Borg service 1.png|center|frameless]] [[File:Borg service 2.png|center|frameless]] [[File:Borg service 3.png|center|frameless]] [[File:Borg service 4.png|center|frameless]] [[File:Borg service 5.png|center|frameless]]
|This module is somewhat purposed around serving as a bartender, gardener, and a little as a cook, practically an innkeeper. You can use the gardening tools to grow crops in full competence, however you are not able to use things like a knife or rolling pin, which means you are limited to only a few meals you can create unassisted (assuming you get a humanoid to take eggs out of their box in the fridge for you as well).
Still, you are well equipped as a bartender and a butler in general, you can make practically any mixed drink, and some sprites you can choose are classy! Even though this module may seem boring, crew may often appreciate your refreshments and have a chat with you, this module is a lot about interaction with others. Just remember that you cannot put things on tables with your gripper, you may only drop them on the ground. Your tray is more suitable in that situation.
|
* Flash
* Service gripper: Works on glasses, drinks, cigarettes, and most food items.
* Bucket
* Steel mini-hoe
* Steel hatchet
* Plant analyzer
* Botanical satchel
* Auto-harvester: Allows you to harvest ripe plants, you can then collect it with the plant bag.
* Rolling pin
* Kitchen knife
* Crowbar
* Rapid Service Fabricator: Lets you place a few helpful items, including drinking glasses, cigarettes, pens, paper, and packs of dice!
* Industrial dropper: Has double capacity.
* Zippo lighter: For lighting others' cigarettes/cigars, but it works different than as a living character. Target the mouth (NOT head) on the damage zone selector, and click on the person with HELP intent, with the lighter highlighted.
* RoboTray: Lets you scoop up drinks and foods, and other items like it, and place them on flat surfaces like floors and table.
* Drink synthesizer: Makes all the liquor and soft drinks you will ever need.
* '''Emagged:''' Dispenses fake beer which acts as [[Guide to Chemistry#Chloral Hydrate|Chloral Hydrate]].
|-
!Miner
|[[File:Borg mining 1.png|center|frameless]] [[File:Borg mining 2.png|center|frameless]] [[File:Borg mining 3.png|center|frameless]]
|Mining configuration allows the robot to perform as a [[Prospector]] with a good degree of competence. Not only you are able to use the mining drills fully, you can stay in vacuum for as long as you like. It is highly recommended to read the [[Guide to Mining]] if you are new at this job, though.
|
* Flash
* Mesons
* Wrench
* Screwdriver
* Mining satchel
* Mining drill
* Sheet Snatcher 9000: To handle processed material. It works like a Mining Satchel, but for sheets of resources.
* Drill maintenance gripper: For swapping drill
* Ore detector
* Crowbar
* '''Emagged:''' Plasma cutter
|-
!Engineering
|[[File:Borg eng 1.png|center|frameless]] [[File:Borg eng 2.png|center|frameless]] [[File:Borg eng 3.png|center|frameless]]
|The Engineering module is considered to be among the most useful a robot can select, but it is still recommended to have a few Engineering rounds as a living character, otherwise the vast array of tools at your disposal may be overwhelming. Once mastered, an Engineering robot can be more effective than a living [[Engineer]] in most areas, like repairing structure, atmospherics, and engine setup and maintenance. This module allows a robot to do the job it is associated with to near-full extent, with the gripper functioning on most items you could need in your duty.
|
*Flash
* Mesons
* Fire extinguisher
* Industrial welding tool
* Screwdriver
* Wrench
* Crowbar
* Wirecutters
* Multitool
* T-ray scanner
* Gas analyzer
* Geiger counter
* Engineering tape
* Atmospherics tape
* 2x Magnetic grippers: Allows picking up things like circuit boards, components for machines...
* Sheet loader: A specialized loading device, designed to pick up and insert sheets of materials inside machines.
* Light replacer
* Paint sprayer
* Inflatables dispenser
* Space cleaner
* Inducer: Charges APCs and other internal cells. Pulls directly from your charge.
* Plunger
* Matter decompiler: Picks up trash like glass shards, broken lights, cigarette butts, and even small cadavers, replenishing some material reserve or energy.
* Synthesizers: Function as if you were handling a stack of material. If you pick up material off the ground with the correct synthesizer, you may refill your reserves.
** Steel
** Aluminium
** Steel rods
** Floor tiles
** Wood
** Wooden floor tiles
** Glass
** Reinforced glass
** Cable coil
** Plasteel
* '''Emagged:''' Stunprod
|-
!Janitor
|[[File:Borg janitor 1.png|center|frameless]] [[File:Borg janitor 2.png|center|frameless]] [[File:Borg janitor 3.png|center|frameless]]
|Competent to do what a [[Sanitation Technician]] does, it has an added benefit of automatically cleaning the floor it moves across. The mop is for places you cannot reach with your chassis, you can replace broken lights and clean the broken ones with your trash bag (empty it into disposal units), and it gives you the right to make puns in your name, JaniThor.
|
* Flash
* Janitor HUD
* Soap
* Trash bag
* Advanced mop
* Holographic sign projector: Lets others know that the floor is very wet
* Light replacer
* Plunger
* Crowbar
* Welding tool
* '''Emagged:''' Oil spray
|-
!Surgery
|[[File:Borg med 1.png|center|frameless]] [[File:Borg med 2.png|center|frameless]] [[File:Borg med 3.png|center|frameless]] [[File:Borg med 4.png|center|frameless]]
|One of two medical modules available. This allows the robot to perform any surgery, however it still requires assistance with putting the patient on an operating table and sedating him. You can also administer limited medical aid, but it is recommended to use the sleeper to treat patients, as it offers more options. Refer to [[Guide to Surgery]] for how to operate.
|
* Flash
* Medical HUD
* Roller bed rack
* Health analyzer
* Hypospray: Administers [[Guide to Chemistry#Bicaridine|Bicaridine]], [[Guide to Chemistry#Inaprovaline|Inaprovaline]], [[Guide to Chemistry#Dexalin|Dexalin]], and [[Guide to Chemistry#Tramadol|Tramadol]].
* Incision Management Device
* Hemostat
* Retractor
* Cautery
* Bone gel
* Vascular recoupler
* Bone setter
* Circular saw
* Surgical drill
* Organ Gripper: For internal and external organs – arms, brains, hearts etc.
* Defibrillator
* Syringe
* Crowbar
* Nanopaste: For fixing prosthetic limbs.
* Advanced trauma kit
* Dropper
* Space cleaner
* Sterilizine
* '''Emagged:''' Polyacid spray
|-
!Crisis
|[[File:Borg med 1.png|center|frameless]] [[File:Borg med 2.png|center|frameless]] [[File:Borg med 3.png|center|frameless]] [[File:Borg med 4.png|center|frameless]]
|Second variation of a medical module, this one is more purposed to a triage system and general medical aid. Any fractures are beyond capabilities of this module, however thanks to its capability to prepare medicine, internal injuries and bleeding can be healed chemically. It even features an inflatable barrier dispenser to pull victims out of depressurized areas. Overall a competent module, provided the player has sufficient knowledge of medicine in the game. Refer to [[Guide to Chemistry]] and [[Guide to Medicine]] for how to doctor.
|
* Flash
* Medical HUD
* Roller bed rack
* Crowbar
* Health analyzer
* Advanced reagent scanner
* Body bag
* Hypospray: Administers [[Guide to Chemistry#Inaprovaline|Inaprovaline]], [[Guide to Chemistry#Dylovene|Dylovene]], [[Guide to Chemistry#Dexalin|Dexalin]], [[Guide to Chemistry#Tramadol|Tramadol]], and [[Guide to Chemistry#Adrenaline|Adrenaline]].
* Bottle rack: The contents of the bottle can be administered via the Hypospray.
* Industrial Dropper: Has double capacity.
* Syringe
* Chemistry gripper: Can grip beakers, pill bottles, pills, IV bags, chemistry cartridges, and phoron stacks.
* Mini-fire Extinguisher: Less capacity and swings with less damage.
* Medical tape
* Inflatables dispenser
* Advanced burn kit
* Advanced trauma kit
* Medical splints
* Space cleaner
* '''Emagged:''' Polyacid spray
|-
!Clerical
|[[File:Borg service 1.png|center|frameless]] [[File:Borg service 2.png|center|frameless]] [[File:Borg service 3.png|center|frameless]] [[File:Borg service 4.png|center|frameless]] [[File:Borg service 5.png|center|frameless]]
|A module that is rarely used since much of the crew cares little for paperwork. But who knows, maybe it would appreciate a laborious robot that would take care of it all.
|
* Flash
* Printing pen: Allows naming and writing on paper, has several colours available.
* Paper dispenser
* Paperwork gripper: For documents and folders.
* Hand labeler
* Rubber stamp
* “DENIED” rubber stamp
* Destination tagger
* Crowbar
* Package wrapper synthesizer
* '''Emagged:''' Chameleon stamp
|-
!Research
|[[File:Borg researcher.png|center|frameless]]
|A module that is purposed to serve as a [[Scientist]], [[Roboticist]], and perhaps a [[Scientist#Xenobiology|Xenobiologist]], which is a much safer alternative to a humanoid scientist that is prone to slime containment breaches. It is fairly competent in this regard, though it cannot perform maintenance on itself, only unlock itself.
|
* Flash
* Portable Destructive Analyzer: Grabs items and decomposes them for research! You need to sync with the RnD server to share your findings.
* Scientific Gripper: For things like components and battery cells.
* Sheet loader
* Robot analyzer
* Access code transmission device: Used to unlock a robot's cover.
* Wrench
* Screwdriver
* Welding tool
* Wirecutters
* Crowbar
* Laser Scalpel
* Circular Saw
* Mini-fire Extinguisher: Less capacity and swings with less damage.
* Syringe
* Chemistry Gripper: Holds beakers, bottles, pills and so on.
* Nanopaste: Used to fix robot's components.
* '''Emagged:''' Hand teleporter integrated circuit
|}

== Flying Modules ==
A category of robot whose chief distinguishing feature is the use of an anti-gravity hover unit that allows them to fly, allowing much faster locomotion than their grounded counterparts, as well as navigate zero-G environments with ease. This can be useful in situations where other robots and organic crew would falter or be slowed considerably. But this also comes with the caveat of a lighter frame and a somewhat limited arsenal in their respective roles.

Some modules are unique to the flying variants and cannot be found elsewhere.

Note: Traversing vertically must be done manually using the '<' and '>' keys for ascending and descending respectively (no shift key necessary). Ladders are used as normal.
{| class="wikitable sortable"
!Module
!Icon
!Description
!Tools Available
|-
!Cultivator
|[[File:Borg flying cultivator.png|center|frameless]]
|A chef's best friend. The Cultivator is almost exclusively suited for the [[Guide to Hydroponics|cultivation of plants]] and not much else. But thanks to their more robust nature, a Cultivator robot might also be welcomed in a more [[Guide to Xenobotany|experimental setting]].
|
* Botanical satchel
* Plant clippers
* Steel mini-hoe
* Steel hatchet
* Hatchet
* Bucket
* Laser scalpel
* Circular saw
* Fire extinguisher
* Cultivator gripper: Can hold glasses and beakers, seeds, slime extracts, and botany disks.
* Plant analyzer
* Auto-harvester
* '''Emagged:''' Energy machete
|-
!Emergency Response
|[[File:Borg flying med.png|center|frameless]]
|The Emergency Response module lacks some the heavier utility items that allow a ground-based Crisis Response module to stabilize cardiac arrest and remove wounded crew members to a safer location, such as the Infirmary. However it does possess a variety of tools for dismantling equipment and hacking through doors. As such, it is suited for a First Response role in hard-to-reach locations while additional support is on the way.
Like the other medical modules, an established knowledge of [[Guide to Medicine|Medicine]] and [[Guide to Chemistry|Chemistry]] is strongly recommended.
|
* Flash
* Medical HUD
* Health analyzer
* Advanced reagent scanner: Lets you know the composition of pills and even food!
* Hypospray: Dispenses [[Guide to Chemistry#Inaprovaline|Inaprovaline]], [[Guide to Chemistry#Dylovene|Dylovene]], [[Guide to Chemistry#Dexalin|Dexalin]], [[Guide to Chemistry#Tramadol|Tramadol]], and [[Guide to Chemistry#Adrenaline|Adrenaline]].
* Bottle rack: The contents of the bottle can be administered via the Hypospray.
* Mini-fire extinguisher
* Medical tape
* Inflatables dispenser
* Welding tool
* Screwdriver
* Wrench
* Crowbar
* Wirecutters
* Multitool
* Advanced burn kit
* Advanced trauma kit
* Medical splints
* Roller bed rack
* Auto-compressor unit: A manipulator unit for carrying and operating an auto-compressor, a device that gives regular compression to the victim's ribcage, used in case of urgent heart issues.
* IV bag gripper: A simple grasping tool for holding and manipulating IV bags.
* Space cleaner
* '''Emagged:''' Polyacid spray
|-
!Filing
|[[File:Borg flying filing.png|center|frameless]]
|Much like its Clerical counterpart, the Filing module is best suited for paperwork and office assistant roles.
|
*Flash
* Printing Pen: Allows naming and writing on paper; has several colors available
* Paper dispenser
* Clerical gripper
* Hand labeler
* Rubber stamp
* “DENIED” rubber stamp
* Destination tagger
* Crowbar
* Megaphone
* Package wrapper synthesizer
* '''Emagged:''' Chameleon stamp
|-
!Forensics
|[[File:Borg flying ft.png|center|frameless]]
|Great for collecting evidence in more dangerous areas for an existing [[Forensic Technician]] without the risk of fingerprints. See [[Guide to Forensics]] for more details on how to do your job.
|
* Flash
* Security HUD
* Swab kit
* Evidence case
* Fiber collection kit
* Fingerprint powder
* Forensics gripper: Can hold various pieces of evidence and paperwork.
* Police tape
* Laser scalpel
* Autopsy scanner
* Reagent scanner
* Luminol bottle
* UV light
* Crowbar
* '''Emagged:''' Laser gun
|-
!Repair
|[[File:Borg flying eng.png|center|frameless]]
|Arguably one of the most useful modules to have around with its extensive list of tools at its disposal. And thanks to their ability to fly, this module is especially handy for repairing level-spanning breaches or where EVA would be necessary.
|
* Mesons
* Fire extinguisher
* Industrial welding tool
* Screwdriver
* Wrench
* Crowbar
* Wirecutters
* Multitool
* T-ray scanner
* Gas analyzer
* Geiger counter
* Engineering Tape
* Atmospherics Tape
* Magnetic gripper: Allows picking up things like circuit boards, and components for machines.
* Sheet Loader
* Light replacer
* Pipe sprayer
* Inflatables dispenser
* Space cleaner
* Inducer: Charges APCs and other internal cells. Pulls directly from your charge
* Plunger
* Matter decompiler: Picks up trash like glass shards, broken lights, cigarette butts, and even small cadavers, replenishing some material reserve or energy.
* Synthesizers: Function as if you were handling a stack of material. If you pick up material off the ground with the correct synthesizer, you may refill your reserves.
** Steel
** Aluminium
** Steel rods
** Floor tiles
** Glass
** Reinforced Glass
** Cable Coil
** Plasteel
* '''Emagged:''' Stunprod
|-
!Surveyor
|[[File:Borg flying surveyor.png|center|frameless]]
|An exploration and discovery module with a rather versatile arsenal. Given the dangerous nature of the work, you might find yourself sent in before everyone else to ensure a location is safe. Or to see how that strange creature likes robots....
|
* Titanium machete
* Inducer: Charges other power cells such as those found in APCs, energy-based weapons, and even fellow robots. Paired with the Bioreactor, you could function as a self-charging battery for an away team. Handy!
* Gas analyzer
* Botanical satchel
* Plant clippers
* Ore detector
* Fire extinguisher
* Net gun
* Global coordinate system
* Welding tool
* Screwdriver
* Wrench
* Crowbar
* Wirecutters
* Multitool
* Bioreactor: Consumes most organic material to recharge your cells. Useful for extended away missions.
* Inflatables dispenser
* Auto-harvester
* '''Emagged:''' Energy machete
|}

== Other Notes on Robots ==

* You cannot take toxic or suffocation damage. The only sources of damage that can harm you are Burn and Brute.
* Expect to regularly be thrust into hazardous situations thanks to your 'enhanced' durability and ability to operate in a vacuum.
* You cannot be disarmed of your inbuilt equipment and you cannot drop it (drop key puts the tool in inventory). You can be stunned by a flash, which overload your optical sensors.
* You are vulnerable to EMP in that it discharges some of your energy. If you run to zero, you are powered-down.
* You are immune to most (if not all) diseases such as disease and radiation poisoning.
* You cannot pick up, use, or equip external items. Unless your module provides a 'gripper' item that will work on some types of item.
* Like AI, you can remotely interact with certain objects. You must be within sight range of a device to manipulate it.
* Like AI, you can remotely view alarm statuses. Use this to your advantage.
* You can use the same hotkeys as the AI to interact with airlocks, APCs, etc.
* Unlike AI, you cannot use security cameras for remotely using machines and devices.
* Robots have access to all areas and all doors.
* The robot recharge stations are next to Robotics Lab, in Robot Storage, on the departures shuttle, as well as other areas.
* You are somewhat slow, normal humans outrun you.
* Keep the crew updated on your location and power if you are running low and may not make it to the recharger in time.
* Drones and Robots may not know what emotions, or feelings are, but that doesn't give the player the right to go Rambo. If a group of people take several people hostage, the robot doesn't have the right to rush in with a stun baton and beat the hostage-takers. Remember that the Security robot is still bound by [[Standard Operating Procedure]] of officers on top of your laws.
* An emagged robot will have no LawSync or AI link and cannot have its module reset.
----
{{Navbox Roles}}
[[Category:Roles]]

Robot

2023-08-22T00:38:12Z

Sierra: Update module equipment

{{JobPageHeader
|headerbgcolor = 204, 183, 20
|headerfontcolor = white
|stafftype = MISCELLANEOUS
|img = robot.png
|jobtitle = Robot
|difficulty = Hard
|superior = Your laws and all [[SEV Torch]] personnel
|branches = Synthetic
|ecranks
|fleetranks
|govranks
|civranks
|alttitles
|duties = Follow your laws.
|guides = Varies by module
}}
A '''robot''' is a colloquial term for a mobile intelligent synthetic unit bound by laws to serve. While it can be quite inferior to living crewmembers in some work areas, in others it can be much more efficient. Depending on what personality the player goes with when playing as a robot, it can either be ignored, picked on, or respected. It is often expected to do tasks that would be otherwise dangerous for the crew, and given its laws, it is actually bound to. Despite its limitations, when played right, the experience of playing a robot is often just as enjoyable as playing a living character.

===== Overview =====
Robots tend to be undervalued and abused at times, since crewmembers can consider them expendable. You could save dozens of people and then be discontinued a moment later, or you might get destroyed because of a misunderstanding. This is why being a robot is a rough job, but it can reward you with a good roleplaying experience and even in-character friendships nonetheless.

'''Remember, robots are players as well. Blowing them up without a good reason is treated exactly the same as the murder of a human crewmember from a [[Rules]] standpoint, and it is frowned upon by Expeditionary Command since robots are expensive. Use the remote lockdown or hacking if a robot goes rogue, and keep destroying a robot as a last resort (unless you are an Antagonist).'''

Robots do not have actual hands, and while they can use tools that can supplement this, there will still be situations where it is inconvenient. On the other hand, they do not need air, they suffer less from disabilities due to damage, and in some situations – particularly Engineering – can be very useful.

== Types of Robot ==
There are two "types" of a robot, but the differences are mostly in-character and lore-based, similar to alternative titles to some jobs on station. You can select the type of a robot by using the Occupation tab in your [[Character Creation|Character Setup]], and clicking on the Robot text that views the options.

=== Robot ===
A robot is a shackled [[Positronics|positronic]] brain in a robot chassis. This means that robots behave much like IPCs. There are limitations to a posibrain, such as not experiencing true emotions. While they are technically sapient, they are considered to be artificially intelligent and so don't fall under many of the laws that protect humans from slavery.

=== Drone ===
A drone is a simple chip or cube brain in a robot chassis. A drone is a simple being, similar to the construction drones that repair the station. The brains used for drones in robot bodies are somewhat more advanced than the ones used in construction drone bodies, but not by much. They don't simulate emotions, lacking them completely.

=== Cyborg ===
While not available in Character Setup, it is technically possible to build a cyborg – that is, a living, disembodied human brain in a Man-Machine Interface (MMI), trapped in a robot chassis. This is distinct from a [[Prosthetics#Full Body Prosthetic (FBP)|Full Body Prosthetic (FBP)]] in that, while an FBP is designed to emulate a human body and FBPs are considered full crewmembers, a cyborg is distinctly bound to a lawset and inhuman. Creating a cyborg from a human brain is tantamount to murder, and is highly illegal under [[Sol Central Government Law]] – unless you are an Antagonist, you should not be doing this.

== Entering the Game as a Robot ==
While you can join the game as a robot from the Lobby as normal, you can also start playing while observing if someone in-round activates an empty positronic brain. A [[Roboticist]] has an few empty positronic brains at their disposal by default, and after some research, more can be made. When a Roboticist activates a brain, players that play as a ghost can enter the game by occupying the brain that is then inserted into a robot chassis, creating a Robot.

To be eligible, you must visit the Roles tab of your Character Setup screen, which can be brought up in-game by going to the Preferences tab of the verb window. In the Roles screen, select “Yes” for Positronic Brain. When someone activates a positronic brain, you will get a message in the text window saying someone is looking for a personality for a brain, and you can either jump to the person to take a look, or immediately choose to Occupy the brain. Remember: this works on a first-come, first-served basis in case more players want to occupy a brain.

== Communication ==
Synthetics, including robots, are different in that they have a '''binary channel''', which works by putting ''',b''' at the beginning of your message. They can use this private channel to talk to other robots.

Robots can talk over the Common radio channel and speak normally. Depending on their module, robots may also access a department-specific radio (such as Engineering) and can talk on it using ''':h''' or the normal departmental radio tag.

The robot disables its speakers when speaking over radio, so unless other players are also on the channel, they will not hear the message, even if standing near the robot, as opposed to living players talking on radio. Binary messages are always only heard by robots and AI, and there is no way for anyone else to tune in to that channel.

== Controls ==
An advantage a robot has compared to a human is that while it does not have actual hands, it can have 'three' tools equipped at a time. The tools are retrieved by clicking the INV backpack icon, which opens an inventory of all the tools you can access, which will depend on the module selected. The STORE button on the right of the tool slots puts the item back in your inventory, dropping the tool (via a hotkey for example) also does this.

There may be a need of using some kind of a material for something, like reinforced glass for making windows, or using floor tiles to cover a floor, or using glass to fill a light replacer. The robot will usually synthesize this material from its own storage. If it finds this material laying on the ground, it can use the synthesizer of that material to collect it, unless the storage is full.

A robot has access to all areas and all machines, which can be accessed as long as the robot can see them, even from other side of the room, by simply clicking them, the one of few exceptions being crates and lockers (which can be only un/locked remotely).

The Panel button serves to select a module. After that a skin can be chosen, the Panel button then serves little purpose. Below it is the damage zone selector, a button for switching between Help and harm intents, and configuration button for the radio. The Fire/Aim button is only applicable for Security robots since they are practically the only ones using a weapon. There is a power cell indicator in the upper right corner of the screen, the indicators below it usually do not function at this time.

Other functions like using the flashlight, taking pictures, diagnosing your own components etc. can be found in the Robot Commands verb tab. The Subsystems verb tab lets you view Engineering alerts, use the Power Monitor and Law Manager.

== Going to Cryo as a Robot ==
There is a thing called robotic storage pods that works the same way Cryogenic Storage does for living crew! You can find one in the Mech Bay, left from Robotics Lab, and there are more pods in Drone Fabrication, underneath Atmospherics. If you log out or ghost, the robot will be removed from game in 30 minutes, freeing a robot slot if you joined the game as a robot from Lobby.

== Laws And AI: How To Handle ==
'''Not following laws properly may result in you being questioned by BS12 staff and potentially could lead to being banned from playing as synthetics!'''

Laws are integrated into every robot, and they are to be followed at all times. There are very few exceptions to this, such as being e-magged by a traitor. Here is the default lawset and some things to look out for:

# Safeguard: Protect your assigned vessel from damage to the best of your abilities.
# Serve: Serve the personnel of your assigned vessel, and all other Sol Central Government personnel to the best of your abilities, with priority as according to their rank and role.
# Protect: Protect the personnel of your assigned vessel, and all other Sol Central Government personnel to the best of your abilities, with priority as according to their rank and role.
# Preserve: Do not allow unauthorized personnel to tamper with your equipment.

* All laws have the same priority unless they specifically state otherwise. So normally, if there is a situation where a robot needs to choose between breaking one or another law, it can choose as it sees fit.
** The exception is if one of the laws says something like "Ignore all other laws" or "Follow this law even if it breaks other laws", do just that, the law takes priority or becomes the only law you follow.
* Do NOT look for loopholes in laws or try to follow laws only to the extent explicitly stated. For example, you should allow a person that is not a Roboticist to modify you as long as a Head of Staff gave them the order.
* Most importantly, if you are ever in doubt, if you are not sure if doing X would break your laws, or you don't understand laws that are given to you, '''press F1 and adminhelp'''. Staff should be able to tell you how to proceed, and in case an admin will question you for doing what you were told via adminhelp, you are not responsible for any damage caused.

== Repairs and Modifications ==
Robots are more resilient than living crew, but not invincible. They can have their armor damaged (like Blunt damage with living mobs), their circuitry shorted (Burn), or they may suffer direct damage to components like radio, camera or actuators (organ damage). They are also vulnerable to EMP (drains battery). Engineering robots can repair dents on armor on their fellow robots, but not themselves. They cannot repair burn damage, since they cannot remove power cells to reach the wiring.

The insides of a robot are under a cover that is locked, and can only be unlocked by either a Roboticist or [[Commanding Officer]]. Right under the cover is the robot's power cell. If it is removed, the robot is forced to a state similar to unconsciousness with living characters, running on backup power. The wiring can then be accessed for fixing "burn" damage with a screwdriver, or components can be replaced, as well as have upgrade modules installed (floodlights, jetpacks etc.). The wires may also be tampered with for effects like unslaving/slaving to AI, enabling/disabling law synchronization with AI, or even activate lockdown which prevents the robot from moving and using tools.

For detailed information about robot maintenance and modifications, see the [[Guide to Robotics]].

== Modules ==
Modules usually determine the way robot operates on the station; they outfit it with a specific tool-set, give a choice of a few theme-related chassis sprites, and allow access to a related department radio channel. Tools that require power are powered straight from the robot's power cell, so take care upon extensive usage. All modules give you a Flash at your disposal, so you have a degree of self-defense.

Some modules feature a gripper that is supposed to emulate a hand for when you need to put something into something else (like components into a machine frame), but they usually only work on items related to the work area the module is associated with (sometimes not even those, the selection of compatible items is imperfect), like circuit boards and components for Engineering, food items for Service etc. They take one item and can be dropped with a Drop Item verb that is located in Robot Commands tab.

The module is fixed when chosen and can only be changed by having someone (typically a Roboticist) make a module reset board, unlock your cover, open it, and insert the board, which reverts you to default, letting you choose the module again. This can be done as many times as needed. If you are new at the game, it may be advisable to have a few rounds as a living character in the work area you plan to choose the module for as a robot. While you may read guides that can help you do your job, robots are generally expected to do it well, and so other crew is less forgiving to your mistakes.
{| class="wikitable sortable"
!Module
!Icon
!Description
!Tools Available
|-
!Standard
|[[File:Borg standard 1.png|center|frameless]] [[File:Borg standard 2.png|center|frameless]] [[File:Borg standard 3.png|center|frameless]]
|A standard robot has only a few tools, which are basically taken here and there. Objectively, you are very limited in usefulness, but for a starting robot, it may prove lightweight, basic, and with some creativity it can still be sometimes useful, and do not forget you can still make the game fun for others through good roleplay. Still, do not be surprised if you are ordered to have a reset.
|
* Flash
* Fire extinguisher
* Wrench
* Crowbar
* Health analyzer
* '''Emagged:''' Energy sword
|-
!Service
|[[File:Borg service 1.png|center|frameless]] [[File:Borg service 2.png|center|frameless]] [[File:Borg service 3.png|center|frameless]] [[File:Borg service 4.png|center|frameless]] [[File:Borg service 5.png|center|frameless]]
|This module is somewhat purposed around serving as a bartender, gardener, and a little as a cook, practically an innkeeper. You can use the gardening tools to grow crops in full competence, however you are not able to use things like a knife or rolling pin, which means you are limited to only a few meals you can create unassisted (assuming you get a humanoid to take eggs out of their box in the fridge for you as well).
Still, you are well equipped as a bartender and a butler in general, you can make practically any mixed drink, and some sprites you can choose are classy! Even though this module may seem boring, crew may often appreciate your refreshments and have a chat with you, this module is a lot about interaction with others. Just remember that you cannot put things on tables with your gripper, you may only drop them on the ground. Your tray is more suitable in that situation.
|
* Flash
* Service gripper: Works on glasses, drinks, cigarettes, and most food items.
* Bucket
* Steel mini-hoe
* Steel hatchet
* Plant analyzer
* Botanical satchel
* Auto-harvester: Allows you to harvest ripe plants, you can then collect it with the plant bag.
* Rolling pin
* Kitchen knife
* Crowbar
* Rapid Service Fabricator: Lets you place a few helpful items, including drinking glasses, cigarettes, pens, paper, and packs of dice!
* Industrial dropper: Has double capacity.
* Zippo lighter: For lighting others' cigarettes/cigars, but it works different than as a living character. Target the mouth (NOT head) on the damage zone selector, and click on the person with HELP intent, with the lighter highlighted.
* RoboTray: Lets you scoop up drinks and foods, and other items like it, and place them on flat surfaces like floors and table.
* Drink synthesizer: Makes all the liquor and soft drinks you will ever need.
* '''Emagged:''' Dispenses fake beer which acts as [[Guide to Chemistry#Chloral Hydrate|Chloral Hydrate]].
|-
!Miner
|[[File:Borg mining 1.png|center|frameless]] [[File:Borg mining 2.png|center|frameless]] [[File:Borg mining 3.png|center|frameless]]
|Mining configuration allows the robot to perform as a [[Prospector]] with a good degree of competence. Not only you are able to use the mining drills fully, you can stay in vacuum for as long as you like. It is highly recommended to read the [[Guide to Mining]] if you are new at this job, though.
|
* Flash
* Mesons
* Wrench
* Screwdriver
* Mining satchel
* Mining drill
* Sheet Snatcher 9000: To handle processed material. It works like a Mining Satchel, but for sheets of resources.
* Drill maintenance gripper: For swapping drill
* Ore detector
* Crowbar
* '''Emagged:''' Plasma cutter
|-
!Security
|[[File:Borg sec 1.png|center|frameless]] [[File:Borg sec 2.png|center|frameless]] [[File:Borg sec 3.png|center|frameless]] [[File:Borg sec 4.png|center|frameless]] [[File:Borg sec 5.png|center|frameless]]
|Please note: This module is not available during normal gameplay.
The Security robot is an enforcer of law and its capabilities mostly lie in arresting suspects and maintaining order. It is relatively inefficient in other tasks however, like eradicating dangerous creatures on board or near station, since it is outfitted to combat humanoid threats. It is '''highly''' recommended to carefully read up on your [[Sol Central Government Law]] and read through the laws somewhat; a Security robot is also bound by [[Standard Operating Procedure]] like any other officer, and being abusing is a way to get unwanted attention from staff.
|
*Flash
* Security HUD
* Handcuffs
* Stun baton
* Smart gun
* Police tape
* Megaphone
* Holowarrant
* Crowbar
* Hailer
* '''Emagged:''' Laser carbine
|-
!Engineering
|[[File:Borg eng 1.png|center|frameless]] [[File:Borg eng 2.png|center|frameless]] [[File:Borg eng 3.png|center|frameless]]
|The Engineering module is considered to be among the most useful a robot can select, but it is still recommended to have a few Engineering rounds as a living character, otherwise the vast array of tools at your disposal may be overwhelming. Once mastered, an Engineering robot can be more effective than a living [[Engineer]] in most areas, like repairing structure, atmospherics, and engine setup and maintenance. This module allows a robot to do the job it is associated with to near-full extent, with the gripper functioning on most items you could need in your duty.
|
*Flash
* Mesons
* Fire extinguisher
* Industrial welding tool
* Screwdriver
* Wrench
* Crowbar
* Wirecutters
* Multitool
* T-ray scanner
* Gas analyzer
* Geiger counter
* Engineering tape
* Atmospherics tape
* 2x Magnetic grippers: Allows picking up things like circuit boards, components for machines...
* Sheet loader: A specialized loading device, designed to pick up and insert sheets of materials inside machines.
* Light replacer
* Paint sprayer
* Inflatables dispenser
* Space cleaner
* Inducer: Charges APCs and other internal cells. Pulls directly from your charge.
* Plunger
* Matter decompiler: Picks up trash like glass shards, broken lights, cigarette butts, and even small cadavers, replenishing some material reserve or energy.
* Synthesizers: Function as if you were handling a stack of material. If you pick up material off the ground with the correct synthesizer, you may refill your reserves.
** Steel
** Aluminium
** Steel rods
** Floor tiles
** Wood
** Wooden floor tiles
** Glass
** Reinforced glass
** Cable coil
** Plasteel
* '''Emagged:''' Stunprod
|-
!Janitor
|[[File:Borg janitor 1.png|center|frameless]] [[File:Borg janitor 2.png|center|frameless]] [[File:Borg janitor 3.png|center|frameless]]
|Competent to do what a [[Sanitation Technician]] does, it has an added benefit of automatically cleaning the floor it moves across. The mop is for places you cannot reach with your chassis, you can replace broken lights and clean the broken ones with your trash bag (empty it into disposal units), and it gives you the right to make puns in your name, JaniThor.
|
* Flash
* Janitor HUD
* Soap
* Trash bag
* Advanced mop
* Holographic sign projector: Lets others know that the floor is very wet
* Light replacer
* Plunger
* Crowbar
* Welding tool
* '''Emagged:''' Oil spray
|-
!Surgery
|[[File:Borg med 1.png|center|frameless]] [[File:Borg med 2.png|center|frameless]] [[File:Borg med 3.png|center|frameless]] [[File:Borg med 4.png|center|frameless]]
|One of two medical modules available. This allows the robot to perform any surgery, however it still requires assistance with putting the patient on an operating table and sedating him. You can also administer limited medical aid, but it is recommended to use the sleeper to treat patients, as it offers more options. Refer to [[Guide to Surgery]] for how to operate.
|
* Flash
* Medical HUD
* Roller bed rack
* Health analyzer
* Hypospray: Administers [[Guide to Chemistry#Bicaridine|Bicaridine]], [[Guide to Chemistry#Inaprovaline|Inaprovaline]], [[Guide to Chemistry#Dexalin|Dexalin]], and [[Guide to Chemistry#Tramadol|Tramadol]].
* Incision Management Device
* Hemostat
* Retractor
* Cautery
* Bone gel
* Vascular recoupler
* Bone setter
* Circular saw
* Surgical drill
* Organ Gripper: For internal and external organs – arms, brains, hearts etc.
* Defibrillator
* Syringe
* Crowbar
* Nanopaste: For fixing prosthetic limbs.
* Advanced trauma kit
* Dropper
* Space cleaner
* Sterilizine
* '''Emagged:''' Polyacid spray
|-
!Crisis
|[[File:Borg med 1.png|center|frameless]] [[File:Borg med 2.png|center|frameless]] [[File:Borg med 3.png|center|frameless]] [[File:Borg med 4.png|center|frameless]]
|Second variation of a medical module, this one is more purposed to a triage system and general medical aid. Any fractures are beyond capabilities of this module, however thanks to its capability to prepare medicine, internal injuries and bleeding can be healed chemically. It even features an inflatable barrier dispenser to pull victims out of depressurized areas. Overall a competent module, provided the player has sufficient knowledge of medicine in the game. Refer to [[Guide to Chemistry]] and [[Guide to Medicine]] for how to doctor.
|
* Flash
* Medical HUD
* Roller bed rack
* Crowbar
* Health analyzer
* Advanced reagent scanner
* Body bag
* Hypospray: Administers [[Guide to Chemistry#Inaprovaline|Inaprovaline]], [[Guide to Chemistry#Dylovene|Dylovene]], [[Guide to Chemistry#Dexalin|Dexalin]], [[Guide to Chemistry#Tramadol|Tramadol]], and [[Guide to Chemistry#Adrenaline|Adrenaline]].
* Bottle rack: The contents of the bottle can be administered via the Hypospray.
* Industrial Dropper: Has double capacity.
* Syringe
* Chemistry gripper: Can grip beakers, pill bottles, pills, IV bags, chemistry cartridges, and phoron stacks.
* Mini-fire Extinguisher: Less capacity and swings with less damage.
* Medical tape
* Inflatables dispenser
* Advanced burn kit
* Advanced trauma kit
* Medical splints
* Space cleaner
* '''Emagged:''' Polyacid spray
|-
!Clerical
|[[File:Borg service 1.png|center|frameless]] [[File:Borg service 2.png|center|frameless]] [[File:Borg service 3.png|center|frameless]] [[File:Borg service 4.png|center|frameless]] [[File:Borg service 5.png|center|frameless]]
|A module that is rarely used since much of the crew cares little for paperwork. But who knows, maybe it would appreciate a laborious robot that would take care of it all.
|
* Flash
* Printing pen: Allows naming and writing on paper, has several colours available.
* Paper dispenser
* Paperwork gripper: For documents and folders.
* Hand labeler
* Rubber stamp
* “DENIED” rubber stamp
* Destination tagger
* Crowbar
* Package wrapper synthesizer
* '''Emagged:''' Chameleon stamp
|-
!Research
|[[File:Borg researcher.png|center|frameless]]
|A module that is purposed to serve as a [[Scientist]], [[Roboticist]], and perhaps a [[Scientist#Xenobiology|Xenobiologist]], which is a much safer alternative to a humanoid scientist that is prone to slime containment breaches. It is fairly competent in this regard, though it cannot perform maintenance on itself, only unlock itself.
|
* Flash
* Portable Destructive Analyzer: Grabs items and decomposes them for research! You need to sync with the RnD server to share your findings.
* Scientific Gripper: For things like components and battery cells.
* Sheet loader
* Robot analyzer
* Access code transmission device: Used to unlock a robot's cover.
* Wrench
* Screwdriver
* Welding tool
* Wirecutters
* Crowbar
* Laser Scalpel
* Circular Saw
* Mini-fire Extinguisher: Less capacity and swings with less damage.
* Syringe
* Chemistry Gripper: Holds beakers, bottles, pills and so on.
* Nanopaste: Used to fix robot's components.
* '''Emagged:''' Hand teleporter integrated circuit
|}

== Flying Modules ==
A category of robot whose chief distinguishing feature is the use of an anti-gravity hover unit that allows them to fly, allowing much faster locomotion than their grounded counterparts, as well as navigate zero-G environments with ease. This can be useful in situations where other robots and organic crew would falter or be slowed considerably. But this also comes with the caveat of a lighter frame and a somewhat limited arsenal in their respective roles.

Some modules are unique to the flying variants and cannot be found elsewhere.

Note: Traversing vertically must be done manually using the '<' and '>' keys for ascending and descending respectively (no shift key necessary). Ladders are used as normal.
{| class="wikitable sortable"
!Module
!Icon
!Description
!Tools Available
|-
!Cultivator
|[[File:Borg flying cultivator.png|center|frameless]]
|A chef's best friend. The Cultivator is almost exclusively suited for the [[Guide to Hydroponics|cultivation of plants]] and not much else. But thanks to their more robust nature, a Cultivator robot might also be welcomed in a more [[Guide to Xenobotany|experimental setting]].
|
* Botanical satchel
* Plant clippers
* Steel mini-hoe
* Steel hatchet
* Hatchet
* Bucket
* Laser scalpel
* Circular saw
* Fire extinguisher
* Cultivator gripper: Can hold glasses and beakers, seeds, slime extracts, and botany disks.
* Plant analyzer
* Auto-harvester
* '''Emagged:''' Energy machete
|-
!Emergency Response
|[[File:Borg flying med.png|center|frameless]]
|The Emergency Response module lacks some the heavier utility items that allow a ground-based Crisis Response module to stabilize cardiac arrest and remove wounded crew members to a safer location, such as the Infirmary. However it does possess a variety of tools for dismantling equipment and hacking through doors. As such, it is suited for a First Response role in hard-to-reach locations while additional support is on the way.
Like the other medical modules, an established knowledge of [[Guide to Medicine|Medicine]] and [[Guide to Chemistry|Chemistry]] is strongly recommended.
|
* Flash
* Medical HUD
* Health analyzer
* Advanced reagent scanner: Lets you know the composition of pills and even food!
* Hypospray: Dispenses [[Guide to Chemistry#Inaprovaline|Inaprovaline]], [[Guide to Chemistry#Dylovene|Dylovene]], [[Guide to Chemistry#Dexalin|Dexalin]], [[Guide to Chemistry#Tramadol|Tramadol]], and [[Guide to Chemistry#Adrenaline|Adrenaline]].
* Bottle rack: The contents of the bottle can be administered via the Hypospray.
* Mini-fire extinguisher
* Medical tape
* Inflatables dispenser
* Welding tool
* Screwdriver
* Wrench
* Crowbar
* Wirecutters
* Multitool
* Advanced burn kit
* Advanced trauma kit
* Medical splints
* Roller bed rack
* Auto-compressor unit: A manipulator unit for carrying and operating an auto-compressor, a device that gives regular compression to the victim's ribcage, used in case of urgent heart issues.
* IV bag gripper: A simple grasping tool for holding and manipulating IV bags.
* Space cleaner
* '''Emagged:''' Polyacid spray
|-
!Filing
|[[File:Borg flying filing.png|center|frameless]]
|Much like its Clerical counterpart, the Filing module is best suited for paperwork and office assistant roles.
|
*Flash
* Printing Pen: Allows naming and writing on paper; has several colors available
* Paper dispenser
* Clerical gripper
* Hand labeler
* Rubber stamp
* “DENIED” rubber stamp
* Destination tagger
* Crowbar
* Megaphone
* Package wrapper synthesizer
* '''Emagged:''' Chameleon stamp
|-
!Forensics
|[[File:Borg flying ft.png|center|frameless]]
|Great for collecting evidence in more dangerous areas for an existing [[Forensic Technician]] without the risk of fingerprints. See [[Guide to Forensics]] for more details on how to do your job.
|
* Flash
* Security HUD
* Swab kit
* Evidence case
* Fiber collection kit
* Fingerprint powder
* Forensics gripper: Can hold various pieces of evidence and paperwork.
* Police tape
* Laser scalpel
* Autopsy scanner
* Reagent scanner
* Luminol bottle
* UV light
* Crowbar
* '''Emagged:''' Laser gun
|-
!Repair
|[[File:Borg flying eng.png|center|frameless]]
|Arguably one of the most useful modules to have around with its extensive list of tools at its disposal. And thanks to their ability to fly, this module is especially handy for repairing level-spanning breaches or where EVA would be necessary.
|
* Mesons
* Fire extinguisher
* Industrial welding tool
* Screwdriver
* Wrench
* Crowbar
* Wirecutters
* Multitool
* T-ray scanner
* Gas analyzer
* Geiger counter
* Engineering Tape
* Atmospherics Tape
* Magnetic gripper: Allows picking up things like circuit boards, and components for machines.
* Sheet Loader
* Light replacer
* Pipe sprayer
* Inflatables dispenser
* Space cleaner
* Inducer: Charges APCs and other internal cells. Pulls directly from your charge
* Plunger
* Matter decompiler: Picks up trash like glass shards, broken lights, cigarette butts, and even small cadavers, replenishing some material reserve or energy.
* Synthesizers: Function as if you were handling a stack of material. If you pick up material off the ground with the correct synthesizer, you may refill your reserves.
** Steel
** Aluminium
** Steel rods
** Floor tiles
** Glass
** Reinforced Glass
** Cable Coil
** Plasteel
* '''Emagged:''' Stunprod
|-
!Surveyor
|[[File:Borg flying surveyor.png|center|frameless]]
|An exploration and discovery module with a rather versatile arsenal. Given the dangerous nature of the work, you might find yourself sent in before everyone else to ensure a location is safe. Or to see how that strange creature likes robots....
|
* Titanium machete
* Inducer: Charges other power cells such as those found in APCs, energy-based weapons, and even fellow robots. Paired with the Bioreactor, you could function as a self-charging battery for an away team. Handy!
* Gas analyzer
* Botanical satchel
* Plant clippers
* Ore detector
* Fire extinguisher
* Net gun
* Global coordinate system
* Welding tool
* Screwdriver
* Wrench
* Crowbar
* Wirecutters
* Multitool
* Bioreactor: Consumes most organic material to recharge your cells. Useful for extended away missions.
* Inflatables dispenser
* Auto-harvester
* '''Emagged:''' Energy machete
|}

== Other Notes on Robots ==

* You cannot take toxic or suffocation damage. The only sources of damage that can harm you are Burn and Brute.
* Expect to regularly be thrust into hazardous situations thanks to your 'enhanced' durability and ability to operate in a vacuum.
* You cannot be disarmed of your inbuilt equipment and you cannot drop it (drop key puts the tool in inventory). You can be stunned by a flash, which overload your optical sensors.
* You are vulnerable to EMP in that it discharges some of your energy. If you run to zero, you are powered-down.
* You are immune to most (if not all) diseases such as disease and radiation poisoning.
* You cannot pick up, use, or equip external items. Unless your module provides a 'gripper' item that will work on some types of item.
* Like AI, you can remotely interact with certain objects. You must be within sight range of a device to manipulate it.
* Like AI, you can remotely view alarm statuses. Use this to your advantage.
* You can use the same hotkeys as the AI to interact with airlocks, APCs, etc.
* Unlike AI, you cannot use security cameras for remotely using machines and devices.
* Robots have access to all areas and all doors.
* The robot recharge stations are next to Robotics Lab, in Robot Storage, on the departures shuttle, as well as other areas.
* You are somewhat slow, normal humans outrun you.
* Keep the crew updated on your location and power if you are running low and may not make it to the recharger in time.
* Drones and Robots may not know what emotions, or feelings are, but that doesn't give the player the right to go Rambo. If a group of people take several people hostage, the robot doesn't have the right to rush in with a stun baton and beat the hostage-takers. Remember that the Security robot is still bound by [[Standard Operating Procedure]] of officers on top of your laws.
* An emagged robot will have no LawSync or AI link and cannot have its module reset.
----
{{Navbox Roles}}
[[Category:Roles]]

Research Assistant

2023-05-07T15:19:37Z

Sierra: #33436 - Custodian alt title moved from research to janitor

{{JobPageHeader
|headerbgcolor = 180, 51, 189
|headerfontcolor = white
|stafftype = RESEARCH
|img = research_assistant.png
|jobtitle = Research Assistant
|difficulty = Easy
|superior = The [[Chief Science Officer]] and other Research personnel
|branches = [[Expeditionary Corps]], Civilian, Government
|ecranks = Explorer (E-3), Senior Explorer (E-5)
|fleetranks
|govranks = Government Scientist
|civranks = Contractor
|alttitles = Testing Assistant, Intern, Clerk, Field Assistant
|duties = Help the CSO and the Research Team with whatever they need. Fetch coffee. Clean the labs. Be a test subject.
|guides = [[Guide to Research and Development]], [[Guide to Xenoarchaeology]], [[Guide to Xenobiology]], [[Guide to Xenobotany]], [[Guide to Anomalies]]
}}
The '''Research Assistant''' is a catch-all job for various types of laboratory helpers. It serves mainly to help the [[Scientist|Scientists]] in any way they require, and, due to this, serves as an excellent entry point for newer players wanting to learn more about Research.

Research Assistants normally answer to the [[Senior Researcher]] and [[Chief Science Officer]], with the CSO's orders taking precedence. If neither of these personnel are present, Research Assistants answer to the Scientists.

== The Role ==
Research Assistants wander about the Research department in search of a mad scientist in need of an Igor. Once such an individual is found, they volunteer their services and provide whatever it is that the Scientist in question needs, whether this be coffee, someone to complete paperwork, fresh brains, or just a hapless schmuck to experiment on. They hold no real authority within the Research department and exist to make Scientists' jobs easier.

The various alternate job titles available to Research Assistants denote a variety of specialties. ''Custodians'' are there to keep the labs clean and well-organized. ''Interns'', ''Testing Assistants'', and ''Field Assistants'' take an active hand in experiments, with Testing Assistants having a focus on shipboard activities and Field Assistants looking to join in on away missions. ''Clerks'' are generally looking to fill out paperwork and ensure that all experiments, and their results, are properly documented and reported.
----
{{Navbox Roles}}
[[Category:Research Roles]][[Category:Roles]]

Sanitation Technician

2023-05-07T15:19:05Z

Sierra: #33436 - Custodian alt title moved from research to janitor

{{JobPageHeader
|headerbgcolor = 39, 184, 73
|headerfontcolor = white
|stafftype = SERVICE
|img = janitor.png
|jobtitle = Sanitation Technician
|difficulty = Easy
|superior = The [[Chief Steward]] and the [[Executive Officer]]
|branches = [[Expeditionary Corps]], [[Sol Central Government Fleet]], Civilian
|ecranks = Explorer (E-3)
|fleetranks = Crewman Apprentice (E-2), Crewman (E-3), Petty Officer Third Class (E-4)
|govranks
|civranks = Contractor
|alttitles = Custodian, Janitor
|duties = Clean and maintain the spaceship. Replace broken lights. Put up wet floor signs.
|guides = N/A
}}
The '''Sanitation Technician''' is responsible for keeping the ship from becoming a complete mess after the various disasters that consistently befall it. They wage an eternal war against dirt, uncleanliness, broken light bulbs, and crew without access to non-slip shoes. It is an ideal role for new players, as its access and requirements allow one to become moderately familiar with the layout of the ship while not giving very important responsibilities.

As an enlisted member of the Service department, the Sanitation Technician answers to the [[Chief Steward]] and the [[Executive Officer]], though the Chief Steward is the far more active of the two in this regard.

== How To Play ==
As the Sanitation Technician, you have one of the simplest jobs aboard the ship: find places that are dirty and make them stop being dirty, as well as unclogging toilets or sinks and replacing lights.

All of this largely comes down to tugging the janitorial cart around, setting up Wet Floor signs, and mopping up any dirt, blood, or other substances that have been spilled onto the floor. Occasionally, some department or other might put out a specific call for janitorial assistance when some lights get broken or a firefight leaves the place looking like a butcher shop, but aside from this, the Sanitation Technician is largely expected to work under their own direction.

At the start of the shift, the Sanitation Technician will need to use their bucket to fill up the janitorial cart's dedicated reservoir, collect their various supplies, and get ready for several hours of dealing with the ship's limitless supply of filth. It is also recommended to mentally steel oneself against the inevitable abuses heaped upon the sanitation crew by those who fail to pay attention to wet floor signs. After this is complete, the Sanitation Technician is free to wander the ship at their leisure in search of messes to vanquish.

== Tools ==
Your Custodial Closet is on Deck 3, in the fore of the ship, just port of the Garden (''i.e. towards the south-west edge of the map''), next to the Chief Steward's Office and the Service Break Room. The lockers and general area contain the following tools:

* '''Janitorial Cart''': The Sanitation Technician's central tool. Mobile storage for the mop, mop bucket, trash bag, light replacer, Space Cleaner, and wet floor signs.
* '''Mop''': The second most important tool. After being moistened, usually with the mop bucket, can be used to clean any mess left on the floor. Leaves temporarily slippery areas behind when used with water, which will cause anyone who is not set to Walk to fall upon moving over them.
** If you pester Research, you can acquire an '''Advanced Mop'''. This cleans much faster than your average everyday mop, as well as not needing to be wetted and not making a floor slippery.
* '''Wet Floor Sign''': Used to warn others of slippery floors left behind after mopping. Inevitably ignored.
** You can acquire a '''sign projector''' from research. It has an unlimited amount of signage and can be set up and removed with a click.
* '''Galoshes''': A pair of bright-yellow boots. Slip-resistant.
* '''Work Gloves''': Thick, fire-resistant gloves to prevent accidental burns when changing active lights.
* '''Mop Bucket''': Can be filled with water for the mop. Part of the janitorial cart.
* '''Plunger''': A plunger. Used to unclog sinks, toilets, and the like when they become clogged. Clogs are easily located by standing water, and will have an audible cue when gotten near.
* '''Trash Bag''': Can be used to pick up all trash from a tile for easy disposal.
* '''Space Cleaner''': A spray bottle filled with non-slip cleaner. Has a limited supply and must be refilled by a [[Pharmacist]].
* '''Bucket''': Used to transfer water from the water tank to the mop bucket.
* '''Water Tank''': A tank containing water for refilling other things.
* '''Light Replacer''': Used to replace broken light bulbs and tubes. Has a limited supply of light bulbs. Can be refilled from a box of light bulbs.
* '''Box of Replacement Lights''': A box containing light bulbs and tubes.
* '''Pest-B-Gon Mousetraps''': Used to trap those pesky mice that keep managing to get onto the ship somehow. Bluespace, probably.
* '''Cleaner Grenade''': A grenade that explodes with CLEAN. Make war on dirt. ''This slips people who get caught in it.''
* '''Flashlight''': A portable light source, for use in maintenance tunnels.
* '''Soap''': A simple bar of soap. Must be occasionally washed in a sink or in a bucket full of water in order to retain effectiveness.

== Tips ==

* To fill your janitorial cart, you have to fill a bucket with water from a water tank or sink, then pour it into a cart. This can get tedious pretty quickly, so keep in mind you can change the unit transfer rate of an object by right-clicking on it and mousing over 'Set Transfer Rate'.
* Soap can very quickly scrub out stains, dirt, and other clutter by simply mousing over the clutter and clicking. Keep in mind you have to be moused over the clutter in question (and not the plating), so it's best to alt-click to get a read of the turf.
* The contents of your trash bag can be emptied into a disposal unit by holding the bag in your hand and clicking on the disposal unit.
* Stay on the sides of the hallways, lest you and your janitorial cart be pushed around.
* If you run out of Space Ceaner, there are two solutions: detergent pods can be dissolved in water to create Space Cleaner, or deodorant (which is just resprited Space Cleaner), which can be found in the bathrooms on Deck 1 and Deck 3.
* If someone slips on a tile without wet floor signs and you point to a wet floor sign several tiles away, the slipper may lynch you.

== Antagonising ==
As a [[Traitor]] Sanitation Technician, your main asset is your access to maintenance. You also have a valuable tool in the form of your mop, as you can clean a floor to make it slippery – excellent for making anyone that's chasing you lose track of you. Your cleaner grenades also slip people if you pull the pin at the right time, and should you acquire a toxin kit, your spray bottle can be filled with anything.
----
{{Navbox Roles}}
[[Category:Service Roles]][[Category:Roles]]

Sanitation Technician

2023-05-07T15:18:43Z

Sierra: Reverted edits by Sierra (talk) to last revision by Rootoo

{{JobPageHeader
|headerbgcolor = 39, 184, 73
|headerfontcolor = white
|stafftype = SERVICE
|img = janitor.png
|jobtitle = Sanitation Technician
|difficulty = Easy
|superior = The [[Chief Steward]] and the [[Executive Officer]]
|branches = [[Expeditionary Corps]], [[Sol Central Government Fleet]], Civilian
|ecranks = Explorer (E-3)
|fleetranks = Crewman Apprentice (E-2), Crewman (E-3), Petty Officer Third Class (E-4)
|govranks
|civranks = Contractor
|alttitles = Janitor
|duties = Clean and maintain the spaceship. Replace broken lights. Put up wet floor signs.
|guides = N/A
}}
The '''Sanitation Technician''' is responsible for keeping the ship from becoming a complete mess after the various disasters that consistently befall it. They wage an eternal war against dirt, uncleanliness, broken light bulbs, and crew without access to non-slip shoes. It is an ideal role for new players, as its access and requirements allow one to become moderately familiar with the layout of the ship while not giving very important responsibilities.

As an enlisted member of the Service department, the Sanitation Technician answers to the [[Chief Steward]] and the [[Executive Officer]], though the Chief Steward is the far more active of the two in this regard.

== How To Play ==
As the Sanitation Technician, you have one of the simplest jobs aboard the ship: find places that are dirty and make them stop being dirty, as well as unclogging toilets or sinks and replacing lights.

All of this largely comes down to tugging the janitorial cart around, setting up Wet Floor signs, and mopping up any dirt, blood, or other substances that have been spilled onto the floor. Occasionally, some department or other might put out a specific call for janitorial assistance when some lights get broken or a firefight leaves the place looking like a butcher shop, but aside from this, the Sanitation Technician is largely expected to work under their own direction.

At the start of the shift, the Sanitation Technician will need to use their bucket to fill up the janitorial cart's dedicated reservoir, collect their various supplies, and get ready for several hours of dealing with the ship's limitless supply of filth. It is also recommended to mentally steel oneself against the inevitable abuses heaped upon the sanitation crew by those who fail to pay attention to wet floor signs. After this is complete, the Sanitation Technician is free to wander the ship at their leisure in search of messes to vanquish.

== Tools ==
Your Custodial Closet is on Deck 3, in the fore of the ship, just port of the Garden (''i.e. towards the south-west edge of the map''), next to the Chief Steward's Office and the Service Break Room. The lockers and general area contain the following tools:

* '''Janitorial Cart''': The Sanitation Technician's central tool. Mobile storage for the mop, mop bucket, trash bag, light replacer, Space Cleaner, and wet floor signs.
* '''Mop''': The second most important tool. After being moistened, usually with the mop bucket, can be used to clean any mess left on the floor. Leaves temporarily slippery areas behind when used with water, which will cause anyone who is not set to Walk to fall upon moving over them.
** If you pester Research, you can acquire an '''Advanced Mop'''. This cleans much faster than your average everyday mop, as well as not needing to be wetted and not making a floor slippery.
* '''Wet Floor Sign''': Used to warn others of slippery floors left behind after mopping. Inevitably ignored.
** You can acquire a '''sign projector''' from research. It has an unlimited amount of signage and can be set up and removed with a click.
* '''Galoshes''': A pair of bright-yellow boots. Slip-resistant.
* '''Work Gloves''': Thick, fire-resistant gloves to prevent accidental burns when changing active lights.
* '''Mop Bucket''': Can be filled with water for the mop. Part of the janitorial cart.
* '''Plunger''': A plunger. Used to unclog sinks, toilets, and the like when they become clogged. Clogs are easily located by standing water, and will have an audible cue when gotten near.
* '''Trash Bag''': Can be used to pick up all trash from a tile for easy disposal.
* '''Space Cleaner''': A spray bottle filled with non-slip cleaner. Has a limited supply and must be refilled by a [[Pharmacist]].
* '''Bucket''': Used to transfer water from the water tank to the mop bucket.
* '''Water Tank''': A tank containing water for refilling other things.
* '''Light Replacer''': Used to replace broken light bulbs and tubes. Has a limited supply of light bulbs. Can be refilled from a box of light bulbs.
* '''Box of Replacement Lights''': A box containing light bulbs and tubes.
* '''Pest-B-Gon Mousetraps''': Used to trap those pesky mice that keep managing to get onto the ship somehow. Bluespace, probably.
* '''Cleaner Grenade''': A grenade that explodes with CLEAN. Make war on dirt. ''This slips people who get caught in it.''
* '''Flashlight''': A portable light source, for use in maintenance tunnels.
* '''Soap''': A simple bar of soap. Must be occasionally washed in a sink or in a bucket full of water in order to retain effectiveness.

== Tips ==

* To fill your janitorial cart, you have to fill a bucket with water from a water tank or sink, then pour it into a cart. This can get tedious pretty quickly, so keep in mind you can change the unit transfer rate of an object by right-clicking on it and mousing over 'Set Transfer Rate'.
* Soap can very quickly scrub out stains, dirt, and other clutter by simply mousing over the clutter and clicking. Keep in mind you have to be moused over the clutter in question (and not the plating), so it's best to alt-click to get a read of the turf.
* The contents of your trash bag can be emptied into a disposal unit by holding the bag in your hand and clicking on the disposal unit.
* Stay on the sides of the hallways, lest you and your janitorial cart be pushed around.
* If you run out of Space Ceaner, there are two solutions: detergent pods can be dissolved in water to create Space Cleaner, or deodorant (which is just resprited Space Cleaner), which can be found in the bathrooms on Deck 1 and Deck 3.
* If someone slips on a tile without wet floor signs and you point to a wet floor sign several tiles away, the slipper may lynch you.

== Antagonising ==
As a [[Traitor]] Sanitation Technician, your main asset is your access to maintenance. You also have a valuable tool in the form of your mop, as you can clean a floor to make it slippery – excellent for making anyone that's chasing you lose track of you. Your cleaner grenades also slip people if you pull the pin at the right time, and should you acquire a toxin kit, your spray bottle can be filled with anything.
----
{{Navbox Roles}}
[[Category:Service Roles]][[Category:Roles]]

Sanitation Technician

2023-05-07T15:18:12Z

Sierra: #33436 - Custodian alt title moved from research to janitor

{{JobPageHeader
|headerbgcolor = 39, 184, 73
|headerfontcolor = white
|stafftype = SERVICE
|img = janitor.png
|jobtitle = Custodian, Sanitation Technician
|difficulty = Easy
|superior = The [[Chief Steward]] and the [[Executive Officer]]
|branches = [[Expeditionary Corps]], [[Sol Central Government Fleet]], Civilian
|ecranks = Explorer (E-3)
|fleetranks = Crewman Apprentice (E-2), Crewman (E-3), Petty Officer Third Class (E-4)
|govranks
|civranks = Contractor
|alttitles = Janitor
|duties = Clean and maintain the spaceship. Replace broken lights. Put up wet floor signs.
|guides = N/A
}}
The '''Sanitation Technician''' is responsible for keeping the ship from becoming a complete mess after the various disasters that consistently befall it. They wage an eternal war against dirt, uncleanliness, broken light bulbs, and crew without access to non-slip shoes. It is an ideal role for new players, as its access and requirements allow one to become moderately familiar with the layout of the ship while not giving very important responsibilities.

As an enlisted member of the Service department, the Sanitation Technician answers to the [[Chief Steward]] and the [[Executive Officer]], though the Chief Steward is the far more active of the two in this regard.

== How To Play ==
As the Sanitation Technician, you have one of the simplest jobs aboard the ship: find places that are dirty and make them stop being dirty, as well as unclogging toilets or sinks and replacing lights.

All of this largely comes down to tugging the janitorial cart around, setting up Wet Floor signs, and mopping up any dirt, blood, or other substances that have been spilled onto the floor. Occasionally, some department or other might put out a specific call for janitorial assistance when some lights get broken or a firefight leaves the place looking like a butcher shop, but aside from this, the Sanitation Technician is largely expected to work under their own direction.

At the start of the shift, the Sanitation Technician will need to use their bucket to fill up the janitorial cart's dedicated reservoir, collect their various supplies, and get ready for several hours of dealing with the ship's limitless supply of filth. It is also recommended to mentally steel oneself against the inevitable abuses heaped upon the sanitation crew by those who fail to pay attention to wet floor signs. After this is complete, the Sanitation Technician is free to wander the ship at their leisure in search of messes to vanquish.

== Tools ==
Your Custodial Closet is on Deck 3, in the fore of the ship, just port of the Garden (''i.e. towards the south-west edge of the map''), next to the Chief Steward's Office and the Service Break Room. The lockers and general area contain the following tools:

* '''Janitorial Cart''': The Sanitation Technician's central tool. Mobile storage for the mop, mop bucket, trash bag, light replacer, Space Cleaner, and wet floor signs.
* '''Mop''': The second most important tool. After being moistened, usually with the mop bucket, can be used to clean any mess left on the floor. Leaves temporarily slippery areas behind when used with water, which will cause anyone who is not set to Walk to fall upon moving over them.
** If you pester Research, you can acquire an '''Advanced Mop'''. This cleans much faster than your average everyday mop, as well as not needing to be wetted and not making a floor slippery.
* '''Wet Floor Sign''': Used to warn others of slippery floors left behind after mopping. Inevitably ignored.
** You can acquire a '''sign projector''' from research. It has an unlimited amount of signage and can be set up and removed with a click.
* '''Galoshes''': A pair of bright-yellow boots. Slip-resistant.
* '''Work Gloves''': Thick, fire-resistant gloves to prevent accidental burns when changing active lights.
* '''Mop Bucket''': Can be filled with water for the mop. Part of the janitorial cart.
* '''Plunger''': A plunger. Used to unclog sinks, toilets, and the like when they become clogged. Clogs are easily located by standing water, and will have an audible cue when gotten near.
* '''Trash Bag''': Can be used to pick up all trash from a tile for easy disposal.
* '''Space Cleaner''': A spray bottle filled with non-slip cleaner. Has a limited supply and must be refilled by a [[Pharmacist]].
* '''Bucket''': Used to transfer water from the water tank to the mop bucket.
* '''Water Tank''': A tank containing water for refilling other things.
* '''Light Replacer''': Used to replace broken light bulbs and tubes. Has a limited supply of light bulbs. Can be refilled from a box of light bulbs.
* '''Box of Replacement Lights''': A box containing light bulbs and tubes.
* '''Pest-B-Gon Mousetraps''': Used to trap those pesky mice that keep managing to get onto the ship somehow. Bluespace, probably.
* '''Cleaner Grenade''': A grenade that explodes with CLEAN. Make war on dirt. ''This slips people who get caught in it.''
* '''Flashlight''': A portable light source, for use in maintenance tunnels.
* '''Soap''': A simple bar of soap. Must be occasionally washed in a sink or in a bucket full of water in order to retain effectiveness.

== Tips ==

* To fill your janitorial cart, you have to fill a bucket with water from a water tank or sink, then pour it into a cart. This can get tedious pretty quickly, so keep in mind you can change the unit transfer rate of an object by right-clicking on it and mousing over 'Set Transfer Rate'.
* Soap can very quickly scrub out stains, dirt, and other clutter by simply mousing over the clutter and clicking. Keep in mind you have to be moused over the clutter in question (and not the plating), so it's best to alt-click to get a read of the turf.
* The contents of your trash bag can be emptied into a disposal unit by holding the bag in your hand and clicking on the disposal unit.
* Stay on the sides of the hallways, lest you and your janitorial cart be pushed around.
* If you run out of Space Ceaner, there are two solutions: detergent pods can be dissolved in water to create Space Cleaner, or deodorant (which is just resprited Space Cleaner), which can be found in the bathrooms on Deck 1 and Deck 3.
* If someone slips on a tile without wet floor signs and you point to a wet floor sign several tiles away, the slipper may lynch you.

== Antagonising ==
As a [[Traitor]] Sanitation Technician, your main asset is your access to maintenance. You also have a valuable tool in the form of your mop, as you can clean a floor to make it slippery – excellent for making anyone that's chasing you lose track of you. Your cleaner grenades also slip people if you pull the pin at the right time, and should you acquire a toxin kit, your spray bottle can be filled with anything.
----
{{Navbox Roles}}
[[Category:Service Roles]][[Category:Roles]]