Sandbox2 - Revision history

Toastewoofs at 20:45, 29 September 2026

2026-09-29T20:45:15Z

← Older revision		Revision as of 20:45, 29 September 2026
Line 9:		Line 9:
	!Rule		!Rule
	!#		!#
	! colspan="3" \|Rules		! colspan="2" \|Rules
	!Examples/Info		!Examples/Info
	!Special Rulings		!Special Rulings
Line 15:		Line 15:
	\| rowspan="7" \|0 - Consent		\| rowspan="7" \|0 - Consent
	\|0.1.		\|0.1.
	\| colspan="3" \|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.		\| 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.
	\|		\|
	\|		\|
Line 21:		Line 21:
	\|0.1.1.		\|0.1.1.
	\|		\|
	~~\| colspan="2"~~ \|In accordance with this, sexual actions that indiscriminately interact with, impact, or are shown to other players are banned.		\|In accordance with this, sexual actions that indiscriminately interact with, impact, or are shown to other players are banned.
	\|		\|
	\|		\|
Line 27:		Line 27:
	\|0.1.2.		\|0.1.2.
	\|		\|
	~~\| colspan="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.		\|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.
	\|		\|
	\|		\|
Line 33:		Line 33:
	\|0.1.3.		\|0.1.3.
	\|		\|
	~~\| colspan="2"~~ \|OOC consent can be revoked at any time, and the other party must respect this.		\|OOC consent can be revoked at any time, and the other party must respect this.
	\|This should typically be done through LOOC.		\|This should typically be done through LOOC.
	\|		\|
Line 39:		Line 39:
	\|0.1.4.		\|0.1.4.
	\|		\|
	~~\| colspan="2"~~ \|Mechanics intended for ERP, such as urination or micro/macro mechanics must not be used against non-consenting players.		\|Mechanics intended for ERP, such as urination or micro/macro mechanics must not be used against non-consenting players.
	\|		\|
	\|		\|
	\|-		\|-
	\|0.2.		\|0.2.
	\| colspan="3" \|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..		\| 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..
	\|		\|
	\|		\|
Line 50:		Line 50:
	\|0.2.1.		\|0.2.1.
	\|		\|
	~~\| colspan="2"~~ \|Quadrupedal animals with no real life parallel may be interacted with sexually, but must be both sentient and sapient.		\|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.		\|Dragons, ash drakes, monsters etc. are all permissible under this rule.
	\|		\|
	\|-		\|-
	\| rowspan="3" \|1 - Non-Con Rules		\| rowspan="8" \|1 - Non-Con Rules
	\|1.1.		\|1.1.
	\| colspan="3" \|The in-game non-con preferences "Non-con - Yes", and "Non-con - Yes (Position)" allow other users to skip escalation for sexual purposes.		\| 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.
	\|For example, they may suddenly grab or drug you without any standard escalation to initiate roleplay.		\|For example, they may suddenly grab or drug you without any standard escalation to initiate roleplay.
	\|		\|
Line 62:		Line 62:
	\|1.1.1.		\|1.1.1.
	\|		\|
	~~\| colspan="2"~~ \|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.		\|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.		\|1.2.
	\| colspan="3" \|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.		\| 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.
	\|		\|
	\|		\|
	\|-		\|-
	\|
	\|1.2.1.		\|1.2.1.
	\|		\|
	~~\| colspan="2"~~ \|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.		\|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.		\|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.		\|1.2.2.
	\|		\|
	~~\| colspan="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.		\|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.		\|For example, arresting someone who failed to strong-arm the Captain into dorms is permissible.
	\|		\|
	\|-		\|-
	\|
	\|1.3.		\|1.3.
	\| colspan="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.		\| 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.
	\|		\|
	\|		\|
	\|-		\|-
	\|
	\|1.3.1.		\|1.3.1.
	\|		\|
	~~\| colspan="2"~~ \|If discomfort with mechanical escalation is voiced in LOOC, you must disregard the conflict~~'''disreg'''should '''ard the conflict'''~~, and either cancel the scene or proceed without mechanics.		\|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.
	\|		\| colspan="2" \|ERP and all other OOC preferences must be obeyed, regardless of the consensual nature of the roleplay scene at hand.
	\|
	\|
	\|
	\|		\|
	\|		\|
	\|}		\|}
	:
	~~:1.1.1.~~
	~~1.2. ERP and OOC preferences must be obeyed, regardless of the consensual nature of the roleplay scene at hand.~~

Toastewoofs at 20:44, 29 September 2026

2026-09-29T20:44:54Z

@@ Line 13: / Line 13: @@
 !Special Rulings
 |-
-| rowspan="3" |
+| rowspan="7" |0 - Consent
 |0.1.
+|
+|
+|
+|
+|
 |-
-|0.1.1.
+|1.2.
+|
+|
+|
+|
+|
 |-
-|0.2.
+|
+|
@@ Line 35: / Line 106: @@
+|
 |}
