Sandbox2: Difference between revisions

From S.P.L.U.R.T. Wiki
← Older edit
VisualWikitext
mNo edit summary
mNo edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__


[[File:Antagonists title.png|frameless|none|495x48px]]
[[File:Erp transparent.png|frameless|none]]
 
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 with it.</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.
ERP rules are important, and must be read before engaging in sexual conduct with another player. ERP rules are some of our most harshly punished rules, due to the nature of the actions they pertain to.


'''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="3" |Rules
! colspan="2" |Rules
!Examples/Info
!Examples/Info
!Special Rulings
!Special Rulings
|-
|-
| rowspan="22" |0 - General Antagonist Rules
| rowspan="7" |0 - Consent
|0.1.
|0.1.
| colspan="3" |Antagonists may choose to be friendly to crew, but receive no special staff protections.
| colspan="2" |You must have either OOC or IC consent before engaging in any sexual action with another player, and/or utilizing features with an intended or inherent sexual on or against another player.
|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.
|0.1.1.
|
|
| 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.
|In accordance with this, sexual actions that indiscriminately interact with, impact, or are shown to other players are banned.
|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.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.
|This means that a traitor could help security kill a blob, but could not help security kill a bloodsucker.
|
|-
|0.2.1.
|
| 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.2.2.
|
| 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.3.
| 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.3.1.
|
| 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.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.
|
|
|-
|0.5.
| colspan="3" |You must not taunt, insult, salt, or otherwise demean or dispirit other players, regardless of circumstances.
|While this covered by the general, OOC rules, this is specifically repeated so that antagonists who lose fights are neither insulted nor insult others.
|
|
|-
|-
|0.5.1.
|0.1.2.  
|
|
| colspan="2" |If a member of security, or any other player violates this rule toward you, you must adminhelp rather than retaliate.
|IC consent inherently implies OOC consent, and players are responsible for ensuring their own comfort and safety when it comes to choosing to engage with sexual content.
|
|
|
|
|-
|-
|0.6.
|0.1.3.
| colspan="3" |You must not perform antagonistic activities, or hide in, the interlink or infinite dorms.
|
|
|OOC consent can be revoked at any time, and the other party must respect this.
|This should typically be done through LOOC.
|
|
|-
|-
|0.6.1.
|0.1.4.
|
|
| colspan="2" |This includes prior to security or crew members being aware of your antagonist status.
|Mechanics intended for ERP, such as urination or micro/macro mechanics must not be used against non-consenting players.
|
|
|
|
|-
|-
|0.7.
|0.2.
| 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 must not engage in sexual interactions with animals that parallel real life, i.e., Ian (canis familiaris, domesticated dog), even if the mob is controlled by a ghost..
|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.
|
|-
|0.7.1.
|
| colspan="2" |This includes tacit implications of sex, and does not necessitate explicit offers.
|
|
|
|
|-
|-
|0.8.
|0.2.1.
| 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.
|
|
|Quadrupedal animals with no real life parallel may be interacted with sexually, but must be both sentient and sapient.
|Dragons, ash drakes, monsters etc. are all permissible under this rule.
|
|
|-
|-
|0.8.1
| rowspan="8" |1 - Non-Con Rules
|
| colspan="2" |Lavaland, deep space, the interlink, infinite dorms are all counted as outside of the station z-level.
|
|
|-
|0.9.
| colspan="3" |Antagonists are subject to Roleplay Rule 0.9 ("Do not play to win") and the following:
|
|
|-
|0.9.1.
|
| 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.9.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.
|
|
|
|-
|0.9.3.
|
|Antagonists should not go out of their way to unfairly deprive other players of their gear (tools, job machinery, etc.) for purely mechanical gain.
|
|For example, an antagonist cannot destroy the chemistry department so medbay can no longer revive officers, but may incidentally destroy part of it to kill an assassination target chemist.
|
|-
|0.10.
| 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.
|
|
|-
|0.10.1.
|
| 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.
|
|
|-
| rowspan="7" |1 - Antagonist Objective Rules
|1.1.
|1.1.
| 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.
| colspan="2" |The in-game non-con preferences "Non-con - Yes", and "Non-con - Yes (Position)" allow other users to skip escalation for sexual purposes.
|Permission from a member of staff may override this rule.
|For example, they may suddenly grab or drug you without any standard escalation to initiate roleplay.
|
|
|-
|-
|1.1.1.
|1.1.1.
|
|
| 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.
|ERP rule 0.1.3. still applies and the revocation of OOC consent must be respected regardless of preferences; however, the initial interaction will not constitute a violation of the rules.
|Natural objectives may override this rule.
|
|-
|1.1.2.
|
| 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.3.
|
| 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.1.4.
|
| colspan="2" |You must ensure that custom objectives are reasonable within roleplay, and are not overly convoluted, non-sensical, or unreasonable.
|
|
|
|
|-
|-
|1.2.
|1.2.
| colspan="3" |You must not make custom objectives or goals vague, wildcards, or non-specific in nature.
| colspan="2" |You must not attempt to involve any other player, regardless of their in-game non-con preferences involved in your non-con scene unless OOC consent is arranged '''in advance''' of the scene starting.
|
|
|
|
Line 182: Line 73:
|1.2.1.
|1.2.1.
|
|
| 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).
|In accordance with this, it is forbidden to call for help using any form of communication, including radios, PDAs, Adminhelp (unless reporting a violation of ERP rules 0.1.3. or 1.1.1.), etc.
|
|Even if you have the OOC consent of security members, or they have not expressed OOC discomfort, it is strictly forbidden to involve security or command in punishing/arresting for a non-con scene.
|
|-
| rowspan="6" |2 - Antagonist Roleplay Rules
|2.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.  
|
|
|-
|-
|2.1.1.
|1.2.2.
|
|
| colspan="2" |This rule also applies to members of security.  
|Where space law has been violated by a failed non-con attempt, it must nonetheless be disregarded and ignored by members of security unless doing so would be a greater impact to roleplay quality.
|Similarly to the directly above, security must not instantly mechanically engage an antagonist in hostage situations.
|For example, arresting someone who failed to strong-arm the Captain into dorms is permissible.
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.
|
|
|-
|-
|2.2.
|1.3.
| colspan="3" |Hostage situations must not exceed 25 minutes without consent of the hostage out-of-character.  
| colspan="2" |Where a non-con roleplay scene involves mechanical action or escalation, it is permitted for either party to fight or fight back; however, this should be contained to furthering roleplay and does not justify meaningless conflict.
|
|
|
|
|-
|-
|2.2.1.
|1.3.1.
|
| 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.
|
|
|-
|If discomfort with mechanical escalation is voiced in LOOC, you must disregard the conflict, and should either cancel the scene or proceed without mechanics.
|2.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.
|
|
|
|
|-
|-
|2.3.1.
|1.4.
|
| colspan="2" |ERP and all other OOC preferences must be obeyed, regardless of the consensual nature of the roleplay scene at hand.
| 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.
|
|
|
|
|}
|}

Latest revision as of 20:45, 29 September 2026


ERP rules are important, and must be read before engaging in sexual conduct with another player. ERP rules are some of our most harshly punished rules, due to the nature of the actions they pertain to.

Rule # Rules Examples/Info Special Rulings
0 - Consent 0.1. You must have either OOC or IC consent before engaging in any sexual action with another player, and/or utilizing features with an intended or inherent sexual on or against another player.
0.1.1. In accordance with this, sexual actions that indiscriminately interact with, impact, or are shown to other players are banned.
0.1.2. IC consent inherently implies OOC consent, and players are responsible for ensuring their own comfort and safety when it comes to choosing to engage with sexual content.
0.1.3. OOC consent can be revoked at any time, and the other party must respect this. This should typically be done through LOOC.
0.1.4. Mechanics intended for ERP, such as urination or micro/macro mechanics must not be used against non-consenting players.
0.2. You must not engage in sexual interactions with animals that parallel real life, i.e., Ian (canis familiaris, domesticated dog), even if the mob is controlled by a ghost..
0.2.1. Quadrupedal animals with no real life parallel may be interacted with sexually, but must be both sentient and sapient. Dragons, ash drakes, monsters etc. are all permissible under this rule.
1 - Non-Con Rules 1.1. The in-game non-con preferences "Non-con - Yes", and "Non-con - Yes (Position)" allow other users to skip escalation for sexual purposes. For example, they may suddenly grab or drug you without any standard escalation to initiate roleplay.
1.1.1. ERP rule 0.1.3. still applies and the revocation of OOC consent must be respected regardless of preferences; however, the initial interaction will not constitute a violation of the rules.
1.2. You must not attempt to involve any other player, regardless of their in-game non-con preferences involved in your non-con scene unless OOC consent is arranged in advance of the scene starting.
1.2.1. In accordance with this, it is forbidden to call for help using any form of communication, including radios, PDAs, Adminhelp (unless reporting a violation of ERP rules 0.1.3. or 1.1.1.), etc. Even if you have the OOC consent of security members, or they have not expressed OOC discomfort, it is strictly forbidden to involve security or command in punishing/arresting for a non-con scene.
1.2.2. Where space law has been violated by a failed non-con attempt, it must nonetheless be disregarded and ignored by members of security unless doing so would be a greater impact to roleplay quality. For example, arresting someone who failed to strong-arm the Captain into dorms is permissible.
1.3. Where a non-con roleplay scene involves mechanical action or escalation, it is permitted for either party to fight or fight back; however, this should be contained to furthering roleplay and does not justify meaningless conflict.
1.3.1. If discomfort with mechanical escalation is voiced in LOOC, you must disregard the conflict, and should either cancel the scene or proceed without mechanics.
1.4. ERP and all other OOC preferences must be obeyed, regardless of the consensual nature of the roleplay scene at hand.
Retrieved from "https://wiki.splurt.space/mediawiki/index.php?title=Sandbox2&oldid=23471"