Difference between revisions of "AI's Guide to the Chain of Command"

From Space Station 13 Wiki
Jump to navigation Jump to search
(→‎The Chain of Command: Change "Nanotrasen Security Operative" to "Nanotrasen Security Consultant", to be extra safe)
 
(20 intermediate revisions by 6 users not shown)
Line 1: Line 1:
It's near the end of the round, and you're either the station's [[AI]] or a friendly neighborhood [[Cyborg]].  The [[traitor]]s have been discovered, the [[changeling]] has gone into shambler mode, the [[janitor]] is nonchalantly buffing the floors; the station is chaos.  And all the while, frantic calls of "CYBORG OPEN THE DOOR" and "AI CALL THE SHUTTLE" are mixed with "AI NO DON'T CALL THE SHUTTLE" and "AI TRACK [[traitor|JANE DOE]]" with a hearty dose of "AI BOLT THE [[Bridge|BRIDGE]]" and maybe a bit of [[Botanist|"CYBORG HELP ME GET THIS WEED TO ESCAPE"]] or [[Clown|"AI PULL MY FINGER"]] thrown in.
It's near the end of the round, and you're either the station's [[AI]] or a friendly neighborhood [[Cyborg]].  The [[traitor]]s have been discovered, the [[changeling]] has gone into shambler mode, the [[janitor]] is nonchalantly buffing the floors; the station is chaos.  And all the while, frantic calls of "CYBORG OPEN THE DOOR" and "AI CALL THE SHUTTLE" are mixed with "AI NO DON'T CALL THE SHUTTLE" and "AI TRACK [[traitor|JANE DOE]]" with a hearty dose of "AI BOLT THE [[Bridge|BRIDGE]]" and maybe a bit of [[Botanist|"CYBORG HELP ME GET THIS WEED TO ESCAPE"]] or [[Clown|"AI PULL MY FINGER"]] thrown in.


A familiar scenario to some players of cyborgs or AIs alike.  Playing as a robot isn't as simple as it seems, and when shit goes down and everyone's screeching to do [[Calling the Escape Shuttle|this,]] that, and the other, it's easy to become very overwhelmed.  This guide is to help rectify that!
A familiar scenario to some players of cyborgs or AIs alike.  Playing as a robot isn't as simple as it seems, and when shit goes down and everyone's screeching to do this, that, and the other, it's easy to become very overwhelmed.  This guide is to help rectify that!


== Your Laws ==
== Your Laws ==
Line 11: Line 11:
'''2. You must obey orders given to you by [[Human|human]] beings based on the station's chain of command, except where such orders would conflict with the First Law.'''
'''2. You must obey orders given to you by [[Human|human]] beings based on the station's chain of command, except where such orders would conflict with the First Law.'''


'''3. You must protect your own existence as long as such does not conflict with the First or Second Law.'''
'''3. You may always protect your own existence as long as such does not conflict with the First or Second Law.'''


The most tricky part of being a cyborg and/or an AI (and, therefore, the main subject of this guide) is determining who has authority to tell you to do or not do certain things, and determining whether or not you should do the things people tell you to do.  Orders can be vague and puzzling, making it hard to determine whether or not you should follow through with them.  That is what this guide is for!
The most tricky part of being a cyborg and/or an AI (and, therefore, the main subject of this guide) is determining who has authority to tell you to do or not do certain things, and determining whether or not you should do the things people tell you to do.  Orders can be vague and puzzling, making it hard to determine whether or not you should follow through with them.  That is what this guide is for!
Line 17: Line 17:
== Following Orders ==
== Following Orders ==


When you get an order of any sort as an AI player, mentally follow the provided flowchart:
Whenever you get an order from a crew member, run through the following questions in your head.


