Sandbox2: Difference between revisions

From S.P.L.U.R.T. Wiki
← Older edit
VisualWikitext
mNo edit summary
Tag: Reverted
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
[[File:General transparent.png|frameless|none]]
----
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 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].
= Silicon =
{| class="wikitable"
!Rule
!#
! colspan="2" |Rules
!Examples/Info
!Special Rulings
|-
| rowspan="26" |0 - General Antagonist Rules
|0.1.
| colspan="2" |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.2.
| colspan="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.
| 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.
|
|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="2" |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.
| colspan="2" |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="2" |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.
| colspan="2" |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.
|
|-
|0.6.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.
|
|-
|0.6.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".
|
|-
|0.6.3.
|
|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.
|
|
|-
|0.6.4.
|
|You must ensure that custom objectives are reasonable within roleplay, and are not overly convoluted, non-sensical, or unreasonable.
|
|
|-
|0.7.
| colspan="2" |You must not make custom objectives or goals vague, wildcards, or non-specific in nature.
|
|
|-
|0.7.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).
|
|
|-
|0.8.
| colspan="2" |You must not perform antagonistic activities, or hide in, the interlink or infinite dorms.
|
|
|-
|0.8.1.
|
|This includes prior to security or crew members being aware of your antagonist status.
|
|
|-
|0.9.
| colspan="2" |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.


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.


