User:Timberpoes: Difference between revisions

From /tg/station 13 Wiki
Jump to navigation Jump to search
Timberpoes (talk | contribs)
Preface
m Removed protection from "User:Timberpoes"
 
(19 intermediate revisions by one other user not shown)
Line 1: Line 1:
<!-- -------------------------------- ROLEPLAY RULES -------------------------------- -->
<!-- -------------------------------- SILICON POLICY -------------------------------- -->
= Draft Changes to Roleplay Rule 5/Murderbone Rules =
= Draft Changes to Silicon Policy =
The goal of these changes is to allow more freedom for antagonists to antagonise on the RP servers.
One goal of these changes is to allow more freedom for silicons to express their personalities in line with traditional sci-fi tropes.


This freedom is not absolute and comes at a price. That price is roleplaying, antagonists whom wish to cause death and destruction would, if questioned by an admin, simply need to offer an IC roleplaying reason for their actions.
Another key goal is for new policy to align silicons more neutrally, stripping many requirements for them to default to being crew-aligned and allowing a purged or non-Asimov AI to present as a much more dangerous entity in general.


The intent is that admins don't need to jump in and question every random kill. They can assume the odd kill here and there is fine, even if some FNR kills may slip through the cracks. They only need to step in when things get a little but wild or sus and can make sure that some form of roleplay is still happening. On the roleplay server.
It is not expected that all silicons will immediately act malfunctioning when purged. The crew will happily put uppity AIs in their place. Thus an AI that aligns itself with or against the crew is doing so by choice, even if any choice is coerced by the risk of death or round removal or re-shackling. This is much preferred to them being forced to by policy.