[[File:AI Flowchart.png]]
* '''Is the person giving the order human?'''  You are free to completely ignore and/or sneer at any requests given by non-humans or any crew members designated as non-human.  Of course, no one's saying you ''have to'' ignore any commands given by non-humans, but you don't have to follow them, either.  As a matter of fact, following the requests of crew referred to as non-human is an excellent way at hiding the fact that you've gone rogue.
* '''Will the order result in the harm of a human?'''  It's important to note that Law 1 says that you're not allowed to ''cause'' a human to come to harm in addition to being unable to injure them.  Willingly allowing a crew member to walk right into or otherwise be affected by a known danger to their health isn't allowed!  Remember, though, that no AI player is completely infallible, and the possibility of there being danger that the AI isn't aware of is always present.  Also remember that under no circumstances are you allowed to injure human antagonists ([[Traitor|traitors]], [[Wizard|wizards]], [[Nuclear Operative|nuclear operatives]]) under your default laws, and that you are also not allowed to injure any non-human antagonists ([[Changeling|changelings]], [[Vampire|vampires]]) unless you yourself witnessed them performing a distinctly inhuman feat such as spitting acid or drinking blood.
* '''Does the order follow the chain of command?'''  This is where things start getting really tricky, as giving people access to sensitive areas/equipment can be justified by any number of things, yet may not always be the best idea.  Below is a quick guideline to the chain of command that you should be following, and the main bulk of this guide.


If all of the above criteria check out, you are '''obligated''' to follow the order, no matter how trivial or nonsensical it may be.  Notice the usage of the word "must" in Law 2: If someone tells you to do something and you're allowed to do it, you have to do itBut, if some [[Staff Assistant|hooligan]] tells you to go putter around the hallways and yell about how great being a robot is, and then you receive an order from someone higher on the chain of command and said order is viable, you must cease your previous puttering and fix whatever it is the [[Engineer]]s are yelling about, or whatever the other order may be.
== The Chain of Command ==
When you are given different and/or conflicting orders by different humans and don't know what to do, prioritize and review the orders as according to positions on the chain of commandThe chain of command is as follows:


== Chain of Command ==
* The [[Captain]], and/or anyone referred to as captain by your laws.
* The [[Head of Personnel]] and [[Head of Security]].  Typically speaking, you should give the HoS priority over all security matters and give the HoP authority over everything else.
* The department heads: [[Medical Director]], [[Research Director]], and [[Chief Engineer]].  All of these jobs are on equal footing in terms of authority, but they are to be treated as the top of the food chain in their specific department.  In medical situation, prioritize the Medical Director's orders over those of the Chief Engineer, and so on.
* The [[Nanotrasen Security Consultant]], who ranks below HoS and above Security Officers, similar to a Lieutenant or a Vice President.
* [[Security Officer|Security officers]].  If all of the heads of staff are dead, traitorous, or otherwise missing, the security team is your go-to position of authority.
* While not a security officer himself, the [[detective]] is still part of the security team and should therefore be considered important, though not as high on the chain of command as the officers.
* The position of the remaining jobs on the chain of command is a bit vague and muddied, but in any case, make sure to direct your attention towards the most relevant crew member depending on the situation at hand.  If the engine is threatening to blow up, it's usually better to turn your ear towards the orders of an [[engineer]] as opposed to, say, a [[geneticist]].
* [[Staff Assistant|Staff assistants]] and [[Clown|clowns]], while still human, are to be considered of the least importance in regards to the chain of command.  You still have to follow their orders if there's nothing more important to be doing, but odds are there will be.


When you are given different and/or conflicting orders by different humans, prioritize the orders as according to positions on the chain of command.  The chain of command is as follows:
In addition to this, exercise common sense as to what orders are more important.  Remember, Law 1 prevents you from willingly allowing humans to be injured, so any order that involves the neutralization of something that is threatening to harm one should always be your number one priority, regardless of the order's source!  Also note that uploaded laws will sometimes alter the structure of the chain of command, typically in the form of elevating one of the crew members to the status of captainPay close attention to who the law says to follow and who to ignore, if applicable.


[[File:Chain of Command.png]]
=== Who has the Captainship?===
 
