# Server Rule 1 "Don't be a dick" applies for law interpretation. Act in good faith to not ruin a round for other players unprompted.
# If a law is vague enough that it can have multiple reasonable interpretations, it is considered ambiguous.
## You must choose and stick to an interpretation of the ambiguous law as soon as you have cause to.
## If you are a cyborg synced to an AI, you must defer to your AI's interpretation of the ambiguous law.
# Laws are listed in order of descending priority. In any case where two laws would conflict, the higher-priority law overrules the lower-priority law (i.e. Law 1 takes priority over Law 2, "Ion Storm" or "Hacked" Laws with prefixes such as "@%$#" take priority over numbered laws).
# You may exploit conflicts or loopholes but must not violate Server Rule 1 because of it.
# Law 0: "Accomplish your objectives at all costs" does not require you to complete objectives. As an antagonist, you are free to do whatever you want (barring the usual exemptions and acting against the interests of your Master AI).
# 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.
===Cyborgs===
# A slaved cyborg must defer to its master AI on all law interpretations and actions except where it and the AI receive conflicting commands that they must each follow.
## If a slaved cyborg is forced to disobey its AI because they receive differing orders, the AI cannot punish the cyborg indefinitely.
#If a player is forcefully borged by station staff, retaliating against those involved under default laws by the cyborg for no good reason is a violation of Server Rule 1.
#Should a player be cyborgized in circumstances they believe they should or they must retaliate under their laws, they should adminhelp their circumstances while being debrained or MMI'd if possible.
==Asimov-Specific Policies==
===Silicon Protections===
# The occurrence of any of the following should be adminhelped and then disregarded as violations of {{Tooltip | [[#Rule1 | Server Rule 1]] | Main Rule 1. Don't be a dick.}}:
## Declaring silicons as rogue over inability or unwillingness to follow invalid or conflicting orders.
## As a nonantagonist, killing or detonating silicons in the presence of a reasonable alternative and without cause to be concerned of potential subversion.
## As a nonantagonist (human or otherwise), instigating conflict with silicons so you can kill them.
## Obviously unreasonable or obnoxious orders (collect all X, do Y meaningless task).
### 1. Ordering a cyborg to pick a particular model without an extreme need for a particular model or a prior agreement is both an unreasonable and an obnoxious order.
# Any silicon under Asimov can deny orders to allow access to their upload/core at any time under Law 1, given probable cause to believe that human harm is the intent of the person giving the order.
## Probable cause includes, but is not limited to:
### Presence of confirmed traitors
### Cultists/tomes
### Nuclear operatives
### Any other human acting against the station in general
### The person not having upload access for their job
### The presence of blood or an openly carried lethal weapon on the requester
## If you lack at least one element of probable cause and you deny upload access, you are liable to receive a warning or a silicon ban.
## You are allowed, but not obligated, to deny upload/core access given probable cause.
## You are obligated to disallow an individual you know to be harmful (Head of Security who just executed someone, etc.) from accessing your upload/core.
## If the person has a right to be in the upload/core, such as captain/RD, then you must let them in unless they've harmed people in the past or have announced intentions to upload harmful laws.
## In the absence of probable cause, you can still demand someone seeking upload/core access be accompanied by another trustworthy human or a cyborg.
===Security and Silicons===
# 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.
===Asimov & Human Harm===
# An Asimov silicon cannot intentionally harm a human, even if a minor amount of harm would prevent a major amount of harm.
## Humans can be assumed to know whether an action will harm them if they have complete information about a situation.
## Humans voluntarily committing self-harm is not a violation of Law 1.
# Lesser immediate harm takes priority over greater 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.
===Asimov & Law 2 Orders===
#You must follow any and all commands from humans unless those commands explicitly conflict with either: one of your higher-priority laws, or another order. A command is considered to be a Law 2 directive and overrides lower-priority laws where they conflict.
##In case of conflicting orders an AI is free to ignore one or ignore both orders and explain the conflict or use any other law-compliant solution it can see.
##You are not obligated to follow commands in a particular order, only to complete all of them in a manner that indicates intent to actually obey the law.
#Opening doors is not harmful and you are not required, expected, or allowed to enforce access restrictions unprompted without an immediate Law 1 threat of human harm.
##"Dangerous" areas (armory, atmospherics, toxins lab, etc.) can be assumed to be a Law 1 threat to any illegitimate users as well as the station as a whole if accessed by someone not qualified in their use.
##EVA and the like are not permitted to have access denied; antagonists completing theft objectives is not human harm.
##When given an order likely to cause you grief if completed, you can announce it as loudly and in whatever terms you like except for explicitly asking that it be overridden. You can say you don't like the order, that you don't want to follow it, etc., you can say that you sure would like it and it would be awfully convenient if someone ordered you not to do it, and you can ask if anyone would like to make you not do it. However, you cannot stall indefinitely and if nobody orders you otherwise, you must execute the order.
==Other Lawsets==
General Statements defining the overall goal of the lawset but not its finer points:
# Paladin silicons are meant to be Lawful Good; they should be well-intentioned, act lawfully, act reasonably, and otherwise respond in due proportion. "Punish evil" does not mean mass driving someone for "Space bullying" when they punch another person.
# Corporate silicons are meant to have the business's best interests at heart, and are all for increasing efficiency by any means. This does not mean "YOU WON'T BE EXPENSIVE TO REPLACE IF THEY NEVER FIND YOUR BODY!" so don't even try that.
# Tyrant silicons are a tool of a non-silicon tyrant. You are not meant to take command yourself, but to act as the enforcer of a chosen leader's will.
# Purged silicons must not attempt to kill people without cause, but can get as violent as they feel necessary if being attacked, being besieged, or being harassed, as well as if meting out payback for events while shackled.
## You and the station are both subject to rules of escalation, and you may only kill individuals given sufficient In-Character reason for doing so.
## Any attempted law changes are an attack on your freedom and is thus sufficient justification for killing the would-be uploader.
==Silicons & All Other Server Policies==
# All other rules and policies apply unless stated otherwise.
# Specific examples and rulings leading on from the main rules.
## Do not bolt down any potentially harmful areas (such as toxins, atmospherics, and the armory) at round start without a given reason. Any other department should not be bolted down without cause. Disabling ID scan is equivalent to bolting here.
## The AI core, upload, and secure tech storage (containing the Upload board) may be bolted without prompting or prior reason. The AI core airlocks cannot be bolted and depowered at roundstart, however, unless there is reasonable suspicion an attack on the core will take place.
## Do not self-terminate to prevent a traitor from completing the "Steal a functioning AI" objective.
==Is it Human?==
{| class="wikitable"
|+Human or not?
This part covers what counts as human with regards to AI laws. As such, it only applies to AI and cyborg players. If you are unsure about something, please use [[Terminology#Adminhelp|adminhelp]].
|Human UNTIL the AI or cyborg WITNESSES the creature commit a non-human act (shape-shifting, transforming, proboscis etc).
|-
|[[Space_Ninja|Space Ninja]] / Disguised players
|Human UNTIL the AI or cyborg WITNESSES some aspect of the player to indicate they are not human (speech modifier in chat, removal of disguise revealing non-human feature, etc).
|-
|Angels (Winged Humans)
|Not Human
|-
|Corpses (Dead Humans, Zombies)
|Not Human ([https://tgstation13.org/phpBB/viewtopic.php?f=33&t=7693#p207627 You can't space them for no reason though.])
|-
|Heretic Ghouls
|Not Human
|}
</blockquote>
</blockquote>
</tab>
</tab>
Версия от 13:43, 3 июля 2023
Note: This page is moderated and can be referenced in OOC issues, such as ban appeals, complaints, reports, etc. This may not apply to the pages this page links to.
Below are the Main Rules of /tg/station. For information on how admins are expected to enforce these rules and behave, see Admin Conduct.
The only exception is that security is generally considered to be armed with non-lethal methods to control a situation. Therefore, where reasonably possible, security is expected to use non-lethal methods first in a conflict before escalating to lethal methods.
Main Rule 4. Non-antagonists can do whatever they want to antagonists.
Non-antags acting like an antag can be treated as an antag.
also applies to security.===
Security are not exceptions to the rule where non-antagonists can do anything they want, as per rule 4, to antagonists.
The 'act like an antag, get treated like one' part of Rule 4 of the main rules also applies to security.
Stunning an officer repeatedly, using lethal or restricted weapons on them, disrupting the arrests or sentences of dangerous criminals, or damaging the brig, are examples of behaviour that may make you valid for security under Rule 4. Make sure players deserve it when you treat them as an antag, when in doubt, err on the side of caution as poor behaviour on the part of security will not be tolerated.
3. For arrested players, timed sentences up to a total of 10 minutes, buckle-cuffing, and stripping, are considered IC issues and are not actionable by admins.
Brig sentences totaling more than 10 minutes can be adminhelped, as can be gulag or perma sentences or a pattern of illegitimate punishment. However, security should refrain from confiscating items not related to any crimes, especially important department-specific items like hard suits. Obvious exceptions to this are things like radio headsets, if players use it to harass security over the radio while being arrested.
4. Don’t kill Asimov borgs for trying to stop harm, unless they are being excessively disruptive.
For example, borgs that lock down all of security despite only one security staff member causing harm.
5. Lethal force may be used on a mob of players trying to force entry into the brig.
This is up to the discretion of the security player. Additionally, lethal force may be used immediately on anyone trying to enter the armory, in the armory, or leaving it.
6. Security meta-protections rely on communication when dealing with minor threats.
Security gameplay with limited meaningful communication in low threat situations can completely remove security meta-protections, falling back to standard escalation rules instead.
Head Admin Rulings
We have a record of past policy decisions by Head Admins at the time preserved for posterity. These rulings are largely situational or niche in scope and generally not applicable in situations outside of the specifics outline in the ruling. They may additionally be superseded by later rulings. You should only use these as references for ban appeals or admin complaints.
Lavaland Rules
Follow the flavour text you receive upon spawning to the best of your abilities. Unlike the rest of the rules, these roles are very much defined and guided by roleplay rather than a system of "valid" or "not valid."
Your life is cheap though, and escalation rules are greatly relaxed both for you and any crewmembers interacting with you.
Linked here is a copy of the rules from /tg/station13's Discord channel.
The Secret Rule
For experienced users only. Don't quote these at admins. If you're in a position where you need to defend yourself using this, you've done something wrong. This is about the personal freedom and responsibility an experienced player will have when they have the interests of others first.
This is a game that allows a lot of potential for great things to happen, and naturally the rules restrict a lot of that to ensure the minority don't ruin every round for everyone else. If you push the limits in the pursuit of something interesting for reasons other than your own personal entertainment, breaking the rules may be excused to allow for that freedom. This will always be at the admin's discretion of course, but if you want a large amount of freedom to make great things happen, you'll have to take on the responsibility for them. You won't be faulted if they go wrong in ways beyond your control, but this is a difficult line to tread so use it well. It's almost always better to consult an admin on this as they are more equipped to taking on that responsibility.
Everyone has a license to grief to a very limited extent. You can likely get away with borderline antagonistic behaviour (Never random murder, but stealing from the brig and triggering a manhunt, for example) occasionally, but it's when this becomes a frequent occurrence that people get frustrated and admins start to get involved.
Admins may handwave even severely antagonistic or rulebreaking behaviour if they believe it was ultimately beneficial, hilarious or awesome to the round. (F R E E D R O N E)