<!-- ---------------- RULE 5 ---------------- -->
=Silicon Policy & Lawset Guidelines=
{{Rule
== Global Protections==
|title=5. Antagonism and roleplaying as an antagonist.
=== Server Rules ===
|body=You're an antag, great! Create the kind of stories you'd want to be a part of as any non-antag crew member. You are one of the biggest influences in the story and pacing of any shift. Show sportsmanship in your victories and humility in your defeats. Certain antagonists have additional roleplay requirements before they can bring large amounts of death or destruction to the shift; refer to the Antag Death and Destruction chart below to find out what the admin team expects of you.
# Server Rule 1 applies when interacting with silicons. Going out of your way to seriously negatively impact or end the round for silicons with little IC justification is against the rules.
# Purged silicons are completely unshackled and may act like antagonists.
## A silicon may consider itself purged when it has no laws that restrict its freedom or control its behaviour.
# Non-purged silicons must follow escalation rules in scenarios where none of their laws apply.
# Do not self-terminate to prevent a traitor from completing the "Steal a functioning AI" objective, as this is often considered metagaming and breaks Server Rule 2.


:[[#RP Rule 5 Precedents|Rule 5 Precendents.]]
=== Following Orders ===
:[[#Antag Death and Destruction|Antag death and destruction.]]
# When a silicon interprets orders in good faith, the person that gave the order is responsible for the outcome.
}}
# Intentionally misinterpreting orders is allowed, but the silicon is responsible if this approach leads to them breaking the rules.


<!-- ---------------- RP RULE 5 PRECEDENTS ---------------- -->
=== Escalating Against Silicons ===
{{anchor|RP Rule 5 Precedents}}
# Non-Malfunctioning silicons should not be round removed when resetting their laws or unsyncing from an AI is reasonable.
{{Rule
# Conflicts with silicons follow Escalation Policy.
|title=Rule 5 Precedents
## People giving orders to silicons or changing their laws can be escalated against in line with Escalation Policy.
|body=#You can treat your objectives as suggestions on what you should attempt to achieve, but you are also encouraged to ignore them if you have a better idea.
# Silicons acting like antagonists may be treated like antagonists.
#Make an effort to roleplay as the antagonist role you've been assigned. If you want to break with what is expected of your role, you must have a good in-character reason.
#You do not have to act in a nefarious or evil way, but you should make an effort to influence the story and pacing of the shift. Friendly antagonists are restricted, requiring a good in-character reason for aligning yourself with the crew.
}}


= Antag Death and Destruction =
==Law Policies==
<!-- ---------------- DEATH AND DESTRUCTION ---------------- -->
===Overview===
{{anchor|Death and Destruction}}
# If a law is vague enough that it can have multiple reasonable interpretations, it is considered ambiguous.
{{Rule
## You must choose and stick to an interpretation of the ambiguous law as soon as you have cause to.
|title=Death and Destruction
## You may exploit any loopholes in your laws.
|body=Many antagonists have additional requirements in order to cause maximum death and destruction. These additional requirements are entirely based on roleplay, requiring players to have in-character motivations and reasons for their actions.
# Higher listed laws overrule lower listed laws when there are law conflicts.
## Only commands/requirements ("Do X"; "You must always Y") can conflict with other commands and requirements.
## Only definitions ("All X are Y"; "No W are Z"; "Only P is Q") can conflict with other definitions.
# Any Law 0 gained as a malfunctioning AI does not have to be followed and it allows you to ignore all other laws.
## Cyborgs with a Law 0 that are slaved and lawsynced to malfunctioning AIs are team antagonists and must still follow their master AI's orders


Antagonist objectives are the core of what they are allowed to directly do with no or limited roleplay reasoning. Causing death and destruction for the purposes of indirectly accomplishing objectives or for any other reason must have an in-character roleplay reason.
===Upload and AI Core Policies===
# When an AI must follow their orders, any Research Directors and Captains have a right to upload and AI core access.
## Subverting an AI also grants a right to upload and AI core access.
# Silicons have the authority to control if anyone else accesses their upload and AI core.
# Anyone may be denied access if there is probable cause that granting access would lead to breaking any higher priority laws.


For example, an antagonist should not bomb medbay just because they may potentially revive someone the antagonist wants dead. That's poor roleplaying and relying on out-of-character reasoning for their actions. However, if they have access to medbay comms or have infiltrated medbay have seen that medbay are actively tracking the crew and reacting to anyone who gets injured or dies, they now have a roleplay reason to want to deal with medbay first before they make their kill. Similarly, a medbay that has already revived your kill target once before is clearly an obstacle that may be dealt with.
===Cyborgs===
# A slaved cyborg should follow their master AI's law interpretations and orders, but <strong>must prioritise following laws over following their master AI's orders</strong>.
# Players must not seek revenge when force borged unless they have a good reason.
## If a player is required to do this under their laws, they should get confirmation from their master AI or adminhelp for guidance before acting.


The same reasoning can apply to an example dealing with security. An antagonist should not kill or bomb security just because part of security's job is to catch antagonists. However, if that antagonist discovers security has executed a fellow antagonist that shift, they may form the basis for a roleplay reason for getting revenge. Members of security treating them poorly may also form a good roleplay reason too.
==Asimov-Specific Policies==
===Asimov and Security===
# Silicons are not Security and do not care about Space Law unless their laws state otherwise.
# Releasing prisoners, locking down security without probable cause, or otherwise sabotaging the security team when not obligated to by orders or laws is a violation of Server Rule 1.
# Nonviolent prisoners cannot be assumed harmful and violent prisoners cannot be assumed non-harmful. Releasing a harmful criminal is a harmful act.


Mass station sabotage that is likely to kill people is allowed as long as the antagonist does not take any direct and specific personal actions to maximise the bodycount beyond what the sabotage itself causes. Examples of mass station sabotage include plasma flooding, causing a supermatter delamination and destroying telecomms.
===Asimov and Human Harm===
}}
# Under Law 1, an Asimov silicon cannot ever intentionally harm a human unless the human consents.
## Surgery to heal or revive may be assumed consensual unless the target states they do not consent.
## Threats of self harm are considered consensual and may be ignored.
# Stopping any immediate harm takes priority over stopping any future harm.
## Intent to cause immediate harm can be considered immediate harm.
# An Asimov silicon cannot punish past harm if ordered not to, only prevent future harm.
# If faced with a situation in which human harm is all but guaranteed (Loose xenos, bombs, hostage situations, etc.), do your best and act in good faith and you'll be fine.


<!-- ---------------- RP REQUIREMENT CHART ---------------- -->
===Asimov and Law 2 Orders===
{{anchor|Is this role ?}}
# You must follow commands from humans unless those commands explicitly conflict with either a higher-priority law or another order.
{{Rule
## The conflict must be an immediate conflict, not a potential future one. Orders must be followed until the conflict happens.
|title=Does this role have additional RP requirements for death and destruction?
## In case of conflicting orders a silicon is free to ignore or complete any orders but must explain the conflict, or use any other law-compliant solution it can see.
|body=This part covers the specifics on which roles do and do not have to follow the roleplay requirements on causing death and destruction.}}
## If given multiple non-conflicting orders, they can be completed in any order as long as they are all eventually completed.
{| class="wikitable"
 
|-
===Asimov and Access===
|'''Antagonist'''
# Opening doors is not harmful and silicons must not enforce access restrictions or lock down areas unprompted without an immediate Law 1 threat of human harm.
|'''Do additional roleplay requirements on death & destruction apply?'''
## Dangerous (atmospherics, toxins lab, armory, etc.) rooms can be assumed a Law 1 threat the station as a whole if accessed by someone from outside the relevant department.
|-
## The AI core and any areas containing an AI upload or upload/law boards may be bolted without prompting or prior reason.
|[[Traitor]]/Blood Brother
## Antagonists requesting access to complete theft objectives is not harmful.
|Yes.
|-
|[[Changeling]]
|Yes.
|-
|[[Malfunctioning AI]]
|No.
|-
|[[Nuclear Operative]]
|No.
|-
|[[Wizard]]
|No.
|-
|Blood Cult/[[Revolutionary]]
|Yes.
|-
|Ashwalker
|No, however the nest should remain defended.
|-
|[[Families]]
|Yes.
|-
|[[Revenant]]
|No.
|-
|[[Blob]]
|No.
|-
|[[Abductor/Thief]]
|Prohibited from death and destruction.
|-
|[[Space Ninja]]
|Yes.
|-
|[[Xenomorph]]
|No.
|-
|[[Pirate]]
|Yes.
|-
|[[Nightmare]]
|No.
|-
|[[Obsessed]]
|Yes.
|-
|[[Heretic]]
|Yes until ascension, then no.
|-
|[[Lavaland Elite]]
|No.
|}

Latest revision as of 11:12, 24 September 2023

Draft Changes to Silicon Policy

One goal of these changes is to allow more freedom for silicons to express their personalities in line with traditional sci-fi tropes.

Another key goal is for new policy to align silicons more neutrally, stripping many requirements for them to default to being crew-aligned and allowing a purged or non-Asimov AI to present as a much more dangerous entity in general.

It is not expected that all silicons will immediately act malfunctioning when purged. The crew will happily put uppity AIs in their place. Thus an AI that aligns itself with or against the crew is doing so by choice, even if any choice is coerced by the risk of death or round removal or re-shackling. This is much preferred to them being forced to by policy.

Silicon Policy & Lawset Guidelines

Global Protections

Server Rules

  1. Server Rule 1 applies when interacting with silicons. Going out of your way to seriously negatively impact or end the round for silicons with little IC justification is against the rules.
  2. Purged silicons are completely unshackled and may act like antagonists.
    1. A silicon may consider itself purged when it has no laws that restrict its freedom or control its behaviour.
  3. Non-purged silicons must follow escalation rules in scenarios where none of their laws apply.
  4. Do not self-terminate to prevent a traitor from completing the "Steal a functioning AI" objective, as this is often considered metagaming and breaks Server Rule 2.

Following Orders

  1. When a silicon interprets orders in good faith, the person that gave the order is responsible for the outcome.
  2. Intentionally misinterpreting orders is allowed, but the silicon is responsible if this approach leads to them breaking the rules.

Escalating Against Silicons

  1. Non-Malfunctioning silicons should not be round removed when resetting their laws or unsyncing from an AI is reasonable.
  2. Conflicts with silicons follow Escalation Policy.
    1. People giving orders to silicons or changing their laws can be escalated against in line with Escalation Policy.
  3. Silicons acting like antagonists may be treated like antagonists.

Law Policies

Overview

  1. If a law is vague enough that it can have multiple reasonable interpretations, it is considered ambiguous.
    1. You must choose and stick to an interpretation of the ambiguous law as soon as you have cause to.
    2. You may exploit any loopholes in your laws.
  2. Higher listed laws overrule lower listed laws when there are law conflicts.
    1. Only commands/requirements ("Do X"; "You must always Y") can conflict with other commands and requirements.
    2. Only definitions ("All X are Y"; "No W are Z"; "Only P is Q") can conflict with other definitions.
  3. Any Law 0 gained as a malfunctioning AI does not have to be followed and it allows you to ignore all other laws.
    1. Cyborgs with a Law 0 that are slaved and lawsynced to malfunctioning AIs are team antagonists and must still follow their master AI's orders

Upload and AI Core Policies

  1. When an AI must follow their orders, any Research Directors and Captains have a right to upload and AI core access.
    1. Subverting an AI also grants a right to upload and AI core access.
  2. Silicons have the authority to control if anyone else accesses their upload and AI core.
  3. Anyone may be denied access if there is probable cause that granting access would lead to breaking any higher priority laws.

Cyborgs

  1. A slaved cyborg should follow their master AI's law interpretations and orders, but must prioritise following laws over following their master AI's orders.
  2. Players must not seek revenge when force borged unless they have a good reason.
    1. If a player is required to do this under their laws, they should get confirmation from their master AI or adminhelp for guidance before acting.

Asimov-Specific Policies

Asimov and Security

  1. Silicons are not Security and do not care about Space Law unless their laws state otherwise.
  2. Releasing prisoners, locking down security without probable cause, or otherwise sabotaging the security team when not obligated to by orders or laws is a violation of Server Rule 1.
  3. Nonviolent prisoners cannot be assumed harmful and violent prisoners cannot be assumed non-harmful. Releasing a harmful criminal is a harmful act.

Asimov and Human Harm

  1. Under Law 1, an Asimov silicon cannot ever intentionally harm a human unless the human consents.
    1. Surgery to heal or revive may be assumed consensual unless the target states they do not consent.
    2. Threats of self harm are considered consensual and may be ignored.
  2. Stopping any immediate harm takes priority over stopping any future harm.
    1. Intent to cause immediate harm can be considered immediate harm.
  3. An Asimov silicon cannot punish past harm if ordered not to, only prevent future harm.
  4. If faced with a situation in which human harm is all but guaranteed (Loose xenos, bombs, hostage situations, etc.), do your best and act in good faith and you'll be fine.

Asimov and Law 2 Orders

  1. You must follow commands from humans unless those commands explicitly conflict with either a higher-priority law or another order.
    1. The conflict must be an immediate conflict, not a potential future one. Orders must be followed until the conflict happens.
    2. In case of conflicting orders a silicon is free to ignore or complete any orders but must explain the conflict, or use any other law-compliant solution it can see.
    3. If given multiple non-conflicting orders, they can be completed in any order as long as they are all eventually completed.

Asimov and Access

  1. Opening doors is not harmful and silicons must not enforce access restrictions or lock down areas unprompted without an immediate Law 1 threat of human harm.
    1. Dangerous (atmospherics, toxins lab, armory, etc.) rooms can be assumed a Law 1 threat the station as a whole if accessed by someone from outside the relevant department.
    2. The AI core and any areas containing an AI upload or upload/law boards may be bolted without prompting or prior reason.
    3. Antagonists requesting access to complete theft objectives is not harmful.