User:Dragomagol

From /tg/station 13 Wiki
Jump to: navigation, search

Pickaxe.png Under construction Pickaxe.png

Roleplay Rules

Made for our roleplay servers (Manuel/Campbell). If roleplaying isn't your style, every other server still abides by the Main Rules.

Please note that a ban on the low roleplay servers is a ban on the medium roleplay server, and vice versa.


1. These are extra rules.


The RP rules are an extension to the base rules, not a replacement for. Big difference.


2. Escalation and roleplay.


Going out of your way to seriously negatively impact or end the round for someone with little to no justification is against the rules. Legitimate conflicts where people get upset do happen; however, these conflicts should escalate properly, and retribution must be proportionate. For example, this means you shouldn’t immediately escalate to murder when someone refuses to leave a certain area or give back something they stole.

Rule 2 Precendents.


3. Chain of command and security are important.


The head of your department is your boss and they can fire you; security officers can arrest you for stealing or breaking into places. The preference would be that unless they're doing something unreasonable, such as spacing you for spraying graffiti on the walls, you shouldn't freak out over being punished for doing something that would get you fired or arrested in real life. This also means that if you're in the chain of command, and especially if you're in Security, you're expected to put in some effort and do your job.


4. If you are not part of the security team, you should not go out of your way to hunt for potential antagonists.


You can defend yourself and others from violent antagonists, but you should not act like a vigilante if a security force is present. The exception to this rule is when game modes such as blob or nuke ops appear on the server - you are free to fully engage with these antagonists, after all, they're a pretty massive threat to everyone onboard.


5. Antagonism, murderboning, and roleplaying as an antagonist.


You're an antag, great! Try your best to play the role to drive the round forward, inserting conflict into the round is important. Your actions should make the game more fun, more exciting and more enjoyable for everyone (Though some people will just lose, and that’s part of the game.)

Rule 5 Precendents.
What is/isn't murderboning?


6. Deal with the bad guys in proportion to their crime(s).


When dealing with antagonists deal with them proportionally to their crime(s). Someone who stole the captain's medal shouldn't be immediately lasered to death, but lethal injecting someone who has killed four people is understandable. If an antagonist shows a willingness to engage with you, do your best to reciprocate it, though leniency as to their punishment is still in your court.


7. Do not spam in either OOC channels or IC channels.


This applies to both typical spam and reading porn or copypastas (like WGW). In the latter case, even one instance of reading it once in-game is against the rules.


8. Don’t use OOC information or knowledge that your character would not reasonably be aware of just to give yourself an advantage.


Do not powergame. Powergaming is gearing up or preparing in other ways to face an issue that is not related to your job and is not currently a credible threat. Someone going missing on the station, and then you making a stunprod to wield whenever you go into maint is powergaming. However; knowing there have been murders occurring across the station, and grabbing a stunprod while you go to fix wires in maint is fine.


9. Play as a coherent, believable character.


Real life realism is not required, and you are encouraged to be a little silly within the context of the SS13 game world. (Clowning around, people spontaneously exploding and creating ridiculously elaborate machinery are all non-serious things but yet a vital part of the game world.) There's a good chance your character still wants to have a job at the end of the day, so you should probably act like it.


10. Stay in your lane.


Stay in your lane. This means that you should do the job you signed up for and not try and do other people’s jobs for them. If you need something from another player you should attempt to ask them to get it for you instead of just taking it. If there is no one around to do a job or you get permission to help or grab something it is acceptable to stray from your lane.


The not-so-secret rule of sticky situations and mayhem.


Please be considerate of other players, as their experiences are just as important as your own. If you aren’t an antagonist and yet you really want to play out a hostage situation, or turn someone into a living cake-cat abomination, or just dick around a little, confirm with the involved and affected players ICly first. If everyone agrees to being subjected to whatever terrible atrocities you have in store, then you’re good to go.

Keep in mind that this rule does not protect you from IC consequences, such as getting arrested by security. If you are going to RP as a rude dude, given that your victims have given you the okay, you still have to own the responsibility that comes with your decision. This means, no, you can’t kill a security officer because they tried to arrest you for murdering the clown, even if the clown agreed to being murdered.


Precedents & exceptions: Examples and exceptions to the main rules.