+:
 :1.1.1.
 .2. ERP and OOC preferences must be obeyed, regardless of the consensual nature of the roleplay scene at hand.

Toastewoofs at 21:01, 15 August 2026

2026-08-15T21:01:00Z

@@ Line 1: / Line 1: @@
 __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.
+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.
 {| class="wikitable"
 !Rule
@@ Line 37: / Line 35: @@
+|
 |}

Toastewoofs: Replaced content with "NOTOC 495x48px 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..."

2026-08-15T21:00:38Z

Replaced content with "__NOTOC__ frameless|none|495x48px 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>'' 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..."

Show changes

Toastewoofs at 19:34, 15 August 2026

2026-08-15T19:34:15Z

← Older revision		Revision as of 19:34, 15 August 2026
Line 164:		Line 164:
	\|-		\|-
	\|1.1.3.		\|1.1.3.
			\|
			\| 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.4.
	\|		\|
	\| 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.		\| 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.
Line 169:		Line 175:
	\|		\|
	\|-		\|-
	\|1.1.4.		\|1.1.5.
	\|		\|
	\| colspan="2" \|You must ensure that custom objectives are reasonable within roleplay, and are not overly convoluted, non-sensical, or unreasonable.		\| colspan="2" \|You must ensure that custom objectives are reasonable within roleplay, and are not overly convoluted, non-sensical, or unreasonable.
Line 176:		Line 182:
	\|-		\|-
	\|1.2.		\|1.2.
	~~\| colspan="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.~~
	\|
	\|-
	~~\|1.3.~~
	\| colspan="3" \|You must not make custom objectives or goals vague, wildcards, or non-specific in nature.		\| colspan="3" \|You must not make custom objectives or goals vague, wildcards, or non-specific in nature.
	\|		\|
	\|		\|
	\|-		\|-
	\|1.3.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).		\| 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).

Toastewoofs at 19:19, 15 August 2026

2026-08-15T19:19:46Z

← Older revision		Revision as of 19:19, 15 August 2026
Line 145:		Line 145:
	\|		\|
	\|-		\|-
	\| rowspan="7" \|1 - Antagonist Objective Rules		\| rowspan="8" \|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="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.
Line 176:		Line 176:
	\|-		\|-
	\|1.2.		\|1.2.
			\| colspan="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.
			\|
			\|-
			\|1.3.
	\| colspan="3" \|You must not make custom objectives or goals vague, wildcards, or non-specific in nature.		\| colspan="3" \|You must not make custom objectives or goals vague, wildcards, or non-specific in nature.
	\|		\|
	\|		\|
	\|-		\|-
	\|1.2.1.		\|1.3.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).		\| 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).

Toastewoofs at 19:04, 15 August 2026

2026-08-15T19:04:54Z

← Older revision		Revision as of 19:04, 15 August 2026
Line 5:		Line 5:
	Antagonists are the primary driving force behind action aboard the station. Assistants too.		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>''		''<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.		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.

Toastewoofs at 19:04, 15 August 2026

2026-08-15T19:04:39Z

← Older revision		Revision as of 19:04, 15 August 2026
Line 4:		Line 4:

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

	~~[[File:General transparent.png\|frameless\|none]]~~
	----		----
	''<big>You're not expected to win; do not expect it, just have fun with it.</big>''		''<big>You're not expected to win; do not expect it, just have fun with it.</big>''

Toastewoofs at 19:04, 15 August 2026

2026-08-15T19:04:08Z

Show changes

Toastewoofs at 18:44, 15 August 2026

2026-08-15T18:44:40Z

← Older revision		Revision as of 18:44, 15 August 2026
Line 167:		Line 167:
	\|		\|
	\|}		\|}





			=== 1. IC Antagonist Rules ===

			:1.1. You must remain friendly when you have stated or posed as such (also known as false-flagging). For example, posing as a friendly changeling in order to isolate a member of security and murder them.
			::1.1.1. This does not extend to coercion or otherwise roleplaying your way to freedom. For example, as a traitor and through roleplay, managing to manipulate a security officer to remove your handcuffs before murdering them.
			:1.2. 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.
			::1.2.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.

			[[File:Capture transparent.png\|frameless\|none]]
			----
			''Caught someone as an abductor? Already made some eggs as a spider?'' Follow these rules:

			=== 2. Capture Rules ===

			:2.1. You must respect roleplay situations. If security is engaging in roleplay you create, or security attempts to roleplay with you, opting to only choose mechanics violates our RP standards
			::2.1.1. This rule also applies to security. Security must not instantly engage in hostage situations, as this violates our roleplay standards also.
			::2.1.2. 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. You must not mechanically guard bodies from recovery by crew for longer than fifteen (15) minutes.
			::2.2.1. This rule principally applies to kudzu man-eaters and spiders, but also applies to other antagonists who may choose to guard a body.
			:2.3. You must not engage in captivity/hostage RP that receives no response for fifteen (15) minutes.
			::2.3.1. Essentially, if security ignores you, you should either kill or release your poor target, to avoid spoiling their whole round.