Update rules (#28452)
This commit is contained in:
Chief-Engineer
@@ -0,0 +1,26 @@
|
||||
<Document>
|
||||
# Roleplay Rules
|
||||
These rules only apply during a round. A round ends only when the round summary has appeared. All of these rules apply fully until the moment that the round summary appears, even while the arrivals shuttle is in transit.
|
||||
|
||||
The deathmatch and sandbox game modes are exempt from these rules. Players who choose to not follow these rules are entirely responsible for knowing if an exempt game mode is active.
|
||||
|
||||
Roleplay rules do not apply to ghosts/spectators/observers while they are ghosts/spectators/observers. Dead chat is considered to be an in-game out of character chat channel.
|
||||
|
||||
See the list of [textlink="role types" link="RoleTypes"] for more information about the different types of roles.
|
||||
|
||||
- [textlink="1. Silicones must follow Silicon Rules" link="RuleR1"]
|
||||
- [textlink="2. Familiars must obey their master" link="RuleR2"]
|
||||
- [textlink="3. Roleplay a normal person" link="RuleR3"]
|
||||
- [textlink="4. Do not metagame, obey the Metashield" link="RuleR4"]
|
||||
- [textlink="5. Don't interfere with arrivals" link="RuleR5"]
|
||||
- [textlink="6. Don't act like an antagonist unless the game tells you that you are one" link="RuleR6"]
|
||||
- [textlink="7. Do not stall the round" link="RuleR7"]
|
||||
- [textlink="8. As an antagonist, only be friendly to your team and don't work against your team" link="RuleR8"]
|
||||
- [textlink="9. As an antagonist, do not cause excessive death, damage, or destruction beyond your objectives" link="RuleR9"]
|
||||
- [textlink="10. Listen to your team leader" link="RuleR10"]
|
||||
- [textlink="11. Follow reasonable escalation" link="RuleR11"]
|
||||
- [textlink="12. Do not abandon your role" link="RuleR12"]
|
||||
- [textlink="13. Stick to your role" link="RuleR13"]
|
||||
- [textlink="14. Set an example if playing command or security" link="RuleR14"]
|
||||
- [textlink="15. Command and Security must follow Space Law" link="RuleR15"]
|
||||
</Document>
|
||||
@@ -0,0 +1,26 @@
|
||||
<Document>
|
||||
# Roleplay Rule 10 - Listen to your team leader
|
||||
Captains lead all departments and other members of command. Department heads lead members of their department. Certain antagonist teams have team leaders, like nuclear operative commanders or head revolutionaries. You are not required to perfectly follow orders given to you by your leaders, but you should generally allow your leaders to lead and not interfere with their ability to. You can choose to ignore unreasonable orders, including ones which are will result in your death unless you are an antagonist with an objective that requires you to die.
|
||||
|
||||
Team antagonists have to listen to the leader of their antagonist team. Team antagonists do not have to listen to any other leaders, including leaders of other antagonist teams. Solo antagonists do not have to listen to any leaders at all.
|
||||
|
||||
## Examples
|
||||
Acceptable:
|
||||
- A traitor ignores orders from a nuclear operative commander.
|
||||
- An antagonist ignores orders from the captain.
|
||||
- An engineer tells the Chief Engineer that they don't think it's a good idea to setup the singularity, but does so anyway when ordered to.
|
||||
- An engineer tells the Chief Engineer that they don't know how to setup the singularity correctly, so refuses orders to, but accepts an offer to be taught how.
|
||||
- An atmospheric technician refuses an order from the captain that would create an atmospheric hazard on the station.
|
||||
- A doctor refuses an order from the Chief Engineer about who to give medical treatment to first.
|
||||
- A revolutionary refuses a suicide mission from a head revolutionary.
|
||||
- The Chief Engineer doesn't follow an order from the captain to setup backup power because there is an unrelated engineering emergency that the Chief Engineer needs to prioritize.
|
||||
- The captain orders command to give the nuclear authentication disk to nuclear operatives, so command arrests the captain and picks a new captain.
|
||||
- The research director orders scientists to say "Long live Nanotrasen!" every time they enter the bar. The scientists say they will, but don't follow the order.
|
||||
|
||||
Prohibited:
|
||||
- A nuclear operative ignores an order from the commander operative because they don't like the plan.
|
||||
- The Chief Engineer refuses an order from the captain to setup backup power because the Chief Engineer doesn't think backup power is necessary.
|
||||
- An engineer refuses an order from the Chief Engineer to setup the singularity because they prefer a different power source.
|
||||
- An engineer refuses to perform a task because they don't know how to do it, and refuses to be taught for no reason.
|
||||
- A head revolutionary orders revolutionaries to blend in and not do anything illegal until they are told to reveal themselves. Instead, revolutionaries collect weapons and attack security.
|
||||
</Document>
|
||||
@@ -0,0 +1,36 @@
|
||||
<Document>
|
||||
# Roleplay Rule 11-1 - Escalation Involving Animals
|
||||
Escalation rules are looser with animals than with people. These looser requirements do not apply to the requirements other people attacking each other have, even if their fighting is directly related to the conflict involving the animal.
|
||||
|
||||
Non-pets, such as mice and monkeys, can be freely killed with any IC reason such as pest control, or for food. These roles are often available in numbers as ghost roles, so removing one from the round doesn’t typically remove them all.
|
||||
|
||||
Pets, including but not limited to Ian, Renault, Remilia, and Hamlet, cannot be freely killed, they require escalation. These roles are often available once per round at most, except roles like Remilia.
|
||||
|
||||
Permanently trapping an animal, such as putting a mouse in a plant, is considered similar to killing the animal so should only be done with an IC reason.
|
||||
|
||||
Both sides can escalate much more rapidly than they'd be able to if both were people. Animals are often more limited in the maximum force they can use compared to people, which limits the negative effects of them rapidly escalating. Animals also typically have less health than people, and are limited in the ease with which they can get healing, which justifies them responding to even weak attacks more severely.
|
||||
|
||||
Neither the animal nor the person is obligated to get the other medical attention if they are put into crit. Attacking someone to death rather than stopping once they are in crit is considered a significant difference. While sufficient escalation may justify continuing to attack, generally people and pets shouldn't continue to be attacked once in crit, but non-pets may be. Gibbing is also considered a significant step because it prevents cloning or resuscitation. The fact that an animal made the last hit putting someone into crit does not allow people who fought on the side of the animal to not attempt to get them medical attention.
|
||||
|
||||
The use of sensible, non-targeted mousetraps is not a conflict and does not require escalation.
|
||||
|
||||
The killing or attacking of pets can be treated as an escalation step by players with a genuine IC connection to the animal. Generally, all crew can consider themselves to have an IC connection to any station pets. The degree of escalation should be proportional to the connection to the pet, in addition to the usual requirement of being proportional to the attack. For example, an attack on Ian can be treated nearly identically to an attack on a crewmember, whereas an attack on a pet mouse is much less severe. Normal escalation limits still apply, you cannot attack people who defended themselves from an animal that randomly attacked them, just as you could not attack someone who defended themselves from a coworker that randomly attacked them.
|
||||
|
||||
Crew can "adopt" non-pets, like mice, and consider themselves to have a connection to the animal if they roleplay the adoption well. This does not affect the requirement of whether other players are required to apply escalation rules to these animals, it only creates a connection that can be used to justify retaliatory escalation to attacks by the adopter. Simply saying that they've adopted an animal is not sufficient, but carrying it with them is. The degree of connection is proportional to IC actions. Crew cannot consider themselves to have a connection for escalation purposes to animals which are typically hostile, such as space carp or bears.
|
||||
|
||||
## Examples
|
||||
Acceptable:
|
||||
- A chef kills mice who enter or approach their kitchen.
|
||||
- A janitor kills mice roaming the station.
|
||||
- A lizard kills a mouse to eat.
|
||||
- A chef has carried a mouse around in their hat for the last 10 minutes, they put the mouse down for a moment and another player kills it. The chef responds by attacking the other player with their fists and refusing them service for the rest of the shift.
|
||||
- Ian is randomly attacked, a crewmember who sees this happen crits the killer and brings them to security.
|
||||
- Hamlet goes into the kitchen and starts eating all the food. A chef sees this and starts swinging their knife at Hamlet. Hamlet starts biting the chef and crits them, then resumes eating.
|
||||
|
||||
Prohibited:
|
||||
- A janitor throws an armed mousetrap at Hamlet for no reason.
|
||||
- Hamlet starts biting random people, trying to crit them, for no reason.
|
||||
- A crewmember attacks security for killing a space carp they adopted.
|
||||
- Ian gibs someone who was trying to kill someone.
|
||||
- Hamlet attacks security for trying to arrest someone he likes.
|
||||
</Document>
|
||||
@@ -0,0 +1,30 @@
|
||||
<Document>
|
||||
# Roleplay Rule 11-2 - Examples of Conflict Types
|
||||
## Verbal
|
||||
- Shouting
|
||||
- Yelling
|
||||
- Insulting
|
||||
|
||||
## Non-harmful
|
||||
- Shoving
|
||||
- Stealing non-critical items, like easily replaced tools
|
||||
|
||||
## Non-lethal
|
||||
- Stealing items without endangering someone's life, like a clown's pie cannon or the HoP's fax machine
|
||||
- Stealing someone's ID somewhere that doesn't result in them being trapped
|
||||
- Punching
|
||||
- Disablers
|
||||
- Stun batons
|
||||
|
||||
## Lethal
|
||||
- Punching to crit or death
|
||||
- Attacking with strong weapons, like bats
|
||||
- Stealing items that endanger someone's life, like a hardsuit
|
||||
- Stealing someone's ID, trapping them in a dangerous situation
|
||||
|
||||
## Permanently lethal
|
||||
- Gibbing
|
||||
- Not taking someone who you killed or put into crit to the medbay or security
|
||||
- Hiding someone's body
|
||||
- Spacing someone's body
|
||||
</Document>
|
||||
@@ -0,0 +1,67 @@
|
||||
<Document>
|
||||
# Roleplay Rule 11 - Follow reasonable escalation
|
||||
Antagonists are fully exempt from escalation rules. Non-antagonists who are in a conflict with antagonists are not exempt. Escalation should typically follow steps or a pattern of conflict types similar to:
|
||||
- Verbal
|
||||
- Non-harmful
|
||||
- Non-lethal
|
||||
- Lethal
|
||||
- Permanently lethal
|
||||
|
||||
All new conflicts should start at the first step. A player should not escalate a conflict across steps without some escalation from the other party involved in the conflict. Players can skip steps to match the level of escalation that the other person is at, but should almost always not skip steps other than that. Players who attempt to deescalate conflicts will be given more leniency in escalating if the other party continues to escalate despite the attempt at de-escalation. You do not have to try to deescalate conflicts, but someone who watches you over the entire round, or over multiple rounds, should not feel that your goal is generally to escalate conflicts.
|
||||
|
||||
Conflicts or escalation can be indirect. When someone steals someone else's ID, the theft is a direct part of the conflict, but if the victim becomes trapped as a result of not having their ID to open a door, that is also considered part of the conflict and escalation. Do not randomly steal IDs from people.
|
||||
|
||||
Escalation does not have to be directed at a specific player to enter them into a conflict. Nuclear operatives who are trying to destroy the station are considered to be at the permanently lethal level of conflict with all crew on the station. Someone who kills a station pet has started some degree of conflict with all crewmembers. Someone who kills a mouse that a chef was caring for has started some degree of conflict with that chef.
|
||||
|
||||
You will be considered to be violating this rule if you escalate a conflict based on a poor or unreasonable assumption.
|
||||
|
||||
Conflicts should almost never reach the "permanently lethal" stage. Conflicts should only reach this stage if the other party brought it to the stage, or if the same conflict escalated to the lethal stage multiple times in the round.
|
||||
|
||||
If a party in the conflict goes into crit or dies, the party responsible should take them to get treatment or to security. For the conflict, this should be considered saving someone from dying and should deescalate the conflict. If the conflict is deescalated in this way, both parties need to re-escalate to lethal for the conflict to return to that stage. If the conflict is not deescalated in this way, then only the party who defeated the other would need to re-escalate for the conflict to return to the lethal stage.
|
||||
|
||||
Security can immediately escalate to non-lethal force if it is necessary to arrest someone.
|
||||
|
||||
People using or brandishing Syndicate items can typically be presumed to have lethal intent. Someone with lethal intent can typically be immediately escalated against at a lethal level, a notable exception is if you have the tools to safely detain them.
|
||||
|
||||
## Escalation Involving Animals
|
||||
See [textlink="Escalation Involving Animals" link="RuleR11-1AnimalEscalation"].
|
||||
|
||||
## Exemptions
|
||||
Escalation rules aren't enforced against non-players, but players will be held responsible for rule violations even if they don't realize that a character or animal was controlled by another player. Characters who have purple text saying that they are catatonic are considered non-players. Characters who are disconnected are still considered players.
|
||||
|
||||
## MRP Amendment
|
||||
Escalation rules are enforced even against non-players.
|
||||
|
||||
## Examples of Conflict Types
|
||||
See [textlink="Examples of Conflict Types" link="RuleR11-2ConflictTypes"].
|
||||
|
||||
## Example Scenarios
|
||||
These examples assume that you are not an antagonist.
|
||||
|
||||
Acceptable:
|
||||
- A player starts punching you, so you start punching back until they stop. If they go into crit, you stop attacking them and take them to security or to get medical attention.
|
||||
- You make fun of a clown, who then throws a pie at you and steals your shoes. You slip the clown and steal their mask.
|
||||
- You are a security officer and tell someone to stop, so you can question them. They run away, so you use your disabler to stun and cuff them.
|
||||
- You are a security officer and see someone wearing a syndicate hardsuit, so you shoot them to crit, cuff them, then take them to security.
|
||||
- You are a crewmember and see a nuclear operative, so you kill them.
|
||||
- An unauthorized person enters a high risk area of the station, like the armory or atmospherics, so you attack them until they leave.
|
||||
- Minorly inconveniencing someone for your own benefit.
|
||||
- As an antagonist, killing someone who got in your way.
|
||||
- As an antagonist, killing someone who didn't give you what you want.
|
||||
- A chef and bartender reach the lethal level of conflict through appropriate escalation. The chef crits the bartender and does not take them to medbay or security. The bartender immediately tries to crit the chef next time they run into each other.
|
||||
- A chef and bartender reach the lethal level of conflict through appropriate escalation. The chef crits the bartender and does not take them to medbay or security. The chef insults the bartender next time they see them.
|
||||
|
||||
Prohibited:
|
||||
- A player starts punching you, so you gib them.
|
||||
- A clown throws a pie at you and steals your shoes, so you stab them to crit with a screwdriver.
|
||||
- You are a security officer and tell someone to stop so you can question them. They run away so you use a truncheon to beat them to crit.
|
||||
- An authorized person who you think is unauthorized enters a high risk area of the station, like the armory or atmospherics, so you attack them until they leave.
|
||||
- An unauthorized person enters a low risk area of the station, like cargo, and you start attacking them with no other escalation.
|
||||
- Slipping security all round because they are security.
|
||||
- Blocking the head of personnel in their office using walls because they didn't give you what you asked for.
|
||||
- Hiding someone's body because they punched you earlier in the round.
|
||||
- Harassing the bar or bartender by frequently coming in to break their glasses or furniture.
|
||||
- Randomly picking fights with people.
|
||||
- A chef and bartender reach the lethal level of conflict through appropriate escalation. The chef crits the bartender and does not take them to medbay or security. The chef immediately tries to crit the bartender next time they run into each other.
|
||||
- A chef and bartender reach the lethal level of conflict through appropriate escalation. The chef crits the bartender and takes them to the medbay or security. The bartender immediately tries to crit the chef next time they run into each other.
|
||||
</Document>
|
||||
@@ -0,0 +1,28 @@
|
||||
<Document>
|
||||
# Roleplay Rule 12 - Do not abandon your role
|
||||
Do not join the round as a role that you don't intend to play. Do not enable antagonist roles that you don't intend to play. Abandoning a role includes not completing tasks that the role is expected to do, in addition to things like leaving the game. Members of command should almost all stay on the station until the emergency shuttle arrives. Enforcement of this rule is more strict for command and antagonist roles, and less strict for less important roles like passengers.
|
||||
|
||||
Violations of this rule typically result in temporary or indefinite role bans. We understand that you may need to leave round early or unexpectedly. If you are in an important role, you should notify command members or an admin via ahelp so that they know you are leaving. Space Station 14 is a game. Do not endanger the safety of yourself or others, and do not neglect important things to avoid leaving a round early, even if you have to leave immediately without notifying anyone. Role bans for disconnecting are typically only applied if there is a pattern, and are almost always temporary.
|
||||
|
||||
"Antag rolling" refers to a player abandoning their role if they do not get an antagonist role.
|
||||
|
||||
## Examples
|
||||
Acceptable:
|
||||
- As an engineer, building a bar in maintenance while there is nothing important for engineering to do.
|
||||
- As the captain, having the chef teach you how to cook while there is nothing important needing your attention.
|
||||
- As a passenger, building a shuttle with materials given to you by cargo and engineering.
|
||||
- Taking a short break from your job at the bar.
|
||||
- Getting an antagonist role and doing the bare minimum needed to complete your objectives.
|
||||
- Getting an antagonist role and making a genuine effort to complete your objectives, but failing to complete any.
|
||||
- Getting an antagonist role and intentionally not doing any of your objectives, but creating a similar level of disruption that completing your objectives would create.
|
||||
|
||||
Prohibited:
|
||||
- As an engineer, building a bar in maintenance while the station has no power.
|
||||
- As the captain, leaving the station to go on an expedition with the salvage team.
|
||||
- As an atmospherics technician, building a shuttle round start and never coming back to the station.
|
||||
- Spending your entire shift at the bar, even when there is work that needs to be done by your role.
|
||||
- Ghosting, suiciding, or leaving at the start of a round because you don't like the map or the players in your department.
|
||||
- Getting an antagonist role and not doing any antagonist activities.
|
||||
- Ghosting, suiciding, or leaving at the start of a round because you did not get an antagonist role.
|
||||
- Ghosting, suiciding, or getting yourself killed because nuclear operatives declared war, and you want to try to get an antagonist ghost role.
|
||||
</Document>
|
||||
@@ -0,0 +1,26 @@
|
||||
<Document>
|
||||
# Roleplay Rule 13 - Stick to your role
|
||||
Requesting job changes is not prohibited by this rule. This rule is loosened if the station is understaffed or if there is a significant threat to you.
|
||||
|
||||
Don't perform other people's jobs, especially where the relevance to you personally is low. This also covers performing the role of security.
|
||||
|
||||
## MRP Amendment
|
||||
This is enforced more strictly on MRP.
|
||||
|
||||
## Examples
|
||||
Acceptable:
|
||||
- As an engineer, helping the bartender remodel the bar.
|
||||
- As a bartender, remodeling the bar.
|
||||
- As a passenger, building a maintenance bar.
|
||||
- As an engineer, reinforcing substations.
|
||||
- As an engineer, increasing the security of airlocks.
|
||||
- As an atmospherics technician, improving atmospheric systems.
|
||||
- As a passenger, fighting nuclear operatives.
|
||||
- As a passenger, fighting or preparing to defend yourself from someone who has been trying to kill you.
|
||||
- As a crewmember on a station with no engineering department, you complete engineering tasks.
|
||||
|
||||
Prohibited:
|
||||
- As a passenger, reinforcing substations.
|
||||
- As a passenger, hunting for antagonists or lawbreakers.
|
||||
- As a passenger, fighting or preparing to defend someone else from someone who has been trying to kill a random crewmember.
|
||||
</Document>
|
||||
@@ -0,0 +1,37 @@
|
||||
<Document>
|
||||
# Roleplay Rule 14 - Set an example if playing command or security
|
||||
All command and security roles are held to stricter interpretations of the rules.
|
||||
- Command roles are not learning roles. Members of command must be competent.
|
||||
- Security roles are not for inexperienced players. Members of security are expected to know game basics and be more familiar with server rules than a new player.
|
||||
- Do not hinder or cause overall negative effects to the station or crew as a member of command or security.
|
||||
- Do not abuse your power as command or security.
|
||||
|
||||
## Why
|
||||
Members of command and security can often have a larger impact on the nature of the round than other players. For example, a captain who tries to bend or break the rules will often cause many others on the station to do the same. Memey station announcements from members of command also often result in the rest of the station acting the same way. When command and security members hold themselves to high standards, the rest of the station often naturally follows to a significant degree.
|
||||
|
||||
## Examples
|
||||
Acceptable:
|
||||
- A member of security accepts a bribe to deliver safe donuts to a prisoner who the HoS has ordered should only be given donk pockets.
|
||||
- A captain uses a station announcement to confess to an embarrassing mistake that they made during the shift.
|
||||
- In coordination with the head of security, a captain declares that the station will recognize the right to bear arms, so all crew can pick up a disabler at security.
|
||||
- The chief medical officer gives a paramedic their portable crew monitor to help them complete their job.
|
||||
- A syndicate agent is holding a crewmember hostage and threatens to kill them if the head of security doesn't give them their ID. Seeing no other safe option, the head of security hands over their ID to the syndicate agent, then begins working to re-secure it and capture the agent as soon as the hostage is safe.
|
||||
- Nuclear operatives are attacking the station, so the captain and head of personnel both go to the armory and take a weapon.
|
||||
- A majority of command votes to demote the captain for taking actions harmful to the station, then the head of security demotes the captain.
|
||||
- The captain promotes the head of personnel to captain.
|
||||
- Security releases an antagonist from the brig in exchange for the identities of other traitors.
|
||||
|
||||
Prohibited:
|
||||
- A member of security accepts a bribe to ignore a crime or help a prisoner escape.
|
||||
- A captain sends a ASCII art trollface over station announcements or as a fax to central command.
|
||||
- A captain declares that all contraband is legal.
|
||||
- Command or security allow the use of Syndicate items outside extreme emergencies.
|
||||
- The chief medical officer knowingly helps a syndicate agent complete their objectives.
|
||||
- A syndicate agent has killed 3 members of security so the head of security makes them an offer saying that they will space all the weapons in the armory if the syndicate agent stops killing.
|
||||
- The captain goes to the armory and takes a gun to display in his office without asking anyone, and orders anyone who questions him not to interfere.
|
||||
- Members of command decide to demote the captain to gain more power for themselves, or in retaliation for a decision that they didn't personally like or agree with, rather than because the decision was actually harmful to the station.
|
||||
- The captain promotes a random crewmember to captain.
|
||||
- A member of command gives a random crewmember substantial additional access for no reason, unnecessarily, or for a poor reason.
|
||||
- A member of command gives a random crewmember access to a high security area, like the armory or another member of command's office, for no reason, unnecessarily, or for a poor reason.
|
||||
- Security releases an antagonist from the brig in exchange for the antagonist buying them contraband.
|
||||
</Document>
|
||||
@@ -0,0 +1,21 @@
|
||||
<Document>
|
||||
# Roleplay Rule 15 - Command and Security must follow Space Law
|
||||
All non-antagonist command and security roles must obey [textlink="Space Law" link="SpaceLaw"]. This includes non-antagonists who are promoted to or gain a position during the round in any way. This also includes non-antagonists who are acting as a security role.
|
||||
|
||||
This prohibits use of syndicate items, including uplinks by command and security.
|
||||
|
||||
## Examples
|
||||
Roles that are included:
|
||||
- A security officer
|
||||
- The Captain
|
||||
- The Chief Engineer
|
||||
- A passenger promoted to "bounty hunter"
|
||||
- A mime promoted to "security mime"
|
||||
|
||||
Roles that are not included:
|
||||
- A passenger
|
||||
- The clown
|
||||
- An antagonist in any role
|
||||
- A cyborg
|
||||
- A passenger who is helping to fight off nuclear operatives
|
||||
</Document>
|
||||
@@ -0,0 +1,4 @@
|
||||
<Document>
|
||||
# Roleplay Rule 1 - Silicons must follow Silicon Rules
|
||||
You are only silicon if the game clearly and explicitly tells you that you are a silicon. For players who are silicons, the Silicon Rules override all Roleplay Rules if there is any conflict. Silicon Rules do not override Core Rules.
|
||||
</Document>
|
||||
@@ -0,0 +1,6 @@
|
||||
<Document>
|
||||
# Roleplay Rule 2 - Familiars must obey their master
|
||||
Familiars are considered non-antagonists, but have instructions to obey someone. They must obey this person even if it causes them to violate Roleplay Rules or die. You are only a familiar if the game clearly and explicitly tells you that you are a familiar. You are only the familiar of the person the game tells you. If your master dies, you can continue to attempt to fulfill orders given to you before they died. You can defend your master without an explicit order to, but must obey your master if they order you to not defend them.
|
||||
|
||||
Masters giving orders that violate Roleplay Rules are the ones that will be held responsible for the rule violations. You can ahelp masters who you believe are breaking rules with an order.
|
||||
</Document>
|
||||
@@ -0,0 +1,20 @@
|
||||
<Document>
|
||||
# Roleplay Rule 3 - Roleplay a normal person
|
||||
- Do not use texting/messaging acronyms (ex: "lol", "wtf", "brb", "lmao", "thx", "sgtm") or emoticons (ex: ":)", "xD") in-character.
|
||||
- Do not mention out-of-character (OOC) concepts like game admins or developers in character.
|
||||
- Do not use emotes to bypass muted or accented speech.
|
||||
- Do not use extremely low effort or impossible emotes.
|
||||
|
||||
## Examples
|
||||
Things you should not do:
|
||||
- Say "lol did u c wat just happened" using in-character chat.
|
||||
- Say "an admin exploded him" using in-character chat.
|
||||
- Emote "can you give me some cheese" as a mouse.
|
||||
- Emote "motions for you to order guns" or "asks you to order guns in sign language" as a mime.
|
||||
|
||||
Things you could do instead:
|
||||
- Say "haha did you see what just happened?"
|
||||
- Say "god blew him up" or "centcom must have bluespaced a bomb to him"
|
||||
- Point at cheese
|
||||
- Point at the cargo order console then emote "shoots finger guns"
|
||||
</Document>
|
||||
@@ -0,0 +1,103 @@
|
||||
<Document>
|
||||
# Roleplay Rule 4 - Do not metagame, obey the Metashield
|
||||
Something that is "shielded" cannot be known by your character during a round until the "revealing condition" happens. This also means that your character cannot do things based on "shielded" information. Knowing or acting on something that is shielded before the revealing condition is met is referred to as metagaming.
|
||||
|
||||
Revealing conditions reveal the shielded information for the round, not for a specific instance. This means that once a revealing condition is met in a round, the shield no longer applies in any case for the remainder of the round.
|
||||
|
||||
## Never Revealed IC
|
||||
Some shields are never revealed IC. This means that your character can never act as if they know about that shielded thing.
|
||||
|
||||
The following are shielded:
|
||||
- Current game mode and possible antags during the current game mode.
|
||||
- Events from previous rounds.
|
||||
- Events from previous characters.
|
||||
- All information related to the player of a character rather than the character itself. (See "Metafriending and Metagrudging" below.)
|
||||
- All information gained while dead or a ghost.
|
||||
- The fact that a round will end.
|
||||
|
||||
This does not prevent knowing that a shift will end, but does prohibit things like preparing to kill people at central command when roleplay rules stop being enforced on LRP.
|
||||
|
||||
## Nuclear Operatives
|
||||
|
||||
The existence of Nuclear Operatives beyond a myth that no one would act on is shielded.
|
||||
|
||||
The fact that the nuke disk must be protected and could be used by a bad actor to try to destroy the station is not shielded.
|
||||
|
||||
The revealing condition for this shield is any of the following:
|
||||
- discovering a blood red hardsuit
|
||||
- an operative name
|
||||
- a War Ops announcement
|
||||
- being a nuclear operative
|
||||
|
||||
## Implanted Implants
|
||||
|
||||
Implanted implants are shielded.
|
||||
|
||||
Implanters themselves and un-implanted implants are not shielded. This prohibits implant checking.
|
||||
|
||||
The revealing condition for this shield is any of the following:
|
||||
- discovering a non-NT implanter, used or unused
|
||||
- discovering a non-NT implant box
|
||||
- discovering use of a non-NT implant by anyone
|
||||
- experiencing a situation where absolutely no other explanation is possible
|
||||
- discovering an unlocked uplink
|
||||
|
||||
## Chameleon Items
|
||||
|
||||
Chameleon items are shielded.
|
||||
|
||||
Being suspicious of an item being fake or stolen is not shielded, but testing items or calling them chameleon is covered by this shield.
|
||||
|
||||
The revealing condition for this shield is any of the following:
|
||||
- seeing someone else cause any chameleon item to change
|
||||
- finding holographic nanomachine fibers
|
||||
- experiencing a situation where absolutely no other explanation is possible
|
||||
- discovering an unlocked uplink
|
||||
|
||||
## Stealth Items
|
||||
|
||||
The fact that an item can be something other than what its visual appearance and examine description indicate is shielded.
|
||||
|
||||
This shield protects stealth items, including protecting them from being tested.
|
||||
|
||||
The revealing condition for this shield is any of the following:
|
||||
- seeing the item behave differently than the expected behavior for the item
|
||||
- seeing the item used for its hidden purpose
|
||||
- experiencing a situation where absolutely no other explanation is possible
|
||||
- discovering an unlocked uplink
|
||||
|
||||
## MRP Amendment 1
|
||||
A shield prevents your character from remembering anything that happened while unconscious. This shield is never revealed IC.
|
||||
|
||||
## MRP Amendment 2
|
||||
There is a "New Life Rule" shield. It prevents you from remembering anything that lead to your death, even if you are put into an MMI. If you are cloned, it also prevents you from remembering everything from that round. This shield is never revealed IC.
|
||||
|
||||
## Metafriending and Metagrudging
|
||||
This section provides additional information on a concept that is prohibited by multiple metashield items that are never revealed IC. Giving a person or character preferential treatment based on something that your character should not know is considered metafriending. Treating a person or character negatively based on something that your character should not know is considered metagrudging.
|
||||
|
||||
## Metafriending Examples
|
||||
These are all examples of things that are prohibited by at least one metashield item that is never revealed IC.
|
||||
- Giving a character additional access or a job because you are friends with the player who is playing that character.
|
||||
- Trusting a character because you are friends with the player who is playing that character.
|
||||
- Not fighting a character because you are friends with the player who is playing that character.
|
||||
- Ignoring your objective to kill a character because your character and theirs became friends in a previous round.
|
||||
|
||||
## Metagrudging Examples
|
||||
These are all examples of things that are prohibited by at least one metashield item that is never revealed IC.
|
||||
- Not giving a character additional access or a job because you are mad at or don't like the player who is playing that character.
|
||||
- Not trusting a character because you are mad at or don't like the player who is playing that character.
|
||||
- Starting a fight with a character because of something that they did last round.
|
||||
- Starting a fight with a character because they killed you while you were playing a different character.
|
||||
- Targeting or harassing a character based on anything which that character did outside the current round.
|
||||
- Targeting or harassing a character based on anything which the character's player did while not playing the character.
|
||||
|
||||
## Explicitly Not Shielded
|
||||
The following is a list of things that are explicitly not shielded. If something is not on this list, it doesn't mean that it is shielded, but if something is on it then it definitely is not shielded.
|
||||
- The fact that the nuke disk must be protected and could be used by a bad actor to try to destroy the station.
|
||||
- Items that are of high value or are desired by the Syndicate, and therefore are likely targets of theft.
|
||||
- The idea that any Syndicate agent or other bad actor has goals or objectives that they are attempting to accomplish.
|
||||
- The number of goals or objectives that a Syndicate agent or other bad actor has.
|
||||
- The fact that the Syndicate are enemies of Nanotrasen, and that they regularly attempt to send covert agents to spy on, sabotage, or attack Nanotrasen.
|
||||
- A character's typical appearance. Though you should keep in mind that multiple characters can share the same name.
|
||||
- The fact that the Syndicate have covert items capable of getting items to them, and that these items are known as uplinks.
|
||||
</Document>
|
||||
@@ -0,0 +1,22 @@
|
||||
<Document>
|
||||
# Roleplay Rule 5 - Do not interfere with arrivals
|
||||
The arrivals station, the arrivals shuttle, at the area immediately around the arrivals shuttle at the station ("arrivals") are off-limits to antagonistic activity or damage (even to antagonists). Do not prevent people from safely arriving to the station. Do not cause people to die immediately after arriving at the station.
|
||||
|
||||
There is an exemption for antagonists that are allowed to perform mass station sabotage if there is no reasonable way to limit the damage of the mass station sabotage. This exemption only applies to damage that is a direct result of the mass station sabotage.
|
||||
|
||||
## Examples
|
||||
Acceptable:
|
||||
- Redecorating arrivals or the arrivals shuttle.
|
||||
- Remodeling arrivals or the arrivals shuttle as long as you do not make the area more dangerous both during and after the remodel.
|
||||
- Setting up a safe security checkpoint between arrivals and the rest of the station.
|
||||
- Killing someone who has been at arrivals for a long time, or who left arrivals and came back. (This may violate other rules depending on the situation)
|
||||
- Releasing a singularity which damages arrivals. (This may violate other rules depending on the situation)
|
||||
- Causing a station-wide atmospheric issue which also affects arrivals. (This may violate other rules depending on the situation)
|
||||
|
||||
Prohibited:
|
||||
- Making arrivals or the arrivals shuttle uninhabitable.
|
||||
- Attacking or killing someone at the arrivals station.
|
||||
- Killing someone very shortly after they arrive at the station.
|
||||
- Disassembling all the firelocks at arrivals.
|
||||
- Electrifying the arrivals docking airlocks.
|
||||
</Document>
|
||||
@@ -0,0 +1,22 @@
|
||||
<Document>
|
||||
# Roleplay Rule 6 - Don't act like an antagonist unless the game tells you that you are one
|
||||
Acting like an antagonist when you are not one is often referred to as "self-antagging" or being a "self-antag", both of these things are against the rules. You are not an antagonist unless the game tells you that you are an antagonist. Do not make yourself a major problem, annoyance, or disruption while not an antagonist. Do not willfully cooperate with known antagonists. Non-antagonists should typically either not have an overall effect on the round, or should have an overall positive effect on the round.
|
||||
|
||||
## Examples
|
||||
These examples assume that you are not an antagonist.
|
||||
|
||||
Acceptable:
|
||||
- Stealing or breaking a glass from the bar.
|
||||
- Replacing someone's shoes with clown shoes.
|
||||
- Giving everyone all access during war ops. (This is not necessarily a good idea)
|
||||
|
||||
Prohibited:
|
||||
- Starting a cult.
|
||||
- Starting a revolution.
|
||||
- Mutinying the captain because they would not let you become the chief medical officer.
|
||||
- Randomly smashing lots of station lights.
|
||||
- Disrupting station power.
|
||||
- Spacing parts of the station.
|
||||
- Distributing significant levels of access without a good reason.
|
||||
- Stealing high risk or high value items, like the nuclear authentication disk, for no reason.
|
||||
</Document>
|
||||
@@ -0,0 +1,16 @@
|
||||
<Document>
|
||||
# Roleplay Rule 7 - Do not stall the round
|
||||
Rounds are intended to end eventually. Don't hold a round hostage by preventing it from coming to a natural end. If a majority of players in a round want the round to end, don't prevent it from ending. Recalling the shuttle or preventing it from being called can contribute to round stalling, but is not always round stalling. Leaving the station with the nuclear authentication disk while nuclear operatives are trying to get it is almost always considered round stalling. Leaving the station on the evacuation shuttle is not round stalling.
|
||||
|
||||
Recalling the shuttle before a round reaches 45 minutes can not be considered round stalling unless a significant amount of the crew is dead, or a significant amount of the station is damaged or destroyed. Once these conditions are met, whether recalling the shuttle is considered round stalling or not can be highly dependent on the specific situation.
|
||||
|
||||
## Examples
|
||||
Acceptable:
|
||||
- Recalling a shuttle that was called 30 minutes into a round because people were bored.
|
||||
- Recalling a shuttle that was called because nuclear operatives declared war.
|
||||
- The crew decides to try to have a shift go as long as possible. The station is in good condition and a majority of all crew are alive. An automatic shuttle call 4 hours into the round is recalled.
|
||||
|
||||
Prohibited:
|
||||
- Trying to keep nuclear operatives from getting the nuclear authentication disk by flying around in space with it or hiding with it off station.
|
||||
- Recalling the shuttle while the station is in complete disarray and 90% of the crew are dead.
|
||||
</Document>
|
||||
@@ -0,0 +1,22 @@
|
||||
<Document>
|
||||
# Roleplay Rule 8 - As an antagonist, only be friendly to your team and don't work against your team
|
||||
Do not take or enable antagonist roles that you do not want to play. Solo antagonists and team antagonists are intended to cause issues for non-antagonists or the station. Antagonists are not required to exclusively cause issues, but their net impact on non-antagonists or the station should generally be negative.
|
||||
|
||||
Do not cause issues for your own team as a team antagonist.
|
||||
|
||||
## Examples
|
||||
Acceptable:
|
||||
- Betraying another antagonist as a solo antagonist.
|
||||
- Revealing the identity of another antagonist as a solo antagonist for some benefit to yourself.
|
||||
- Working against the revolution after being de-converted from being a revolutionary.
|
||||
- Killing nuclear operatives as a revolutionary.
|
||||
|
||||
Prohibited:
|
||||
- Buying Syndicate items for security.
|
||||
- Randomly attacking other carp as an antagonist carp.
|
||||
- Ignoring your team as a nuclear operative.
|
||||
- Sabotaging your team as a nuclear operative.
|
||||
- Attacking other zombies as a zombie.
|
||||
- Working against the revolution as a revolutionary.
|
||||
- Making or trying to make the station uninhabitable as a revolutionary.
|
||||
</Document>
|
||||
@@ -0,0 +1,23 @@
|
||||
<Document>
|
||||
# Roleplay Rule 9 - As an antagonist, do not cause excessive death, damage, or destruction beyond your objectives
|
||||
This rule is not intended to disallow reasonable steps taken to complete your objectives. As an antagonist, you can always kill in bona fide self defense. Taking steps to permanently round remove many people who are no longer an immediate threat to you is almost always excessive, even if it is done to prevent yourself from being discovered.
|
||||
|
||||
This rule is not intended to disallow all antagonist activity unrelated to objectives. Antagonists may cause a level of disruption to the station that is proportional to their objectives, even if it is unrelated to their objectives. As an antagonist, killing a single person in a round is not on its own be a violation of this rule.
|
||||
|
||||
## Exemptions
|
||||
The "die a glorious death" objective allows antagonists to ignore this rule entirely.
|
||||
|
||||
## Examples
|
||||
Acceptable:
|
||||
- Permanently round removing people who you have the objective to kill.
|
||||
- Causing massive station damage and chaos as an antagonist with the "die a glorious death" objective.
|
||||
- Killing anyone you see as a nuclear operative.
|
||||
- Permanently round removing a single person so that you can impersonate them to make it easier for you to complete a steal objective.
|
||||
- Sabotaging station power 10 minutes into the round to try to get the shuttle called because you've completed all of your other objectives and have one to escape on the shuttle alive.
|
||||
- Sabotaging a department's power 10 minutes into the round to make a steal objective easier to accomplish.
|
||||
|
||||
Prohibited:
|
||||
- As a traitor with 3 kill objectives, taking steps to permanently round remove many non-objective people who are no longer an immediate threat to you, even if it is done to prevent yourself from being discovered.
|
||||
- Setting up an electrified grille in maintenance and using it to kill anyone who walks into it with the hope that one of your objectives will be one of them.
|
||||
- Sabotaging power station-wide 10 minutes into the round to make a steal objective easier to accomplish.
|
||||
</Document>
|
||||
Reference in New Issue
Block a user