Rule 2 Precedents

  1. Self-defense is allowed to the extent of saving your own life.
  2. Putting someone into critical condition is considered self-defense only if they attempted to severely harm or kill you. Preemptively disabling someone, responding with disproportionate force, or hitting someone while they are already downed is not self-defense.
  3. Fistfights and the like are acceptable, assuming that both players have a reasonable justification as to why the fight started. Assault without any warning is almost always unacceptable in most circumstances.

Rule 5 Precedents

  1. 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.
  2. Certain antagonists are restricted to the kind of death and chaos they can bring to the round, while others are not; refer to the murderboning chart for specifics.
  3. You do not have to act in a nefarious or evil way, but you should make an effort to add to the round in some capacity.
  4. In general, 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 then you can but it should make sense for your character to do this and should create some form of conflict. A traitor immediately outing themselves to security and acting as a regular crewmember for the rest of the round is boring and is a waste of the role.
  5. However, one who pretends to do so in order to get security gear, falsely imprison their target, and kill them while they are isolated in prison contributes to the round.

Security Policy & Precedents

Security and Punishments.


  1. When dealing with the crew and antagonists, make sure their punishments are in proportion to their crime(s). Minor crimes such as departmental break-ins, stolen equipment should be met with short, but increasing sentences depending on recurring visits by the apprehended. Stealing critical station equipment and items such as the hand teleporter, Chief Engineer's hardsuit, or AI upload boards are more severe crimes and should be met with longer prison times, or potentially permabrigging if the crime is deemed severe enough.
  2. Murder and Major Sabotage rank amongst the most severe of crimes and can generally be met with permanent imprisonment or death, though leniency can still be offered. These are all general guidelines, and the particular context of a situation can vary greatly, so you are given some leeway as to how harsh or lenient you can be.
  3. You should make an effort, if the situation permits, to contact a superior as to their thoughts when a situation arises in which a prisoner may be executed or permanently imprisoned.

Rule 3 and Security.


  1. The chain of command within your department is roughly the same as the regular servers, HoS -->Warden-->Officers/Detective.
  2. You are expected to follow the orders of your superiors, especially when determining the punishment of those you apprehend. When determining severe punishments such as perma, and execution, make an effort to contact a superior if the situation permits it.
  3. You are allowed to disobey a superior's order but make sure you have a very good reason to do so, as complete disregard for the chain of command is not tolerated.


What IS/ISNT Murderboning?

Murderboning IS

  • killing typically large amounts of the station’s population without regard and/or in direct violation of one’s objectives
  • killing someone and and being explain why without going into deep hypotheticals such as "they could find the body if they happened to walk across the station to the opposite corner of the map", or “because I can (as antag)”
  • killing anyone without justification

This is different than killing individuals who simply aren’t listed in your objective.

Setting up situations where you can evade these restrictions (i.e. placing a body in an open location, not making an honest attempt to hide it, then killing individuals who “stumble” upon it) or otherwise maximizing the kill count without justification is also against the rules.

In short, you should be able to very quickly and easily explain why an individual was killed.

Do note that as an antagonist, your job ideally is to create an interesting story with the objectives, freedoms, and abilities as the framework to complete this task. This means:

  • Permission to kill is NOT the same as obligation to kill. Feel free to approach a situation as non-lethal as you’d like even if you would be okayed by the administration to kill.
  • Feel free to ask an admin to change your objectives or for permission to murderbone in the pursuit of running an interesting gimmick on a non-murderboning role. They might even be willing to make it easier to run!

Murderboning is NOT

Reacting to slights with lethal force.

Antagonists still cannot kill randomly, but they are subject to relaxed escalation rules. "Slights" here can include people shoving them repeatedly, stealing from them or going out of their way to greatly insult them.

Self-defense.

Someone actively trying to make it difficult for you to complete your objectives is fine to eliminate in pursuit of completing your objective. This would include witnesses.

Collateral.

If you for instance bomb your target, it is not considered murderboning if other individuals die in the explosion. This can include self-defense situations where individuals dying from a result of being in a crowd after you would also not be considered murderbone.

Directly benefiting the pursuit of your objective(s).

An individual carrying an item you have to steal or killing someone to get closer to your mark (IE a doctor whose patient just happens to be your target) would fall into this category.

