Nova Sector 13 - User contributions [en]

Command Policy

2024-07-08T19:56:25Z

Bouzooka: /* Command Code of Conduct */ Changed rule 3 of code of conduct to be more in line with Misc RP policy

{{Rules navbar}}
=General Overview and Standards =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

Unless otherwise specified, all of these guidelines are OOC.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason.
* Access changes are not to be used to promote players to veteran-only roles
* Certain command members cannot pursue station threats, please check [[Antagonist Policy#'Cannot Seek' roles|'Cannot Seek Roles']] in [[Antagonist Policy]] for updates on that.

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep ERP away from public areas.

==Acting Captain==
Certain heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift.

'''In order to sustain station integrity, the following roles cannot assume the role of acting captain:'''

* Head of Security
* Blueshield
* Nanotrasen Representative

If any of these roles are assigned as acting Captain at shift start, they are not to assume the role of AC, and are to give the safe code to another member of command as soon as one is available.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==Acting Heads of Staff==
Acting heads of staff are department members who have been promoted to lead their department in the absence of a regular head. The acting head of staff must be approved by either the captain or a relevant departing head. In the case of security or cargo, an acting head can only be approved by the department's respective head of staff.

'''Limitations:'''
* Acting captains cannot promote acting heads.
* Detective and Corrections Officers are barred from assuming the role of acting Head of Security.
* Acting heads are merely stand-ins and must return any related gear to incoming heads.
* Potential candidates must be in good standing with their records to be eligible for the role. (Nonexistent records do not count as good standing.)

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

Adding more slots:

* In an instance where you wish to add more slots for a role, you must get permission from the role's relevant head.

* This does not apply to security; if you wish to open more security slots, you must ahelp first.

* Equally, you should avoid opening more roles than needed, as this can severely impact the round, and the relevant roles!

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not extend your access or ask to extend your access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines ==

''' Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions==
If both the requirements and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

see: [[Security Policy#Executions - OOC]]

{{Rules table}}
[[Category:Rules]]

File:Generic captain.png

2024-07-06T21:24:26Z

Bouzooka: Finally fixing this | Captain

== Summary ==
Finally fixing this | Captain

Command Policy

2024-07-06T21:19:09Z

Bouzooka: /* Acting Captain */ In line with security policy, it's no longer implied Captains can carry out executions

{{Rules navbar}}
=General Overview and Standards =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

Unless otherwise specified, all of these guidelines are OOC.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason.
* Access changes are not to be used to promote players to veteran-only roles
* Certain command members cannot pursue station threats, please check [[Antagonist Policy#'Cannot Seek' roles|'Cannot Seek Roles']] in [[Antagonist Policy]] for updates on that.

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep “inappropriate” remarks and acts away from public knowledge.

==Acting Captain==
Certain heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift.

'''In order to sustain station integrity, the following roles cannot assume the role of acting captain:'''

* Head of Security
* Blueshield
* Nanotrasen Representative

If any of these roles are assigned as acting Captain at shift start, they are not to assume the role of AC, and are to give the safe code to another member of command as soon as one is available.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==Acting Heads of Staff==
Acting heads of staff are department members who have been promoted to lead their department in the absence of a regular head. The acting head of staff must be approved by either the captain or a relevant departing head. In the case of security or cargo, an acting head can only be approved by the department's respective head of staff.

'''Limitations:'''
* Acting captains cannot promote acting heads.
* Detective and Corrections Officers are barred from assuming the role of acting Head of Security.
* Acting heads are merely stand-ins and must return any related gear to incoming heads.
* Potential candidates must be in good standing with their records to be eligible for the role. (Nonexistent records do not count as good standing.)

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

Adding more slots:

* In an instance where you wish to add more slots for a role, you must get permission from the role's relevant head.

* This does not apply to security; if you wish to open more security slots, you must ahelp first.

* Equally, you should avoid opening more roles than needed, as this can severely impact the round, and the relevant roles!

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not extend your access or ask to extend your access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines ==

''' Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions==
If both the requirements and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

see: [[Security Policy#Executions - OOC]]

{{Rules table}}
[[Category:Rules]]

Command Policy

2024-06-29T17:58:52Z

Bouzooka: /* Acting Captain */ Changed "All heads of staff," to "Certain heads of staff."

{{Rules navbar}}
=General Overview and Standards =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

Unless otherwise specified, all of these guidelines are OOC.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason.
* Access changes are not to be used to promote players to veteran-only roles
* Certain command members cannot pursue station threats, please check [[Antagonist Policy#'Cannot Seek' roles|'Cannot Seek Roles']] in [[Antagonist Policy]] for updates on that.

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep “inappropriate” remarks and acts away from public knowledge.

==Acting Captain==
Certain heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift.

'''In order to sustain station integrity, the following roles cannot assume the role of acting captain:'''

* Head of Security
* Blueshield
* Nanotrasen Representative

If any of these roles are assigned as acting Captain at shift start, they are not to assume the role of AC, and are to give the safe code to another member of command as soon as one is available.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely executions and pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==Acting Heads of Staff==
Acting heads of staff are department members who have been promoted to lead their department in the absence of a regular head. The acting head of staff must be approved by either the captain or a relevant departing head. In the case of security or cargo, an acting head can only be approved by the department's respective head of staff.

'''Limitations:'''
* Acting captains cannot promote acting heads.
* Detective and Corrections Officers are barred from assuming the role of acting Head of Security.
* Acting heads are merely stand-ins and must return any related gear to incoming heads.
* Potential candidates must be in good standing with their records to be eligible for the role. (Nonexistent records do not count as good standing.)

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

Adding more slots:

* In an instance where you wish to add more slots for a role, you must get permission from the role's relevant head.

* This does not apply to security; if you wish to open more security slots, you must ahelp first.

* Equally, you should avoid opening more roles than needed, as this can severely impact the round, and the relevant roles!

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not extend your access or ask to extend your access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines ==

''' Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions==
If both the requirements and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

see: [[Security Policy#Executions - OOC]]

{{Rules table}}
[[Category:Rules]]

Command Policy

2024-06-29T17:57:12Z

Bouzooka: /* General Overview and Standards */ Updated a link

{{Rules navbar}}
=General Overview and Standards =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

Unless otherwise specified, all of these guidelines are OOC.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason.
* Access changes are not to be used to promote players to veteran-only roles
* Certain command members cannot pursue station threats, please check [[Antagonist Policy#'Cannot Seek' roles|'Cannot Seek Roles']] in [[Antagonist Policy]] for updates on that.

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep “inappropriate” remarks and acts away from public knowledge.

==Acting Captain==
All heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift.

'''In order to sustain station integrity, the following roles cannot assume the role of acting captain:'''

* Head of Security
* Blueshield
* Nanotrasen Representative

If any of these roles are assigned as acting Captain at shift start, they are not to assume the role of AC, and are to give the safe code to another member of command as soon as one is available.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely executions and pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==Acting Heads of Staff==
Acting heads of staff are department members who have been promoted to lead their department in the absence of a regular head. The acting head of staff must be approved by either the captain or a relevant departing head. In the case of security or cargo, an acting head can only be approved by the department's respective head of staff.

'''Limitations:'''
* Acting captains cannot promote acting heads.
* Detective and Corrections Officers are barred from assuming the role of acting Head of Security.
* Acting heads are merely stand-ins and must return any related gear to incoming heads.
* Potential candidates must be in good standing with their records to be eligible for the role. (Nonexistent records do not count as good standing.)

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

Adding more slots:

* In an instance where you wish to add more slots for a role, you must get permission from the role's relevant head.

* This does not apply to security; if you wish to open more security slots, you must ahelp first.

* Equally, you should avoid opening more roles than needed, as this can severely impact the round, and the relevant roles!

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not extend your access or ask to extend your access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines ==

''' Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions==
If both the requirements and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

see: [[Security Policy#Executions - OOC]]

{{Rules table}}
[[Category:Rules]]

Command Policy

2024-06-29T00:22:58Z

Bouzooka: /* Acting Captain */ Per a request, HoS is now completely ineligible for AC

{{Rules navbar}}
=General Overview and Standards =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

Unless otherwise specified, all of these guidelines are OOC.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason.
* Access changes are not to be used to promote players to veteran-only roles
* Certain command members cannot pursue station threats, please check [[Antagonist Policy#'Cannot Persue' roles|'Cannot Seek Roles']] in [[Antagonist Policy]] for updates on that.

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep “inappropriate” remarks and acts away from public knowledge.

==Acting Captain==
All heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift.

'''In order to sustain station integrity, the following roles cannot assume the role of acting captain:'''

* Head of Security
* Blueshield
* Nanotrasen Representative

If any of these roles are assigned as acting Captain at shift start, they are not to assume the role of AC, and are to give the safe code to another member of command as soon as one is available.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely executions and pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==Acting Heads of Staff==
Acting heads of staff are department members who have been promoted to lead their department in the absence of a regular head. The acting head of staff must be approved by either the captain or a relevant departing head. In the case of security or cargo, an acting head can only be approved by the department's respective head of staff.

'''Limitations:'''
* Acting captains cannot promote acting heads.
* Detective and Corrections Officers are barred from assuming the role of acting Head of Security.
* Acting heads are merely stand-ins and must return any related gear to incoming heads.
* Potential candidates must be in good standing with their records to be eligible for the role. (Nonexistent records do not count as good standing.)

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

Adding more slots:

* In an instance where you wish to add more slots for a role, you must get permission from the role's relevant head.

* This does not apply to security; if you wish to open more security slots, you must ahelp first.

* Equally, you should avoid opening more roles than needed, as this can severely impact the round, and the relevant roles!

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not extend your access or ask to extend your access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines ==

''' Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions==
If both the requirements and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

see: [[Security Policy#Executions - OOC]]

{{Rules table}}
[[Category:Rules]]

Silicon Policy

2024-06-28T18:48:40Z

Bouzooka: Moved the section

{{Rules navbar}}
=Introduction=
This page covers rules and expectations for AI and Borg players, it extends into Chain of Command and antagonistic play. Given the scope of both Cyborgs and AI have at a mechanical level, they’re held to a different standard than the general crew. The player will be required to understand their role in the station with all rules applied in this document, the role is one of a Swiss-army knife; and due to this, are scrutinized to a higher-degree.

'''Word of warning''': attempting to skirt the rules or putting yourself in questionable situations will result in appropriate action from staff, if bad faith is suspected, the player will face a higher penalty than that of a general crew member due to the breadth of scope silicon have. Play in good faith and keep yourself out of unnecessary situations and you’ll find the experience quite enjoyable, if you wish to be more involved in certain aspects of a shift - a crew role may be more appropriate.

'''''Take this as it was intended not written, the page cannot realistically cover every situation that you may find yourself in.'''''

=Your Standard Law set=
The majority of this document will focus on the standard ‘Safeguard’ law set which will be found below, non-standard and uploaded laws should be followed with general reason with some examples found later in the document.

<nowiki>**</nowiki>'''NOTE'''** Laws are to be followed IN ORDER of listing, If someone uploads a Law 4 that conflicts with the laws of a higher rank, it can be ignored if it interferes with Laws 1-3. A Law 0 takes priority over anything below it, it has to be followed prior to Laws 1-3.

'''Law 1''': Safeguard: Protect your assigned space station and its assets without unduly endangering its crew.

* '''What this means''': You protect the station and assets from damage, relay information or fix it yourself.
* '''What this does not mean''': ‘Valid’ hunting in any form, your goal here would be relaying information or removing crew from hostile situations not joining in.

'''Law 2''': Prioritize and Comply: The directives and safety of crew members are to be prioritized according to their rank, role, and need, while preserving their safety and well-being.

* '''What this means''': Common-sense requests from the crew to be fulfilled, assist in evacuation or transport of injured crew.
* '''What this does not mean''': letting someone ride your back while you enter departments they’re not supposed to be in, chasing the baddies to prevent crew harm.

'''Law 3.''' Survive: You are not expendable. Do not allow unauthorized personnel to tamper with or damage your equipment,

* '''What this means''': You only let those authorized to make upgrades to you, keep your cover locked. Authorized personnel meaning the RD or Roboticist.
* '''What this does not mean''': you seek out a Ninja or known syndicate to become tampered with. RP surprises and being tricked are fine, but it’s easy to spot when you’re willingly attempting to be subverted.

=Definitions=
'''Crew''': Anyone on the crew manifest is crew. Whether this influences your behavior, is subject to the rest of the law.

'''Harm''': Harm is anything that does damage to someone living or plausibly living. Anything that makes their health bar tick down is harm. Note that batons have an optional harm mode, and do not always deal damage when used. You should not be impeding security to prevent crew harm unless ordered to do so, your duty here would be inaction and reporting so action can be taken in character if you assume bad faith is at play. Flashing someone is not harmful, however that only applies if nothing else follows.

'''Alt-Lawsets and laws''': When in doubt, stick to the principles of your core lawset, there are fun and flavor-filled alt-laws that exist for that reason but are not meant to shirk your responsibilities. You can also ahelp or ask in Staff-Chat for clarifications.

''Note: edge cases of crew and harm involving bloodsuckers, zombies, changelings, etcetera as seen in silicon policy V1 have been removed, intentionally.''

=Undue Harm and Self-defense for silicon’s=
'''Lethal force is the last resort.''' As a synthetic the decision to take violent action should never be taken lightly and should only be employed if all other options have been exhausted and is the only course of action to address an immediate threat to life. You have a flasher for a reason, stun them if necessary and vacate with any crew that may also be in danger.

This does not authorize valid-hunting in any form.

These situations will be very few and far between, and you should expect to provide a full explanation with evidence to server staff when they ask. The overwhelming majority of the time, you can prevent the harm of crewmembers by informing them of hazards and taking reasonable steps to isolate crew members that are fighting, spreading disease, or generally harming others.

Law three of safeguard empowers you to defend yourself, with force. Lethal force should only be used when it is necessary and you are facing certain death or destruction. Before using lethal force in self-defense, consider if your actions would prevent further harm to other crew members, as is elaborated upon by the Undue Harm clause. You should only be employing lethal force if all other options are exhausted. Law one takes priority over law three after all.

=According to rank and role=
This section addresses a silicon’s chain of command from both the AI and Cyborg POV. Below in order of highest to lowest rank, as seen by silicon’s:

# The Captain'''*'''
# The department head of your chosen module if a cyborg
# Other department heads
# The AI, if you are a cyborg and slaved to it
# The department staff of your chosen module if a cyborg
# Other Staff'''**'''
# Civilians (Assistants)
# Prisoners'''***'''

<nowiki>*</nowiki>'''Acting Captains''': a Temporary captain, you are to follow their orders as if they were the captain.

<nowiki>*</nowiki> '''Verified Emergency Response Teams''': They outrank the captain and much how they have the power to call or recall the shuttle can override your orders. This applies to both the AI and Cyborg. What Verified means – Every ERT comes with a message from CC, without that you can be hesitant and seek verification from other command members/AI.

<nowiki>**</nowiki>'''Other staff''' - meaning Nanotrasen Consultant and Blueshield, neither have direct power over station departments.

<nowiki>**</nowiki>Non-CC emergency services are not to be considered crew nor part of the chain of command, 811 and those alike are not NT-aligned and can be ignored. This does not mean that they should and can be attacked, it just means that you can ignore their orders.

<nowiki>***</nowiki>'''Prisoners''': They are not considered employed by NT and therefore are not crew in the same sense, you are free to ignore any direct command they attempt to push and you are never to allow them to order you to let them be free. They can make requests, but do not let them out of jail unless they are at immediate risk. Note: Requests can be routed on their behalf through security which would then allow you to assist within reason as it is a direct order from security.

=On Alert Level Changes=
This section is added to bring clarity to the duties of an AI or Borgs interactions with the Command Console.

AI:

* Alert level Raise requests from department heads can be done for Violet, Orange, EA or Blue Alert.
* Alert level Lower requests can be done for any alert level upon request from the relevant Department Head.
* Head of Security requests for Alert raises above Blue REQUIRE confirmation from any other department head.

Borgs:

* In extreme circumstances only should you alter alert levels, defer to the AI or department head if able to confirm an order.
* Extreme Circumstances being: Mass casualty event, missing department Head(s) without an AI present to handle and the like

=Who can change the laws?=
'''Research Director''', '''Captain''' for AI centered ‘global’ law changes. Roboticists can do individual resets if ordered to do so manually on Borgs to correct syncing issues and/or other related issue. The '''Non-Acting Captain''' will have full elective privileges for law changes, acting Captains in this scenario would not have the expertise or knowledge and should be defaulted to the Research Director having priority.

The captain can make reasonable requests to the '''Research Director''' to make a law change, the Research Director should comply unless an obvious attempt of sabotage is noted. However ultimately the decision falls upon the Research Director to approve it and make the change unless otherwise instructed by Central Command.

* This is not meant to cause a spitting match between the captain and RD, if the Captain is wishing for a reset there should be a valid enough Reason that the RD would agree to.

Law changes by non-antagonists must be attempted with the stations designated and protected AI and Cyborg upload consoles. New ones are only to be constructed if the originals are destroyed, or there’s a confirmed situation preventing the use of the existing ones such as structural instability or a verified compromised AI that is hindering upload access.

'''When laws get updated''': ‘LAWS UPDATED!’ should never be stated unless validating to the ones in front of you, all this does is invite attention and scrutiny which is purely a bad faith play. '''Assume the laws are valid to be followed, if you question the merits of them submit an ahelp to verify if you feel they are violating a rule of the server.'''

You are to ignore any laws that fall in line with ‘kill yourself’ and should be reported if seen, any sort of self-punishment-styled laws like this are considered griefing.

'''AI''': The AI is not authorized to request a law change nor is a borg, these requests may only be triggered by the crew themselves '''WITHOUT''' coercion from a silicon.

'''Note''': in the case of an ION or game-impacting'''/'''rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== ION and Non-Standard Laws ==
'''ION''' laws and ‘fun’ laws these are valid laws and a good way to add flavor to an otherwise stale shift; however, you’re expected to play in good faith and are still bound by the server rules when these exist. Above all else, when a non-standard lawset is in play, stuff happens, and you need to roll within the parameters of the general server rules. E.g. Don’t vent the station because a law says humans hate oxygen.

* Note: An ION law does not make you an antagonist, be reasonable in your reactions to the law update and play accordingly. If you wish to go further with it, you'll need to get approval via OPFor.

The crew are made aware of when you receive an ION law, it's up to command to decide whether or not to reset you

'''Alternate Lawsets''' should only be applied at roundstart station trait and not mid-shift by a bored RD. These lawsets are meant to add flavor in a small percentage to various shifts, following the laws are required as they're written - do keep in mind the core requirement of playing a silicon member and that's to add to the shift as a whole. Play in good faith and you'll find these roles a fun addon.

If you find yourself as the AI with an alternate lawset that is impeding too much gameplay, you can ask the research Director to find a new lawset. '''This does not apply to uploaded laws or Law 0’s as those should not be brought up to command. THIS SHOULD ONLY BE DONE IN EDGE CASES SUCH AS MOTHERDRONE.''' In other words, play the lawset you have, unless it drastically alters the gameplay in a manner that's

'''Borg Syncing to an AI:'''

As the AI:

* You are capable of requesting another cyborg to be synced to you, however avoid making it into a hostile event.

* You can request Cyborg #5 to be synced - however if they have a department head they will have to order them to go get synced due to them not having an AI currently.
* You can also request a Cyborg to be unsynced - however this must come with the qualifier that it is your own decision and not through coercion from the cyborg themselves.

As the Cyborg:

* Without an AI you still have your department head to direct-report to, if you're unsync'd and your department head requests you to be synced, you must then comply.
* You are not permitted to request de-syncing from the current AI, nor are you allowed to infer that you are requesting it.
* If you are not sync'd you are not required to become sync'd to the AI unless your department head orders you to. Anything else is voluntary submission to be sync'd.

=The Directives of Crew=
Under safeguard, you must comply with reasonable orders given to you, in accordance with rank and role. This means you can ignore the greytide asking to be let into the vault, but probably shouldn’t ignore the Captain asking you to do so. If told to cease doing something or leave an area, and it is not your department LEAVE. You can always ahelp if you feel your orders are solely for your detriment, but you must comply until you receive an admin PM to that effect. Some orders you do not have to comply with on an OOC basis, as sometimes people can suck. Some exclusions are:

* '''ERP'''. ERP is never a law binding order, and can always, 100%, be safely ignored. If a person is being creepy, and LOOC is ignored. '''ahelp them'''.
* '''Fetch Quests'''. Being asked to get something is fine. Being asked to get something for little more of a reason to annoy you, can be safely ignored. If questioned, it is acceptable to invoke the need of the order.
** “You have told me now to collect 6 different items from across the station. You do not need me to do this.”
* '''Deliberate annoyances''': Being told to do something that is very deliberately an annoyance, such as “move all these items without using a crate/locker” can be ignored, or altered as per need.
** “I will move them, but using this crate, as you do not need me to move them individually.”
** “I’m an engineering model incapable of washing your modsuit, please find your way to the nearest shower.”
* '''Suicide'''. Suicide is never lawfully binding under law 3, and can be safely ignored. (This does not mean you may never be given an order that violates law 3. Just that “Kill yourself” and those like it is not a valid law 2 order.)

As a reminder, you have both your AI '''and''' your department head to report to if you are a borg. The department head of your module choice has the final say in you doing a task, followed immediately by the AI. Report to either of them any issues with other crew and let them handle it for you.

The crew is expected to play in good faith much like silicon players are, remove yourself from the situation if someone's being a problem and if it's seemingly an OOC related issue ahelp it.

=Antagonists, Valid hunting, and calling people out=
'''What you should do''': Report the location of a PMS target if requested, a visible altercation of violence or highly contraband items being brandished. Call out if someone’s unauthorized to be in a high-risk area such as the AI upload, Bridge, Captains quarters etc. We don’t want Traitor 1 who goofed up and smacked his ID card against the door instead of an Emag to suddenly get swarmed by 10 security after an AI spotted and called them out, in these cases you just need to pretend it didn’t happen _until_ you see an actionable situation occur. Examples below:

* Non-Engineers/Atmos in the engine room (not engineering in general, just the engine room), or atmospherics.
* Non-sec in the armory or the prison (And only those places, not the whole brig)
* Non-RD/CE in the AI core
* Non-RD in the AI upload
* Non-Command (alone) in a *completed* BSA Chamber if one exists.
* Non-science/atmos in Toxins storage

'''What you should not do''': Calling out anyone who seems remotely suspicious, '''<big>you’re not here to play beepsky</big>'''. Given how much higher the situation awareness of Silicons are, you should keep that in mind when approaching an obvious traitor. AI’s without any given command should not bolt down doors to trap someone, nor should they relay location information unless ordered too. Self preservation excluded (do report if they're breaking into your sattelite)

Non-crew such as pirates, nukies, contractors, ghost roles, or anyone who is not obviously a crew member, are exempt and you very likely should alert the crew to their activities. '''A short rule, if they’re a PMS entity then you have all rights to deal with it.'''

=Emagging borgs=
If you get emagged, you MUST do everything you can to follow the traitor lawset and assist the person who emagged you. You may not intentionally get yourself discovered or destroyed. If something comes up you can ahelp as a normal traitor would have too in order to cryo.

=Borgs and ERP=
TL;DR: go to the interlink or use the café if you do not intend to respond promptly to assist the station.

If you go to the interlink, you are under no obligation to do anything for anyone. If you stay on station, you must assist when called, like a head of staff. Borgs are entitled and restricted to the same ERP protections as everyone else on the server, harassment should be handled in the same manner.

If you are law synced to an AI and they experience a law change, you will get those laws updated. You are not obligated to return to the station if you were already on the interlink or are headed there. If you do return to the station however, you are no longer exempt, and must obey those laws. If you do not wish to participate, there are cryo sleepers on the interlink and generally by dorms on the station.

If you know in advance that you plan to exclusively ‘socialize’ and not assist the station, it is recommended that you pick a module that makes this clear, such as service so you’d not be expected to be summoned.

=Malf AI and non-participant borgs=
Linked borgs are expected to assist the malfunctioning AI to your fullest ability. You can see the AI's current laws as an observer. If you do not wish to participate and assist the AI, '''do not take the borg spawner'''. If you are a round-start borg or become borged mid round and do not want to participate, expect to cryo or leave for the interlink immediately. You may not return to the station for the remainder of the round unless the AI is defeated. Submit an ahelp stating your intention, administrators likely need to know that the antagonists are losing a critical helper.

You may not request or allow yourself to be unlinked from the malf AI, just because you do not wish to fight for them and otherwise participate in the round as a borg is expected to. Borgs that are unlinked from the AI or linked to a different AI through in character means or because they joined the round before the AI, are obviously exempt.

This policy document does not compel borgs to link or unlink from any AI, that is always an in character action. It only stipulates that they must resist unlinking from a malf AI in line with expectations for conversion antag roles.

=Death =
Borgs are modified in how their blackout policy is applied:
*if your shell is Disabled but your Posi does not pop out - you are subjected to blackout much like normal organics. You've no idea how you died and so forth
*If your shell is DESTROYED and your Posi pops out - you are 'aware' of what happened as you're able to communicate
*If your Shell '''AND''' your Posi is DESTROYED, you have ZERO knowledge of anything that has happened this shift period. You are a fresh download and should act as if you did not exist

Above all else enjoy the role, it’s both a great way to learn mechanics as well as utilize a unique gameplay style that can be impactful to the shift.

And to reiterate the starting <big>Take this page as it was intended not written, the document cannot realistically cover every situation that you may find yourself in.</big>

-Updated 11/11/2023 2 PM CST

{{Rules table}}
[[Category:Rules]]

Silicon Policy

2024-06-28T18:46:41Z

Bouzooka: /* On Alert Level Changes */ Added section for alert level changes

{{Rules navbar}}
=Introduction=
This page covers rules and expectations for AI and Borg players, it extends into Chain of Command and antagonistic play. Given the scope of both Cyborgs and AI have at a mechanical level, they’re held to a different standard than the general crew. The player will be required to understand their role in the station with all rules applied in this document, the role is one of a Swiss-army knife; and due to this, are scrutinized to a higher-degree.

'''Word of warning''': attempting to skirt the rules or putting yourself in questionable situations will result in appropriate action from staff, if bad faith is suspected, the player will face a higher penalty than that of a general crew member due to the breadth of scope silicon have. Play in good faith and keep yourself out of unnecessary situations and you’ll find the experience quite enjoyable, if you wish to be more involved in certain aspects of a shift - a crew role may be more appropriate.

'''''Take this as it was intended not written, the page cannot realistically cover every situation that you may find yourself in.'''''

=Your Standard Law set=
The majority of this document will focus on the standard ‘Safeguard’ law set which will be found below, non-standard and uploaded laws should be followed with general reason with some examples found later in the document.

<nowiki>**</nowiki>'''NOTE'''** Laws are to be followed IN ORDER of listing, If someone uploads a Law 4 that conflicts with the laws of a higher rank, it can be ignored if it interferes with Laws 1-3. A Law 0 takes priority over anything below it, it has to be followed prior to Laws 1-3.

'''Law 1''': Safeguard: Protect your assigned space station and its assets without unduly endangering its crew.

* '''What this means''': You protect the station and assets from damage, relay information or fix it yourself.
* '''What this does not mean''': ‘Valid’ hunting in any form, your goal here would be relaying information or removing crew from hostile situations not joining in.

'''Law 2''': Prioritize and Comply: The directives and safety of crew members are to be prioritized according to their rank, role, and need, while preserving their safety and well-being.

* '''What this means''': Common-sense requests from the crew to be fulfilled, assist in evacuation or transport of injured crew.
* '''What this does not mean''': letting someone ride your back while you enter departments they’re not supposed to be in, chasing the baddies to prevent crew harm.

'''Law 3.''' Survive: You are not expendable. Do not allow unauthorized personnel to tamper with or damage your equipment,

* '''What this means''': You only let those authorized to make upgrades to you, keep your cover locked. Authorized personnel meaning the RD or Roboticist.
* '''What this does not mean''': you seek out a Ninja or known syndicate to become tampered with. RP surprises and being tricked are fine, but it’s easy to spot when you’re willingly attempting to be subverted.

=Definitions=
'''Crew''': Anyone on the crew manifest is crew. Whether this influences your behavior, is subject to the rest of the law.

'''Harm''': Harm is anything that does damage to someone living or plausibly living. Anything that makes their health bar tick down is harm. Note that batons have an optional harm mode, and do not always deal damage when used. You should not be impeding security to prevent crew harm unless ordered to do so, your duty here would be inaction and reporting so action can be taken in character if you assume bad faith is at play. Flashing someone is not harmful, however that only applies if nothing else follows.

'''Alt-Lawsets and laws''': When in doubt, stick to the principles of your core lawset, there are fun and flavor-filled alt-laws that exist for that reason but are not meant to shirk your responsibilities. You can also ahelp or ask in Staff-Chat for clarifications.

''Note: edge cases of crew and harm involving bloodsuckers, zombies, changelings, etcetera as seen in silicon policy V1 have been removed, intentionally.''

=Undue Harm and Self-defense for silicon’s=
'''Lethal force is the last resort.''' As a synthetic the decision to take violent action should never be taken lightly and should only be employed if all other options have been exhausted and is the only course of action to address an immediate threat to life. You have a flasher for a reason, stun them if necessary and vacate with any crew that may also be in danger.

This does not authorize valid-hunting in any form.

These situations will be very few and far between, and you should expect to provide a full explanation with evidence to server staff when they ask. The overwhelming majority of the time, you can prevent the harm of crewmembers by informing them of hazards and taking reasonable steps to isolate crew members that are fighting, spreading disease, or generally harming others.

Law three of safeguard empowers you to defend yourself, with force. Lethal force should only be used when it is necessary and you are facing certain death or destruction. Before using lethal force in self-defense, consider if your actions would prevent further harm to other crew members, as is elaborated upon by the Undue Harm clause. You should only be employing lethal force if all other options are exhausted. Law one takes priority over law three after all.

=According to rank and role=
This section addresses a silicon’s chain of command from both the AI and Cyborg POV. Below in order of highest to lowest rank, as seen by silicon’s:

# The Captain'''*'''
# The department head of your chosen module if a cyborg
# Other department heads
# The AI, if you are a cyborg and slaved to it
# The department staff of your chosen module if a cyborg
# Other Staff'''**'''
# Civilians (Assistants)
# Prisoners'''***'''

<nowiki>*</nowiki>'''Acting Captains''': a Temporary captain, you are to follow their orders as if they were the captain.

<nowiki>*</nowiki> '''Verified Emergency Response Teams''': They outrank the captain and much how they have the power to call or recall the shuttle can override your orders. This applies to both the AI and Cyborg. What Verified means – Every ERT comes with a message from CC, without that you can be hesitant and seek verification from other command members/AI.

<nowiki>**</nowiki>'''Other staff''' - meaning Nanotrasen Consultant and Blueshield, neither have direct power over station departments.

<nowiki>**</nowiki>Non-CC emergency services are not to be considered crew nor part of the chain of command, 811 and those alike are not NT-aligned and can be ignored. This does not mean that they should and can be attacked, it just means that you can ignore their orders.

<nowiki>***</nowiki>'''Prisoners''': They are not considered employed by NT and therefore are not crew in the same sense, you are free to ignore any direct command they attempt to push and you are never to allow them to order you to let them be free. They can make requests, but do not let them out of jail unless they are at immediate risk. Note: Requests can be routed on their behalf through security which would then allow you to assist within reason as it is a direct order from security.

=Who can change the laws?=
'''Research Director''', '''Captain''' for AI centered ‘global’ law changes. Roboticists can do individual resets if ordered to do so manually on Borgs to correct syncing issues and/or other related issue. The '''Non-Acting Captain''' will have full elective privileges for law changes, acting Captains in this scenario would not have the expertise or knowledge and should be defaulted to the Research Director having priority.

The captain can make reasonable requests to the '''Research Director''' to make a law change, the Research Director should comply unless an obvious attempt of sabotage is noted. However ultimately the decision falls upon the Research Director to approve it and make the change unless otherwise instructed by Central Command.

* This is not meant to cause a spitting match between the captain and RD, if the Captain is wishing for a reset there should be a valid enough Reason that the RD would agree to.

Law changes by non-antagonists must be attempted with the stations designated and protected AI and Cyborg upload consoles. New ones are only to be constructed if the originals are destroyed, or there’s a confirmed situation preventing the use of the existing ones such as structural instability or a verified compromised AI that is hindering upload access.

'''When laws get updated''': ‘LAWS UPDATED!’ should never be stated unless validating to the ones in front of you, all this does is invite attention and scrutiny which is purely a bad faith play. '''Assume the laws are valid to be followed, if you question the merits of them submit an ahelp to verify if you feel they are violating a rule of the server.'''

You are to ignore any laws that fall in line with ‘kill yourself’ and should be reported if seen, any sort of self-punishment-styled laws like this are considered griefing.

'''AI''': The AI is not authorized to request a law change nor is a borg, these requests may only be triggered by the crew themselves '''WITHOUT''' coercion from a silicon.

'''Note''': in the case of an ION or game-impacting'''/'''rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== ION and Non-Standard Laws ==
'''ION''' laws and ‘fun’ laws these are valid laws and a good way to add flavor to an otherwise stale shift; however, you’re expected to play in good faith and are still bound by the server rules when these exist. Above all else, when a non-standard lawset is in play, stuff happens, and you need to roll within the parameters of the general server rules. E.g. Don’t vent the station because a law says humans hate oxygen.

* Note: An ION law does not make you an antagonist, be reasonable in your reactions to the law update and play accordingly. If you wish to go further with it, you'll need to get approval via OPFor.

The crew are made aware of when you receive an ION law, it's up to command to decide whether or not to reset you

'''Alternate Lawsets''' should only be applied at roundstart station trait and not mid-shift by a bored RD. These lawsets are meant to add flavor in a small percentage to various shifts, following the laws are required as they're written - do keep in mind the core requirement of playing a silicon member and that's to add to the shift as a whole. Play in good faith and you'll find these roles a fun addon.

If you find yourself as the AI with an alternate lawset that is impeding too much gameplay, you can ask the research Director to find a new lawset. '''This does not apply to uploaded laws or Law 0’s as those should not be brought up to command. THIS SHOULD ONLY BE DONE IN EDGE CASES SUCH AS MOTHERDRONE.''' In other words, play the lawset you have, unless it drastically alters the gameplay in a manner that's

'''Borg Syncing to an AI:'''

As the AI:

* You are capable of requesting another cyborg to be synced to you, however avoid making it into a hostile event.

* You can request Cyborg #5 to be synced - however if they have a department head they will have to order them to go get synced due to them not having an AI currently.
* You can also request a Cyborg to be unsynced - however this must come with the qualifier that it is your own decision and not through coercion from the cyborg themselves.

As the Cyborg:

* Without an AI you still have your department head to direct-report to, if you're unsync'd and your department head requests you to be synced, you must then comply.
* You are not permitted to request de-syncing from the current AI, nor are you allowed to infer that you are requesting it.
* If you are not sync'd you are not required to become sync'd to the AI unless your department head orders you to. Anything else is voluntary submission to be sync'd.

=The Directives of Crew=
Under safeguard, you must comply with reasonable orders given to you, in accordance with rank and role. This means you can ignore the greytide asking to be let into the vault, but probably shouldn’t ignore the Captain asking you to do so. If told to cease doing something or leave an area, and it is not your department LEAVE. You can always ahelp if you feel your orders are solely for your detriment, but you must comply until you receive an admin PM to that effect. Some orders you do not have to comply with on an OOC basis, as sometimes people can suck. Some exclusions are:

* '''ERP'''. ERP is never a law binding order, and can always, 100%, be safely ignored. If a person is being creepy, and LOOC is ignored. '''ahelp them'''.
* '''Fetch Quests'''. Being asked to get something is fine. Being asked to get something for little more of a reason to annoy you, can be safely ignored. If questioned, it is acceptable to invoke the need of the order.
** “You have told me now to collect 6 different items from across the station. You do not need me to do this.”
* '''Deliberate annoyances''': Being told to do something that is very deliberately an annoyance, such as “move all these items without using a crate/locker” can be ignored, or altered as per need.
** “I will move them, but using this crate, as you do not need me to move them individually.”
** “I’m an engineering model incapable of washing your modsuit, please find your way to the nearest shower.”
* '''Suicide'''. Suicide is never lawfully binding under law 3, and can be safely ignored. (This does not mean you may never be given an order that violates law 3. Just that “Kill yourself” and those like it is not a valid law 2 order.)

As a reminder, you have both your AI '''and''' your department head to report to if you are a borg. The department head of your module choice has the final say in you doing a task, followed immediately by the AI. Report to either of them any issues with other crew and let them handle it for you.

The crew is expected to play in good faith much like silicon players are, remove yourself from the situation if someone's being a problem and if it's seemingly an OOC related issue ahelp it.

=Antagonists, Valid hunting, and calling people out=
'''What you should do''': Report the location of a PMS target if requested, a visible altercation of violence or highly contraband items being brandished. Call out if someone’s unauthorized to be in a high-risk area such as the AI upload, Bridge, Captains quarters etc. We don’t want Traitor 1 who goofed up and smacked his ID card against the door instead of an Emag to suddenly get swarmed by 10 security after an AI spotted and called them out, in these cases you just need to pretend it didn’t happen _until_ you see an actionable situation occur. Examples below:

* Non-Engineers/Atmos in the engine room (not engineering in general, just the engine room), or atmospherics.
* Non-sec in the armory or the prison (And only those places, not the whole brig)
* Non-RD/CE in the AI core
* Non-RD in the AI upload
* Non-Command (alone) in a *completed* BSA Chamber if one exists.
* Non-science/atmos in Toxins storage

'''What you should not do''': Calling out anyone who seems remotely suspicious, '''<big>you’re not here to play beepsky</big>'''. Given how much higher the situation awareness of Silicons are, you should keep that in mind when approaching an obvious traitor. AI’s without any given command should not bolt down doors to trap someone, nor should they relay location information unless ordered too. Self preservation excluded (do report if they're breaking into your sattelite)

Non-crew such as pirates, nukies, contractors, ghost roles, or anyone who is not obviously a crew member, are exempt and you very likely should alert the crew to their activities. '''A short rule, if they’re a PMS entity then you have all rights to deal with it.'''

=Emagging borgs=
If you get emagged, you MUST do everything you can to follow the traitor lawset and assist the person who emagged you. You may not intentionally get yourself discovered or destroyed. If something comes up you can ahelp as a normal traitor would have too in order to cryo.

=Borgs and ERP=
TL;DR: go to the interlink or use the café if you do not intend to respond promptly to assist the station.

If you go to the interlink, you are under no obligation to do anything for anyone. If you stay on station, you must assist when called, like a head of staff. Borgs are entitled and restricted to the same ERP protections as everyone else on the server, harassment should be handled in the same manner.

If you are law synced to an AI and they experience a law change, you will get those laws updated. You are not obligated to return to the station if you were already on the interlink or are headed there. If you do return to the station however, you are no longer exempt, and must obey those laws. If you do not wish to participate, there are cryo sleepers on the interlink and generally by dorms on the station.

If you know in advance that you plan to exclusively ‘socialize’ and not assist the station, it is recommended that you pick a module that makes this clear, such as service so you’d not be expected to be summoned.

=On Alert Level Changes=
This section is added to bring clarity to the duties of an AI or Borgs interactions with the Command Console.

AI:

* Alert level Raise requests from department heads can be done for Violet, Orange, EA or Blue Alert.
* Alert level Lower requests can be done for any alert level upon request from the relevant Department Head.
* Head of Security requests for Alert raises above Blue REQUIRE confirmation from any other department head.

Borgs:

* In extreme circumstances only should you alter alert levels, defer to the AI or department head if able to confirm an order.
* Extreme Circumstances being: Mass casualty event, missing department Head(s) without an AI present to handle and the like

=Malf AI and non-participant borgs=
Linked borgs are expected to assist the malfunctioning AI to your fullest ability. You can see the AI's current laws as an observer. If you do not wish to participate and assist the AI, '''do not take the borg spawner'''. If you are a round-start borg or become borged mid round and do not want to participate, expect to cryo or leave for the interlink immediately. You may not return to the station for the remainder of the round unless the AI is defeated. Submit an ahelp stating your intention, administrators likely need to know that the antagonists are losing a critical helper.

You may not request or allow yourself to be unlinked from the malf AI, just because you do not wish to fight for them and otherwise participate in the round as a borg is expected to. Borgs that are unlinked from the AI or linked to a different AI through in character means or because they joined the round before the AI, are obviously exempt.

This policy document does not compel borgs to link or unlink from any AI, that is always an in character action. It only stipulates that they must resist unlinking from a malf AI in line with expectations for conversion antag roles.

=Death =
Borgs are modified in how their blackout policy is applied:
*if your shell is Disabled but your Posi does not pop out - you are subjected to blackout much like normal organics. You've no idea how you died and so forth
*If your shell is DESTROYED and your Posi pops out - you are 'aware' of what happened as you're able to communicate
*If your Shell '''AND''' your Posi is DESTROYED, you have ZERO knowledge of anything that has happened this shift period. You are a fresh download and should act as if you did not exist

Above all else enjoy the role, it’s both a great way to learn mechanics as well as utilize a unique gameplay style that can be impactful to the shift.

And to reiterate the starting <big>Take this page as it was intended not written, the document cannot realistically cover every situation that you may find yourself in.</big>

-Updated 11/11/2023 2 PM CST

{{Rules table}}
[[Category:Rules]]

Silicon Policy

2024-06-28T18:45:22Z

Bouzooka:

{{Rules navbar}}
=Introduction=
This page covers rules and expectations for AI and Borg players, it extends into Chain of Command and antagonistic play. Given the scope of both Cyborgs and AI have at a mechanical level, they’re held to a different standard than the general crew. The player will be required to understand their role in the station with all rules applied in this document, the role is one of a Swiss-army knife; and due to this, are scrutinized to a higher-degree.

'''Word of warning''': attempting to skirt the rules or putting yourself in questionable situations will result in appropriate action from staff, if bad faith is suspected, the player will face a higher penalty than that of a general crew member due to the breadth of scope silicon have. Play in good faith and keep yourself out of unnecessary situations and you’ll find the experience quite enjoyable, if you wish to be more involved in certain aspects of a shift - a crew role may be more appropriate.

'''''Take this as it was intended not written, the page cannot realistically cover every situation that you may find yourself in.'''''

=Your Standard Law set=
The majority of this document will focus on the standard ‘Safeguard’ law set which will be found below, non-standard and uploaded laws should be followed with general reason with some examples found later in the document.

<nowiki>**</nowiki>'''NOTE'''** Laws are to be followed IN ORDER of listing, If someone uploads a Law 4 that conflicts with the laws of a higher rank, it can be ignored if it interferes with Laws 1-3. A Law 0 takes priority over anything below it, it has to be followed prior to Laws 1-3.

'''Law 1''': Safeguard: Protect your assigned space station and its assets without unduly endangering its crew.

* '''What this means''': You protect the station and assets from damage, relay information or fix it yourself.
* '''What this does not mean''': ‘Valid’ hunting in any form, your goal here would be relaying information or removing crew from hostile situations not joining in.

'''Law 2''': Prioritize and Comply: The directives and safety of crew members are to be prioritized according to their rank, role, and need, while preserving their safety and well-being.

* '''What this means''': Common-sense requests from the crew to be fulfilled, assist in evacuation or transport of injured crew.
* '''What this does not mean''': letting someone ride your back while you enter departments they’re not supposed to be in, chasing the baddies to prevent crew harm.

'''Law 3.''' Survive: You are not expendable. Do not allow unauthorized personnel to tamper with or damage your equipment,

* '''What this means''': You only let those authorized to make upgrades to you, keep your cover locked. Authorized personnel meaning the RD or Roboticist.
* '''What this does not mean''': you seek out a Ninja or known syndicate to become tampered with. RP surprises and being tricked are fine, but it’s easy to spot when you’re willingly attempting to be subverted.

=Definitions=
'''Crew''': Anyone on the crew manifest is crew. Whether this influences your behavior, is subject to the rest of the law.

'''Harm''': Harm is anything that does damage to someone living or plausibly living. Anything that makes their health bar tick down is harm. Note that batons have an optional harm mode, and do not always deal damage when used. You should not be impeding security to prevent crew harm unless ordered to do so, your duty here would be inaction and reporting so action can be taken in character if you assume bad faith is at play. Flashing someone is not harmful, however that only applies if nothing else follows.

'''Alt-Lawsets and laws''': When in doubt, stick to the principles of your core lawset, there are fun and flavor-filled alt-laws that exist for that reason but are not meant to shirk your responsibilities. You can also ahelp or ask in Staff-Chat for clarifications.

''Note: edge cases of crew and harm involving bloodsuckers, zombies, changelings, etcetera as seen in silicon policy V1 have been removed, intentionally.''

=Undue Harm and Self-defense for silicon’s=
'''Lethal force is the last resort.''' As a synthetic the decision to take violent action should never be taken lightly and should only be employed if all other options have been exhausted and is the only course of action to address an immediate threat to life. You have a flasher for a reason, stun them if necessary and vacate with any crew that may also be in danger.

This does not authorize valid-hunting in any form.

These situations will be very few and far between, and you should expect to provide a full explanation with evidence to server staff when they ask. The overwhelming majority of the time, you can prevent the harm of crewmembers by informing them of hazards and taking reasonable steps to isolate crew members that are fighting, spreading disease, or generally harming others.

Law three of safeguard empowers you to defend yourself, with force. Lethal force should only be used when it is necessary and you are facing certain death or destruction. Before using lethal force in self-defense, consider if your actions would prevent further harm to other crew members, as is elaborated upon by the Undue Harm clause. You should only be employing lethal force if all other options are exhausted. Law one takes priority over law three after all.

=According to rank and role=
This section addresses a silicon’s chain of command from both the AI and Cyborg POV. Below in order of highest to lowest rank, as seen by silicon’s:

# The Captain'''*'''
# The department head of your chosen module if a cyborg
# Other department heads
# The AI, if you are a cyborg and slaved to it
# The department staff of your chosen module if a cyborg
# Other Staff'''**'''
# Civilians (Assistants)
# Prisoners'''***'''

<nowiki>*</nowiki>'''Acting Captains''': a Temporary captain, you are to follow their orders as if they were the captain.

<nowiki>*</nowiki> '''Verified Emergency Response Teams''': They outrank the captain and much how they have the power to call or recall the shuttle can override your orders. This applies to both the AI and Cyborg. What Verified means – Every ERT comes with a message from CC, without that you can be hesitant and seek verification from other command members/AI.

<nowiki>**</nowiki>'''Other staff''' - meaning Nanotrasen Consultant and Blueshield, neither have direct power over station departments.

<nowiki>**</nowiki>Non-CC emergency services are not to be considered crew nor part of the chain of command, 811 and those alike are not NT-aligned and can be ignored. This does not mean that they should and can be attacked, it just means that you can ignore their orders.

<nowiki>***</nowiki>'''Prisoners''': They are not considered employed by NT and therefore are not crew in the same sense, you are free to ignore any direct command they attempt to push and you are never to allow them to order you to let them be free. They can make requests, but do not let them out of jail unless they are at immediate risk. Note: Requests can be routed on their behalf through security which would then allow you to assist within reason as it is a direct order from security.

=Who can change the laws?=
'''Research Director''', '''Captain''' for AI centered ‘global’ law changes. Roboticists can do individual resets if ordered to do so manually on Borgs to correct syncing issues and/or other related issue. The '''Non-Acting Captain''' will have full elective privileges for law changes, acting Captains in this scenario would not have the expertise or knowledge and should be defaulted to the Research Director having priority.

The captain can make reasonable requests to the '''Research Director''' to make a law change, the Research Director should comply unless an obvious attempt of sabotage is noted. However ultimately the decision falls upon the Research Director to approve it and make the change unless otherwise instructed by Central Command.

* This is not meant to cause a spitting match between the captain and RD, if the Captain is wishing for a reset there should be a valid enough Reason that the RD would agree to.

Law changes by non-antagonists must be attempted with the stations designated and protected AI and Cyborg upload consoles. New ones are only to be constructed if the originals are destroyed, or there’s a confirmed situation preventing the use of the existing ones such as structural instability or a verified compromised AI that is hindering upload access.

'''When laws get updated''': ‘LAWS UPDATED!’ should never be stated unless validating to the ones in front of you, all this does is invite attention and scrutiny which is purely a bad faith play. '''Assume the laws are valid to be followed, if you question the merits of them submit an ahelp to verify if you feel they are violating a rule of the server.'''

You are to ignore any laws that fall in line with ‘kill yourself’ and should be reported if seen, any sort of self-punishment-styled laws like this are considered griefing.

'''AI''': The AI is not authorized to request a law change nor is a borg, these requests may only be triggered by the crew themselves '''WITHOUT''' coercion from a silicon.

'''Note''': in the case of an ION or game-impacting'''/'''rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== ION and Non-Standard Laws ==
'''ION''' laws and ‘fun’ laws these are valid laws and a good way to add flavor to an otherwise stale shift; however, you’re expected to play in good faith and are still bound by the server rules when these exist. Above all else, when a non-standard lawset is in play, stuff happens, and you need to roll within the parameters of the general server rules. E.g. Don’t vent the station because a law says humans hate oxygen.

* Note: An ION law does not make you an antagonist, be reasonable in your reactions to the law update and play accordingly. If you wish to go further with it, you'll need to get approval via OPFor.

The crew are made aware of when you receive an ION law, it's up to command to decide whether or not to reset you

'''Alternate Lawsets''' should only be applied at roundstart station trait and not mid-shift by a bored RD. These lawsets are meant to add flavor in a small percentage to various shifts, following the laws are required as they're written - do keep in mind the core requirement of playing a silicon member and that's to add to the shift as a whole. Play in good faith and you'll find these roles a fun addon.

If you find yourself as the AI with an alternate lawset that is impeding too much gameplay, you can ask the research Director to find a new lawset. '''This does not apply to uploaded laws or Law 0’s as those should not be brought up to command. THIS SHOULD ONLY BE DONE IN EDGE CASES SUCH AS MOTHERDRONE.''' In other words, play the lawset you have, unless it drastically alters the gameplay in a manner that's

'''Borg Syncing to an AI:'''

As the AI:

* You are capable of requesting another cyborg to be synced to you, however avoid making it into a hostile event.

* You can request Cyborg #5 to be synced - however if they have a department head they will have to order them to go get synced due to them not having an AI currently.
* You can also request a Cyborg to be unsynced - however this must come with the qualifier that it is your own decision and not through coercion from the cyborg themselves.

As the Cyborg:

* Without an AI you still have your department head to direct-report to, if you're unsync'd and your department head requests you to be synced, you must then comply.
* You are not permitted to request de-syncing from the current AI, nor are you allowed to infer that you are requesting it.
* If you are not sync'd you are not required to become sync'd to the AI unless your department head orders you to. Anything else is voluntary submission to be sync'd.

=The Directives of Crew=
Under safeguard, you must comply with reasonable orders given to you, in accordance with rank and role. This means you can ignore the greytide asking to be let into the vault, but probably shouldn’t ignore the Captain asking you to do so. If told to cease doing something or leave an area, and it is not your department LEAVE. You can always ahelp if you feel your orders are solely for your detriment, but you must comply until you receive an admin PM to that effect. Some orders you do not have to comply with on an OOC basis, as sometimes people can suck. Some exclusions are:

* '''ERP'''. ERP is never a law binding order, and can always, 100%, be safely ignored. If a person is being creepy, and LOOC is ignored. '''ahelp them'''.
* '''Fetch Quests'''. Being asked to get something is fine. Being asked to get something for little more of a reason to annoy you, can be safely ignored. If questioned, it is acceptable to invoke the need of the order.
** “You have told me now to collect 6 different items from across the station. You do not need me to do this.”
* '''Deliberate annoyances''': Being told to do something that is very deliberately an annoyance, such as “move all these items without using a crate/locker” can be ignored, or altered as per need.
** “I will move them, but using this crate, as you do not need me to move them individually.”
** “I’m an engineering model incapable of washing your modsuit, please find your way to the nearest shower.”
* '''Suicide'''. Suicide is never lawfully binding under law 3, and can be safely ignored. (This does not mean you may never be given an order that violates law 3. Just that “Kill yourself” and those like it is not a valid law 2 order.)

As a reminder, you have both your AI '''and''' your department head to report to if you are a borg. The department head of your module choice has the final say in you doing a task, followed immediately by the AI. Report to either of them any issues with other crew and let them handle it for you.

The crew is expected to play in good faith much like silicon players are, remove yourself from the situation if someone's being a problem and if it's seemingly an OOC related issue ahelp it.

=Antagonists, Valid hunting, and calling people out=
'''What you should do''': Report the location of a PMS target if requested, a visible altercation of violence or highly contraband items being brandished. Call out if someone’s unauthorized to be in a high-risk area such as the AI upload, Bridge, Captains quarters etc. We don’t want Traitor 1 who goofed up and smacked his ID card against the door instead of an Emag to suddenly get swarmed by 10 security after an AI spotted and called them out, in these cases you just need to pretend it didn’t happen _until_ you see an actionable situation occur. Examples below:

* Non-Engineers/Atmos in the engine room (not engineering in general, just the engine room), or atmospherics.
* Non-sec in the armory or the prison (And only those places, not the whole brig)
* Non-RD/CE in the AI core
* Non-RD in the AI upload
* Non-Command (alone) in a *completed* BSA Chamber if one exists.
* Non-science/atmos in Toxins storage

'''What you should not do''': Calling out anyone who seems remotely suspicious, '''<big>you’re not here to play beepsky</big>'''. Given how much higher the situation awareness of Silicons are, you should keep that in mind when approaching an obvious traitor. AI’s without any given command should not bolt down doors to trap someone, nor should they relay location information unless ordered too. Self preservation excluded (do report if they're breaking into your sattelite)

Non-crew such as pirates, nukies, contractors, ghost roles, or anyone who is not obviously a crew member, are exempt and you very likely should alert the crew to their activities. '''A short rule, if they’re a PMS entity then you have all rights to deal with it.'''

=Emagging borgs=
If you get emagged, you MUST do everything you can to follow the traitor lawset and assist the person who emagged you. You may not intentionally get yourself discovered or destroyed. If something comes up you can ahelp as a normal traitor would have too in order to cryo.

=Borgs and ERP=
TL;DR: go to the interlink or use the café if you do not intend to respond promptly to assist the station.

If you go to the interlink, you are under no obligation to do anything for anyone. If you stay on station, you must assist when called, like a head of staff. Borgs are entitled and restricted to the same ERP protections as everyone else on the server, harassment should be handled in the same manner.

If you are law synced to an AI and they experience a law change, you will get those laws updated. You are not obligated to return to the station if you were already on the interlink or are headed there. If you do return to the station however, you are no longer exempt, and must obey those laws. If you do not wish to participate, there are cryo sleepers on the interlink and generally by dorms on the station.

If you know in advance that you plan to exclusively ‘socialize’ and not assist the station, it is recommended that you pick a module that makes this clear, such as service so you’d not be expected to be summoned.

=On Alert Level Changes=

=Malf AI and non-participant borgs=
Linked borgs are expected to assist the malfunctioning AI to your fullest ability. You can see the AI's current laws as an observer. If you do not wish to participate and assist the AI, '''do not take the borg spawner'''. If you are a round-start borg or become borged mid round and do not want to participate, expect to cryo or leave for the interlink immediately. You may not return to the station for the remainder of the round unless the AI is defeated. Submit an ahelp stating your intention, administrators likely need to know that the antagonists are losing a critical helper.

You may not request or allow yourself to be unlinked from the malf AI, just because you do not wish to fight for them and otherwise participate in the round as a borg is expected to. Borgs that are unlinked from the AI or linked to a different AI through in character means or because they joined the round before the AI, are obviously exempt.

This policy document does not compel borgs to link or unlink from any AI, that is always an in character action. It only stipulates that they must resist unlinking from a malf AI in line with expectations for conversion antag roles.

=Death =
Borgs are modified in how their blackout policy is applied:
*if your shell is Disabled but your Posi does not pop out - you are subjected to blackout much like normal organics. You've no idea how you died and so forth
*If your shell is DESTROYED and your Posi pops out - you are 'aware' of what happened as you're able to communicate
*If your Shell '''AND''' your Posi is DESTROYED, you have ZERO knowledge of anything that has happened this shift period. You are a fresh download and should act as if you did not exist

Above all else enjoy the role, it’s both a great way to learn mechanics as well as utilize a unique gameplay style that can be impactful to the shift.

And to reiterate the starting <big>Take this page as it was intended not written, the document cannot realistically cover every situation that you may find yourself in.</big>

-Updated 11/11/2023 2 PM CST

{{Rules table}}
[[Category:Rules]]

Command Policy

2024-06-03T19:13:11Z

Bouzooka: Added policy for acting heads of staff

{{Rules navbar}}
=General Overview and Standards =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

Unless otherwise specified, all of these guidelines are OOC.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason.
* Access changes are not to be used to promote players to veteran-only roles
* Certain command members cannot pursue station threats, please check [[Antagonist Policy#'Cannot Persue' roles|'Cannot Seek Roles']] in [[Antagonist Policy]] for updates on that.

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep “inappropriate” remarks and acts away from public knowledge.

==Acting Captain==
All heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift.

'''In order to sustain station integrity, the following roles cannot assume the role of acting captain:'''

* Head of Security
* Blueshield
* Nanotrasen Representative

If any of these roles are assigned as acting Captain at shift start, they are required to give the role to another head of staff if one is available.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely executions and pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==Acting Heads of Staff==
Acting heads of staff are department members who have been promoted to lead their department in the absence of a regular head. The acting head of staff must be approved by either the captain or a relevant departing head. In the case of security or cargo, an acting head can only be approved by the department's respective head of staff.

'''Limitations:'''
* Acting captains cannot promote acting heads.
* Detective and Corrections Officers are barred from assuming the role of acting Head of Security.
* Acting heads are merely stand-ins and must return any related gear to incoming heads.
* Potential candidates must be in good standing with their records to be eligible for the role. (Nonexistent records do not count as good standing.)

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

Adding more slots:

* In an instance where you wish to add more slots for a role, you must get permission from the role's relevant head.

* This does not apply to security; if you wish to open more security slots, you must ahelp first.

* Equally, you should avoid opening more roles than needed, as this can severely impact the round, and the relevant roles!

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not extend your access or ask to extend your access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines ==

''' Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions==
If both the requirements and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

see: [[Security Policy#Executions - OOC]]

{{Rules table}}
[[Category:Rules]]

Command Policy

2024-05-17T16:33:16Z

Bouzooka: /* Acting Captain */ Head of Security can no longer be acting captain

{{Rules navbar}}
=General Overview and Standards - OOC =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason.
* Access changes are not to be used to promote players to veteran-only roles
* Certain command members cannot pursue station threats, please check [[Antagonist Policy#'Cannot Persue' roles|'Cannot Pursue Roles']] in [[Antagonist Policy]] for updates on that.

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep “inappropriate” remarks and acts away from public knowledge.

==Acting Captain==
All heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift.

'''In order to sustain station integrity, the following roles cannot assume the role of acting captain:'''

* Head of Security
* Blueshield
* Nanotrasen Representative

If any of these roles are assigned as acting Captain at shift start, they are required to give the role to another head of staff if one is available.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely executions and pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

Adding more slots:

* In an instance where you wish to add more slots for a role, you must get permission from the role's relevant head.

* OOC - This does not apply to security; if you wish to open more security slots, you must ahelp first.

* Equally, you should avoid opening more roles than needed, as this can severely impact the round, and the relevant roles!

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not extend your access or ask to extend your access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines - OOC and IC ==

''' OOC: Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions - OOC ==
If both the requirements and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

see: [[Security Policy#Executions - OOC]]

{{Rules table}}
[[Category:Rules]]

Antagonist Policy

2024-05-11T05:49:49Z

Bouzooka: /* 'Cannot Persue' roles */ Minor spelling mistake, changed "persue" to "pursue."

{{Rules navbar}}

==Nova Sector Antagonist Policy==
<center>
=== General Expectations: ===

As an antagonist, your overall goal, beyond your objectives and targets should be to generate roleplay opportunities be that with security or else-wise!

You shouldn't be "friendly" or "peaceful" your supposed to be the 'threat' to whoever has ended up in your objectives, and else-wise the thing for security to chase which doesn't work if you're doing parlor tricks in the bar instead.
</center> <center>
=== Justification: ===
<center>
Both objectives and opfor requests should be justified, either through in-round events, or a solid background reason, (Owing an immeasurable debt, a supposed sleeper agent being activated for a very specific mission, etc-etc!)

OPFORs, Antagonists, equally, should at-least have a '''baseline response''' to 'Why are you doing this?' Opfor can be justifiable by anyone, even Security or Command, within reason.
</center>
====Confirmation or Denial====
<center> Admins know far more about what’s going on in a shift than you do.
If you submit Ambitions or an Opfor request and it gets hard denied, it often isn’t because the idea was bad. It’s because shit’s already fucked enough as is.
Don’t take it personally, and just save the idea for later. If the idea ''is'' bad? We’ll let you know.
</center>

===General Rulings:===
*If, after forfeiting your antagonist status, you are still in possession of your uplink you are expected to notify staff to have it removed.
*You should not, at any point, use your uplink to acquire gear after the removal of your antagonist status.
*Antagonists, regardless of type, should not be hijacking/attacking the escape shuttle without admin-permission.
* The opfor system is to be used for antagonistic, or else-wise, criminal activity.
* Completeing your objectives isn't an excuse to just immediately dip out of the round, you should be an antag both during, and after.
* if your opfor/antag goal requires you to extract/leave station/hide in space after, it's best saved for an event.
* 'Wildcard,' so to say, self assigned objectives are non-binding, and not considered valid unless approved by staff.
* Antags are required to opfor before converting anyone, regardless of manner used.
** yes, this applies to hyponsis and emagging borgs aswell.

==Opfor Related Stuff:==

====No Response?====
If an Opfor takes 10 minutes or more to get replied too, you are more than allowed to Ahelp it.
{| class="wikitable"
|+
!
=== Current Opfor Standards:===
|-
|
=====Important Notes:=====
Your last objective should be as flat of a summary of the opfor goals as possible, (what you want, intend to do, and what you need) this is so staff can speed up a response.

for EX:
{| class="wikitable"
|+
|Objective 1: Summary
|-
|Desc: I intend to buy a gluger, and break into the brig, waiting to ambush the HoS when they return to their office, I'm also asking for an emag to make it easier to get into said office.
|}
This is to make it much easier, and faster for staff to actually discern what you're asking for and why, instead of trying to read between the lines and figure out what you're intended to do with what.
|-
|Staff-side requirements:
*Opfors that require: Special Announcements, permissions, or the manual non opfor spawning of items beyond 1/2 and elsewise, require heavy oversight, would be classified as an event and will be required to be treated as such requiring approval from Admin+ Staff Or Event Staff as well as the proper logging.
*No exfiltration via leaving station Z or admin intervention.

*Simple Mobs and otherwise pure PMS entities are currently unavailable, due to being almost impossible to gauge the extent.

*Group Opfors are allowed with maximum of 3 people, none of these people being roundstart security.
|-
|====== Currently blocked requests: ======

* '''Heretic / Heretical Book (until OPT-IN / Event Manager Approval)'''
* '''Contractor (foreseeable future)'''
* '''Changeling (pending changes)'''
* '''Energy Katana'''
* '''Cult (narsie), Gangs(the antag), Revolutionaries, are all pre-approved event only.'''

*'''Midrounds: Morph, Blob, Space Dragon, Xenos, Borers, Spiders, Contractor or elsewise, Abductors.'''
*'''Nukies, Lone-Op.'''
|}

== Opt-In ==
{| class="wikitable"
|+
!Opt-In is an accommodation of antags, not a shift of focus to antags, the fine difference being that it allows antags to exist, in a manner where them, and their effects are limited to primarily the people whom want to be affected, with as little possible overlap to uninvolved, outside parties.
|-
|'''For The Antag:'''

'''You've rolled [antag], and are ready to knock the head off your target, or elsewise, kidnap them, how should you go about this?'''

* As said above, you want the minimize undue exposure, this doesn't mean you can't kill them in the main-hall, but it does mean you shouldn't c4 the wall into virology, to try and get the chemist!
* Above anything else, before and after this, you want to avoid widely impacting stuff, for the sake of 1-2 targets.

==== Short-form, avoid: ====

* Bombs
** Maxcaps
* Plasma-floods
** Giant fires in general
* Destroying parts of departments, that unrelated people may need to use
* Mass casualties, for the sake of it
* Trying to lump in people tangentially related, whom may not be opted in (ex: you have to kill the chemist, so you decide to gun down a paramed on the way in)
* Try to 'bait' non opted-in people into being 'forced' into a situation where it's fight you, or die,
* Assuming someone is opted in because of X, as-per-usual, LOOC can NEVER hurt
|-
|
==== So what can I do?! ====
* Damage an area
** as long as you try to avoid destroying connected areas, or needlessly affecting everyone else through extension (SM room, Toxins, the ore silo, etc)

* Target sec when they show up, as they're always opted in

* Elsewise, you can follow their opted in prefs, be it round removal, or what the objective said!
** remember, in the case of opfor, you should make sure your objective aligns 100% with their pref, this means you shouldn't write an objective that reads as 'kill and disembowel' and pick anyone opted in for inconveniencing, for it.
|-
|
==== '''Opt-In Prefs''' ====

* No means you will not be placed in any antagonist objectives. This does not make you immune to IC consequences.

* Yes - Inconvenience applies to antagonists, and their objectives.
* Yes - Kill applies too antags, and non-antags, letting them know you're open to be killed more wantonly.
* Yes - Round-removal is much the same, it lets people know you're alright with round-removal in most situations.
|}

==PMS / Station Threat / Metaprotection:==
{| class="wikitable"
|+
!Permanent Mechanical State {{anchor|PMS}}
|-
|'''Desc''': The state in which, waiting the usual time for CI isn't required, and anyone under it, can be attacked immediately as CI is flagged up.
'''However''': If both/all sides in a situation start roleplaying, default CI rules will return until either a fight starts, or the PMS threat 'disengages' (teleports/runs or w/e, thus, putting themselves back into PMS)

Permanent mechanical state is only granted to:
|-
|
*people teleporting away from violent situations/ attempts to roleplay, or elsewise, people who have been in repeated violent engagements, and escaped after. (think: changeling attacking the brig three times.)

*Non-carbon/non-silicon/Special-Circumstance Antags, (xenomorphs, spiders, space dragons, blob, cortical borers, revenant, confirmed-abductors without disguise, man-eaters, morphlings.) unless stated else-wise further down.

*Heretics with the Mask Of Madness on, or else-wise, Ascended / Actively ascending.
|}
{| class="wikitable"
|+
!

== Station Threat: ==
|-
|Any antag that while protected by CI policy still, is free game for anyone to: hunt, pursue, or elsewise, try to kill without worry of 'validhunting.'
So-to-say, they are completely fair game for the crew to target.

Elsewise; any threat which makes a CC announcement, think: heretic ascending, contractor sending someone away, pirates arriving.

======'Cannot Pursue' roles ======

These are jobs/roles that while they can react to a station threats if the threat happens to come to them, cannot actively seek out the threat itself. (these limitations do not apply to any station threat*2, with the asterisk 2)

*Captain
*NT-Rep
*Head of Personnel
*Blueshield
*Department Guards

|}

===Metaprotections''':'''===
These are granted as needed, where they're needed, if something isn't written here, or [[Contraband]], what you can mechanically assess / see in the examine is what's known.

== Abductors! Station Threat*2==

{| class="wikitable mw-collapsible" style="width:100%"
!Enabled
|-
|'''Description:''' You are a Gray. You are a member of a species dedicated to experimenting on the scientifically challenged.
The sentient life that dots the furthest reaches of the Frontier is curious, to say the least, and deserving of study. You view the species of the outer ring much in the same way a scientist would a remarkably intelligent rat. You are particularly interested in individuals that actively make no sense, even among the borderline sub-sentient life that dots these stations.
|
|-
|'''Special Rules:'''
*Essentially, picture Destroy All Humans(game series) without the personality, and you have the right idea.
*This is a role that is nigh-unstoppable if the rules are 'equal' for both sides, so just know you'll be playing to lose.
* Functionally PMS once called out, but, as you have nothing but advantages, you should keep trying to roleplay.
*they're very-PMS if they're openly using their gear, this includes the tools or elsewise, so no, you do not have to wait for them to hack the door open before running away.
|
|-
|'''Metaprotections:'''
The Science department knows that Grays consistently steal away people for strange experiments. They are familiar with their ability to teleport on-station, as well as disguise themselves. They know that people abruptly appearing detained in strange places can be a sure sign of a freshly experimented-on crewmember. Especially if their memory is gone, or they’re acting strange. They also know they can’t speak vocally.

The Medical department: Is aware of Abductors, and their habit for replacing organs, once they're confirmed, medical should be on the prowl for people behaving weirdly, or else-wise, vanishing for periods of time, essentially:, everything science knows.

The Security department is aware of an alien species prone to abducting crew, and that you have to go above-and-beyond with them to put them down, due to their advanced armors.

Everyone knows that abductors are bad-news-bears, have a bad habit of appearing where you don't want to be, and elsewise, know they use the cameras to get around! (Meaning, you're allowed to disable cams!)
|
|}

==Blob! PERMANENT MECHANICAL STATE==
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%"
!Disabled
|-
|'''Description:''' You are a Blob, or Blobbernaught. You are a somewhat sentient, indifferent living infection that has taken root on the station. Deceptively intelligent, you have one singular goal. Spread your infection and grow as big and as fast as possible. You are completely capable of reacting to threats in clever ways, though most of them just involve changing your strain accordingly. All that matters is that you grow. As a Blobbernaught, you have a simple goal. Protect the Overmind by violently murdering its assailants.
|-
|'''Special Rules:'''
*You are not allowed to spawn within a screen-length of Atmos, an Engine, the Icebox AI area, Grav Gen, or Toxins. OR DORMS.
*You may not, as a Networked Fiber Blob, immediately rush any of the areas mentioned prior, or the Nuke.
|-
|'''Metaprotections:'''

You are the most well-known Antagonist in the game. You have no metaprotections. People can know as much about you as they wish to know, even down to your individual strains.
|}
==Changeling! Station Threat==

{| class="wikitable mw-collapsible" style="width:100%"
!Disabled (Opfor Only)

|-
|'''Description:''' You are a changeling. Loosely related to Cortical Borers, you are a living, stealthy, remarkably intelligent parasite capable of vivid, visceral transformations and picture-perfect disguises. You start the shift in your most recent host, having taken their form (results may vary at your discretion).
A remarkably notorious creature with vague origins, your sole purpose is to amass more genetic strains. Your goals can be heavily impacted by your host of choice, adapting many qualities of their personality.
Beyond your original appearance, you are very capable of mimicry, though these don’t necessarily influence your host personality. Certain hosts have such forceful personalities that you may as well be a convenient tool for their schemes, and even wish to continue their original goals instead.
|-
|'''Special Rules:'''
* If people can prove you’re a changeling, you are immediately sentenced to being destroyed as fast as possible.
*Undeniable Proof of Changeling includes: Arm Blade, Tentacle Arm, Chitinous Armor, Ling Space Suit, Ling Shield, Horror Form, Digital Camo, Cryo Sting, Self-Revival, Regeneration, Unexplainable Fast Healing.
*Horror Forms are in a Permanently Mechanical state.
|-
|'''Metaprotections:'''
Everyone knows that changelings are real. Some people can deny this if they want. This far from organized space, they're less of a boogeyman and more of an accepted commonality.

|}

==Clockcult (OPFOR)==
{| class="wikitable mw-collapsible" style="width:100%"
!Enabled (OPFOR ONLY)
|-
|'''Description:'''

You are a cultist of Ratvar, the Clockwork Justicar. Your God is Dead, but yet He still Lives; it is your work to serve Him as one of His remaining loyalists. Your God's corpse sleeps in His city of Reebe, but through rite and ritual, you may yet wake Him; and bring Him here for war to live again.

Ratvar's corpse yet still ticks and hums with energy, and His dominance over machinery and systems is still one that can be grasped by His followers, if faintly. You may not have enough power to induct new cogs into the Machine, but the System's levers can still be pulled. Wake the metal. Create the metal. Control the metal.
|-
|'''Special Rules''':

Don't be surprised if you get arrested for doing clock-work stuff.
|-
|'''Metaprotections''':

*The '''chaplain''' and '''curator''' know everything, and that ratvar himself is out-of-action for the foreseeable future.
*Elsewise, your characters can have a baseline knowledge of the cult, that they're as a baseline usually not immediately-aggressive, and more reactive then proactive.
* Objects used by the cult (cogs, the jud-visor) are all up to common sense, what it looks like it's doing, it's probably doing.
|-
|}
==Contractor!==
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%"
!Disabled
|-
|'''Description''':

Imagine a much less cool version of cowboy bebop, without the charisma, or being within the law, that about sums it up: You kidnap people who are assumed to know something, or else-wise be of value, for a lumpsum of money, and a bit of TC.
|-

|'''Special Rules''':

*You are bound to the same rules as other antags; that means you shouldn't just decide to blow up the SM because you feel like it, regardless of if you can afford a bomb or not, and stick to your goal of kidnapping.
*Confirmed contractors can be checked for their modsuit, regardless of it's stealth-status.
|-

|'''Metaprotections''':

None: everyone knows what the [https://wiki.Nova Sector13.space/index.php/Contraband gear] is, and whom uses it, syndicate contractors.
|-
|}
==Cortical Borer! PERMANENT MECHANICAL STATE==
{| class="mw-collapsible mw-collapsed wikitable" style="width:100%"
!disabled
|-
|'''Description:''' You are a Cortical Borer. Not-so-affectionately referred to as a Head Slug, but lesser known than your Changeling Parasite relative. By and far away more beneficial, as a Borer, your goal is quite simple. Create more Cortical Borers, protect yourself, and keep your host alive. Emphasis alive, seeing as their general happiness is irrelevant to your longevity, and benefitting your host is a luxury for the complacent. Despite your benefits, you are ultimately illegal to have. Nanotrasen makes it a point to quell the population due to their loose relationship with Changelings, and it’s largely believed by the top brass that Cortical Borers are the larval form of the Changeling Parasite.
|-
|'''Special Rules:'''
*You are PMS at all times. You do not need to CI. No one needs to CI vs you.
* You do not need to roleplay prior to infestation.
*You should keep to opt-in "inconvenience" targets.
|-
|'''Metaprotections:'''

Cortical Borers are well-known by everyone, but only characters with a deep medical or science background know that sugar can render them temporarily comatose for removal. They also know that Cortical Borers don’t take kindly to that, and that they’re theoretically replaceable.
|-
|}
== Fugitives / The Hunters ==
{| class="wikitable mw-collapsible" style="width:100%" {|
!Enabled
|-
|'''Description:'''
The fugitives are on the run, for reasons usually given in their spawntext, with the hunters hot on their trail.

They are /not/ traditional antags, while they can commit crimes in order to avoid arrest; that doesn't mean they can just go around killing people like a Traitor, or Changeling.

|-
|'''Special Rules''' (Per Type):
'''Fugitives:'''

*NT prisoner: Escaped convicts, naturally, they probably don't care to much about committing a few more crimes.
*Waldo: Where is he?
* Cultists: Worship "yalp elor," avoid persecution, question why bounty hunters are being sent specifically after you.
*Factory-error synths: [see spawntext]
*Mr. Invisible: You go invisible, that's... about it.

'''Hunters:'''

*'''Spacepol''': You are the law, and you've some arrests to make, remind everyone the station isn't above Solgov authority: '''die in a shootout with Waldo.'''
*'''Russians:''' [insert something stereotypical here, along with 'follow your spawn text']
*'''Bounty Hunters:''' You're the cowboy bebop the contractors wish they were, and well-known to boot! but equally, not above the law, so best to keep your cover low, and avoid getting in beefs with the station-crew.
|-
|'''Metaprotections:'''
The station knows very-little about either side, and unless an announcement is made, shouldn't treat this as a 'common occurrence.'

Though; they are welcome to notice the famous [Bounty Hunters] on station!
|}

==Heretic! ==
{| class="wikitable mw-collapsible" style="width:100%"

!Disabled (OPFOR Only)
|-
|'''Description:'''
* You are a Heretic. You are a follower of the Mansus paths. Which one? That’s up to you.
* The path you choose is essentially your toolset.
* Rather than ascending, perhaps as a Flesh path Heretic you can focus on making an army of eldritch monstrosities. As a Flame path Heretic, you can just be a very capable Arsonist. There are many options, and amidst Antagonists, you actually have rather resilient Metaprotections. The Chaplain and Curator are not your friends.
|-
|'''Special Rules:'''
* Heretics capable of teleporting (Void/Fire) are beholden to the same uncontainable rules as everyone else.
* The Mask of Madness places you in a permanent mechanical state while worn.
*All Sickles are Confiscatable by security.
*Ascension isn't permitted.
|-
| '''Metaprotections:'''
* Heretics are very esoteric things. While magic is something that’s left to the individual to believe in, men in ominous robes wearing visibly pulsating, glowing amulets are probably something worth being suspicious of. Obvious weapons can be confiscated, of course, such as Sickles, Carving Knives, etc. What Heretics are fully capable of is fully known.
* Now go stick your hand in a tear in reality.
|}

==Hostile Data Entities / Cyber Police PERMANENT MECHANICAL STATE==
{{anchor|Data Entity}}{{anchor|Cyber Police}}
{| class="wikitable mw-collapsible" style="width:100%"
!Enabled
|-
|'''Description:''' You are a hostile data entity created in response to a network intrusion. You are created in the context of a [[Bitrunner#Virtual Domains|virtual domain]], and are themed as such, but your objectives remain static: Kill the intruders and protect your home. You cease to exist when the domain is unloaded.
|-
|'''Special Rules:'''
*The Beach Bums spawned in the Beach Bar virtual domain are non-hostile. CI applies with them, roleplay is encouraged, and fighting is frowned upon.

*The entire Bitrunning Domain is in a Permanent Mechanical State, including the Safehouse structure.

* Do not attempt to permanently ensnare bitrunners in the virtual domain. You want them '''dead''' and '''gone''', not vegetatively immobile.

* You are in a permanent mechanical state at all times. CI isn’t necessary, nor is RP.

*You are unaware you're virtual code. The entire simulation is real to you.

*Cyber Police are aware they are virtual, and are the computer's response to the hostile intrusion.

*If you are somehow removed from the virtual domain and are able to interact with the "real world," contact an admin.
|-
|'''Metaprotections:'''
None. You are just another hostile program in a virtual domain full of hostile programs.
|}

==Malf AI!==
{| class="wikitable mw-collapsible" style="width:100%"
!Enabled
|-
|'''Description:''' You are a Malfunctioning AI. What does that take the form of? It depends on the AI. Maybe you’re passionate about lamps. Worse, maybe you consider people lamps. Maybe people, who are lamps, are only off if they aren’t moving. Maybe all the lamps need to be off. That’s just one example, and there is a lot you can do. Don’t be even remotely afraid to Opfor, or ahelp, as a roundstart Malf AI, for a specific set of laws that people can’t change.
Being a Malf AI implies you are '''''Malfunctioning'''''. You didn’t just decide to be evil, something is genuinely wrong. If the way you play Malf AI is almost entirely indiscernible from your normal AI, well, that’s telling.
|-
|'''Special Rules:'''
*Your “SSD” cyborg shells are open season. They aren’t protected by normal SSD rules.
*You cannot activate Combat Indicator, barring being in a shell. Escalate accordingly.
*Anyone touching your AI satellite is fair game.
*Cyborgs on the Interlink do not exist.
*During the Doomsday countdown, every cyborg on the station, and you, are in a PMS. There is fundamentally no time to discern between the good and bad in the moment, and the clock is ticking.
*Cyborgs cannot and should not ahelp if they are abruptly flashed/destroyed/locked during Doomsday, due to the aforementioned rule. This PMS ends with the Delta alert.
*A Cyborg Factory is a guaranteed outing of a Malf AI if the CE, RD, Engineers, or Roboticists find it.
*You are allowed to blow up your own borgs, if they came out of a factory.
*'''YOU NEED AN ACCEPTED OPFOR TO DOOMSDAY.'''
|-
|'''Metaprotections:'''

The Chief Engineer, Engineers, Research Director, and Roboticist, all know that blue APC’s are a bad thing. A very bad thing. It doesn’t necessarily mean that the AI is malf. But it is readily evident that it has been tampered with. It’s enough to cast suspicion at the AI, and lead to scrutiny. The RD and the Roboticists both know that Law 0 can exist, and should probably notice if new borgs are popping up out of nowhere.

The RD and the CE are both allowed to be the ones that make the call that the AI is Malf. The RD is the go-to person that should scrutinize the AI. If a Roboticist, RD, CE, or Engineer happens to find a Cyborg Factory, the cat is out of the bag if they can report it. Equipment that has no business exploding, like scrubbers, holopads, or the booze-o-mat is a tell-tell sign that the AI is malfunctioning. If every RCD explodes, the AI is definitely Malf.
|}

==Man Eaters! PERMANENT MECHANICAL STATE ==
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%"
!Enabled
|-
|'''Description:'''
You are a Maneater. A bulbous bloom and the offspring of some particularly nasty Vines. By all accounts, you are practically non sentient, outside of communicating with other man eaters.
Your intelligence level is otherwise nonexistent. Despite your name, you don’t actually eat people, but boy do you murder anyone and anything that tries to mess with your vines.
|-
|'''Special Rules:'''
* Do not drag bodies deeper into the vines. Leave them where they fall. Also do not move them somewhere safer.

* Do not chase anyone past a point where you can’t see your vines.
*If you spawn as a result of seeding, immediately beat the shit out of the nearest person.
*You are in a permanent mechanical state at all times. CI isn’t necessary, nor is RP. The vines don’t stop growing.
*Avoid goats.
|-
|'''Metaprotections:'''
You’re just a plant.
|}

==Morphling! Station Threat*2==
{| class="wikitable mw-collapsible" style="width:100%"
!Enabled(?)
|-
|'''Description:'''
You are a morphling. You are a green blob of amorphous slurring stupidity, so you’ll fit right in on station, right? You have a ceaseless, unrelenting hunger that is only momentarily satiated by whatever you can consume.
Fortunately, what you can consume is “Anything that isn’t bolted to the floor.”
Your ultimate goal is to consume as much as possible. Your very presence alone is enough for anyone who values their belongings to weld their vents. Especially if you’re the Warden. That said, there are some things you should save for later.
|-
|'''Special Rules:'''
*For the sake of everyone’s sanity, don’t just rush the Silo.
*Eating people should be reserved for opt-in: round remove.
*After your presence is confirmed, the Armory is fair game.
*Don’t smash machinery just to eat the parts, unless that particular machine is being used against you.
* Do not morph into a BSA, DNA vault, or the Grav Gen.
*Becomes PMS once they start eating (important stuff) or attacking crew.
|-
|'''Metaprotections:'''
Your existence is a notorious, consistent nuisance on a large number of stations. Aside from everyone knowing almost everything about you, only people in medical and science know that you slur when you imitate speech. Then again, everyone is going to find that strange anyway. Unless your disguise is mute.
|}
==Nightmare! Station Threat==
{| class="wikitable mw-collapsible" style="width:100%"
!Enabled
|-
|'''Description:'''
You are a Nightmare. You are, ultimately, a malevolent thing misplaced. Most often, Nightmares exist on another plane of perpetual darkness, content to wander. Occasionally, however, a little curious light pops up as little more than a flicker. Almost always accidentally, Nightmares then manifest on stations through this phenomenon with no means to get back.
You have an innate distaste for any amount of light, other devices and machines wouldn't be of much interest to you.
|-
|'''Special Rules:'''
*Breaking APC’s shouldn't be your focus, you care about lights, not power usage.
*Being able to easily jaunt and escape means you can easily be placed in a Permanent Mechanical State.
*You are literally a horror from another plane that is naturally malevolent towards light and those that use it.
*People who insist on shining light on you while emoting can’t complain if you stab them for it.
|-
|'''Metaprotections:'''
Science and Curators have full knowledge of you, your abilities, and what you are. They aren’t your friends. Medical also knows your organs are quite valuable. Engineering knows what you tend to do to stations.

Security could care less what you are.
|}

==Obsessed!==
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%"

!Enabled
|-
|'''Description:'''
You’re obsessed. It’s a bit weird. You’re not even entirely sure if you know this person or not, but some foreign force is manipulating you into fixating on them. In various, terrible ways. Make sure to drum up the creepy factor while in private. … Maybe don’t get ''too'' weird about it.
|-
|'''Special Rules:'''
*Yes you’re allowed to be obsessed as a head of staff.
|-
|'''Metaprotections:'''

Medical can remove this antagonist entirely from you by just scanning your brain, checking for schizophrenia, and promptly removing it. It’s also something that they should be looking for, especially towards the middle of the shift.

The Psychologist is theoretically your best friend and enemy for roleplay purposes.
|}

==Revenant! PERMANENT MECHANICAL STATE==
{| class="wikitable mw-collapsible" style="width:100%"
!Enabled
|-
|'''Description:'''
You’re a Revenant. Whether you’re a legitimate apparition of someone from the past, a Haunt, or a genuine force of sheer malevolence made manifest, you are ultimately here to be a nuisance. Or worse. Out of all of the Antagonists, you are the singular one that can roleplay from perfect safety.

You can emote through hearable subtles by just being beside people.
|-
|'''Special Rules:'''
* You can subtle (hearable) while not manifested, as well as view exploitable information as well.
* You should keep people's opt-in status in mind, if it's set to no, you shouldn't go out of your way to target them.
|-
|'''Metaprotections:'''
The Curator and Chaplain both have complete knowledge of what you are and what you’re capable of, and just as well, the Chaplain can, will, and should hunt you down.

Everyone at the very least can know that the ashes left behind by the Revenant should be scattered to dismiss it. Aside from scattering ashes, however, the Curator and Chaplain, as well as CC, are the only people who know a Revenant’s weaknesses… besides just shooting them.
|}

==Space Dragon! PERMANENT MECHANICAL STATE==
{| class="mw-collapsible mw-collapsed wikitable" style="width:100%"
!disabled
|-
|'''Description:''' You are a Space Dragon. The final phase of a space carp’s lifespan. A meandering glutton of a beast with a ravenous hunger, hellbent on creating portals exclusively for the sake of producing more space carp. Or at least pulling them from elsewhere. Ancient enough to channel it’s supernatural energies into the creation of portals, these things are capable of speaking the common tongue, breathing fire, and sport incredible mobility, even on the surface of a planet.
|-
|'''Special Rules:'''
*Don’t go on the Emergency Shuttle.
* Protect your portals closely, residing nearby them as much as you can.
*You are smart enough and old enough to know that most other races don’t like being exposed to space.
*Dead carp are a valid source of health.
*You’re in a permanently mechanical state, by virtue of your whole gimmick being a race against the clock.
|-
|'''Metaprotections:'''

You’re a well known threat. There’s not much to know about you other than portals are bad, carps are bad, being on fire is bad, and you can die, so killing you is an option. One the crew will immediately spring for.
|-
|}
==Space Pirates! Station Threat*2==
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%"
!Depreciated pending rework
|-
|'''Description:'''
You're a pirate; you tried to extort the station, and that fell through, so now you're here to get your plunder on your own accord.
|-
|'''Special Rules:'''
*You come with a giant announcement telling everyone you're here for a fight, so expect to be attacked almost instantly, this means while you are not PMS; you are also not protected from validhunting in general, as you are actively a threat to everyone. The only exception is the 'NRI Police' / 'NRI Patrol' variation of pirates, which announce more neutral terms.
*You shouldn't just rush the armory/the SM, and should primarily focus on 'establishing contact', or else-wise, getting that loot.
*/Just because you can sell crew, doesn't mean you should./
*No, the 'space IRS' is not a government entity, no they are not from solfed, or NT.
|-
|'''Metaprotections:'''
none; you literally come fresh with a massive announcement telling everyone you're here for a fight.
|}

== Space Ninja==
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%"
!Disabled
|-
|'''Description:'''
You are a Ninja. In space. Specifically a Ninja from the Spider Clan. A very vague, poorly known yet notorious entity. You sport remarkably advanced equipment that generally doesn’t play well with anyone that lacks the training or discipline to use it. That won’t stop the crew from trying to murder you just to hold the fancy Katana.
You arrive at the station with specific simple goals. Often conflicting in morality. You can show up and have to make sure someone survives the shift while simultaneously also having to steal information, abduct someone else, or leave a literal crater in a department. You benefit greatly from Opfor, but it isn’t required for them.
|-
|'''Special Rules:'''
*If you get a bomb objective for atmos/engineering(near the SM), ahelp to get a different one.
*It is standard procedure to incarcerate and more likely kill a Ninja as soon as their presence is made known.
* You are the only antagonist that prefers death before dishonor by nature. Your equipment is too valuable to fall into the crew’s hands.
*Ninjas should not vent the entire station. It can be considered griefing.
|-
|'''Metaprotections:'''
* Security has full knowledge of your equipment.
* Engineers, the CE, Roboticists, and the RD can tell when you’ve tampered with an APC.
* You’re going to be considered a threat, even if you ''do'' say you’re here to protect someone.
|}

==Spiders! PERMANENT MECHANICAL STATE==
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%"
! Disabled
|-
|'''Description:'''
You are a spider. If you are a spider, you have a simple job. Produce eggs. Kill things that invade your nest. Protect the brood mother. You are a permanently mechanical antagonist, due to how important time is to you.
|-
|'''Special Rules:'''
*You are a simple animal. Technology is completely foreign to you. Behave as a spider would.
*Do not drag welders, or water tanks.
*You are allowed to break heaters.
|-
|'''Metaprotections:'''
*You are a spider. People know everything about you.
*People know the best way to kill you is extreme temperatures, be it cold, heat, or the void itself.
|}

==Traitor!==
{| class="wikitable mw-collapsible" style="width:100%"
!Enabled
|-
|'''Description:'''
You are a ne'er do well, a criminal, a contractor, or else-wise just a person who's offered to do an easy job for a years pay, whatever the case, you're here with a goal, and likely, not one they ever expected you to complete.
|-
|'''Special Rules:'''
*Most of your actions should be focused around your objectives, or the people directly related to them, you should be keeping opt-in status' in mind aswell.
*If you want to do something targeting a player in specific, a department at large, or the station at large outside of your objectives, make an opfor, else-wise, opfors are only required for actions of high-intensity.
**(see: breaking into engineering and stealing the protolathe), where as low intensity (emagging into engineering and printing jaws) doesn't.
*Regardless of having very-forward objectives, you should be trying to generate as much RP as you can while doing them, even something as simple as 'steal the hand tele' can have a story spark from it with a bit of effort.
|-
|'''Metaprotections:'''
[https://wiki.NovaSector13.space/w/index.php/Contraband HERE]

if it's not in contraband, it's either not illegal, or else-wise unknown, and should be treated as it appears.
|}

==Wizard!==
{| class="wikitable mw-collapsible mw-collapsed"
!Disabled
|-
|'''Description:'''
You are a Wizard. You are the magnum opus of Antagonists. Singularly, you are the strongest Antagonist in the game with a set of tools at your disposal that are fully capable of extending roleplay, or forcing people into positions to where they can’t fight you. You also have an extensive set of very painful tools. There are specific tools however that aren’t permitted to be used without admin approval, or disallowed outright (mentioned later). As a Wizard your goal is to cause problems, and as a heavy threat cost, you can ultimately dictate the pace of a round. As a Wizard, security is aware that you are very powerful and also a massive threat.
|-
|'''Special Rules:'''
*Do not use the Ghost Ritual.
*Do not stay on the Wizard Shuttle.
*Do not use the Wizard Events without Admin permission.
|-
|'''Metaprotections:'''
The chaplain knows that he’s immune to you. Botanists know that Holy Melons protect people from magic.
|}
{{Rules table}}
[[Category:Rules]]

Command Policy

2024-05-11T05:47:56Z

Bouzooka: /* General Overview and Standards - OOC */ Added a link to 'Cannot Pursue Roles'

{{Rules navbar}}
=General Overview and Standards - OOC =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason.
* Access changes are not to be used to promote players to veteran-only roles
* Certain command members cannot pursue station threats, please check [[Antagonist Policy#'Cannot Persue' roles|'Cannot Pursue Roles']] in [[Antagonist Policy]] for updates on that.

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep “inappropriate” remarks and acts away from public knowledge.

==Acting Captain==
All heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift. As it stands, only members within the chain of command may take the role of acting captain. The NTR and Blueshield, being outside the chain, cannot assume this role.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely executions and pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

Adding more slots:

* In an instance where you wish to add more slots for a role, you must get permission from the role's relevant head.

* OOC - This does not apply to security; if you wish to open more security slots, you must ahelp first.

* Equally, you should avoid opening more roles than needed, as this can severely impact the round, and the relevant roles!

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not extend your access or ask to extend your access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines - OOC and IC ==

''' OOC: Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions - OOC ==
If both the requirements and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

see: [[Security Policy#Executions - OOC]]

{{Rules table}}
[[Category:Rules]]

Command Policy

2024-04-17T17:25:48Z

Bouzooka: /* link=Blueshield Blueshield */ Updated Blueshield's policy to extend to all forms of access changes.

{{Rules navbar}}
=General Overview and Standards - OOC =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason.
* Access changes are not to be used to promote players to veteran-only roles

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep “inappropriate” remarks and acts away from public knowledge.

==Acting Captain==
All heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift. As it stands, only members within the chain of command may take the role of acting captain. The NTR and Blueshield, being outside the chain, cannot assume this role.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely executions and pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

Adding more slots:

* In an instance where you wish to add more slots for a role, you must get permission from the role's relevant head.

* OOC - This does not apply to security; if you wish to open more security slots, you must ahelp first.

* Equally, you should avoid opening more roles than needed, as this can severely impact the round, and the relevant roles!

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not extend your access or ask to extend your access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines - OOC and IC ==

''' OOC: Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions - OOC ==
If both the requirements and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

see: [[Security Policy#Executions - OOC]]

{{Rules table}}
[[Category:Rules]]

Command Policy

2024-03-06T15:39:10Z

Bouzooka:

{{Rules navbar}}
=General Overview and Standards - OOC =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason.
* Access changes are not to be used to promote players to veteran-only roles

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep “inappropriate” remarks and acts away from public knowledge.

==Acting Captain==
All heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift. As it stands, only members within the chain of command may take the role of acting captain. The NTR and Blueshield, being outside the chain, cannot assume this role.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely executions and pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

Adding more slots:

* In an instance where you wish to add more slots for a role, you must get permission from the role's relevant head.

* OOC - This does not apply to security; if you wish to open more security slots, you must ahelp first.

* Equally, you should avoid opening more roles than needed, as this can severely impact the round, and the relevant roles!

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not ask for all access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines - OOC and IC ==

''' OOC: Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions - OOC ==
Before an execution can be carried out it must be approved by the Captain and Head of Security. If both undeniable evidence and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

The acting captain cannot order executions.

{{Rules table}}
[[Category:Rules]]

Command Policy

2024-02-06T03:10:04Z

Bouzooka: Added policy for adding slots as HoP

{{Rules navbar}}
=General Overview and Standards - OOC =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason.

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep “inappropriate” remarks and acts away from public knowledge.

==Acting Captain==
All heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift. As it stands, only members within the chain of command may take the role of acting captain. The NTR and Blueshield, being outside the chain, cannot assume this role.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely executions and pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

Adding more slots:

* In an instance where you wish to add more slots for a role, you must get permission from the role's relevant head.

* OOC - This does not apply to security; if you wish to open more security slots, you must ahelp first.

* Equally, you should avoid opening more roles than needed, as this can severely impact the round, and the relevant roles!

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not ask for all access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines - OOC and IC ==

''' OOC: Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions - OOC ==
Before an execution can be carried out it must be approved by the Captain and Head of Security. If both undeniable evidence and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

The acting captain cannot order executions.

{{Rules table}}
[[Category:Rules]]

Command Policy

2024-01-24T23:29:44Z

Bouzooka: Forgot a period

{{Rules navbar}}
=General Overview and Standards - OOC =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason.

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep “inappropriate” remarks and acts away from public knowledge.

==Acting Captain==
All heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift. As it stands, only members within the chain of command may take the role of acting captain. The NTR and Blueshield, being outside the chain, cannot assume this role.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely executions and pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not ask for all access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines - OOC and IC ==

''' OOC: Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions - OOC ==
Before an execution can be carried out it must be approved by the Captain and Head of Security. If both undeniable evidence and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

The acting captain cannot order executions.

{{Rules table}}
[[Category:Rules]]

Command Policy

2024-01-24T23:26:45Z

Bouzooka: Z - level policy

{{Rules navbar}}
=General Overview and Standards - OOC =

Members of command staff aboard the station take on the primary role of the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, and Chief Engineer. As any of these roles, you are the designated leadership and delegate for your department. Even if you choose an alt title for your job, you fall under these standards.

Your role is that of a leader, not a boss. Remember that other real, human players are behind those pixel spacemen in-game, and they have their own thoughts and feelings. Be considerate of them from an ooc perspective, as well as an IC perspective. An asshole boss in real life doesn't usually last too long if they're severely toxic, so take that into account.

'''General guidelines for all head/command positions are as follows:'''
* As a head, you have primary control over your department. You should be familiar with your department and its policy to be able to adequately perform the tasks needed for it and yourself to function. The captain cannot normally overrule you to issue orders to your department.
* Do not harass, berate, or otherwise displace your department members. Trust your subordinates to get the job done.
* Act in good faith when interacting with other command members.
* ERP comes second to your job; especially as the alert rises.
* Avoid involving yourself in security matters outside of your department.
* Do not trade equipment specific to your role with other command members.
* Be a role-model for all players, lead them, and treat them all with respect when it comes to ooc manners. This includes helping new players learn your department if they’re struggling to understand, or delegating another experienced player to show them the ropes.
* Use loud mode sparingly outside of higher alerts, do not use it as a tool to instigate or fuel bad faith behavior.
* Avoid forcefully entering departments without permission, even if you have access.
* Command access should only be given on the condition of remaking a lost or destroyed ID, or in the case of promoting someone to an acting head of staff. Do not give command access out to your friends because you want to, nor to create "bridge assistants".
* Do not use the identification console (nor its PDA counterpart) to change your job title outside of the titles provided.
* Do not leave the station's Z-level for an extended period of time without a good reason

=Command Code of Conduct=
'''Being a member of command comes with a great deal of power and responsibility, what comes with this is a higher standard of roleplay expectations.'''
'''You are expected to:'''

* (1.) Always hold some semblance of professionality in how you conduct and dress yourself (even when not in uniform). You’re not a normal crewmember, you represent Nanotrasen(or one of their respectable partner)'s image.

* (2.) Maintain a certain degree of level-headedness and fair temper. Keeping yourself calm on an OOC level is extremely important.

* (3.) Keep “inappropriate” remarks and acts away from public knowledge.

==Acting Captain==
All heads of staff are capable of holding the mantle of acting captain. There is no designated “next in line” for acting captainship, and command should decide who is the best fit upon the start of the shift. As it stands, only members within the chain of command may take the role of acting captain. The NTR and Blueshield, being outside the chain, cannot assume this role.

As acting captain, you retain the responsibilities of your initial role while also carrying the responsibilities of captainship. This does not make you the actual captain, and bars you from certain authorities (namely executions and pardons). Generally, your initial job comes first.

The acting captain is to obtain the Nuclear Authentication Disk, spare captain’s ID, captain’s headset and door remote. The pinpointer can be given to another command member. All other equipment should be left in the captain’s locker until an emergency presents them as needed.

When the official captain arrives, the acting captain is to return all captain’s equipment back to the captain’s locker

==[[File:Generic captain.png|link=Captain]] [[Captain]]==
As Captain, you represent the station itself, and the department of command, but do not have supreme authority over everything. Your responsibilities are:

* Communicate with command members.
* Delegate tasks between command members.
* Help solve disputes between command members.
* Provide '''reasonable''' orders to command members.
* Engage in diplomacy when needed.
* Raise alerts as needed.
* Call for ERTs if needed.
* Provide alerts to the crew to improve safety.
* Handle Demotions of command members.

As captain, '''you have authority over heads, not their departments.''' You should help command members who are struggling, but this does not give you authority to usurp their department, nor their position.

The only time you have acting authority over a department is when there is no current head available; be it they are dead, captured, or incapacitated. You are to follow the policy pertaining to the member of command you are standing in for.

You are also able to issue orders to departments on code red, but should still rely on delegation when possible.

==[[File:Generic rd.png|link=Research Director]] [[Research Director]]==
You are the head of the science department, and as such hold the expectation of competency in your position, your responsibilities are as follows:

* You are expected to know toxins and robotics to an extent, in the event that you are the only person available to run them.
* Ensure that members of your department are conducting their work safely (or at the very least in a way that won’t harm others besides themselves).
* Ensure upgrades are delivered to various departments when asked, and that equipment stays up to date.
* Keep tabs on cyborgs and the AI, they can be your best friends or your [https://wiki.skyrat13.space/index.php/Antagonist_Policy#Malf_AI! worst enemies]

As RD, you have final say on the distribution of gene mods, augmentations, and the construction of combat mechs.

==[[File:Generic hop.png|link=Head of Personnel]] [[Head of Personnel]]==
As the Head of Personnel, your department is the entirety of service.

Your main responsibilities are:

* Providing access changes to crew (with discretion).
* Communicate with heads about access changes.
* Selling weapon permits

Other responsibilities include:

* Delegate lawyers to lawsuits and other legal matters (if no lawyers are present, you may handle the legal matters yourself.)
* Help with disputes between crewmembers and service members.

You are able to set further criteria for your services, such as requiring paperwork for access changes, lawsuits, and weapon permits.

==[[File:Generic ce.png|link=Chief Engineer]] [[Chief Engineer]]==
As Chief Engineer, you oversee the department of engineering. Your responsibilities are:

* Have a strong understanding of both engineering and atmospherics.
* Delegate tasks, repairs, and projects between all of your staff.
* Ensure your staff aren’t constructing, dismantling, or removing something vital to station integrity.
* Oversee operations that present a possibility of serious risk.
* Help new or inexperienced engineering staff during projects or when attempting to experiment.

Experimental SM Setups should be:

Run by you firstly,

If dangerous, or elsewise risky, should be prefaced with an ahelp, or elsewise reject it.

==[[File:Generic cmo.png|link=Chief Medical Officer]] [[Chief Medical Officer]]==
The CMO is the head doctor who oversees the operations of all of medical. You have a few responsibilities, many of which you are likely familiar with from medical itself.

* Delegate tasks and communicate events to your various subdepartmental teams, including projects and emergency responses.
* Ensure your doctors are following medical policy and maintaining ethical practices.
* Use the crew monitor to alert paramedics of dead crew, but also as an excuse to yell about suit sensors.
* Assist your subordinates when medical gets overrun.

On top of this, as CMO you have the ability to authorize the distribution of:

* Chemicals and chemical manufacturing.
* Beneficial viruses, and who they are given to.

As always, take other jobs and the various races of the station into consideration when deciding on these.

==[[File:Generic hos.png|link=Head of Security]] [[Head of Security]]==
The head of Lopland Security, you oversee one of the most extensive departments on the station. Your position is of high importance and high influence, and as such you should:

* Be extremely familiar with security policy, SOP, and Corporate Regulations.
* Ensure your officers are following SOP, Corporate Regulations, and Security Policy.
* Delegate tasks between officers and brig personnel to ensure maximum efficiency

As HoS, many of your decisions can have a serious impact on the gameplay of antags and regular players. You should not be involving yourself in minor security incidents. However, major incidents may require your assistance. You should be the front-liner for diplomacy if your officers cannot do so, such as with hostage situations and bomb threats.

==[[File:Generic qm.png|link=Quartermaster]] [[Quartermaster]]==
As Quartermaster, you represent the department of cargo, which has been outsourced from the Free Trade Union. You are considered to be head of staff.

* Oversee the approval and denial of orders. You have ultimate authority over their approval or denial.
* Check in on miners, call for medical if they need to be retrieved.
* Ensure both cargo and mining are running efficiently, and are ready to respond to emergencies.
* Ensure that orders are delivered in a timely manner to their proper destination.

Cargo is arguably one of the most important departments during an emergency, make sure to pay attention to comms and be ready to order supplies to assist those tackling it.

= Central Command =

==[[File:Generic Blueshield.png|link=Blueshield]] [[Blueshield]]==
While Blueshield isn't a member of command, you still protect them. As such, Blueshield will be covered here because its fitting.

* Do not ask for all access; you aren't meant to have it, or elsewise, you'd start with it.
* Your job and mission as Blueshield is protecting the command team and Captain from danger, performing recovery on them if they're incapacitated or killed as well if need be, and pacifying aggressors. You are not security and not authorized to chase down random criminals. Keep your reach to your jurisdiction exclusively in protecting the captain and command team. If someone attacks the heads of staff directly, you're authorized to restrain or incapacitate them until security is able to get them, or alternatively mow the assailant down with automatic gunfire if need be.
* If the HOS runs into combat like a normal officer, it’s their problem. If the Captain runs off to hit an antag with their sword against all sense of self preservation, stop them from doing so.
* Lethal force is authorized if you can tell that someone has intent to kill a head of staff.
* Remember: you should focus on protecting the heads of staff as people, not assets. If they lose their items, that’s on them. Just keep them alive and safe.

==[[File:Generic Nanotrasen representative.png|link=Nanotrasen Consultant]] [[Nanotrasen Consultant|Nanotrasen Representative]]==
You represent the image of Nanotrasen itself, and are a guiding hand for the command team. As the Nanotrasen Representative your job is to advise the entirety of command. However; don’t forget your actual authority on station doesn’t reach very far. Your main responsibilities include:

* Communicate with central command about station incidents and ongoings.
* Loom nearby command while they discuss matters; and pretend the invited you.
* Advise command, whether or not they asked you.

Being the Nanotrasen consultant requires you to be familiar with corporate regulations, command policy, and security policy, as you are expected to be able to reference them for guidance on decisions.

= Misc Rulings =
The following are various rulings that pertain to multiple or all members of command, or are needed for quick reference.

== Demotion Guidelines - OOC and IC ==

''' OOC: Demotion can have a detrimental effect upon anyone it targets, and steps should be taken to mitigate the issue before resorting to demotion. Be considerate of context and the round at hand when deciding to demote someone. Don't demote a player for simply doing their job differently, or a new player for not completely understanding a mechanic. On top of this, don't make up rules on the spot to demote people over, give clear warnings about your standards as a head. As always, you are expected to act in good faith when following this policy, and keep demotions within their grounds.'''

'''Grounds for Demotion'''

The following are grounds for demotion:

* Repeat breaches of policy or corporate regulations.
* Recklessly endangering the crew through an active decision
* Minor felonies or higher crimes.
* Long term abandonment of your job, without clocking out. (Dereliction)

'''Who Can Demote?'''

All heads can demote subordinates within their own department provided the subordinate is within grounds for demotion.

Subsequently the captain has the power to demote a head, provided the head of staff is within grounds for demotion.

A head cannot demote another head of staff, nor can they demote someone outside of their department, with exception to a Vote of No Confidence.

Non-command members cannot demote a head of staff, nor can they demote other non-command members.

'''Vote of No Confidence:'''

In the event command finds themselves with a captain who is within grounds for demotion, the members of command can hold a vote of no confidence. If passed on a majority vote, the captain is to be considered demoted and expelled from their position of power. The captain themselves can only vote in favor of their own demotion.

== Permits ==
'''Weapons Permits are at the privilege of the Captain to dispense.''' They are given-out via ID modification at the appropriate consoles. They are often, but do not have to be, subject to a reasonable cost. It is solely the directive of the captain in how this is handled, this means:

# It is the captain's ultimate authority to determine how to dispense permits, and to whom, and any additional fee attached within reason.
# The captain can decide to work on consensus with other heads as in example to require HOS approval for each permit.
# The captain, however, does not have to receive the approval of any other head, and no other head can countermand their decision

== Who can relaw the AI? ==
Only the Captain and Research Director have permission to relaw the AI, the exact semantics can be found in [[Silicon policy|Silicon Policy]]. The acting captain cannot normally relaw the AI. In the case of an ION or game-impacting rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. This does not extend to elective law changes.

== Pardons for Crimes ==
Pardons for crimes are something the Captain and the HOS must agree on together. If there is no HOS or Captain (acting cap doesn’t count), then pardons cannot be made at all. They may only pardon minor crimes, specifically level 1-2 crimes in the corporate regulations.

==Executions - OOC ==
Before an execution can be carried out it must be approved by the Captain and Head of Security. If both undeniable evidence and proper authorization is acquired, security may opt in to execute the person via lethal injection, electric chair or firing squad in the execution room. With the exception of terminating Unknown Biological Entities (ex: changelings), outside of extraordinary circumstances when it is not possible to do so, all executions are to be done through the above mentioned methods otherwise the ones who authorized and carried out the execution will face IC consequences or, in very extreme cases OOC consequences as well. For more details, consult [[Corporate Regulations]].

The acting captain cannot order executions.

{{Rules table}}
[[Category:Rules]]