Template:ERP 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.

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.