Участник:Dragomagol
Main Rules - read these if nothing else
0. Enforcement of these rules is at the discretion of admins.
Admins are fully accountable for any consequences should they invoke this rule. Admins are also allowed to intervene in rounds when it is in the best interest of the playerbase.
1. Don't be a dick
We're all here to have a good time, supposedly. Going out of your way to seriously negatively impact or end the round for someone with little IC justification is against the rules, this also includes harassing a player OOC (Out of character). Legitimate conflicts where people get upset do happen however, as detailed in the escalation section of the rules.
2. Do not use information gained outside of in-character means.
I.e. metagaming. This especially refers to communication between players outside of the game via things like Skype, known as metacomms. Characters are otherwise allowed to know everything about ingame mechanics or antagonists, as well as keep persistent friendships or relationships with other characters when not for the purpose of unfair advantage by teaming up together for little IC reason.
3. Do not say in character (IC) things in the out of character (OOC) chat channel.
Do not say OOC things in IC either. There is an exception for OOC in IC where terms like 'clickdrag X to Y, or look for the tab' is used to help a player.
4. Lone antagonists can do whatever they want.
Short of metagaming/comms, bug/exploit abuse, erotic/creepy stuff, OOC in IC or IC in OOC, and spawn-camping arrivals. Team antagonists can do whatever they want as per lone antagonists, as long as it doesn’t harm their team. Non-antagonists can do whatever they want to antagonists as per lone antagonists, but non-antagonists are not allowed to pre-emptively search for, hinder or otherwise seek conflict with antagonists without reasonable prior cause. Non-antags acting like an antag can be treated as an antag.
5. Players in a head of staff, AI/Silicon role, or a team conversion role require a minimum amount of effort; generally considered to be not logging out at or near roundstart.
Notify admins if you cannot play these roles and must leave near round start and make an attempt to inform other players IC as well for head of staff or AI roles. Abuse of a job position, particularly Rule 1 breaking abuse, is not allowed.
6. In-game administration rulings are final.
Incidences of admin abuse, negligence or disputed rulings can be taken to the forums. If an admin says something was 'looked into, handled, resolved' etc, regarding an issue, it is unlikely an admin will provide any further information. Admins are under no obligation to reveal IC information. Deliberately lying or misrepresenting facts in adminhelps will be dealt with harshly.
7. If you regularly come close to breaking the rules without actually breaking them, it will be treated as the rules being broken.
Repeated instances of the same rules being broken may be met with harsher consequences. Baiting people into situations where you can report them to admins will be dealt with harshly.
8. Erotic/creepy stuff is not allowed.
No form of erotic roleplay is allowed on the servers, including things that could be construed as sexual by unwilling participants.
9. Players need to be the age of 18 or above.
This rule is for the benefit of and is meant to protect people who shouldn't be playing here due to the nature of the SS13 community. Your age won't be hunted down, but if you admit it to us in admin PMs, or other places within the /tg/Station13 community (the official Discord server, forums, OOC chat, etc.), you're getting banned.
10. Losing is part of the game.
Your character will frequently die, sometimes without even a possibility of avoiding it. Events will often be out of your control. No matter how good or prepared you are, sometimes you just lose.
11. Bigotry is not allowed.
Intentionally seeking to demean others due to their actual or perceived race, sex, gender, orientation or the like is not tolerated.
It is not our goal to create or enforce a list of banned words and instead our goal to eject bigotry from the community. Enforcement will be less PC based and more common sense based with that goal in mind.
The above rule applies to ALL OOC bigotry, even when expressed in IC. There is no racism in 2564, just species-ism, There is no homophobia, just xenophiliapobia, etc.
Admins are encouraged to use rule 1 to deal with instances where """IC""" bigotry is excessive or designed as a mask for ooc bigotry.
Precedents & exceptions: Examples and exceptions to the main rules.
Read for detailed clarification on each main rule. Players are subject to precedents but depending on how much of a dick they were, they can be either advised of the precedent to being banned for it.
Rule 0 Precedents.
- Rule 0 should only be invoked by admins when it is in the best interests of the server.
- Admins have intervened before and will do so again in situations where a player regardless of antag status has repeatedly delayed round-end by recalling the shuttle when most other players are dead or want to leave.
- Admins may mirror bans from other servers at their discretion.
- Admins may ban accounts linked to the use of proxies, CID randomizers, DLL use, or other similar things, at their discretion.
- Admins may ask players in possession of multiple alt accounts to choose one to play on and ban the other accounts.
Rule 1 Precedents.
- Random murders are not acceptable nor is the killing of other players for poor or little reasoning such as ‘My character is insane’. Each unjustified kill is normally met with one 24 ban.
- Spamming any channel is not allowed, this goes for radio spam, AI vox announcement spam, paper at camera spam and other forms of spam. Non-antagonists doing so may not defend themselves and may suffer from IC or OOC consequences. Antagonists can to a certain extent, moreso with reading things like WGW over the radio, but may be told by admins to stop if it becomes excessive. Spamming can result from in-game admin intervention ending in you dying, to admin warnings, to bans for excessive or repeated spamming.
- Rules still apply until the emergency escape shuttle has reached Centcom and the round-end antagonist report has appeared. When the shuttle has reached Centcom, players are free to act as per lone antagonists, detailed in Rule 4. Non-antagonist grief upon the shuttle, from spamming flashbangs for no reason to spraying space lube, can be met with instant 5 (five) minute bans or more.
- Unprovoked grief (occasionally known as greytiding), repeated cases of minor unprovoked grief, and unprovoked grief targeted towards specific players or groups (i.e. metagrudging) fall under rule 1. Admins may follow up on grief with allowing the affected parties to ignore normal escalation policy or measures such as warnings or bans.
- Players who attempt to break into the captain's office, head of personnel's office, or the bridge at or near roundstart for no legitimate reason put themselves at risk for being legitimately killed by the captain, heads of staff, or security.
- You may defend your workplace from trespassers who damage or steal property within that space with significantly greater force than elsewhere. If someone is severely disruptive and returns after ejected, this opens them up to "fun" of the creative workplace death variety.
- Raiding and griefing on servers other than /tg/ may result in bans.
- Starting a fight in OOC/Dead chat and/or harassing someone across multiple rounds after being informed to stop by an admin may end in a server ban. Conflicts are something that happen, but going out of your way to repeatedly do this will not be tolerated.
- Regularly starting a round just to see if you are an antagonist (antag rolling) then exiting it (via any means) is not allowed. This also covers any attempts to maximize antagonist probability.
Rule 1 Related Rulings
Rule 2 Precedents.
- Metacomms, the use of methods of communication outside of SS13 IC channels, is a very serious rule violation and may be met with permanent bans for all related accounts. If players are sharing the same IP or know each other in real life or the like, inform the admins first, otherwise it may look suspicious. Players are allowed to introduce new players that they know to the game but all communication and explanations should be done in game if possible. Admins can also help in these situations if requested.
- Similar to how characters are allowed to know everything about in-game mechanics or antagonists under rule 2, characters are allowed to have persistent knowledge/relationships/friendships with the caveat that knowledge of a character being an antagonist from a previous round is not used.
- Character friendships should not be exploitative in nature or be used to gain an unfair advantage. Having an IC friendship with another player does not, for example, justify giving them all-access each round.
- Atmos techs are not allowed to edit atmos at roundstart so that the AI cannot use it for malicious purposes. While this might not make sense IC, it's a necessary OOC precedent for some game mechanics to work. Atmos techs are allowed if they have any reasonable suspicion of the AI being rogue.
Rule 3 Precedents.
- Excessively OOC names fall under rule 3. Make a minimum effort to have your name fit in a setting involving a wacky space station in the future. A firstname lastname minimum is required for humans and felinids; other species may instead choose to use the default names assigned to them, such as those given through random names, or otherwise any name that is species-appropriate. Honorifics and nicknames are allowed as long as only one additive is used at a time, i.e "James Williams Jr." or "James "One-Eye" Williams". Admins may get involved if your name is dumb and can approve or disallow names at their discretion while in-game.
- Excessively OOC is defined as names which are intentionally hard to read/spell, references to in-game mechanics or OOC terminology, and any form of nonsensical/bad-faith name (ex. Adolf Hitler, FAGGOT PUNCHER, Poop Boy, xXrobustspaceman420Xx etc).
- Clowns, mimes, silicons, wizards, and nuke ops have significantly more leeway in choosing their names, but try to be reasonable.
- References to the current round, even if vague; is still considered being IC in OOC.
- Due to their tendency to reveal a lot of information from the current round, streaming is not permitted on our servers, with the exception of special events pre-designated by admins.
- Using netspeak terms like "ur", "wtf", "lmao" etc. IC is considered OOC in IC, as are emoticons like ":)".
IC/OOC Related Rulings
| Referencing the gamemode ICly | It's OOC in IC if you say something similar to "It's revs" but it's okay if you say "There is a revolution." Basically make it sound like you're not referencing the fact that you're in a round. | PKPenguin321 |
| Pile on ick ock | Pile on ick ock is defined as a bunch of people teasing someone for IC in OOCing. It's okay until it crosses the line into being spam. Admins can mute OOC/individual players if it gets to that point. | Ausops |
| IC reactions to OOC in IC | It's okay as long as you're not crossing the line into OOC in IC. | Ausops |
Rule 4 Precedents.
- Non-antagonists are allowed to assist antagonists given sufficient IC reasoning but assisting an antagonist doesn't mean you get to act like one . If in doubt, ask an admin if a particular action is okay. Depending on the level of assistance, sufficient IC reasoning could be simply treating everyone who goes into medbay regardless of them being a murderer or not, all the way to being threatened under pain of death by an antagonist to do something.
- The relationship between xeno queen and xeno is treated the same as malf AI and borg, and are considered team antagonists for the purpose of main rule 4. Xenos should prioritize following the directions of their queen where possible.
Antagonist Directive Priorities
- In situations where you wind up with multiple simultaneous antagonist assignments (i.e. a Revolutionary and a Traitor), your team goals, objectives, and directives should take precedence. Furthermore, if someone had to go out of their way to convert you to their team, their goals, objectives, and directives become the priority. Refer to the following flowchart:
- Brainwashing/construct orders/Silicon Laws -> Cult -> Revs -> Blood Brother -> Wizard Apprentice/Abductor Teams/Other niche antags -> Nuke Ops -> Traitors
Antagonist Rulings
Rule 5 Precedents.
- Minimum levels of effort for heads of staff, silicon roles, and team antagonist generally include not logging out/going AFK at or near round start due to the importance of those roles within the round for progression. Constant logging out or going AFK may be given warnings by admins, and may progress to jobbans.
- Ghosting out, going AFK, suiciding, or logging off when converted to a team antagonist position can result in warnings from an admin; extending to bans for repeated behaviour from an individual. This also extends to when Command/Security mindshield implanting an individual to their side in said modes. At most within team antagonist, it is expected players to not maliciously harm their team's progress and assist if they are able to the best of their abilities.
- Let an admin know if you cannot or do not want to play any of the above mentioned roles. Admins will attempt to transfer the role to someone else. Obviously, if an admin does so for a player, the player must not use knowledge of that antagonist position existing.
- Abuse of position; as in being deliberately incompetent or malicious in their position is not allowed. Deliberate incompetence or malice can result in warnings or bans, depending on severity. Example would be a chemist constantly abusing the position to make space lube and lubing hallways, they may be warned and then jobbanned if further abuse happens.
Rule 6 Precedents.
- Incidents of admin abuse or negligence should be reported along with a date and time, along with details to pinpoint the incident in the logs, to any full admin via IRC or forum PM or posted on the admin complaints sub-forum located at https://tgstation13.org/phpBB/viewforum.php?f=23 or taken to the #supportbus IRC channel on the Rizon network. Incidents of poorly conducted admin events may also be taken to https://tgstation13.org/phpBB/viewforum.php?f=37 in their respective feedback threads, for less serious complaints.
- Lying in adminhelps, misrepresenting facts deliberately, or logging off when an admin has asked a question may result in permabans. Admins will not automatically place bans for players logging off however, and will generally wait a while in case real life situations caused a player to disconnect or go AFK.
| Adminshopping | Admin shopping is defined as going to different admins until you get a favorable ruling. It's highly frowned upon, don't do it. | Feemjmeem/Agreed with by other headmins |
| Admin intervention without anyone ahelping | It's allowed. | Ausops |
| Killing nonhostile admin spawned entities | Against the rules, don't do it. | PKPenguin321 |
Silicon Policy
Law Policies
Overview
- 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.
- Voluntary debraining / cyborgization is considered a nonharmful medical procedure.
- Involuntary debraining and/or borging of a human is harmful and silicons must prevent as any other harmful act.
- 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 Server Rule 1:
- Declaring silicons as rogue over inability or unwillingness to follow invalid or conflicting orders.
- Ordering silicons to harm or terminate themselves or each other without good cause.
- 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.
- Threatening self-harm to force an AI to do something it otherwise wouldn't.
- 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 the upload 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 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.
- If the person has a right to be in the upload, 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 access be accompanied by another trustworthy human or a cyborg.
- Probable cause includes, but is not limited to:
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.
- While Human Harm can be cause to impede Security, note that this should only be done so far as preventing immediate likely harm. Attempting to permanently lockdown Security or detain the entire Security team is likely to fall afoul of Server Rule 1 even with cause.
- 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?
| AI / cyborgs | Not human |
| Monkeys | Not human |
| NPCs / critters / animals | Not human |
| Hulks | Not human as long as their hulk is active. |
| Lizards / Plasmamen / Flypeople / Catpeople | Not human |
| Wraiths & revenants | Not human |
| Blobs | Not human |
| Syndicate traitors | Human |
| Nuclear Operatives | Human |
| Magic Users (wizards, cultists, heretics) | Human |
| Gang leaders and members | Human |
| Changelings | Human UNTIL the AI or cyborg WITNESSES the creature commit a non-human act (shape-shifting, transforming, proboscis etc). |
| Angels (Winged Humans) | Not Human |
| Corpses (Dead Humans) | Not Human (You can't space them for no reason though.) |
Silicon Headmin Rulings
Past rulings from Head Admins about Silicon Policy.
Silicon Protections Rulings
| Detonating cyborgs with little reason/alternatives | Don't do it. | Ikarrus |
| Spacing brains, MMIs, and intellicards | You can always do it as an antagonist, you should have a very good reason as a nonantagonist. | Dorsidwarf/Ausops |
| Roboticists making unslaved borgs for no reason | Link to relevant thread. The discussion derailed into code discussion but the ruling is that roboticists cannot make unslaved borgs for no reason. | |
| Calling silicons rogue for little/no reason | Against the rules, don't do it. | TehSteveo/KorPhaeron |
| Laws ordering silicons to kill themselves | Whether silicons have to follow it depends on wording of law. You must have a good reason as a nonantagonist and you're free to do it as an antagonist. | Ausops |
| Can you order force-borged cyborgs to pick a certain module? | Yes. | Scaredy/An0n3 |
Is It Harm? Rulings
| Silicons and harm in situations where you can't tell if they're being harmed or not. | Use common sense to decide if harm is going on. | |
| Is mindswap considered harm? | No, but if an Asimov silicon has mindswap and is ordered not to use it by a human, it can't use it. This is kind of an edge case. | Jordie0608 |
| Is slipping human harm? | Only if the object they're holding falls on them and causes brute damage. | Ausops |
| Silicons and Fight Clubs | It's considered self harm if they're willingly fighting. Silicons shouldn't interfere if it's self harm. If they're being forced to fight, it's human harm and silicons should intervene. | Thunder12345/Agreed with by headmins |
Is It Human? Rulings
| Holoparasites and Asimov | Holoparasites aren't human- a cyborg can attack the holoparasite but not the human. If the parasite recalls and the human is in critical, the borg must give him medical attention. | KorPhaeron and Shadowlight213 |
| Asimov and Corpses | Corpses aren't human. You can't space them for no reason though. | Shaps/Lzimann |
| Are augmented humans still human? | Yes, they are. There's a helpful chart in silicon policy to help explain this, reference that and adminhelp if there's still a question. | Scones |
| Is chaplain with dark blessing human? | Chaplain with a dark blade is human. It's a fancy arm add on. We don't make people silicon for having augments, even full ones. | Hulkamania |
Silicons and Security Rulings
| AIs shutting security down because of law one (discussion) | This is already covered in silicon policy. Here's the discussion thread on it. | |
| Silicons and Prisoners | If a nonharmful prisoner asks to be released, they can be released. If a harmful one asks to be released, don't release them unless security is harming them. In all cases release prisoners being harmed by security. (assuming all prisoners are human and you are asimov) | PKPenguin321 |
Silicons and Antagonists Rulings
| Cyborgs alerting the crew they're about to be emagged | You can tell the crew you are about to be emagged, but once you have traitor laws, you must follow them. | |
| AI suiciding to prevent subversion | Context: |
KorPhaeron |
| Asking to be deconstructed and then outing person who emagged you as an emagged borg | Don't do it. | PKPenguin321 |
Laws Rulings
| Do wizards mindswapped into a silicon have to follow laws? | Yes, they do. If you have laws then you must follow them unless you have a law zero. (When in doubt, adminhelp it.) | Ikarrus |
| AIs asking for law changes | An Asimov silicon cannot ask their laws to be changed. | HotelBravoLima |
| Letting people in to upload laws | If the person has a right to be there, 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. | Armhulenn |
| Do caks remember past lives? | Yes. Not really silicon policy but it's related to MMIs/borging. | KorPhaeron |
| Silicons using leet speak | Silicons are not allowed to leet speak (e.g. l33t sp34k), but typing in a 'glitchy' manner is allowed on roleplay grounds | Hulkamania |
Drone Rulings
| Are drones valid? | Only if they do something to annoy you. Mass killing drones for no reason is not okay. | KorPhaeron |
| Drones and permabrig | You can go in to fix damage. You might still get dronebanned if you let people out, it will likely be handled case-by-case. | |
| Do silicons count as a being under drone laws? | Yes, treat them as any other crew member. | QuartzCrystal |
Law Interpretation Rulings
Outdated Silicon Headmin Rulings
These rulings are no longer relevant, primarily due to code changes.
| Drone Policy Guidelines | Guide to drone policy. | Stickymayhem |
| Drones and atmospherics | Improving atmos is okay. Cutting pipes/turning off plasma is not okay. Fighting the symptoms of plasma in the distro is fine though. | Shadowlight213 |
| Drones building autocloners | Fine unless done to interfere with other players. | Ausops |
| Drones and Powersinks | Drones cannot destroy powersinks under the same logic of them not being able to defuse bombs or stop plasma floods. | Ausops |
| Security Cyborg Policies | Just a few random questions related to security cyborgs. If a cyborg is acting as security/releasing prisoners then this is probably relevant as well. Link to answers. | Pandarsenic |
| Asimov and gang dominators | This can probably be applied to other nonharmful antagonist objectives. If a human orders you not to destroy it, don't destroy it. Other than that, Asimov does not forbid you from destroying it. | Ausops |
| If a borg linked to a rogue AI is emagged then does the emagged laws or AI law zero take priority? | Very niche case and is probably impossible since emags should sever the connection to the AI. Starmute made a good post on AI law priority if you are confused. |