Sandbox: Difference between revisions

From S.P.L.U.R.T. Wiki
mNo edit summary
Tags: Reverted Visual edit
mNo edit summary
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
[[File:General transparent.png|frameless|none]]
 
[[File:Antagonists title.png|frameless|none|495x48px]]
 
Antagonists are the primary driving force behind action aboard the station. Assistants too.
----
----
This section is the most important section, and pertains to your general conduct while in-game. These rules have precedence over all of your actions while playing on SPLURT.
''<big>You're not expected to win; do not expect it, just have fun.</big>''
 
This section is the most important section, and pertains to your general conduct as an antagonist. These rules have precedence over all of your actions while playing as an antagonist on SPLURT. Antagonists are still subject to all other OOC, roleplay, ERP, etc. rules.


'''At minimum, you should be familiar with these rules'''. If you are confused about these rules, please ask a staff member in [https://discord.com/channels/908082639704064051/1062140155441451129 #staff-questions], or make a [https://discord.com/channels/908082639704064051/952356538016747550/952359401883312218 discord ticket].
'''At minimum, you should be familiar with these rules'''. If you are confused about these rules, please ask a staff member in [https://discord.com/channels/908082639704064051/1062140155441451129 #staff-questions], or make a [https://discord.com/channels/908082639704064051/952356538016747550/952359401883312218 discord ticket].
Line 12: Line 17:
!Special Rulings
!Special Rulings
|-
|-
| rowspan="7" |G0 - Server Safety Rules
| rowspan="19" |A0 - General Antagonist Rules
|G0.1.
|A0.1.
| colspan="3" |Violating either Discords terms of service (ToS) or BYONDs ToS is prohibited.
| colspan="3" |Antagonists may choose to be friendly to crew, but receive no special staff protections.
|
|If an antagonist has demonstrated themself to be friendly, security cannot break this roleplay on the sole basis that the antagonist is an antagonist. Escalation rules apply.
|
|
|-
|-
|G0.2.  
|A0.1.1.
| colspan="3" |Underage characters, or playing non-sentient feral characters is not allowed under any circumstance.
|
|
| colspan="2" |If you have posed as friendly toward others, you must escalate properly in order to reset your status, regardless of your antagonist type.
|For example, a traitor that has roleplayed surrendering may not suddenly start killing again without proper escalation.
This does not extend to coercion or otherwise roleplaying your way to freedom, such as managing to manipulate a security officer to remove your handcuffs before murdering them.
|
|
|-
|-
|G0.3.  
|A0.2.  
| colspan="3" |Playing real-life animals (such as Ian) for sexual purposes is also not permitted.
| colspan="3" |Antagonists may not friendtag. Friendtagging is defined as an antagonist cooperating with security in order to perform the role and function of security against threats that do not directly oppose them.  
|Interacting with creatures that are of fantasy nature or animals that are different enough from real life animals are okay to ERP with. (Ian is off-limits, but ash drakes are allowed.)
|This means that a traitor could help security kill a blob, but could not help security kill a bloodsucker.
|
|
|-
|-
|G0.4.  
|A0.2.1.  
| colspan="3" |Using slurs, regardless of kind, and whether in-character or out-of-character (through OOC or LOOC) is prohibited.
|Using slurs (such as the f-slur) within a private area between consenting parties is allowed, so long as this is kept to subtler anti-ghost and is used solely in a non-offensive manner.
|
|-
|G0.5.
| colspan="3" |Spreading hate speech toward any group or bigotry is not allowed here, we host a diverse range of people from all backgrounds, even if you dislike a group of people, keep it to yourself.
|
|
| colspan="2" |Antagonists with opposing objectives are permitted to fight among themselves, separate from security.
| rowspan="2" |Colluding with security to achieve an objective is valid, but antagonists doing so can still violate rule 0.2. should they pursue any irrelevant security actions.
|
|
|-
|-
|G0.6.  
|A0.2.2.  
| colspan="3" |Do not violate the privacy of any community member (staff or player), including doxxing, whether accidental or purposeful.
|
|
| colspan="2" |Antagonists with the same, exclusive objective (i.e., steal the Chief Engineer's blueprints) are permitted to fight among themselves, separate from security.
|
|
|-
|-
|G0.7.
|A0.3.  
| colspan="3" |Do not create lag to the server (increasing TD or ping), including DDOSing and threats thereof.
| colspan="3" |If you murder someone in an open area (likely to be discovered in 15 minutes) and do not mechanically require access to their body, the loot on their body (including items in its possession), or mechanically require their body to perform an antagonist function (such as changeling sucking) then you '''must''' leave their body alone.
|
|If you murder someone in a closed or hidden area (not likely to be discovered in 15 minutes), you '''may''' move the body to a more discoverable location, but this is not required.
|
|
|-
|-
| rowspan="27" |G1 - General Rules
|A0.3.1.  
|G1.1.  
| colspan="3" |Do not metagame or metacommunicate
|
|
|
| colspan="2" |You must not attempt to hide or otherwise destroy bodies, no matter the original location, '''except''' if the player of the body you have killed has their round remove (RR) preferences set to "Yes".
|-
|G1.1.1.
|
| colspan="2" |This includes not discussing real-world constructs such as business organizations, politics, current global situations, etc.
|
|
|
|
|-
|-
|G1.1.2.
|A0.4.
|
| colspan="3" |You may not round-remove (RR) players without their explicit consent, whether through their round removal (RR) prefences being set to "Yes", or them telling you via (L)OOC.
| colspan="2" |You may reference music or games, and may choose to treat them as old media (as SS13 is set far in the future, typically.)
|Non-antagonists have different rules for round removal.
|
|
|-
|G1.1.3.
|
| colspan="2" |You may not use syndicate radio implants or encryption keys as non-syndicate.
|
|
|
|-
|-
|G1.2.  
|A0.5.
| colspan="3" |Speak English
| colspan="3" |You must not perform antagonistic activities, or hide in, the interlink or infinite dorms.
|
|
|
|
|-
|-
|G1.2.1.  
|A0.5.1.
|
|
| colspan="2" |If a staff member believes that your level of English will not allow you to follow our rules, you may be asked to leave.
| colspan="2" |This includes prior to security or crew members being aware of your antagonist status.
|
|
|
|
|-
|-
|G1.2.2.
|A0.6.
|
| colspan="3" |You must not bait people into mechanically compromising situations using sexual advances or offers that they otherwise would not have entered into.
| colspan="2" |You may speak non-English languages in LOOC if you are in a private setting, such as dorms or infinidorms, but this should be kept between two people and not performed in a group.
|For example, telling someone that you will "give them a good time" to get them into a room you then bolt, only to kill them.
|
 
|
 
|-
Other parties may consent via (L)OOC to waive this rule.
|G1.3.
| colspan="3" |Be respectful to all community members, whether player or staff.
|
|
|-
|G1.3.1.
|
| colspan="2" |Targeted harassment, conspiracies to drive off/get another player in trouble, and giving out player usernames/ckeys without permission are prohibited.
|
|
|-
|G1.3.2.
|
| colspan="2" |Reasonable IC drama can be permitted, if kept in moderation. The best rule of thumb is whether or not everybody involved is enjoying the interaction. If you feel unsure, use LOOC.
|Pervasive, round-to-round IC drama may violate this rule.
<u>Politely</u> ignoring somebody you do not want to interact with is permitted and encouraged.
|
|-
|G1.3.3.
|
| colspan="2" |Publicly complaining about other players in Discord is prohibited, even without stating the player’s name. Said player will likely see your message and know exactly what you refer to.
|
|
|-
|G1.4.
| colspan="3" |Do not perform, or attempt to perform the duties of a staff member as non-staff, including vigilante moderation or backseat moderation.
|
|
|-
|G1.4.1.
|
| colspan="2" |Accusing other players of rule-breaking, threatening punishment, and/or threatening to call the staff is prohibited. If somebody is breaking the rules, contact the moderation staff. Threatening to contact us tends to start/worsen drama and may get you in trouble.
|
|
|
|-
|-
|G1.4.2.
|A0.6.1.
|
| colspan="2" |Observing the round solely to search for rule-breaking is prohibited. Many behaviors may seem questionable without context and many rules deliberately include grey areas. This is a primary duty of staff members.
|
|
|
| colspan="2" |This includes tacit implications of sex, and does not necessitate explicit offers.
|-
|G1.5.
| colspan="3" |Do not bring IC information into OOC chat either to disseminate this information or to escalate an IC issue into OOC. This is termed as "mixing".
|
|
|
|
|-
|-
|G1.6.  
|A0.7.
| colspan="3" |Do not disconnect if contacted by the moderation team.
| colspan="3" |You must not leave the station z-level after you have been pursued by security at any point in the round prior. A wanted status assumes indefinite pursuit.
|
|If required by an antagonist objective, such as the acolyte requiring bones or watcher sinew, you may leave the z-level for the minimum amount of time it takes to get these resources. Idling, or spending more than 15 minutes (rough guideline) in lavaland constitutes a violation of rule 0.8.
|
|
|-
|-
|G1.6.1.
|A0.7.1
|
|
| colspan="2" |Disconnecting when contacted about a rule violation will be regarded as an attempt to avoid punishment. If you must leave, say something first.
| colspan="2" |Lavaland, deep space, the interlink, infinite dorms are all counted as outside of the station z-level.
|
|
|
|
|-
|-
|G1.6.2.
|A0.8.
|
| colspan="3" |Antagonists are subject to Roleplay Rule R0.9 ("Do not play to win") and the following:
| colspan="2" |We will be understanding if your internet cuts out at a bad time, but you may need to contact us through Discord.
|
|
|
|
|-
|-
|G1.7.
|A0.8.1.
| colspan="3" |The intent of the rules is more important than the letter.
|
|
|
| colspan="2" |This is a blanket rule for any poor-faith antagonist gameplay that comes as a result of antagonists unfairly exploiting game mechanics or roleplay in order to achieve their objectives ("greentext"). Staff are encouraged to use their best judgement when enforcing this rule.
|-
|G1.7.1.
|
| colspan="2" |The rules deliberately contain some grey areas, as it is not possible to detail every potential situation which does or does not violate the rules. The intent and thus enforcement of the rules is to provide an enjoyable roleplaying environment and to curate SPLURT to a server which can host such an environment.
|
|
|
|
|-
|-
|G1.7.2.  
|A0.8.2.
|
|
| colspan="2" |As such, a staff member may permit a rule to not be enforced if everybody involved in the situation is enjoying themselves; conversely, a situation which upsets a large number of players may need admin intervention even if not specifically addressed in the rules.
|Antagonists simply going about their objectives in a normal manner (for example, shooting an assassination target to death) should not be impacted by this rule.
|
|
|
|-
|G1.7.2.1.
|
|
|If allowing a behavior is likely to lead to repeat instances of minor negative behaviors that detracts from SPLURT as a whole, then this must be enforced against.
|
|
|
|
|-
|-
|G1.7.3.  
|A0.9.
|
| colspan="3" |You must not loot space ruins. Space-tiding is permitted, but most players have no reason to do so as an antagonist, as you are disallowed from taking loot.
| colspan="2" |Attempting to find a technicality in the wording of the rules will be ignored. If your behavior is causing problems for many other players, it must stop.
|
|
|
|
|-
|-
|G1.8.  
|A0.9.1.
| colspan="3" |Staff maintain final say.
|
|
| colspan="2" |If you became an antagonist after space-tiding and looting, you must stop looting (and typically return to the station), but may continue to use any items you possess.
|
|
|-
|G1.8.1.
|
| colspan="2" |As implied by rule 1.7, the enforcement of the rules is flexible and thus up to interpretation by the moderation team. Our job is to tackle problems not mentioned in the rules and never seen before by anybody on the team: if an admin tells you to do something, do it; if an admin tells you to stop, stop.
|If you disagree with a ruling, contact the staff member after the situation settles. We frequently need to make quick decisions on limited information and may not be able to fully address your concerns in the heat of the moment.
|
|
|-
|-
|G1.8.2.  
| rowspan="8" |A1 - Antagonist Objective Rules
|
|A1.1.
| colspan="2" |If you suspect bias, you may discuss your case with up to three other members of staff, as outlined in the staffing guidelines for SPLURT.
| colspan="3" |You must ensure custom objectives are appropriate to your antagonist role, the roleplay setting, and do not avoid antagonist actions in full or rebuke the fun of others.
|
|Permission from a member of staff may override this rule.
|
|
|-
|-
|G1.8.3.
|A1.1.1.
|
| colspan="2" |Pressing the issue further will be considered harassment.
|
|
| colspan="2" |You must not make your custom objective/goal something that violates any of our current rules or involves a mass amount of killing or station destruction.
|Natural objectives may override this rule.
|
|
|-
|-
| rowspan="16" |G2 - Malice Rules
|A1.1.2.
|G2.1.
| colspan="3" |Do not harass someone over their character, kinks, grammar or preferred roleplaying style
|
|
| colspan="2" |You must not avoid performing antagonist actions, or subvert the purpose of an antagonist role by setting a custom objective that is entirely mundane and non-antagonistic.
|For example, the custom objectives "have sex", "Protect [ERP partner]", or "Behave for security and obey Nanotrasen".
|
|
|-
|-
|G2.2.  
|A1.1.3.
| colspan="3" |Do not meta-grudge a player or their character for their past actions against you, by either killing them, griefing them, being problematic toward them OOCly, or through taking intentional malicious actions against them IC (such as demoting them for no reason).
|
|
| colspan="2" |Antagonist objectives may not be completely silent or unnoticeable by crew, regardless of if they do not constitute a violation of rule 1.1.2.
|For example, a custom objective to emag 3 doors.
|
|
|-
|-
|G2.3.  
|A1.1.4.
| colspan="3" |Do not reveal someone's CKey, discord account, or list of characters they play without express permission.
|
|
|
| colspan="2" |You must ensure that custom objectives are appropriate to your specific antagonist role. For example, a bloodsucker should not have a custom objective to help the syndicate.
|-
|G2.4.
| colspan="3" |Do not lie to staff about what you or another player did. This includes misrepresenting or withholding the truth.
|
|
|
|
|-
|-
|G2.5.
|A1.1.5.
| colspan="3" |Do not prevent a player from engaging with the round without a valid reason, such as barring them from your department as a head of staff for no reason.
|
|
|
| colspan="2" |You must ensure that custom objectives are reasonable within roleplay, and are not overly convoluted, non-sensical, or unreasonable.
|-
|G2.6.
| colspan="3" |Do not abuse bugs, quirks or exploits in a disruptive manner to get the upper-hand against another player.
|
|
|-
|G2.7.
| colspan="3" |Do not bait someone into typing before attacking them.
|
|
|-
|G2.8.
| colspan="3" |Do not use size changing quirks or gear to make your character smaller for mechanical advantage against a player
|
|
|
|
|-
|-
|G2.8.1.  
|A1.2.
|
| colspan="3" |You must not make custom objectives or goals vague, wildcards, or non-specific in nature.
| colspan="2" |The current minimum size for Command, Security, and Antagonists is 0.8 or 80%.
|
|
|
|
|-
|-
|G2.8.2.
|A1.2.1.
|
| colspan="2" |Characters naturally smaller than 80% (0.8) cannot play as a role expected to end up in combat. This includes command, security and antagonist roles.
|
|
|
|-
| colspan="2" |You may be vague so long as the actions, or intent behind the actions is specific. For example, "Murder a member of R&D" is vague, but specifies the action to be committed (murder) and the intent (to kill a member of R&D).
|G2.9.
| colspan="3" |Do not disrespect or harass staff. While we allow players to voice their disagreements with staff members, or voice their opinions on rulings a staff member has made, making fun of, or harassing staff is prohibited. Staff are both players and volunteers; if you have a genuine issue with a staff member, speak to their direct superior.
|
|
|
|
|-
|-
|G2.10.  
| rowspan="6" |A2 - Antagonist Roleplay Rules
| colspan="3" |Do not touch, loot or otherwise harm or inconvenience players who are AFK (SSD).
|A2.1.
|
| colspan="3" |You must respect roleplay situations created by yourself and others, and may not interrupt roleplay for mechanics without proper escalation.
|For example, a security officer opts to point their gun at you and talk rather than immediately shooting you constitutes entering into roleplay, and this must be respected.
|
|
|-
|-
|G2.10.1.
|A2.1.1.
|
| colspan="2" |You may strip a player of important or unique assets who has been SSD for more than 30 minutes (this can be checked through examining them) only if you are then placing the player into cryo storage. Important or unique assets include irreplaceable head items, job-specific items that would be hard to replace, etc. You must not strip any personal, disposable (such as medication, etc.) or antagonist items while doing this, and should disregard any antagonist evidence you may or may not find while doing this - just cryo the player with the antagonist gear in their possession.
|
|
| colspan="2" |This rule also applies to members of security.
|Similarly to the directly above, security must not instantly mechanically engage an antagonist in hostage situations.
Either party unduly interrupting a hostage or captive roleplay scenario must do so showing clear intent to escalate to mechanics. A good way of doing this is the Combat Indicator, but this should be done by giving grace and making it clear that this is going to happen through roleplay prior regardless.
|
|
|-
|-
|G2.10.2.  
|A2.2.
|
| colspan="3" |Hostage situations must not exceed 25 minutes without consent of the hostage out-of-character.  
| colspan="2" |Players who go SSD mid-fight are not instantly protected, but it is reasonably required that any attempts to kill the player are ceased, as they are now able to be non-lethally detained.
|
|
|
|
|-
|-
|G2.10.3.
|A2.2.1.
|
| colspan="2" |Players who do not have the SSD icon, but are visibly AFK (not moving, not responding) are only protected if it is reasonable for the person performing any actions impacting them to be aware that they are AFK.
|
|
| colspan="2" |If the hostage expresses that they no longer wish to engage in the roleplay, whether due to needing to leave OOCly, or no longer enjoying the roleplay, escalation to mechanics or roleplay de-escalation should occur within 10 minutes.
|Please submit an AdminHelp for staff oversight in this instance.
|
|
|-
|-
|G2.11.
|A2.3.
| colspan="3" |Do not powergame.  
| colspan="3" |Situations where the body of another player is kept away from rescue by crew must not exceed 15 minutes without the consent of the other player out-of-character.
|This is defined as "a player making themselves un-killable, highly resistant to all forms of damage, or making themselves absurdly powerful compared to other players.". Violations of this rule always constitute a violation of our playing-to-win rules.
|Round removal (RR) preferences set to "Yes" count as consent.
|
|
|-
|-
| rowspan="3" |G3 - Impact Rules
|A2.3.1.
|G3.1.  
| colspan="3" |You must not cause damage to the station that is impactful to players without a valid reason.
|
|
|
|-
| colspan="2" |This rule principally applies to kudzu man-eaters and spiders, but also applies to other antagonists who may choose to guard a body.
|G3.1.1.
|
| colspan="2" |You may only perform End Of Round Grief (EORG) on the Central Command Z-level. This is the area you arrive in after the emergency shuttle lands.
|The pod waystation (where emergency pods end up) may not be griefed.
|
|-
|G3.2.
| colspan="3" |You must consider your impact on the round when performing antagonistic actions. If you are a traitor on low chaos, you shouldn't suddenly be murdering every player on the server.
|
|
|
|
|}
|}

Latest revision as of 11:11, 20 October 2026


Antagonists are the primary driving force behind action aboard the station. Assistants too.


You're not expected to win; do not expect it, just have fun.

This section is the most important section, and pertains to your general conduct as an antagonist. These rules have precedence over all of your actions while playing as an antagonist on SPLURT. Antagonists are still subject to all other OOC, roleplay, ERP, etc. rules.

At minimum, you should be familiar with these rules. If you are confused about these rules, please ask a staff member in #staff-questions, or make a discord ticket.

Rule # Rules Examples/Info Special Rulings
A0 - General Antagonist Rules A0.1. Antagonists may choose to be friendly to crew, but receive no special staff protections. If an antagonist has demonstrated themself to be friendly, security cannot break this roleplay on the sole basis that the antagonist is an antagonist. Escalation rules apply.
A0.1.1. If you have posed as friendly toward others, you must escalate properly in order to reset your status, regardless of your antagonist type. For example, a traitor that has roleplayed surrendering may not suddenly start killing again without proper escalation.

This does not extend to coercion or otherwise roleplaying your way to freedom, such as managing to manipulate a security officer to remove your handcuffs before murdering them.

A0.2. Antagonists may not friendtag. Friendtagging is defined as an antagonist cooperating with security in order to perform the role and function of security against threats that do not directly oppose them. This means that a traitor could help security kill a blob, but could not help security kill a bloodsucker.
A0.2.1. Antagonists with opposing objectives are permitted to fight among themselves, separate from security. Colluding with security to achieve an objective is valid, but antagonists doing so can still violate rule 0.2. should they pursue any irrelevant security actions.
A0.2.2. Antagonists with the same, exclusive objective (i.e., steal the Chief Engineer's blueprints) are permitted to fight among themselves, separate from security.
A0.3. If you murder someone in an open area (likely to be discovered in 15 minutes) and do not mechanically require access to their body, the loot on their body (including items in its possession), or mechanically require their body to perform an antagonist function (such as changeling sucking) then you must leave their body alone. If you murder someone in a closed or hidden area (not likely to be discovered in 15 minutes), you may move the body to a more discoverable location, but this is not required.
A0.3.1. You must not attempt to hide or otherwise destroy bodies, no matter the original location, except if the player of the body you have killed has their round remove (RR) preferences set to "Yes".
A0.4. You may not round-remove (RR) players without their explicit consent, whether through their round removal (RR) prefences being set to "Yes", or them telling you via (L)OOC. Non-antagonists have different rules for round removal.
A0.5. You must not perform antagonistic activities, or hide in, the interlink or infinite dorms.
A0.5.1. This includes prior to security or crew members being aware of your antagonist status.
A0.6. You must not bait people into mechanically compromising situations using sexual advances or offers that they otherwise would not have entered into. For example, telling someone that you will "give them a good time" to get them into a room you then bolt, only to kill them.


Other parties may consent via (L)OOC to waive this rule.

A0.6.1. This includes tacit implications of sex, and does not necessitate explicit offers.
A0.7. You must not leave the station z-level after you have been pursued by security at any point in the round prior. A wanted status assumes indefinite pursuit. If required by an antagonist objective, such as the acolyte requiring bones or watcher sinew, you may leave the z-level for the minimum amount of time it takes to get these resources. Idling, or spending more than 15 minutes (rough guideline) in lavaland constitutes a violation of rule 0.8.
A0.7.1 Lavaland, deep space, the interlink, infinite dorms are all counted as outside of the station z-level.
A0.8. Antagonists are subject to Roleplay Rule R0.9 ("Do not play to win") and the following:
A0.8.1. This is a blanket rule for any poor-faith antagonist gameplay that comes as a result of antagonists unfairly exploiting game mechanics or roleplay in order to achieve their objectives ("greentext"). Staff are encouraged to use their best judgement when enforcing this rule.
A0.8.2. Antagonists simply going about their objectives in a normal manner (for example, shooting an assassination target to death) should not be impacted by this rule.
A0.9. You must not loot space ruins. Space-tiding is permitted, but most players have no reason to do so as an antagonist, as you are disallowed from taking loot.
A0.9.1. If you became an antagonist after space-tiding and looting, you must stop looting (and typically return to the station), but may continue to use any items you possess.
A1 - Antagonist Objective Rules A1.1. You must ensure custom objectives are appropriate to your antagonist role, the roleplay setting, and do not avoid antagonist actions in full or rebuke the fun of others. Permission from a member of staff may override this rule.
A1.1.1. You must not make your custom objective/goal something that violates any of our current rules or involves a mass amount of killing or station destruction. Natural objectives may override this rule.
A1.1.2. You must not avoid performing antagonist actions, or subvert the purpose of an antagonist role by setting a custom objective that is entirely mundane and non-antagonistic. For example, the custom objectives "have sex", "Protect [ERP partner]", or "Behave for security and obey Nanotrasen".
A1.1.3. Antagonist objectives may not be completely silent or unnoticeable by crew, regardless of if they do not constitute a violation of rule 1.1.2. For example, a custom objective to emag 3 doors.
A1.1.4. You must ensure that custom objectives are appropriate to your specific antagonist role. For example, a bloodsucker should not have a custom objective to help the syndicate.
A1.1.5. You must ensure that custom objectives are reasonable within roleplay, and are not overly convoluted, non-sensical, or unreasonable.
A1.2. You must not make custom objectives or goals vague, wildcards, or non-specific in nature.
A1.2.1. You may be vague so long as the actions, or intent behind the actions is specific. For example, "Murder a member of R&D" is vague, but specifies the action to be committed (murder) and the intent (to kill a member of R&D).
A2 - Antagonist Roleplay Rules A2.1. You must respect roleplay situations created by yourself and others, and may not interrupt roleplay for mechanics without proper escalation. For example, a security officer opts to point their gun at you and talk rather than immediately shooting you constitutes entering into roleplay, and this must be respected.
A2.1.1. This rule also applies to members of security. Similarly to the directly above, security must not instantly mechanically engage an antagonist in hostage situations.

Either party unduly interrupting a hostage or captive roleplay scenario must do so showing clear intent to escalate to mechanics. A good way of doing this is the Combat Indicator, but this should be done by giving grace and making it clear that this is going to happen through roleplay prior regardless.

A2.2. Hostage situations must not exceed 25 minutes without consent of the hostage out-of-character.
A2.2.1. If the hostage expresses that they no longer wish to engage in the roleplay, whether due to needing to leave OOCly, or no longer enjoying the roleplay, escalation to mechanics or roleplay de-escalation should occur within 10 minutes. Please submit an AdminHelp for staff oversight in this instance.
A2.3. Situations where the body of another player is kept away from rescue by crew must not exceed 15 minutes without the consent of the other player out-of-character. Round removal (RR) preferences set to "Yes" count as consent.
A2.3.1. This rule principally applies to kudzu man-eaters and spiders, but also applies to other antagonists who may choose to guard a body.