|
|
| 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 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. |
|
| |
|
| Similarly, LRP players should be able to rely on concepts they understand from LRP as much as possible. To aid this goal when it comes to non-objective kills, antags rely on super relaxed escalation from the main server rules. In a sick twist of fate, they can even escalate against people who don't RP with them and try to avoid all contact and communication - in addition to people who are overly polite, nice, kind or helpful because the weak should fear the strong.
| | =Silicon Policy & Lawset Guidelines= |
| | | ==Law Policies== |
| {{Rule
| | ===Overview=== |
| |title=Other headmin-driven changes
| | # If a law is vague enough that it can have multiple reasonable interpretations, it is considered ambiguous. |
| |body=Roundstart malf AI disabled in return for midround malf AI having the shackles removed?
| | ## 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). |
| {{Rule
| | # You may exploit conflicts or loopholes. |
| |title=Optional examples left out of the rules for brevity
| | # 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). |
| |body=For example, an antagonist whose character is a Syndicate loyalist can't kill people just because of that. But if such a Syndicate loyalist witnesses someone spreading anti-Syndicate propaganda, this could reasonably lead to a fight and the other player's death. If they got revived and were witnessed doing it again, escalation may permit round removal.
| | # 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. |
| For example, an antagonist should not pre-emptively attack a department just because they may hypothetically get in the way of completing objectives. That antagonist would instead need to investigate or infiltrate the departments to build up a reason for attacking them, such as medbay monitoring suit sensors and sending paramedics out to anyone whom gets hurt or security actively arresting, brigging and especially executing people.
| |
| }}
| |
| | |
| = Reworded Rule 5 and Modified Precedents =
| |
| <!-- ---------------- RULE 5 ---------------- -->
| |
| {{Rule
| |
| |title=5. Antagonism and roleplaying as an antagonist.
| |
| |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 modesty 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.
| |
| | |
| :[[#RP Rule 5 Precedents|Rule 5 Precendents.]]
| |
| :[[#Antag Death and Destruction|Antag death and destruction.]]
| |
| }}
| |
| | |
| <!-- ---------------- RP RULE 5 PRECEDENTS ---------------- -->
| |
| {{anchor|RP Rule 5 Precedents}}
| |
| {{Rule
| |
| |title=Rule 5 Precedents
| |
| |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.
| |
| #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 =
| |
| <!-- ---------------- DEATH AND DESTRUCTION WITH OBJECTIVES ---------------- -->
| |
| {{anchor|With Objectives}}
| |
| {{Rule
| |
| |title=With Objectives
| |
| |body=Antagonist objectives are the core of what antagonists are allowed to directly do with no or limited roleplay reasoning. There is no hard limit on this freedom and actions taken to directly accomplish an objective do not have to be proportionate.
| |
| | |
| Causing death and destruction to help with indirectly accomplishing objectives must have an in-character roleplay reason. If questioned about a chain of events involving indirect actions, the antagonist should be able to clearly explain what events in the current shift led them to their course of action without resorting to hypotheticals.
| |
| | |
| If a player or department directly interferes with the completion of an objective, this is no longer a hypothetical as the antagonist can now point to specific events in the shift to justify their actions.
| |
| | |
| 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.
| |
| }}
| |
| | |
| <!-- ---------------- DEATH AND DESTRUCTION WITHOUT OBJECTIVES ---------------- -->
| |
| {{anchor|Without Objectives}}
| |
| {{Rule
| |
| |title=Without Objectives
| |
| |body=When wanting to cause death and destruction not related to objectives, restricted antagonists may instead rely on extremely relaxed escalation.
| |
| | |
| They may escalate lethally sooner and with less justification, may use more lethal methods to escalate and may rely on antagonistic reasons for escalating. Such reasons may include escalating against people who are excessively polite or helpful as well as being mean or rude, escalating against groups of people who exclude them or escalating against people who ignore or avoid attempts to communicate entirely.
| |
| | |
| They have no obligation to treat their victims, but escalating over minor issues should not result in the antagonist taking steps to permanently round remove the other player unless escalation policy would otherwise permit it.
| |
| }}
| |
| | |
| <!-- ---------------- RP REQUIREMENT CHART ---------------- -->
| |
| {{anchor|Is this role ?}}
| |
| {{Rule
| |
| |title=Does this role have additional RP requirements for death and destruction?
| |
| |body=This part covers the specifics on which roles do and do not have to follow the roleplay requirements on causing death and destruction.}}
| |
| {| class="wikitable"
| |
| |-
| |
| |'''Antagonist'''
| |
| |'''Do additional roleplay requirements on death & destruction apply?'''
| |
| |-
| |
| |[[Traitor]]/Blood Brother
| |
| |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.
| |
| |}
| |