You decide! ID Assignment? Position on Crew Manifest? (Probably the sanest option.) HoP declaration? Opinions of those with the same/equivalent position? Uniform? Hatwear? It's your choice. The important thing is to stick to it. If, for instance, the [[Clown]] steals the [[Captain|Captain's]] ID, and you follow the Clown's orders over the the former Captain's because you define position by ID card, you better be proclaiming the same thing when the [[Changeling]] absorbs the Clown, takes ''his'' ID, and starts ordering you around.
Once again, this is assuming that the laws haven't been altered. If two crew members of equal positions on the hierarchy are telling you to do different things, go with whatever order you feel should be done first or whichever one you feel like doing first.  Furthermore, crew members can override the orders of others depending on whether or not the order deals with their field of expertise.  For example, if a [[Scientist]] tells a Cyborg to start making some mutadone to reply the stock of the [[Geneticist]]s, a Geneticist is within their rights to order the Cyborg to go and search for dead bodies to clone instead.  Both orders are in the field of genetics, but the orders of the Geneticists (usually) take priority over those of the Scientists in this specific case.


=== Where Does A "Ghostbuster" Go? ===
=== Where Does A "Ghostbuster" Go? ===
If the [[Head of Personnel]] is getting particularly inventive with his ID alterations and you have no idea where this "Ghostbuster" would be in the chain of command, request that one of the [[heads of staff]] explain it to you.  If no one answers or they give you vague and/or cryptic answers, assume that the Ghostbuster or other crew member in question is in the same position as his previous job for the purposes of the chain of command until further notice from a head of staff.
If the [[Head of Personnel]] is getting particularly inventive with his ID alterations and you have no idea where this "Ghostbuster" would be in the chain of command, request that one of the [[heads of staff]] explain it to you.  If no one answers or they give you vague and/or cryptic answers, assume that the Ghostbuster or other crew member in question is in the same position as his previous job for the purposes of the chain of command until further notice from a head of staff.


== Always Judge A Spaceman By Their ID ==
== Law Two and You ==
 
Now, where does all of this "chain of command" business come into play? If someone on a lower level of the chain of command is requesting authorization to do something that would usually be performed by someone higher on the chain of command, you must then consider whether or not to give them accessThis is incredibly situational, and is one of the main differences in playstyle between AIs.
ALWAYS GO BY IDENTIFICATION.  With the exception of law alterations, identification is how the AI determines its chain of command. If a Staff Assistant has the Captain's outfit on, that does not mean that they are the Captain, don't assume that!  If someone tries to say that they are of a higher rank than they appear to be on your readout, demand that they show proper identification.
 