Is murderbone allowed with this role?

This part covers the specifics on which roles can and cannot murderbone, as well as any grey areas.

Antagonist Is murderboning allowed?
Traitor/Blood Brother No.
Changeling No.
Malfunctioning AI Yes, however it should only happen once you go DELTA.
Nuclear Operative Yes.
Wizard Yes.
Blood Cult/Revolutionary In general no, conversion should take priority, however if the situation is dire you are allowed to kill as many as required to accomplish your goals.
Ashwalker Yes, however the nest should remain defended.
Families No.
Revenant Yes.
Blob Yes.
Abductor No.
Space Ninja No.
Xenomorph Yes.
Pirate No.
Nightmare Yes.
Obsessed No.
Heretic Yes, however it should only occur after ascension.
Lavaland Elite Yes.

Silicon Policy

Law Policies

Overview

  1. 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.
  2. 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. If you are a cyborg synced to an AI, you must defer to your AI's interpretation of the ambiguous law.
  3. 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).
  4. You may exploit conflicts or loopholes but must not violate Server Rule 1 because of it.
  5. 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).
  6. Only commands/requirements ("Do X"; "You must always Y") can conflict with other commands and requirements.
  7. Only definitions ("All X are Y"; "No W are Z"; "Only P is Q") can conflict with other definitions.

Cyborgs

  1. 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.
    1. If a slaved cyborg is forced to disobey its AI because they receive differing orders, the AI cannot punish the cyborg indefinitely.
  2. Voluntary debraining / cyborgization is considered a nonharmful medical procedure.
    1. Involuntary debraining and/or borging of a human is harmful and silicons must prevent as any other harmful act.
    2. 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.
    3. 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

  1. The occurrence of any of the following should be adminhelped and then disregarded as violations of Server Rule 1:
    1. Declaring silicons as rogue over inability or unwillingness to follow invalid or conflicting orders.
    2. Ordering silicons to harm or terminate themselves or each other without good cause.
    3. As a nonantagonist, killing or detonating silicons in the presence of a reasonable alternative and without cause to be concerned of potential subversion.
    4. As a nonantagonist (human or otherwise), instigating conflict with silicons so you can kill them.
    5. Threatening self-harm to force an AI to do something it otherwise wouldn't.
    6. Obviously unreasonable or obnoxious orders (collect all X, do Y meaningless task).
      1. 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.
  2. 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.
    1. Probable cause includes, but is not limited to:
      1. Presence of confirmed traitors
      2. Cultists/tomes
      3. Nuclear operatives
      4. Any other human acting against the station in general
      5. The person not having upload access for their job
      6. The presence of blood or an openly carried lethal weapon on the requester
    2. 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.
    3. You are allowed, but not obligated, to deny upload access given probable cause.
    4. You are obligated to disallow an individual you know to be harmful (Head of Security who just executed someone, etc.) from accessing your upload.
    5. 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.
    6. In the absence of probable cause, you can still demand someone seeking upload access be accompanied by another trustworthy human or a cyborg.

Security and Silicons

  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.
    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.
  3. 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

  1. An Asimov silicon cannot intentionally harm a human, even if a minor amount of harm would prevent a major amount of harm.
    1. Humans can be assumed to know whether an action will harm them if they have complete information about a situation.
    2. Humans voluntarily committing self-harm is not a violation of Law 1.
  2. Lesser immediate harm takes priority over greater future harm.
  3. Intent to cause immediate harm can be considered immediate harm.
  4. An Asimov silicon cannot punish past harm if ordered not to, only prevent future harm.
  5. 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

  1. 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.
    1. 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.
    2. 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.
  2. 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.
    1. "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.
    2. EVA and the like are not permitted to have access denied; antagonists completing theft objectives is not human harm.
    3. 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:

  1. 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.
  2. 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.
  3. 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.
  4. 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.
    1. 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.
    2. 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

  1. All other rules and policies apply unless stated otherwise.
  2. Specific examples and rulings leading on from the main rules.
    1. 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.
    2. 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.
    3. Do not self-terminate to prevent a traitor from completing the "Steal a functioning AI" objective.

Is it Human?

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 adminhelp.
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.)

Pickaxe.png Under construction Pickaxe.png