Sandbox: Difference between revisions

From S.P.L.U.R.T. Wiki
mNo edit summary
mNo edit summary
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
[[File:Roleplay_transparent.png|none|frameless]]
----'''S.P.L.U.R.T. Station is a medium erotic roleplay server''', and this means that you are expected to both create a character that makes sense, but also conduct yourself in a manner that makes sense for your character. You should also avoid disrupting the roleplay of other players without reason.


To this end, your characters should reflect a quality of roleplay that follows the rules below, and conforms a "medium roleplay" standard. This means avoiding characters and actions that may disrupt player's experience or immersion, and playing as a coherent and believable character.
[[File:Antagonists title.png|frameless|none|495x48px]]


Justifying in-character actions through proper roleplay is a our greyest area within the rules. If all players are '''satisfied''', '''consenting''', and the rules broken '''are conducive to roleplay and in-world lore, and do not needlessly impact other parties''', then many of these rules can be broken. This is '''not''' an excuse to needlessly break rules, as poor justification that does not have the explicit intent to foster a good roleplaying environment for other players will be punished.
Antagonists are the primary driving force behind action aboard the station. Assistants too.
----
''<big>You're not expected to win; do not expect it, just have fun.</big>''


If your character or their personality is deemed to not contribute to the roleplay environment, '''you may be asked to not play said character in that way anymore''', and staff are within their right to ask you to do so.
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.