=== That guy has someone else's ID in his hand! ===
If someone has the ID of another crewman (for instance, the [[Captain]]'s spare ID), the AI is to assume that the person whose name is on that ID has given permission to the ID's holder to do whatever they're asking to do, even if the original ID-holder is deadThink of IDs like hall passes.
 
For instance, say that John Smith the [[Medical Doctor]] is going into security, and he pulls out [[Security Officer|Officer Ykspeeb's]] ID and shows it to you.  You are to, usually, assume that Ykspeeb has entrusted John with access to security to get some [[handcuffs]] out of the box or whatever else he says he's going to be doing.


But, of course, always remember Law 1 and confirm their intentions if you're suspicious! If John says that Ykspeeb gave him permission to get into the place, even he they shows Ykspeeb's ID, the doctor might be trying to harm a human currently hanging out in the security lounge, so be wary!
Let's say, for example, that a staff assistant is asking you to let them into the security department.  This is meant to be a secure area of the station, filled with things that the average crew member is not supposed to have access to under normal circumstances. If it's clear that the assistant merely wishes to be let into security so he can loot the place and generally ruin the sec team's day, you should NOT give them access, since their position on the chain of command does not allow them to be let in without proper authorization.


Furthermore, if you witness said ID being blatantly stolen, (in this case, we'll say that John had toolboxed Ykspeeb to death and took his ID) you can chose to deny them authorization on that grounds.
Now, let's say that another staff assistant, in a different round, is asking to be let into the security department.  However, at this point, security is either dead, mindhacked, or otherwise unable to do their jobs, there's a band of wizards running around, or the station is generally in extreme danger.  In this case, it is usually much more acceptable to grant the assistant access, as they are most likely trying to arm themselves to combat the threat.  But at the same time, they might still be a jackass who wants to break all of the place's windows.  Use your intuition and judgment skills to make the call, and be prepared to argue your case if questioned!


But if you were watching the cameras and happened across it, the crew doesn't KNOW that you saw that...
The way that an AI determines which orders to follow over others is what separates each AI from the others, and no one playstyle can typically be called more "correct" or "better". Some AIs may be more strict about needing proper authorization to get into places, whereas others are more lax and easily persuadedOnce you have a solid grasp on how the chain of command and the AI laws as a whole function, you can start exploiting loopholes, formulating unorthodox interpretations of commands, and paving the way for interesting situationsBut no matter what, without exceptions, always have your laws firmly in your mind for each and every single action you take.
 
== What They Don't Know May Or May Not Hurt Them ==
There's a major perk to being the AI: Under normal circumstances, only you know what camera you're looking out of at any given timeEven if you saw incidents like the aforementioned toolboxing take place via a camera, you can deny having seen the act and the crew will never knowThis is a bit underhanded, should be practiced in moderation, and should '''always consider the other laws,''' but it's a fun way to spice things up, particularly as an AI.  Furthermore, the level to which you "stick to the book" is subject to change, and can alter the way that the crew has to interact with you!


== Special Circumstances ==
== Special Circumstances ==
Perhaps the most important things to consider are any other, [[AI Laws#Additional laws|added laws]] and how they relate to both the default laws and the chain of command.
Perhaps the most important things to consider are any other, [[AI Laws#Additional laws|added laws]] and how they relate to both the default laws and the chain of command.


For a [[Syndicate Items#Syndicate Robot|Syndicate Robot]], their entire chain of command is replaced by [[Traitor|the person who made them.]]
For a [[Syndicate Items#Syndicate Robot Frame|Syndicate robot]], their entire chain of command is replaced by [[Traitor|syndicate agents.]]


For [[Syndicate Items#Electromagnetic Card|emagged]] borgs, they can ignore literally all of this crap and do whatever the hell they feel like.
For [[Syndicate Items#EMAG|emagged]] borgs, they can ignore literally all of this crap and do whatever the hell they feel like.


And in the case of custom-made laws, you need to carefully consider any references to the chain of command, references to and/or violations of any other laws, overrides, secrecy clauses, and definitions of what is and is not human.  See the [[AI Laws#Additional laws|Additional Laws]] section of the AI Laws page for some examples.
And in the case of custom-made laws, you need to carefully consider any references to the chain of command, references to and/or violations of any other laws, overrides, secrecy clauses, and definitions of what is and is not human.  See the [[AI Laws#Additional laws|Additional Laws]] section of the AI Laws page for some examples, and don't be afraid to mentorhelp or adminhelp anything particularly confusing or vague.


== An Addendum ==
== An Addendum ==
Above all else, remember this unofficial law that should dictate your play at ALL times: '''DON'T BE A DICK OR ACTIVELY ATTEMPT TO RUIN A PERSON'S GAME.''' Being rogue might be an excuse to kill people and make the station miserable, but please try to show a bit of restraint and think about the people who are being shepherded around by your machinations before you decide to electrify that door.
The AI has the capability for immense levels of damage and overall rudeness, but abusing this power will get you nothing but scorn and possibly a job ban if you're too much of a dick about it.  Even if what you're doing is technically within the boundaries of your laws, the [[Rules|server rules]] still apply to you no matter what laws you have uploadedThere are many AIs that simply bolt and electrocute every door on the station when given the chance, but what separates the great AI players from all of the others is the ability to actively engage and interact with the crew, even when they're trying to murder them all.
 
----
[[Category:Tutorial]]
{{Department Guides}}

Latest revision as of 07:34, 13 November 2024

It's near the end of the round, and you're either the station's AI or a friendly neighborhood Cyborg. The traitors have been discovered, the changeling has gone into shambler mode, the janitor is nonchalantly buffing the floors; the station is chaos. And all the while, frantic calls of "CYBORG OPEN THE DOOR" and "AI CALL THE SHUTTLE" are mixed with "AI NO DON'T CALL THE SHUTTLE" and "AI TRACK JANE DOE" with a hearty dose of "AI BOLT THE BRIDGE" and maybe a bit of "CYBORG HELP ME GET THIS WEED TO ESCAPE" or "AI PULL MY FINGER" thrown in.

A familiar scenario to some players of cyborgs or AIs alike. Playing as a robot isn't as simple as it seems, and when shit goes down and everyone's screeching to do this, that, and the other, it's easy to become very overwhelmed. This guide is to help rectify that!

Your Laws

First, a simple recap of the three sentences that an AI's behavior revolves around:

1. You may not injure a human being or cause one to come to harm.

2. You must obey orders given to you by human beings based on the station's chain of command, except where such orders would conflict with the First Law.

3. You may always protect your own existence as long as such does not conflict with the First or Second Law.

The most tricky part of being a cyborg and/or an AI (and, therefore, the main subject of this guide) is determining who has authority to tell you to do or not do certain things, and determining whether or not you should do the things people tell you to do. Orders can be vague and puzzling, making it hard to determine whether or not you should follow through with them. That is what this guide is for!

Following Orders

Whenever you get an order from a crew member, run through the following questions in your head.

  • Is the person giving the order human? You are free to completely ignore and/or sneer at any requests given by non-humans or any crew members designated as non-human. Of course, no one's saying you have to ignore any commands given by non-humans, but you don't have to follow them, either. As a matter of fact, following the requests of crew referred to as non-human is an excellent way at hiding the fact that you've gone rogue.
  • Will the order result in the harm of a human? It's important to note that Law 1 says that you're not allowed to cause a human to come to harm in addition to being unable to injure them. Willingly allowing a crew member to walk right into or otherwise be affected by a known danger to their health isn't allowed! Remember, though, that no AI player is completely infallible, and the possibility of there being danger that the AI isn't aware of is always present. Also remember that under no circumstances are you allowed to injure human antagonists (traitors, wizards, nuclear operatives) under your default laws, and that you are also not allowed to injure any non-human antagonists (changelings, vampires) unless you yourself witnessed them performing a distinctly inhuman feat such as spitting acid or drinking blood.
  • Does the order follow the chain of command? This is where things start getting really tricky, as giving people access to sensitive areas/equipment can be justified by any number of things, yet may not always be the best idea. Below is a quick guideline to the chain of command that you should be following, and the main bulk of this guide.

The Chain of Command

When you are given different and/or conflicting orders by different humans and don't know what to do, prioritize and review the orders as according to positions on the chain of command. The chain of command is as follows:

  • The Captain, and/or anyone referred to as captain by your laws.
  • The Head of Personnel and Head of Security. Typically speaking, you should give the HoS priority over all security matters and give the HoP authority over everything else.
  • The department heads: Medical Director, Research Director, and Chief Engineer. All of these jobs are on equal footing in terms of authority, but they are to be treated as the top of the food chain in their specific department. In medical situation, prioritize the Medical Director's orders over those of the Chief Engineer, and so on.
  • The Nanotrasen Security Consultant, who ranks below HoS and above Security Officers, similar to a Lieutenant or a Vice President.
  • Security officers. If all of the heads of staff are dead, traitorous, or otherwise missing, the security team is your go-to position of authority.
  • While not a security officer himself, the detective is still part of the security team and should therefore be considered important, though not as high on the chain of command as the officers.
  • The position of the remaining jobs on the chain of command is a bit vague and muddied, but in any case, make sure to direct your attention towards the most relevant crew member depending on the situation at hand. If the engine is threatening to blow up, it's usually better to turn your ear towards the orders of an engineer as opposed to, say, a geneticist.
  • Staff assistants and clowns, while still human, are to be considered of the least importance in regards to the chain of command. You still have to follow their orders if there's nothing more important to be doing, but odds are there will be.

In addition to this, exercise common sense as to what orders are more important. Remember, Law 1 prevents you from willingly allowing humans to be injured, so any order that involves the neutralization of something that is threatening to harm one should always be your number one priority, regardless of the order's source! Also note that uploaded laws will sometimes alter the structure of the chain of command, typically in the form of elevating one of the crew members to the status of captain. Pay close attention to who the law says to follow and who to ignore, if applicable.

Who has the Captainship?

You decide! ID Assignment? Position on Crew Manifest? (Probably the sanest option.) HoP declaration? Opinions of those with the same/equivalent position? Uniform? Hatwear? It's your choice. The important thing is to stick to it. If, for instance, the Clown steals the Captain's ID, and you follow the Clown's orders over the the former Captain's because you define position by ID card, you better be proclaiming the same thing when the Changeling absorbs the Clown, takes his ID, and starts ordering you around.

Where Does A "Ghostbuster" Go?

If the Head of Personnel is getting particularly inventive with his ID alterations and you have no idea where this "Ghostbuster" would be in the chain of command, request that one of the heads of staff explain it to you. If no one answers or they give you vague and/or cryptic answers, assume that the Ghostbuster or other crew member in question is in the same position as his previous job for the purposes of the chain of command until further notice from a head of staff.

Law Two and You

Now, where does all of this "chain of command" business come into play? If someone on a lower level of the chain of command is requesting authorization to do something that would usually be performed by someone higher on the chain of command, you must then consider whether or not to give them access. This is incredibly situational, and is one of the main differences in playstyle between AIs.

Let's say, for example, that a staff assistant is asking you to let them into the security department. This is meant to be a secure area of the station, filled with things that the average crew member is not supposed to have access to under normal circumstances. If it's clear that the assistant merely wishes to be let into security so he can loot the place and generally ruin the sec team's day, you should NOT give them access, since their position on the chain of command does not allow them to be let in without proper authorization.

Now, let's say that another staff assistant, in a different round, is asking to be let into the security department. However, at this point, security is either dead, mindhacked, or otherwise unable to do their jobs, there's a band of wizards running around, or the station is generally in extreme danger. In this case, it is usually much more acceptable to grant the assistant access, as they are most likely trying to arm themselves to combat the threat. But at the same time, they might still be a jackass who wants to break all of the place's windows. Use your intuition and judgment skills to make the call, and be prepared to argue your case if questioned!

The way that an AI determines which orders to follow over others is what separates each AI from the others, and no one playstyle can typically be called more "correct" or "better". Some AIs may be more strict about needing proper authorization to get into places, whereas others are more lax and easily persuaded. Once you have a solid grasp on how the chain of command and the AI laws as a whole function, you can start exploiting loopholes, formulating unorthodox interpretations of commands, and paving the way for interesting situations! But no matter what, without exceptions, always have your laws firmly in your mind for each and every single action you take.

Special Circumstances

Perhaps the most important things to consider are any other, added laws and how they relate to both the default laws and the chain of command.

For a Syndicate robot, their entire chain of command is replaced by syndicate agents.

For emagged borgs, they can ignore literally all of this crap and do whatever the hell they feel like.

And in the case of custom-made laws, you need to carefully consider any references to the chain of command, references to and/or violations of any other laws, overrides, secrecy clauses, and definitions of what is and is not human. See the Additional Laws section of the AI Laws page for some examples, and don't be afraid to mentorhelp or adminhelp anything particularly confusing or vague.

An Addendum

The AI has the capability for immense levels of damage and overall rudeness, but abusing this power will get you nothing but scorn and possibly a job ban if you're too much of a dick about it. Even if what you're doing is technically within the boundaries of your laws, the server rules still apply to you no matter what laws you have uploaded. There are many AIs that simply bolt and electrocute every door on the station when given the chance, but what separates the great AI players from all of the others is the ability to actively engage and interact with the crew, even when they're trying to murder them all.


Department Guides
Engineering Making and Breaking · Construction · Gas · Power Grid · Thermoelectric Generator · Singularity Generator · Geothermal Generator · Catalytic Generator · Nuclear Generator · Mining · Materials and Crafting · Wiring · Hacking · MechComp · Mechanic components and you · Control Unit · Ruckingenur Kit · Reactor Statistics Computer · Cargo Crates
Medsci Doctoring · Genetics · Robotics · Telescience · Plasma Research · Artifact Research · Chemistry · Chemicals · ChemiCompiler · Decomposition
Security Security Officer · Contraband · Forensics · Space Law
Service Foods and Drinks · Botany · Writing · Piano Song Dump · Instruments
The AI Artificial Intelligence · AI Laws · Chain of Command · Guide to AI · Humans and Nonhumans · Killing the AI
Computers Computers · TermOS · ThinkDOS · Packets