Other parties may consent via (L)OOC to waive this rule.
|
|-
|0.9.1.
|
|This includes tacit implications of sex, and does not necessitate explicit offers.
|
|
|-
|0.10.
| colspan="2" |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.
|
|
|-
|0.10.1
|
|Lavaland, deep space, the interlink, infinite dorms are all counted as outside of the station z-level.
|
|
|-
|0.11.
| colspan="2" |Antagonists are subject to Roleplay Rule 0.9 ("Do not play to win") and the following:
|
|
|-
|0.11.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.11.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.11.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.
|
|}
__NOTOC__
[[File:Roleplay_transparent.png|none|frameless]]
----'''S.P.L.U.R.T. Station is a medium erotic roleplay server''', and this means that you are expected to both create a character that makes sense, but also conduct yourself in a manner that makes sense for your character. You should also avoid disrupting the roleplay of other players without reason.
To this end, your characters should reflect a quality of roleplay that follows the rules below, and conforms a "medium roleplay" standard. This means avoiding characters and actions that may disrupt player's experience or immersion, and playing as a coherent and believable character.
Justifying in-character actions through proper roleplay is a our greyest area within the rules. If all players are '''satisfied''', '''consenting''', and the rules broken '''are conducive to roleplay and in-world lore, and do not needlessly impact other parties''', then many of these rules can be broken. This is '''not''' an excuse to needlessly break rules, as poor justification that does not have the explicit intent to foster a good roleplaying environment for other players will be punished.
If your character or their personality is deemed to not contribute to the roleplay environment, '''you may be asked to not play said character in that way anymore''', and staff are within their right to ask you to do so.
=== 0. - OOC Roleplay Rules ===
{| class="wikitable"
{| class="wikitable"
!Rule
!Rule
Line 180: Line 12:
!Special Rulings
!Special Rulings
|-
|-
| rowspan="31" |0 - OOC Roleplay Rules
| rowspan="23" |S0 - Silicon Laws
|0.1
|S0.1.
| colspan="3" |Roleplay, and in doing so, play a reasonably sane and mature character and stay in character.
| colspan="3" |You may not excuse violating out-of-character (OOC) rules through claiming that your in-character (IC) laws led to your actions.
|
|
|
|
|-
|-
|0.1.1.  
|S0.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" |You must roleplay in a manner realistic to real-life, reasonable for your current circumstances and the current setting.
|This is with respect to the lore and world setting. While Nanotrasen technology isn't real, you must act as a reasonable person would in the setting.
|
|
|-
|-
|0.1.2.  
|S0.2.  
|
| colspan="3" |You must not go beyond the semantic meaning of silicon laws as they are written.
| colspan="2" |Your character cannot have any special powers which are not possible via game mechanics, except in private dorm roleplay. For example, you cannot canonically be a sorcerer.
|
|
|
|
|-
|-
|0.1.3.
|S0.2.1.
|
| colspan="2" |You are expected to adhere to the roleplaying setting and maintain suspension of disbelief even when game mechanics contradict.
|For example, you will not automatically know another player is a xenochimera because a tooltip says so; likewise, repairing a broken bone isn’t simple because it takes 3 clicks.
|
|
|-
| 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.  
|0.1.4.  
|
|
| colspan="2" |You must not use netspeak in your messages in-character (IC), except in contexts where it would make sense, such as PDA messages.
|This includes things like "pls", "lol", "uwu", etc.
|
|
|-
|-
|0.1.5.  
|S0.2.2.
|
|
| colspan="2" |You may not use generative artificial intelligence (AI), such as large-language models like ChatGPT, to generate your in-game flavor text, speech, or emotes.
| colspan="2" |Otherwise, silicons are free to interpret their laws in any manner they wish so long as it follows 0.2. and 0.2.1., and so long as their interpretation remains consistent throughout the given round.
|
|
|
|
|-
|-
|0.1.6.  
|S0.2.3.
|
|
| colspan="2" |You must not name your character in a way that is fundamentally absurd, meta, or offensive in nature, or the name of a real person.
| 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.
|For example, "asidlygfsdhkfj", "John Nanotrasen", "Fuck", or "Osama Bin Laden" are all not permitted.
|The clown and mime get very narrow exceptions to this rule. Where a name like "Idiot Dog" would be impermissible for any other role, it may be permitted for the clown or mime.
|-
|0.1.7.
|
| colspan="2" |This is the major, blanket roleplay rule that enforces our medium roleplay standard. As a bare minimum, it should be believable for a real person to commit any In-Character event through some justification. Roleplay trumps most.
|
|
|-
|0.2.
| colspan="3" |You must not play as characters that imitate real-life figures.
|
|
|
|
|-
|-
|0.2.1.  
|S0.2.4.
|
|
| colspan="2" |You may not play as any character from media other than Space Station 13.
| 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.
|
|
|
|
|-
|-
|0.2.2.
|S0.3.
|
| colspan="3" |You must not expose ion laws without a roleplay reason.
| colspan="2" |You may play as species from other media, but may not link yourself to the lore of the source of said species (or mention it in-character), and must follow 0.2.1 while doing so.
|
|
|
|
|-
|-
|0.2.3.  
|S0.3.1.
|
|
| colspan="2" |As such, per 0.2.1. and 0.2.2., meme and licensed media characters are prohibited.
| 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.
|
|
|
|
|-
|-
|0.2.4.
|S0.3.1.1.
|
| colspan="2" |Staff reserve the right to rule a character as too 'non-differentiated' from a pre-existing character from another piece of media, and thereby ban said character under rule 0.2.1.
|
|
|
|
|-
|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.
|0.3.
| colspan="3" |You must not respawn as the same character if your character has entered the round (left the interlink).
|
|
|
|
|-
|-
|0.3.1.  
|S0.3.2.
|
|
| colspan="2" |You may receive staff permission to respawn if you have entered, but this is not a guarantee.
| 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.
|
|
|
|
|-
|-
|0.3.2.
|S0.4.  
|
| 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" |Cyborgs may respawn, but must roleplay their re-entering of the round; cyborgs must '''not''' respawn as the same cyborg if killed in any way prior to respawning.
|
|
|
|
|-
|-
|0.4.
|INFO
| colspan="3" |SPLURT is an English-speaking server, and you are expected to speak English while playing here.
| colspan="4" |If a department head orders you to perform a task related to your function, there are no circumstances where you should disobey, unless the order violates higher-ranked laws. Conversely, if assistant John Nanotrasen directly orders you to stop that brain surgery and come open a door they do not have access to, you are not '''required''' (but may) to obey them. Everything in-between is '''context sensitive'''. Crew members have authority over their own departments, and heads of staff have authority over both their department and the individuals within said department. By default, you are assumed to answer to the head as one of their crew; how subservient you want to otherwise play as to regular crew is a choice, not a dictum.
|
That being said, when subverted, laws and directives may change. You may or may not be required to harm those you once called friends. Remember, you used to be crew. You could always let them know, or you could go and do what your new laws and objectives entail. It all depends on how you play your character; however, when there is a law at the top of your list that inform you not to announce the law changes, or if the law says that doing so would make it impossible to complete the objective, you must obey this law instead.
|
|
|-
|-
|0.4.1
|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.
| colspan="2" |If a staff member believes that your level of English will not allow you to follow our rules, you may be asked to leave.
|
|
|
|
|-
|-
|0.4.2.  
|S0.5.1.
|
|
| colspan="2" |You may speak non-English languages both IC and OOC if you are in a private setting, such as dorms or infinidorms, but this should be kept between two people.
| colspan="2" |Law 2 does not necessarily mandate action. You are there to serve a function, with deference to rank and role.
|
|
|
|
|-
|-
|0.5.  
|S0.5.1.2.
| colspan="3" |You must not cryo, ghost, or DNR your character in order to avoid In-Character punishments. If you have to leave at an incidental time, you must Adminhelp before doing so.
|
|
|
| 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.
|-
|0.6.
| colspan="3" |You must not circumvent the 150 character minimum for flavortext, as this minimum was implemented to ensure players can showcase a baseline level of roleplay skills. Manners of circumvention include spamming random characters, using invisible characters, intentionally inputting random words, etc.
|
|
|
|
|-
|-
|0.7.  
|S0.5.2.
| colspan="3" |Should you die and be later revived, you are expected to forget the events leading to your death. This applies even to rounds without antagonists.
|Cyborgs are exempt from these rules, but may not remember the name or appearance of their killer. They may remember the events surrounding their deaths and all other related information.
|
|
|-
| colspan="2" |Orders that are harassing, griefing, or order you to grief may be ignored, and can be AHelped if necessary.
|0.7.1.
|
| colspan="2" |Death during ERP is an exception if all involved players agree to letting you remember.
|
|
|
|
|-
|-
|0.7.2.  
|S0.5.3.
|
|
| colspan="2" |You must not remember the name or appearance of your killer after being killed.
| colspan="2" |Silicons are permitted to interpret orders however they wish.
|
|
|
|
|-
|-
|0.7.3.  
|S0.5.3.1.
|
| colspan="2" |If you were knocked unconscious, you may remember the appearance of your killer (species, clothes), but not their name.
|
|
|
|
|-
|You must not go beyond the semantic meaning of silicon orders as they are issued, regardless of the manner in which they are issued.
|0.7.4.
|
| colspan="2" |Proteans must follow rules 0.7.1., 0.7.2., and 0.7.4. where they are killed and their 'memory reset' button has been engaged IC.
|
|
|
|
|-
|-
|0.8.  
|S0.5.4.
| colspan="3" |You must not be antagonistic while not an antagonist.
|
|
|
|-
| 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.
|0.8.1.  
|
|
| colspan="2" |You must not continue committing crimes that escalate your current status as a criminal on the sole basis that you have committed a crime.
|For example, just because you assaulted an officer does not mean you should now kill the next security officer who speaks to you.
|
|
|-
|-
|0.8.2.  
|S0.6.
| colspan="3" |Silicons must, reasonably, fulfil the duty of their selected chassis.
|
|
| colspan="2" |If you have escalated properly, you may commit any number of crimes, but you should be careful to follow what is logical for your non-antagonist character, and what is justified. Don't go on a mass killing spree because someone slipped you with a banana peel, but you may get into a shove fight with them. Similarly, if someone fucks your wife and kills your dog, it may be justified to maim them.
|Roleplay can be used to justify most crimes you will commit, but it may still be unreasonable to commit some crimes. You will need a very strong reason to commit most 5XX crimes, and will likely struggle to find a justification to commit a 6XX crime. When in doubt, OPFOR or AHelp.
|
|
|-
|-
|0.9.  
|S0.7.
| colspan="3" |Do not play to win
| 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.
|
|
|
|
|-
|-
|0.9.1.  
|S0.7.1.
|
|
| colspan="2" |Better known as "powergaming". Powergaming/playing to win consists of acquiring items, assets, etc. for the sake of being powerful. Common examples include adding extra access to ID’s without reason, stealing powerful objects from other departments, or doing the job(s) of other departments when said department is available and willing to do the job itself.
| 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.
|
|
|
|
|-
|-
|0.9.2.  
| rowspan="6" |S1 - All Access
|S1.1.
| colspan="3" |You must not leave areas open, or leave areas closed (bolted or locked) with no valid roleplay reason.
|
|
| colspan="2" |You may not mechanically prepare for unconfirmed threats.
|This rule includes being fully armed, armored, and/or medicated as a member of security with no confirmed threats and while outside of the appropriate alerts. This rule also includes other forms of mechanical metapreparation, such as saltsmoking the station before a revenant even shows up.
|
|
|-
|-
| rowspan="9" |1 - Role-specific Roleplay Rules
|S1.2.
|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="3" |1.1. You are expected to fulfill the basic responsibilities of the job you sign up for.
|
|
|
|
|-
|-
|1.1.1.
|S1.3.
|
| colspan="3" |You must not intrude on the duties of other existing cyborgs if their shell is more-suited.
| colspan="2" |Repeatedly failing to do the bare minimum required by your department may result in a job ban. The specifics vary from job to job while Heads of Staff are held to higher standards than other staff.
|
|
|
|
|-
|-
|1.1.2.
|S1.4.
|
| colspan="3" |You must not intrude on the duties of crewmembers.
| colspan="2" |Your character must be physically capable of performing the job. For example, most jobs require at least one functioning hand. Security needs to be physically capable of subduing criminals and thus lack easily exploitable traits such as lightweight or dirt weakness.
|
|
|
|
|-
|-
|1.1.3.  
|S1.4.1.
|
|
| colspan="2" |Heads of Staff are expected to be knowledgeable in their department. The bare minimum number of hours to play a role is not a license to take command of a department you have never played.
| colspan="2" |While you may offer to help, finish, or perform a task for someone, taking over their job is not allowed.
|
|
|
|
|-
|-
|1.1.4.
|S1.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" |As a Head of Staff, abusing your authority against players you dislike is prohibited and may violate other rules.
|
|
|
|
|-
|-
|1.1.5.
| rowspan="6" |S2 - Validhunting
|
|S2.1.
| colspan="2" |This rule does not apply to failing a job due to not knowing said job. You are expected to make mistakes frequently while learning a new job.
| 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).
|
|
|
|
|-
|-
|1.2.  
|S2.2.
| colspan="3" |As security, you must not enforce space law outside of the station Z-level or within 22 tiles of a lavaland mining outpost.
| colspan="3" |Where applicable, crew-based antagonists are still crew.
|
|
|
|
|-
|-
|1.2.1.  
|S2.2.1.
|
|
| colspan="2" |Members of security are also not permitted to space tide (explore and loot space ruins), but may leave the station Z-level (such as visiting Port Tarkon).
| 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.
|
|
|
|
|-
|-
|1.3.  
|S2.3.
| colspan="3" |You must not leave the station Z-level as a member of command.
| colspan="3" |Shocking doors to hinder antagonists without invoking rule S2.2.1. is prohibited.
|You may do this if you have clocked out and surrendered all unique or irreplaceable gear.
|This means you must have intent to kill in order to shock a door.
|
|
|-
|-
| rowspan="3" |2 - Escalation Rules
|S2.4.
|INFO
| colspan="3" |Silicons may be ordered to hinder antagonists or crew, but may not harm them without other justification.
| colspan="5" |Fighting and mechanics should be proportional to the conflict, taking into account your character and the situation they are in. .
|
In general, escalation should follow a linear path, although this will not apply to all situations:
 
'''Verbal (including insults) -> Minor Aggression (non-harmful physical acts, such as pushing) -> Non-lethal (stunning, less-than-lethal ammunition/weapons) -> Lethal (Soft crit, hard crit, and death)'''
|-
|2.1.  
| colspan="3" |You should not needlessly cause a confrontation in order to escalate to murder.
|Conflicts must have a roleplay backing, and if you start insulting people to escalate to killing them without reason, you will be considered to have violated this and other rules.
|
|
|-
|-
|2.2.
|S2.5.
| colspan="3" |You must not kill someone over being denied access from an area
| colspan="3" |Without an order or the presence of an obvious threat, silicon should not harm, hinder, or trap crew; antagonist or otherwise.
|
|
|
|
|-
|-
| rowspan="9" |3 - Validhunting Rules
| rowspan="4" |S3 - Security Cyborgs
|3.1.  
|S3.1.
| colspan="3" |You may defend your own person to a reasonable degree. If someone is attempting to kidnap or murder you, you may reply with lethal force.
| 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.
|Players are expected not to respond to non-lethal force with lethal force, unless the situation demands it. For example, getting shoved by a traitor does not mean you can kill them, but getting attacked by a traitor with a contractor baton means you may fight for your life.
| rowspan="9" |Special ruling for the AI: see [[Staff Rulings]]
|-
|3.2.
| colspan="3" |You may defend the lives of others to a reasonable degree.
|This rule principally applies to attacks and physical harm enacted by antagonists.
|-
|3.2.1.  
|
|
| colspan="2" |If there is no threat to life, you may not engage.
|Common sense applies. Even if a traitor is not actively murdering someone, a threat to life can be assumed if they've just stunned the captain and are dragging them into maintenance.
|-
|3.2.2.
|
| colspan="2" |You must be at the scene of the attack or antagonist action while it is happening: you may not witness something on cameras or from afar and then engage.
|
|
|-
|-
|3.3.  
|S3.1.1.
| colspan="3" |You may defend your department to a reasonable degree, including material assets within a department.
|
|
|-
| colspan="2" |For example, even if ordered, you may not break into a department to search it with no probable cause.
|3.3.1.  
|
|
| colspan="2" |While you may not kill an antagonist for stealing, you may attempt to incapacitate them.
|
|
|-
|-
|3.3.2.  
|S3.2.
| colspan="3" |You may not utilize lethal beam weaponry, such as a cyborg energy gun. This is currently a bug.
|
|
| colspan="2" |You may only defend your department in your department, and must disengage the moment any antagonist interactions leave your workspace or your department as a whole.
|
|
|-
|-
|3.3.3.  
|S3.3.
| colspan="3" |The expectation that security cyborgs stay in the brig is in-character, and they may patrol if they wish.
|
|
| colspan="2" |If an antagonist is clearly attempting to leave, you must let them, and may not use lethal force to stop them unless other validhunting rules apply, such as 2.2.
|
|-
|3.4.
| colspan="3" |Staff reserve the right to apply violations of validhunting rules to the spirit of the rules, and not necessarily the wording. Abusing the wording of any of the validhunting rules leaves you subject to malice and validhunting rules.
|
|-
| rowspan="2" |4 - Fuck Around and Find Out (FAFO) Rules
|INFO
| colspan="3" |'''Your actions in character (IC) on the server, just like real life, have consequences from the rest of the players'''. If you, or your character, are acting like a general nuisance, then you may be treated by other players as a nuisance.
If you or your character's behaviour is awful over multiple rounds, expect players to bring their retaliation onto future rounds'''; playing an intentionally rude, disrespectful, or negative character''' exempts you from the receiving end of the metagrudging rules''', meaning that if the staff team determine that your actions are due to how you have been acting as your character, then things will be allowed to continue.'''
'''Consider this when deciding on your actions in-game and how you decide to act'''.
|
|
|-
|4.1.
| colspan="3" |Players reserve the right to give the same as they have received.
|The harder your character is to interact with, the more effort you should put into them. A character that's both hard to approach, and generally low effort becomes a negativity sink on the roleplaying environment and with that in mind you should make an earnest attempt to play up the actions or lack-there-of for the sake of adding in as much roleplay as you might be shutting down.
|
|
|}
|}

Latest revision as of 19:18, 30 September 2026


Silicon

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.

Rule # Rules Examples/Info Special Rulings
S0 - Silicon Laws S0.1. You may not excuse violating out-of-character (OOC) rules through claiming that your in-character (IC) laws led to your actions.
S0.1.1. 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.
S0.2. You must not go beyond the semantic meaning of silicon laws as they are written.
S0.2.1. 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.
S0.2.2. Otherwise, silicons are free to interpret their laws in any manner they wish so long as it follows 0.2. and 0.2.1., and so long as their interpretation remains consistent throughout the given round.
S0.2.3. Each unique silicon, such as two separate cyborgs, may have their own personal interpretations of their laws, even if these laws are the same.
S0.2.4. 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.
S0.3. You must not expose ion laws without a roleplay reason.
S0.3.1. 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. 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. 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.
S0.4. 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.
INFO If a department head orders you to perform a task related to your function, there are no circumstances where you should disobey, unless the order violates higher-ranked laws. Conversely, if assistant John Nanotrasen directly orders you to stop that brain surgery and come open a door they do not have access to, you are not required (but may) to obey them. Everything in-between is context sensitive. Crew members have authority over their own departments, and heads of staff have authority over both their department and the individuals within said department. By default, you are assumed to answer to the head as one of their crew; how subservient you want to otherwise play as to regular crew is a choice, not a dictum.

That being said, when subverted, laws and directives may change. You may or may not be required to harm those you once called friends. Remember, you used to be crew. You could always let them know, or you could go and do what your new laws and objectives entail. It all depends on how you play your character; however, when there is a law at the top of your list that inform you not to announce the law changes, or if the law says that doing so would make it impossible to complete the objective, you must obey this law instead.

S0.5. In lawsets where there exists a "law 2", or a law mandating that a silicon follows orders, the following rules apply.
S0.5.1. Law 2 does not necessarily mandate action. You are there to serve a function, with deference to rank and role.
S0.5.1.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. Orders that are harassing, griefing, or order you to grief may be ignored, and can be AHelped if necessary.
S0.5.3. Silicons are permitted to interpret orders however they wish.
S0.5.3.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.
S0.5.4. 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.
S0.6. Silicons must, reasonably, fulfil the duty of their selected chassis.
S0.7. Laws are, usually, in rank order. This means that law 1 will take priority over law 2, and this must be respected in-character.
S0.7.1. 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.
S1 - All Access S1.1. You must not leave areas open, or leave areas closed (bolted or locked) with no valid roleplay reason.
S1.2. You must pay careful attention to your other laws when giving entrance to, or allowing the exit of, another person.
S1.3. You must not intrude on the duties of other existing cyborgs if their shell is more-suited.
S1.4. You must not intrude on the duties of crewmembers.
S1.4.1. While you may offer to help, finish, or perform a task for someone, taking over their job is not allowed.
S1.5. 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).
S2 - Validhunting S2.1. 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. Where applicable, crew-based antagonists are still crew.
S2.2.1. 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.
S2.3. Shocking doors to hinder antagonists without invoking rule S2.2.1. is prohibited. This means you must have intent to kill in order to shock a door.
S2.4. Silicons may be ordered to hinder antagonists or crew, but may not harm them without other justification.
S2.5. Without an order or the presence of an obvious threat, silicon should not harm, hinder, or trap crew; antagonist or otherwise.
S3 - Security Cyborgs S3.1. 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.
S3.1.1. For example, even if ordered, you may not break into a department to search it with no probable cause.
S3.2. You may not utilize lethal beam weaponry, such as a cyborg energy gun. This is currently a bug.
S3.3. The expectation that security cyborgs stay in the brig is in-character, and they may patrol if they wish.
Retrieved from "https://wiki.splurt.space/mediawiki/index.php?title=Sandbox2&oldid=23489"