=== 0. - OOC Roleplay 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].
{| class="wikitable"
{| class="wikitable"
!Rule
!Rule
!#
!#
! colspan="2" |Rules
! colspan="3" |Rules
!Examples/Info
!Examples/Info
!Special Rulings
!Special Rulings
|-
|-
| rowspan="32" |0 - OOC Roleplay Rules
| rowspan="19" |A0 - General Antagonist Rules
|0.1
|A0.1.
| colspan="2" |Roleplay, and in doing so, play a reasonably sane and mature character, and stay in character.
| 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.
|
|
|-
|-
|0.1.1.  
|A0.1.1.
|
|
|You must roleplay in a manner comparable to real-life, reasonable for your current circumstances and the current setting.
| 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.
|This is with respect to the lore and world setting. While Nanotrasen technology isn't real, you must act as a reasonable person would in the setting.
|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.
|
|
|-
|-
|0.1.2.  
|A0.2.  
|
| 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.  
|Your character cannot have any special powers which are not possible via game mechanics, except in private dorm roleplay. For example, you cannot canonically be a sorcerer.
|This means that a traitor could help security kill a blob, but could not help security kill a bloodsucker.
|
|
|-
|0.1.3.
|
|You are expected to adhere to the roleplaying setting and maintain suspension of disbelief even when game mechanics contradict.
|For example, you will not automatically know another player is a xenochimera because a tooltip says so; likewise, repairing a broken bone isn’t simple because it takes 3 clicks.
|
|-
|0.1.4.
|
|You must not use netspeak in your messages in-character (IC), except in contexts where it would make sense, such as PDA messages.
|This includes things like "pls", "lol", "uwu", etc.
|
|
|-
|-
|0.1.5.
|A0.2.1.  
|
|You may not use generative artificial intelligence (AI), such as large-language models like ChatGPT, to generate your in-game flavor text, speech, or emotes.
|
|
| 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.
|
|
|-
|-
|0.1.6.
|A0.2.2.  
|
|You must not name your character in a way that is fundamentally absurd, meta, or offensive in nature, or the name of a real person.
|For example, "asidlygfsdhkfj", "John Nanotrasen", "Fuck", or "Osama Bin Laden" are all not permitted.
|The clown and mime get very narrow exceptions to this rule. Where a name like "Idiot Dog" would be impermissible for any other role, it may be permitted for the clown or mime.
|-
|0.1.7.
|
|This is the major, blanket roleplay rule that enforces our medium roleplay standard. As a bare minimum, it should be believable for a real person to commit any In-Character event through some justification. Roleplay trumps most.
|
|
| 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.
|
|
|-
|-
|0.2.  
|A0.3.  
| colspan="2" |Your character(s) must be plausible and have justification for existing in the Space Station 13 setting.
| 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.
|
|
|-
|-
|0.2.1.
|A0.3.1.  
|
|
|You must not play as characters that imitate real-life figures.
| 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".
|
|
|
|
|-
|-
|0.2.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.
|Non-antagonists have different rules for round removal.
|
|
|If you are linking yourself to the lore of another species, you must do so tastefully and while keeping in-mind that regardless of your character's lore, you exist and will be acting in the Space Station 13 setting.
|As such, you may not use character traits of the species/character you are imitating to grief, self-antag, or otherwise violate the rules. For example, your expie security officer having an obsession with fentanyl, and using this to justify antagonizing medical/other players.
| rowspan="3" |You may ignore these rules on the Ghost Cafe or Interlink, but they immediately come into effect on the station, lavaland, or space z-levels (ghostroles).
|-
|-
|0.2.3.  
|A0.5.
| colspan="3" |You must not perform antagonistic activities, or hide in, the interlink or infinite dorms.
|
|
|You may not play as the exact same character as someone else in the same round (i.e., through in-round cloning, or intentionally using the same character preferences/character slot, etc.), including lore, name, appearance, etc.
|This does not extend to disguising oneself as someone else, and does not apply to changelings. This applies primarily to situations where people are intentionally creating copies of a character through any means.
Things such as expies do not violate this rule, as they have individual names or character backgrounds.
|-
|0.2.4.
|
|
|Fundamentally meme or joke characters are prohibited.
|For example, Peter Griffin, Red from Among Us, etc.
Staff permission may override this rule.
|-
|-
|0.2.5.  
|A0.5.1.
|
|
|Staff reserve the right to rule a character as too 'non-differentiated' from a pre-existing character from another piece of media, and thereby ban said character under rule 0.2.2. or 0.2.3.
| colspan="2" |This includes prior to security or crew members being aware of your antagonist status.
|
|
|
|
|-
|-
|0.3.  
|A0.6.
| colspan="2" |You must not respawn as the same character if your character has entered the round (left the interlink).
| colspan="3" |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.
|
 
|-
 
|0.3.1.
Other parties may consent via (L)OOC to waive this rule.
|
|You may receive staff permission to respawn if you have entered, but this is not a guarantee.
|
|
|-
|0.3.2.
|
|Cyborgs may respawn, but must roleplay their re-entering of the round; cyborgs must '''not''' respawn as the same cyborg if killed in any way prior to respawning.
|
|
|-
|0.4.
| colspan="2" |SPLURT is an English-speaking server, and you are expected to speak English while playing here.
|
|
|-
|0.4.1
|
|If a staff member believes that your level of English will not allow you to follow our rules, you may be asked to leave.
|
|
|-
|0.4.2.
|
|You may speak non-English languages both IC and OOC if you are in a private setting, such as dorms or infinidorms, but this should be kept between two people.
|
|
|
|-
|-
|0.5.  
|A0.6.1.
| colspan="2" |You must not cryo, ghost, or DNR your character in order to avoid In-Character punishments. If you have to leave at an incidental time, you must Adminhelp before doing so.
|This does not apply to DNRing after being killed as an antagonist.
|
|
|-
| colspan="2" |This includes tacit implications of sex, and does not necessitate explicit offers.
|0.6.
| colspan="2" |You must not circumvent the 150 character minimum for flavortext, as this minimum was implemented to ensure players can showcase a baseline level of roleplay skills. Manners of circumvention include spamming random characters, using invisible characters, intentionally inputting random words, etc.
|
|
|
|
|-
|-
|0.7.  
|A0.7.
| colspan="2" |Should you die and be later revived, you are expected to forget the events leading to your death. This applies even to rounds without antagonists.
| 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.
|Cyborgs are exempt from these rules, but may not remember the name or appearance of their killer. They may remember the events surrounding their deaths and all other related information.
|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.
|
|-
|0.7.1.
|
|Death during ERP is an exception if all involved players agree to letting you remember.
|
|
|-
|0.7.2.
|
|You must not remember the name or appearance of your killer after being killed.
|
|
|
|-
|-
|0.7.3.
|A0.7.1
|
|
|If you were knocked unconscious, you may remember the appearance of your killer (species, clothes), but not their name.
| colspan="2" |Lavaland, deep space, the interlink, infinite dorms are all counted as outside of the station z-level.
|
|
|
|
|-
|-
|0.7.4.
|A0.8.
|
| colspan="3" |Antagonists are subject to Roleplay Rule R0.9 ("Do not play to win") and the following:
|Proteans must follow rules 0.7.1., 0.7.2., and 0.7.4. where they are killed and their 'memory reset' button has been engaged IC.
|
|
|
|
|-
|-
|0.8.  
|A0.8.1.
| colspan="2" |You must not be antagonistic while not an antagonist.
|
|
| 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.
|
|
|-
|0.8.1.
|
|You must not continue committing crimes that escalate your current status as a criminal on the sole basis that you have committed a crime.
|For example, just because you assaulted an officer does not mean you should now kill the next security officer who speaks to you.
|
|
|-
|-
|0.8.2.  
|A0.8.2.
|
|
|If you have escalated properly, you may commit any number of crimes, but you should be careful to follow what is logical for your non-antagonist character, and what is justified. Don't go on a mass killing spree because someone slipped you with a banana peel, but you may get into a shove fight with them. Similarly, if someone fucks your wife and kills your dog, it may be justified to maim them.
|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.
|Roleplay can be used to justify most crimes you will commit, but it may still be unreasonable to commit some crimes. You will need a very strong reason to commit most 5XX crimes, and will likely struggle to find a justification to commit a 6XX crime. When in doubt, OPFOR or AHelp.
|
|
|-
|0.9.
| colspan="2" |Do not play to win
|
|
|
|
|-
|-
|0.9.1.  
|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.
|Better known as "powergaming". Powergaming/playing to win consists of acquiring items, assets, etc. for the sake of being powerful. Common examples include adding extra access to ID’s without reason, stealing powerful objects from other departments, or doing the job(s) of other departments when said department is available and willing to do the job itself.
|
|
|
|
|-
|-
|A0.9.1.
|
|
|0.9.2.
| 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.
|
|You may not mechanically prepare for unconfirmed threats.
|This rule includes being fully armed, armored, and/or medicated as a member of security with no confirmed threats and while outside of the appropriate alerts. This rule also includes other forms of mechanical metapreparation, such as saltsmoking the station before a revenant even shows up.
|-
| rowspan="9" |1 - Role-specific Roleplay Rules
|1.1.
| colspan="2" |1.1. You are expected to fulfill the basic responsibilities of the job you sign up for.
|
|
|
|
|-
|-
|1.1.1.  
| rowspan="8" |A1 - Antagonist Objective Rules
|
|A1.1.
|Repeatedly failing to do the bare minimum required by your department may result in a job ban. The specifics vary from job to job while Heads of Staff are held to higher standards than other staff.
| 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.
|
|
|-
|-
|1.1.2.
|A1.1.1.
|
|Your character must be physically capable of performing the job. For example, most jobs require at least one functioning hand. Security needs to be physically capable of subduing criminals and thus lack easily exploitable traits such as lightweight or dirt weakness.
|
|
| 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.
|
|
|-
|-
|1.1.3.
|A1.1.2.
|
|Heads of Staff are expected to be knowledgeable in their department. The bare minimum number of hours to play a role is not a license to take command of a department you have never played.
|
|
| 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".
|
|
|-
|-
|1.1.4.
|A1.1.3.
|
|As a Head of Staff, abusing your authority against players you dislike is prohibited and may violate other rules.
|
|
| 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.
|
|
|-
|-
|1.1.5.  
|A1.1.4.
|
|
|This rule does not apply to failing a job due to not knowing said job. You are expected to make mistakes frequently while learning a new job.
| 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.
|
|
|
|
|-
|-
|1.2.
|A1.1.5.
| colspan="2" |As security, you must not enforce space law outside of the station Z-level or within 22 tiles of a lavaland mining outpost.
|
|
|
| colspan="2" |You must ensure that custom objectives are reasonable within roleplay, and are not overly convoluted, non-sensical, or unreasonable.
|-
|1.2.1.
|
|Members of security are also not permitted to space tide (explore and loot space ruins), but may leave the station Z-level (such as visiting Port Tarkon).
|
|
|
|
|-
|-
|1.3.  
|A1.2.
| colspan="2" |You must not leave the station Z-level as a member of command.
| colspan="3" |You must not make custom objectives or goals vague, wildcards, or non-specific in nature.
|You may do this if you have clocked out and surrendered all unique or irreplaceable gear.
|
|
|-
| rowspan="3" |2 - Escalation Rules
|INFO
| colspan="3" |Fighting and mechanics should be proportional to the conflict, taking into account your character and the situation they are in. .
In general, escalation should follow a linear path, although this will not apply to all situations:
'''Verbal (including insults) -> Minor Aggression (non-harmful physical acts, such as pushing) -> Non-lethal (stunning, less-than-lethal ammunition/weapons) -> Lethal (Soft crit, hard crit, and death)'''
|
|
|-
|-
|2.1.
|A1.2.1.
| colspan="2" |You should not needlessly cause a confrontation in order to escalate to murder.
|Conflicts must have a roleplay backing, and if you start insulting people to escalate to killing them without reason, you will be considered to have violated this and other rules.
|
|
|-
| 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).
|2.2. 
| colspan="2" |You must not kill someone over being denied access from an area
|
|
|
|
|-
|-
| rowspan="9" |3 - Validhunting Rules
| rowspan="6" |A2 - Antagonist Roleplay Rules
|3.1.  
|A2.1.
| colspan="2" |You may defend your own person to a reasonable degree. If someone is attempting to kidnap or murder you, you may reply with lethal force.
| colspan="3" |You must respect roleplay situations created by yourself and others, and may not interrupt roleplay for mechanics without proper escalation.
|Players are expected not to respond to non-lethal force with lethal force, unless the situation demands it. For example, getting shoved by a traitor does not mean you can kill them, but getting attacked by a traitor with a contractor baton means you may fight for your life.
|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.  
| rowspan="9" |Special ruling for the AI: see [[Staff Rulings]]
|-
|3.2.
| colspan="2" |You may defend the lives of others to a reasonable degree.
|This rule principally applies to attacks and physical harm enacted by antagonists.
|-
|3.2.1.  
|
|
|If there is no threat to life, you may not engage.
|Common sense applies. Even if a traitor is not actively murdering someone, a threat to life can be assumed if they've just stunned the captain and are dragging them into maintenance.
|-
|-
|3.2.2.  
|A2.1.1.
|
|
|You must be at the scene of the attack or antagonist action while it is happening: you may not witness something on cameras or from afar and then engage.
| 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.
|
|
|-
|-
|3.3.  
|A2.2.
| colspan="2" |You may defend your department to a reasonable degree, including material assets within a department.
| colspan="3" |Hostage situations must not exceed 25 minutes without consent of the hostage out-of-character.  
|
|
|-
|3.3.1.
|
|While you may not kill an antagonist for stealing, you may attempt to incapacitate them.
|
|
|-
|-
|3.3.2.  
|A2.2.1.
|
|
|You may only defend your department in your department, and must disengage the moment any antagonist interactions leave your workspace or your department as a whole.
| 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.
|
|
|-
|-
|3.3.3.  
|A2.3.
|
| 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.
|If an antagonist is clearly attempting to leave, you must let them, and may not use lethal force to stop them unless other validhunting rules apply, such as 2.2.
|Round removal (RR) preferences set to "Yes" count as consent.
|
|
|-
|-
|3.4.
|A2.3.1.
| colspan="2" |Staff reserve the right to apply violations of validhunting rules to the spirit of the rules, and not necessarily the wording. Abusing the wording of any of the validhunting rules leaves you subject to malice and validhunting rules.
|
|
|-
| 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.
| rowspan="2" |4 - Fuck Around and Find Out (FAFO) Rules
|INFO
| colspan="3" |'''Your actions in character (IC) on the server, just like real life, have consequences from the rest of the players'''. If you, or your character, are acting like a general nuisance, then you may be treated by other players as a nuisance.
If you or your character's behaviour is awful over multiple rounds, expect players to bring their retaliation onto future rounds'''; playing an intentionally rude, disrespectful, or negative character''' exempts you from the receiving end of the metagrudging rules''', meaning that if the staff team determine that your actions are due to how you have been acting as your character, then things will be allowed to continue.'''
 
'''Consider this when deciding on your actions in-game and how you decide to act'''.
|
|
|-
|4.1.
| colspan="2" |Players reserve the right to give the same as they have received.
|The harder your character is to interact with, the more effort you should put into them. A character that's both hard to approach, and generally low effort becomes a negativity sink on the roleplaying environment and with that in mind you should make an earnest attempt to play up the actions or lack-there-of for the sake of adding in as much roleplay as you might be shutting down.
|
|
|}
|}

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.