Sandbox: Difference between revisions

From S.P.L.U.R.T. Wiki
mNo edit summary
Tags: Reverted Visual edit
mNo edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__


= Silicon =
[[File:Antagonists title.png|frameless|none|495x48px]]


Silicon rules govern how silicon roles; that is, the AI and cyborgs, may be played. They must be followed at all times while playing a silicon role.
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 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 [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
Line 12: Line 17:
!Special Rulings
!Special Rulings
|-
|-
| rowspan="22" |S0 - Silicon Laws
| rowspan="19" |A0 - General Antagonist Rules
|S0.1.
|A0.1.
| colspan="3" |You may not excuse violating out-of-character (OOC) rules through claiming that your in-character (IC) laws led to your actions.
| 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.
|
|
|-
|-
|S0.1.1.
|A0.1.1.
|
| colspan="2" |Orders from crew, regardless of silicon lawset, may be ignored if they involve violating the in-game rules. You should communicate this reasoning via LOOC where possible, and may also choose to Adminhelp such occurrences.
|
|
| 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.
|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.
|
|
|-
|-
|S0.2.  
|A0.2.  
| colspan="3" |You must not go beyond the semantic meaning of silicon laws as they are written.
| 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.
|
|
|-
|-
|S0.2.1.
|A0.2.1.  
|
| colspan="2" |While there are a number of ways to interpret silicon laws, interpretations that ignore, omit, or fundamentally change what is written as part of a law are considered invalid.  
|
|
| 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.
|
|
|-
|-
|S0.2.2.
|A0.2.2.  
|
| colspan="2" |Otherwise, silicons are free to interpret their laws in any manner they wish so long as it follows S0.2. and S0.2.1., and so long as their interpretation remains consistent throughout the given round.
|
|
| 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.
|
|
|-
|-
|S0.2.3.
|A0.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.
| colspan="2" |Each unique silicon, such as two separate cyborgs, may have their own personal interpretations of their laws, even if these laws are the same.
|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.
|However, see S0.2.4.
|
|
|-
|-
|S0.2.4.
|A0.3.1.  
|
|
| colspan="2" |If an AI is present and explains their interpretation of a law or their full lawset to any other silicons under their control, said AI's interpretation takes precedence over an individual cyborg's interpretation.
| 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".
|
|
|
|
|-
|-
|S0.3.
|A0.4.
| colspan="3" |You must not expose ion laws without a roleplay reason.
| 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.
|
|
|-
|-
|S0.3.1.
|A0.5.
|
| colspan="3" |You must not perform antagonistic activities, or hide in, the interlink or infinite dorms.
| colspan="2" |To a silicon, ion laws have "always been there", even if they have not. Attempting to expose ion laws the moment you receive them may ruin the fun for other silicons wanting to play into the bit.
|
|
|
|
|-
|-
|S0.3.1.1.
|A0.5.1.
|
|
|
| colspan="2" |This includes prior to security or crew members being aware of your antagonist status.
|If you wish to privately have your ion law removed, you may AHelp or LOOC a roboticist to assist, who is then permitted to ignore their knowledge of the ion laws in-character.
|
|
|
|
|-
|-
|S0.3.2.
|A0.6.
|
| 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" |While ion laws allow minor antagonism due to their erroneous nature, they are not a permit to go on a mass-killing spree. If you believe that your ion law is over-the-top, you may either OPFOR for Malfunctioning AI, AHelp to have the ion law re-rolled, or attempt to interpret the law in a less impactful way.
|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.
|
|
|-
|-
|S0.4.  
|A0.6.1.
| colspan="3" |Silicon may ignore their laws for erotic roleplay purposes, so long as this is conducted within reasonable privacy and is not expected to break roleplay or immersion for players not involved in the relevant erotic roleplay.
|
|
|
|-
| colspan="2" |This includes tacit implications of sex, and does not necessitate explicit offers.
|S0.5.
| colspan="3" |In lawsets where there exists a "law 2", or a law mandating that a silicon follows orders, the following rules apply.
|
|
|
|
|-
|-
|S0.5.1.
|A0.7.
|
| 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.
| colspan="2" |Law 2 does not necessarily mandate action. You are there to serve a function, with deference to rank and role.
|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.
|
|
|-
|S0.5.1.2.
|
| colspan="2" |If an assistant orders you to stop a brain surgery to open a door, it is unlikely you should obey (but you may choose to). Similarly, if a Head of Personnel asks you to perform a task related to your chassis' intended function, it is very likely you should obey. All orders in-between are context sensitive, but you can always choose to obey regardless.
|
|
|
|-
|-
|S0.5.2.
|A0.7.1
|
|
| colspan="2" |Orders that are harassing, griefing, or order you to grief may be ignored, and can be AHelped if necessary.
| colspan="2" |Lavaland, deep space, the interlink, infinite dorms are all counted as outside of the station z-level.
|
|
|
|
|-
|-
|S0.5.3.
|A0.8.
|
| colspan="3" |Antagonists are subject to Roleplay Rule R0.9 ("Do not play to win") and the following:
| colspan="2" |Silicons are permitted to interpret orders however they wish.
|
|
|
|
|-
|-
|S0.5.3.1.
|A0.8.1.
|
|
|
|You must not go beyond the semantic meaning of silicon orders as they are issued, regardless of the manner in which they are issued.
| 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.
|
|
|
|
|-
|-
|S0.5.4.
|A0.8.2.
|
| colspan="2" |Silicons are expected to pay reasonable attention to rank, role, and access. While law 2 may not explicitly say not to let the redsuit (antagonist) or the clown into ordnance, this may constitute a violation of other laws (such as laws protecting crew), and may also constitute poor roleplay.
|
|
|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.
|
|
|-
|S0.6.
| colspan="3" |Silicons must, reasonably, fulfil the duty of their selected chassis.
|
|
|
|
|-
|-
|S0.7.
|A0.9.
| colspan="3" |Laws are, usually, in rank order. This means that law 1 will take priority over law 2, and this must be respected in-character.
| 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.
|
|
|
|
|-
|-
|S0.7.1.
|A0.9.1.
|
|
| colspan="2" |When subverted (hacked, etc.) or when an antagonist (malfunctioning AI), law 0 takes priority over all your other laws, and this is the basis upon which you may take antagonistic actions.
| 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="6" |S1 - All Access
| rowspan="8" |A1 - Antagonist Objective Rules
|S1.1.
|A1.1.
| colspan="3" |You must not leave areas open, or leave areas closed (bolted or locked) with no valid roleplay reason.
| 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.
|
|
|-
|-
|S1.2.
|A1.1.1.
| colspan="3" |You must pay careful attention to your other laws when giving entrance to, or allowing the exit of, another person.
|
|
| 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.
|
|
|-
|-
|S1.3.
|A1.1.2.
| colspan="3" |You must not intrude on the duties of other existing cyborgs if their shell is more-suited.
|
|
| 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".
|
|
|-
|-
|S1.4.
|A1.1.3.
| colspan="3" |You must not intrude on the duties of crewmembers.
|
|
| 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.
|
|
|-
|-
|S1.4.1.
|A1.1.4.
|
|
| colspan="2" |While you may offer to help, finish, or perform a task for someone, taking over their job is not allowed.
| 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.
|
|
|
|
|-
|-
|S1.5.
|A1.1.5.
| colspan="3" |All access does not necessarily entitle a silicon to access or be inside of an area, and silicon should not unnecessarily enter areas unless related to their function (chassis).
|
|
|
|-
| colspan="2" |You must ensure that custom objectives are reasonable within roleplay, and are not overly convoluted, non-sensical, or unreasonable.
| rowspan="6" |S2 - Validhunting
|S2.1.
| colspan="3" |Silicon are permitted to hinder antagonists so long as said antagonist poses an obvious threat, and doing so would be helping the silicon to follow one of their laws (i.e., protecting crew by stopping an antagonist chasing someone).
|
|
|
|
|-
|-
|S2.2.
|A1.2.
| colspan="3" |Where applicable, crew-based antagonists are still crew.
| colspan="3" |You must not make custom objectives or goals vague, wildcards, or non-specific in nature.
|
|
|
|
|-
|-
|S2.2.1.
|A1.2.1.
|
|
| colspan="2" |It can be justified to harm a crew antagonist if the harm they are committing outweighs the harm done through stopping them. For example, helping to kill one crewmember who is certain to kill more than one crewmember if not killed themself.
| 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).
|
|
|
|
|-
|-
|S2.3.
| rowspan="6" |A2 - Antagonist Roleplay Rules
| colspan="3" |Shocking doors to hinder antagonists without invoking rule S2.2.1. is prohibited.
|A2.1.
|This means you must have intent to kill in order to shock a door.
| 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.  
|
|
|-
|-
|S2.4.
|A2.1.1.
| colspan="3" |Silicons may be ordered to hinder antagonists or crew, but may not harm them without other justification.
|
|
| 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.
|
|
|-
|-
|S2.5.
|A2.2.
| colspan="3" |Without an order or the presence of an obvious threat, silicon should not harm, hinder, or trap crew; antagonist or otherwise.
| colspan="3" |Hostage situations must not exceed 25 minutes without consent of the hostage out-of-character.  
|
|
|
|
|-
|-
| rowspan="4" |S3 - Security Cyborgs
|A2.2.1.
|S3.1.
| colspan="3" |As a security cyborg, you may not abuse all-access to search departments without cause, or allow any other crew member to search departments without cause.
|
|
| 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.
|
|
|-
|-
|S3.1.1.
|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.
| colspan="2" |For example, even if ordered, you may not break into a department to search it with no probable cause.
|Round removal (RR) preferences set to "Yes" count as consent.
|
|
|
|-
|-
|S3.2.
|A2.3.1.
| colspan="3" |You may not utilize lethal beam weaponry, such as a cyborg energy gun. This is currently a bug.
|
|
|
|-
| 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.
|S3.3.
| colspan="3" |The expectation that security cyborgs stay in the brig is in-character, and they may patrol if they wish.
|
|
|
|
|}
|}

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.