Template:AntagonistStandards

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
0 - General Antagonist Rules	0.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.
	0.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.
	0.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.
	0.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.
	0.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.
	0.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.		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.	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.	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.		If a member of security, or any other player violates this rule toward you, you must adminhelp rather than retaliate.
	0.6.	You must not perform antagonistic activities, or hide in, the interlink or infinite dorms.
	0.6.1.		This includes prior to security or crew members being aware of your antagonist status.
	0.7.	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.
	0.7.1.		This includes tacit implications of sex, and does not necessitate explicit offers.
	0.8.	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.
	0.8.1		Lavaland, deep space, the interlink, infinite dorms are all counted as outside of the station z-level.
	0.9.	Antagonists are subject to Roleplay Rule 0.9 ("Do not play to win") and the following:
	0.9.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.
	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.	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.		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.
1 - Antagonist Objective Rules	1.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.
	1.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.
	1.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".
	1.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.
	1.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.
	1.1.5.		You must ensure that custom objectives are reasonable within roleplay, and are not overly convoluted, non-sensical, or unreasonable.
	1.2.	You must not make custom objectives or goals vague, wildcards, or non-specific in nature.
	1.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).
2 - Antagonist Roleplay Rules	2.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.
	2.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.
	2.2.	Hostage situations must not exceed 25 minutes without consent of the hostage out-of-character.
	2.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.
	2.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.
	2.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.