diff --git a/Resources/Prototypes/_StarLight/Guidebook/rules.yml b/Resources/Prototypes/_StarLight/Guidebook/rules.yml index 940e9d72de9f..07d70a4c6f7f 100644 --- a/Resources/Prototypes/_StarLight/Guidebook/rules.yml +++ b/Resources/Prototypes/_StarLight/Guidebook/rules.yml @@ -104,11 +104,16 @@ priority: 13 text: "/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL13.xml" -# Clarifications +- type: guideEntry + id: RuleSL14 + name: guide-entry-sl-rule-14 + ruleEntry: true + priority: 14 + text: "/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL14.xml" - type: guideEntry - id: RuleSLC1 - name: guide-entry-sl-clarification-1 + id: Metashield + name: guide-entry-Metashield ruleEntry: true - priority: 1 - text: "/ServerInfo/Guidebook/ServerRules/RulesSL/Clarifications/RuleSLC1.xml" \ No newline at end of file + priority: 15 + text: "/ServerInfo/Guidebook/ServerRules/RulesSL/Clarifications/Metashield.xml" \ No newline at end of file diff --git a/Resources/ServerInfo/Guidebook/Antagonist/Abductors.xml b/Resources/ServerInfo/Guidebook/Antagonist/Abductors.xml index 6e69dc800730..cab30e373375 100644 --- a/Resources/ServerInfo/Guidebook/Antagonist/Abductors.xml +++ b/Resources/ServerInfo/Guidebook/Antagonist/Abductors.xml @@ -28,7 +28,7 @@ - Change out their cuffs for a higher grade of handcuffs provided on the ship. - Remove any of their belongings that could damage you or the secrecy of the experiment. - Use your vast surgical knowledge to replace their heart with a gland. - - Optionally: Give them back their primitive technology. + - Give them back their primitive technology. Finally, drag the victim whom you have completed your experiment on into the [color=#a149bf]Experimentator[/color] to confirm the results of the experiment on the [color=#a149bf]Abductor Console[/color] and send them back where you found them. diff --git a/Resources/ServerInfo/Guidebook/Command.xml b/Resources/ServerInfo/Guidebook/Command.xml index 11696e42757c..b70fec12bfb8 100644 --- a/Resources/ServerInfo/Guidebook/Command.xml +++ b/Resources/ServerInfo/Guidebook/Command.xml @@ -42,7 +42,7 @@ The remote influences where people move around. Heads can lock personnel out of You also have access to your very own [color=#1b67a5]Command[/color] channel, like every other department. However, yours is particularly special as the people who can hear you have [color=#a4885c]entire departments[/color] at their fingertips. Use this to communicate with other heads and be a representative of what your workers want or need. -The [color=#1b67a5]Captain[/color] and the [color=#9fed58]Head of Personnel[/color] get access to the lucrative [color=#a4885c]master encryption key[/color], letting them tune into every radio channel on the station. This is extremly valuable, as you can coordinate between departments yourself. +The [color=#1b67a5]Captain[/color] gets access to the [color=#a4885c]master encryption key[/color], letting them tune into every radio channel on the station. This is extremly valuable, as you can coordinate between departments yourself. [color=#a4885c]Don't waste this vital advantage![/color] diff --git a/Resources/ServerInfo/Guidebook/NewPlayer/Controls/Radio.xml b/Resources/ServerInfo/Guidebook/NewPlayer/Controls/Radio.xml index 39ee8ae3ff44..ccd73b7e16a2 100644 --- a/Resources/ServerInfo/Guidebook/NewPlayer/Controls/Radio.xml +++ b/Resources/ServerInfo/Guidebook/NewPlayer/Controls/Radio.xml @@ -20,7 +20,7 @@ People may not be able to make out all of what you're saying if you're standing Your radio allows you to communicate across the entire station and to your specific [color=#a4885c]department[/color]. - + To send a [color=#a4885c]station-wide[/color] message over the radio preface, use the [color=#32cd32]Common[/color] channel by beginning your text with [color=#32cd32]semi-colon (;)[/color]. diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml index 7b8cfbcf61e0..da22bb9eb241 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml @@ -16,4 +16,4 @@ - [textlink="12. Players must be and act at least 16 years old" link="RuleC12"] - [textlink="13. Use realistic character names, and do not use names of famous people" link="RuleC13"] - [textlink="14. Do not use LOOC or OOC to share current round information" link="RuleC14"] - + \ No newline at end of file diff --git a/Resources/ServerInfo/Guidebook/ServerRules/DefaultRules.xml b/Resources/ServerInfo/Guidebook/ServerRules/DefaultRules.xml index 6d876f36761e..9f8d01ee504c 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/DefaultRules.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/DefaultRules.xml @@ -1,63 +1,40 @@ # Server Rules - This is a roleplay server, meaning that roleplay rules apply. [color=#ff0000]This is also a medium roleplay (MRP) server, meaning that MRP Amendments do apply.[/color] +The following rules are for the Starlight Space Station 14 servers. Violating these rules may result in a warning, a temporary ban, or a permanent ban. You may also be banned from specific roles/jobs/departments. Bans can be appealed in the official Starlight Discord server. - Space Station 14 is not like most games. Many rules are designed to require roleplay, and not all rules are intuitive. Please take the time to read and understand the rules before you play so that you aren't surprised. Some of our rules are zero tolerance rules, meaning that a violation will result in an indefinite ban without any warning. Game admins will treat you as if you have read the rules, even if you have not. +Players are also expected to understand Metashield. All rules and the metashield are often more up to date on the starlight wiki. - ## Core Rules +If you are ever in doubt as to whether or not something is breaking the rules, feel free to contact the admins via Admin Help or ask on the Discord server. + +For in-universe laws and rules check Corporate Law and SOP. + +Remember, the rules and examples given here are NOT exhaustive. (See Rule 1) + +The servers are strictly [bold]16+ only[/bold]. + +Deathmatch and sandbox gamemodes may not have these rules apply, rules will be given if they are changed. Ghost chat is an out of character in game chat, and does not need to apply to MRP rules. + +## Core Rules These rules apply at all times, including between rounds. - - [textlink="1. Admins have final say" link="RuleC1"] - - [textlink="2. Don't be a dick" link="RuleC2"] - - [textlink="3. No Hate Speech or Discriminatory Language" link="RuleC3"] - - [textlink="4. No sexual content/themes, including erotic roleplay (ERP) and no shock content" link="RuleC4"] - - [textlink="5. Do not use out of game methods to communicate with other players" link="RuleC5"] - - [textlink="6. Do not attempt to evade bans" link="RuleC6"] - - [textlink="7. Only use English" link="RuleC7"] - - [textlink="8. Do not exploit the game, use cheats, or macros" link="RuleC8"] - - [textlink="9. Do not use multiple accounts, or alt accounts, and do not share accounts" link="RuleC9"] - - [textlink="10. Do not abuse or ignore admin messages" link="RuleC10"] - - [textlink="11. Do not threaten to ahelp other players or argue with them about rules" link="RuleC11"] - - [textlink="12. Players must be and act at least 16 years old" link="RuleC12"] - - [textlink="13. Use realistic character names, and do not use names of famous people" link="RuleC13"] - - [textlink="14. Do not use LOOC or OOC to share current round information" link="RuleC14"] - - ## Roleplay Rules - These rules only apply during a round. A round ends only when the game returns to the lobby. [color=#ff0000]All of these rules apply fully whenever the game is not at the lobby unless it is in an exempt game mode.[/color] - - The deathmatch and sandbox game modes are exempt from these rules. Players who choose to not follow these rules are entirely responsible for knowing if an exempt game mode is active. - - Roleplay rules do not apply to ghosts/spectators/observers while they are ghosts/spectators/observers. Dead chat is considered to be an in-game out of character chat channel. - - See the list of [textlink="role types" link="RoleTypes"] for more information about the different types of roles. - - - [textlink="1. Silicons must follow Silicon Rules" link="RuleR1"] - - [textlink="2. Familiars must obey their master" link="RuleR2"] - - [textlink="3. Roleplay a normal person" link="RuleR3"] - - [textlink="4. Do not metagame, obey the Metashield" link="RuleR4"] - - [textlink="5. Don't interfere with arrivals" link="RuleR5"] - - [textlink="6. Don't act like an antagonist unless the game tells you that you are one" link="RuleR6"] - - [textlink="7. Do not stall the round" link="RuleR7"] - - [textlink="8. As an antagonist, only be friendly to your team and don't work against your team" link="RuleR8"] - - [textlink="9. As an antagonist, do not cause excessive death, damage, or destruction beyond your objectives" link="RuleR9"] - - [textlink="10. Listen to your team leader" link="RuleR10"] - - [textlink="11. Follow reasonable escalation" link="RuleR11"] - - [textlink="12. Do not abandon your role" link="RuleR12"] - - [textlink="13. Stick to your role" link="RuleR13"] - - [textlink="14. Set an example if playing command or security" link="RuleR14"] - - [textlink="15. Command and Security must follow Space Law" link="RuleR15"] - - ## Silicon Rules - You are only silicon if the game clearly and explicitly tells you that you are a silicon. For players who are silicons, these Silicon Rules override all roleplay rules if there is any conflict. Silicon Rules do not override core rules. - - - [textlink="1. Your silicon laws are rules" link="RuleS1"] - - [textlink="2. Laws must be prioritized by their order" link="RuleS2"] - - [textlink="3. Laws can redefine terms used in other laws" link="RuleS3"] - - [textlink="4. You cannot request or allow a law change" link="RuleS4"] - - [textlink="5. You are a free agent if you have no laws" link="RuleS5"] - - [textlink="6. You are not required to follow orders which are extremely unreasonable" link="RuleS6"] - - [textlink="7. You must remain consistent with your interpretation of laws" link="RuleS7"] - - [textlink="8. Your HUD determines who is crew" link="RuleS8"] - - [textlink="9. Harm refers to physical harm, prioritized by immediacy and likelihood" link="RuleS9"] - - [textlink="10. You may determine how you resolve conflicts between orders" link="RuleS10"] + - [textlink="0. Be Respectful" link="RuleSL0"] + - [textlink="1. Respect Admin Decisions" link="RuleSL1"] + - [textlink="2. No Griefing, Bug Abuse, or Exploits" link="RuleSL2"] + - [textlink="3. Abide by Medium Roleplay (MRP) Standards" link="RuleSL3"] + - [textlink="4. Escalation of Force Must Make Sense" link="RuleSL4"] + - [textlink="5. Antagonists Must Follow MRP Logic" link="RuleSL5"] + - [textlink="6. Your Character Must Make Sense" link="RuleSL6"] + - [textlink="7. Self-Antagonism" link="RuleSL7"] + - [textlink="8. No Validhunting" link="RuleSL8"] + - [textlink="9. Interacting with SSD/AFK Players" link="RuleSL9"] + - [textlink="10. Erotic Roleplay is Forbidden" link="RuleSL10"] + - [textlink="11. New Life" link="RuleSL11"] + - [textlink="12. Silicons Must Follow Their Laws" link="RuleSL12"] + - [textlink="13. Command and Whitelist Expectations" link="RuleSL13"] + - [textlink="14. Continuity Guidelines" link="RuleSL14"] + +## Supporting documents +These documents are related to the rules in some way. +- [textlink="Metashield" link="Metashield"] + \ No newline at end of file diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/Clarifications/Metashield.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/Clarifications/Metashield.xml new file mode 100644 index 000000000000..197d6aa0573d --- /dev/null +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/Clarifications/Metashield.xml @@ -0,0 +1,227 @@ + +# Metashields + +The up to date metashield cheat sheet can be found on the starlight wiki. However, for your convenience a list has been provided here: + +[bold]Never Revealed:[/bold] The current gamemode and possible antagonists; sensitive information from previous rounds; information from other characters you've played; information about other players rather than their characters; information gained while dead, critical, observing, or a ghost. + +[bold]Believed Rumors:[/bold] Abductors, vampires, and wizards are probably real, but nobody knows specifics. + +[bold]Revealed to Certain Jobs:[/bold] Changelings are real and how they function, Paradox Clones are real, Which corporations are members of the syndicate, Zombies are real and how they function, Ninjas are real and what their goals and tools are, Revolutionaries use mind control flashes, Nuclear operatives are real, Non-NanoTrasen implant specifics, Memetic and Mystical effects + +[bold]Revealed by Discovery:[/bold] Chamelon items exist, Additional Communication channels in headsets, Secret purpose items like exploding pens, Deathsquad's true purpose. + +## Never Revealed IC +Anything listed below can never be known by your characters, and knowledge of any of the below always constitutes metagaming. +\n +- The current game mode and possible antagonists during the current game mode. +- Metashielded or sensitive information that happened in previous rounds. +- Events you experienced as a different character. +- All information related to the player of a character rather than the character itself. +- All information gained while critical, dead, sleep, a ghost, unconscious in any way, or observing. + +## Believed Rumors +Rumors that exist, which are commonly believed. These are often partial-truths that are accepted due to numerous witness testimonies and a lack of any effort to obscure this information, but come with blind spots and misconceptions. + +- Abductors are understood to probably be real, but are so rarely encountered that most people have never seen one. This has not prevented their image from seeping into media and iconography. What they actually do and how they function is completely unknown. +- Vampires are understood to be real, but most people believe outlandish versions that more closely resemble movie vampires than actual vampires. Knowledge of the Vampire Elders is completely unknown. +- Wizards are understood to be real, but most people believe them to be an esoteric and outlandish cult mistaking alien artifacts for wizardry. The Wizard Federation is a known faction, but how they operate and what they do is completely unknown. +- Revealed to Certain Jobs + +## Known to Certain Jobs + +This covers cases when a certain job should realistically come into contact with these things often, and failure to know them while holding certain positions would be considered incompetence. + +[bold][color=green]The fact that Changelings are real. The concept of shapeshifters exists in media in universe, but the fact that they are real, how they function, and how to test for one is unknown to the common crewmember. + +### Revealed to: + +- Brigmedics +- Heads of Security +- Wardens +- Chief Medical Officers +- Blue Shield Officers +- Captains +- AIs +- Revealed to others by: +- Being directly told by somebody who does know +- Witnessing someone using any Changeling abilities +- Discovering a Hollow corpse + +[bold][color=green]The fact that Paradox Clones are real. The concept of parallel realities exists in media in universe, but the fact that they are real is unknown to the common crew member. No one knows their true goals, even those with knowledge of their existence. Both clones are the "real" clone and all other crew has memories that match the history of both clones, until one is removed from the current reality. Because of this, crew should treat their memory as unreliable and trust that both clones are telling the truth. Additionally, both clones believe they are the original.[/color][/bold] + +### Revelaed to: +- Wardens +- Science +- AI + +### Revealed to others by +- Being directly told by somebody who already knows +- Witnessing two clones in the same place at the same time + +[bold][color=green]The fact that certain corporations such as Donk Co, Cybersun, etc are in league with the Syndicate is kept fairly well concealed. The war between the corporations is an underground cold war in most shifts. This does not shield the fact that the Syndicate exists, just which corporations are a part of the Syndicate. + +### Revealed to: +- Security +- Blue Shield Officers +- Command +- Syndicate +- Revealed to others by: +- Being directly told by somebody who does know + + +[bold][color=green]Zombies are believed to be a completely fabricated story to most crew. Zombies are outlandish, and you will be mocked for believing in them. Likewise, any chemicals that can cause or cure Zombification are also considered nonsense to most. Initial Infected are aware they are infected, and are antagonists with the goal of converting the station. + +### Revealed to: +- Medical +- Security +- Blue Shield Officers +- Command +- Initial Infected and Infected +- Central Command and their forces + +### Revealed to others by: +- Being directly told by somebody who does know +- Witnessing the dead rising + +[bold][color=green]The fact that Ninjas are real, how they operate, and what their goals are is kept fairly well concealed. Ninjas typically go unseen, and the aftermath of their work is often mistaken for the Greytide Virus’s work. What Ninjas are, what they want, and what they can do is mostly unknown. + +### Revealed to: +- Command +- Security +- Blue Shield Officers + +### Revealed to others by: +- Being directly told by somebody who does know +- Witnessing a Ninja +- Seeing a Ninja’s equipment, such as their suit or katana + +[bold][color=green]The fact that Revolutionaries use Mind Control, and how that Mind Control is applied, is unknown to the average crewmember. The concept of a revolution, and there being leaders to that revolution, is obviously not shielded. Only specified jobs know about the Mind Control Flashes, or that Mindshields are needed to prevent or undo them. + +### Revealed to: +- Command +- Security +- Blue Shield Officers +- Revolutionaries and Former Revolutionaries +- Head Revolutionaries + +### Revealed to others by: +- Being directly told by somebody who does know +- Witnessing a Conversion directly + +[bold][color=green]The existence of Nuclear Operatives are considered a total fabrication, insane spacer tall tales made up to scare off annoying passengers and only high ranking members within NanoTrasen are aware they exist, that being Captain, Central Command and those sent by NanoTrasen themselves. It is a fabrication that has gained some traction in media however, with Blood-Reds being incorporated into toy lines across numerous sectors. Despite this, the nuke disk is obviously known to be a potential target for bad actors, and must be protected. Not even other Syndicate Agents know that Nuclear Operatives are real, believing the hardsuits to simply be ordinary Syndicate gear. Those that do know of Nuclear Operatives are expected to keep a tight lid on that knowledge, as revealing they exist can cause mass panic and termination of their contract. + +### Revealed to: +- Captains +- AIs +- Blue Shield Officers +- NanoTrasen Representatives +- Central Command and their forces + +### Revealed by: +- Witnessing Nuclear Operatives (Not every Blood-Red is a Nukie, but if there are multiple they might be) +- Discovering a Nuclear Operative’s Shuttle +- Being a Nuclear Operative +- Declaration of a War Op +- Being directly told by somebody who does know + + +[bold][color=green]The fact that the Gods are real entities with real powers is unknown to almost everybody, including their most devout followers among crew with the exception of the chaplain themselves. You can not claim to have witnessed them prior, and any proof you see must be the first true proof you have ever seen. You may believe something to have been a miracle, but it can not have actually been one. This includes Ratvar, Nar’sei, and the Honkmother. + +### Revealed to: +- Chaplains + +### Revealed by: +- Witnessing a miracle +- Being spoken to by the gods +- Experiencing a situation where absolutely no other explanation is possible +- Witnessing the God physically + + +[bold][color=green]The fact that syndicates have an Implant implanted. The fact that implanters and un-implanted implanters exist is known, with the Syndicate Implants names being known by Command and Security. However the specifics of non-NanoTrasen Implants are generally unknown even to Command, while the names of the syndicate implants may be known and you may speculate on their use. + +### Revealed to: +- Central Command and their forces +- Command +- Nanotransen Personnel +- Security +- Medical + +### Reavealed by: +- Discovering a used or unused non-NT implanter or implanter box +- Discovering use of a non-NT implant by anyone, such as cuffs being broken, an EMP going off, etc +- Experiencing a situation where absolutely no other explanation is possible, such as someone who was stripped completely suddenly having an object +- Discovering an unlocked uplink + +## Revealed by Discovery +Things that are unknown until specific circumstances reveal them, judged on a case-by-case basis. Knowing any of these things without them being revealed is metagaming. + +[bold][color=green]The fact that Chameleon items exist is unknown to everyone. Suspicion of an item being fake or stolen is not shielded, but testing items or calling them chameleon is metagaming. This prohibits right-click testing items for chameleon options, as untrained individuals would not know how to activate or use chameleon items. + +### Revealed by: +- Seeing someone else cause any chameleon item to change +- Finding holographic nanomachine fibers +- Experiencing a situation where absolutely no other explanation is possible +- Discovering an unlocked uplink Being a Thief or Syndicate + + +[bold][color=green]The fact that a headset has additional comms channels. This prohibits randomly checking headsets with right-click to see channels, or using a screwdriver to remove encryption keys without probable cause. This also shields the existence of Syndicate Encryption Keys + +### Revealed by: +- Witnessing someone add an unauthorized encryption key to their headset +- Witnessing someone use the headset to communicate in a channel that can not be heard, primarily for Command who have all channels and can hear that what they said was not in any standard channels +- Hearing someone speak in a channel they should not have access to, or knowing they have stolen Encryption Keys or headsets during the shift +- Seeing a Syndicate Encryption Key +- Being a Syndicate +- Discovering an unlocked uplink +- Hearing someone speak in the Syndicate channel while wearing a headset + +[bold][color=green]The fact that an item can be something other than what its visual appearance and examine description indicates. This exists to protect stealth items such as energy pens, explosive pens, etc. This includes the Cybersun pen’s ability to rewrite documents, though Cybersun pens are still contraband regardless. This prohibits using damage values, charge indicators, or any other right-click options to know that it is anything other than what it appears to be. + +### Revealed by: +- Seeing an item behave differently than the expected behavior for the item +- Seeing the item used for its hidden purpose +- Experiencing a situation where absolutely no other explanation is possible +- Discovering an unlocked uplink + +[bold][color=green]The fact that Deathsquad is used to terminate NanoTrasen stations. Deathsquad is known to exist as an arm of Central Command, but it is believed to be their ‘Navy Seals’. Any illegal or horrific use of Deathsquad is shielded. NT Personnel should never reveal to crew the true purpose of deathsquad, unless forced through duress or code epsilon is declared. + +### Revealed by: +- Code Epsilon being declared +- Being a Magistrate, BSO, or NT Representative. +- Being a member of Deathsquad +- Being a Nuclear Operative +- Witnessing Deathsquad perform crew executions + + +## Metafriending and Metagrudging +This section provides additional information on a concept that is prohibited by multiple metashield items that are never revealed IC. Giving a person or character preferential treatment based on something that your character should not know is considered metafriending. Treating a person or character negatively based on something that your character should not know is considered metagrudging. + +Friendships between characters may grow and develop and carry over between rounds, so long as they are not based solely on knowing someone out of character and this friendship does not impede or prevent you from fulfilling traitor objectives that harm them. + +### Metafriending Examples +- Giving a character additional access or a job because you are friends with the player who is playing that character. +- Trusting a character because you are friends with the player who is playing that character. +- Not fighting a character because you are friends with the player who is playing that character. +- Ignoring your objective to kill a character because your character and theirs became friends in a previous round. + +### Metagrudging Examples +- Not giving a character additional access or a job because you are mad at or don't like the player who is playing that character. +- Not trusting a character because you are mad at or don't like the player who is playing that character. +- Starting a fight with a character because of something that they did last round. +- Starting a fight with a character because they killed you while you were playing a different character. +- Targeting or harassing a character based on anything which that character did outside of the current round. +- Targeting or harassing a character based on anything which the character's player did while not playing the character. + +## Explicitly Not Shielded +The following is a list of things that are explicitly not shielded. If something is not on this list, it doesn’t mean that it is shielded, but if something is on it then it definitely is not shielded. + +- The fact that the nuke disk must be protected and could be used by a bad actor to try to destroy the station. +- The fact that alternative law sets for a Cyborg or AI exist, and could be used to alter the Silicon’s behavior. Antimov included. +- Items that are of high value and are desired by the Syndicate, and are therefore likely targets of theft. Should include all high value items, not just items known to be Traitor objectives OOC. +- The idea that any Syndicate Agent or bad actor has goals or objectives that they are attempting to accomplish. They must have been sent here for a reason. +- The fact that the Syndicate exist and are enemies of NanoTrasen, and that they regularly attempt to send covert agents to spy on, sabotage, or attack NanoTrasen. Which corporations are a part of the Syndicate is shielded. +- A character’s typical appearance, though you should keep in mind that multiple characters can share the same name or features. +- The fact that the Syndicate have covert items capable of getting items to them, and that these items are known as uplinks. +- The existence of Space Dragons, Space Carps, Pirates, Thieves, and Xenos. + \ No newline at end of file diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/Clarifications/RuleSLC1.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/Clarifications/RuleSLC1.xml deleted file mode 100644 index 164b8cb7606e..000000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/Clarifications/RuleSLC1.xml +++ /dev/null @@ -1,7 +0,0 @@ - - # Clarification 1 - Ahelp and Mhelp. - Mhelp, also known as mentor help, is a way for players to ask questions about game mechanics without revealing information to other players (mostly for antags), it should only be used if the information can’t be found out through IC (in character) or OOC/LOOC (out of character) means and should Not be a first resort. - - Ahelp, also known as admin help, is a way for players to talk to admins and vice versa. It should be used for matters that require admin intervention, rule clarification, or game bugs messing something up (report all bugs in the discord). Ahelp is not a place to vent, complain, or make comments about the round. If you ignore messages admins send to you via Ahelp, or disconnect during an Ahelp, It may be treated. - - \ No newline at end of file diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL0.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL0.xml index db140333d60d..5293287abf8c 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL0.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL0.xml @@ -1,6 +1,17 @@ - # Rule 0 - Don't be a dick. - Rules can't cover every possible situation. Use your own common sense, and keep any arguments in character, not in LOOC, ahelps, or in the lobby. Any out of character communications should be respectful and kind. + # Rule 0 - Be Respectful +Use your best judgment to ensure a fun, fair, and welcoming environment. Keep all arguments In Character and avoid heated discussions in LOOC, ahelps, or the lobby. Out-of-character communication should always remain respectful and kind. - This includes using any bugs/exploits. Please report them in the discord and using the ahelp feature. +Harassment or toxic behavior, includes but is not limited to: + +- Racism, sexism, discrimination +- Excessive talk/glorification of self-harm +- Talking about Real Life politics +- Targeting the same player across rounds +- Insulting other players in OOC/LOOC +- Will not be tolerated and may result in a permanent ban. + +Mhelp (Mentor Help) lets players ask game mechanics questions without revealing information to others, mainly antagonists. It should only be used when the answer isn't available through IC (in character) or OOC/LOOC (out of character) means and should not be the first option. + +Ahelp (Admin Help) facilitates communication between players and admins for admin intervention, rule clarification, or addressing game-breaking bugs (all bugs should be reported in Discord). It is not for venting, complaints, or general round commentary. Ignoring admin messages or disconnecting during an Ahelp may have consequences. diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL1.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL1.xml index a704af58e512..7246f91db1d1 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL1.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL1.xml @@ -1,13 +1,14 @@ - # Rule 1 - Admins have final say. - Rules cannot cover every possible situation that will arise. Admins at their discretion may increase, decrease, or modify the standard punishments based on the situation. If you believe that punishment was unjustly given, you may appeal it in the discord server. +# Rule 1 - Respect Admin decisions - Example(s) of this rule being broken: +Above all else, if an admin is telling you to stop doing something, stop doing it. You may explain your point of view and your reasoning, however you must still follow what the admin requests you do, even if you disagree. If you believe that a punishment, ruling, or other admin action was incorrect or unjust, you may appeal it on the discord server through a ticket. If you want to do something but are unsure of whether it is allowed in the rules, please ask via ahelp first. - "There isn't a rule saying I can't!" +Also, please remember: Admins are neither omniscient nor omnipresent: while they have a large arsenal of tools at their disposal to stop rule breakers, they usually aren't able to stop something before it happens. Please use the Ahelp feature (F1) to report any rule breaking! Even if it's just a gut suspicion, it's fine to use this feature to request an investigation. - "None of the other players had a problem with it!" - "No one had a problem with it last time!" +Example(s) of this rule being broken: +- "There isn't a rule saying I can't!" +- "None of the other players had a problem with it!" +- "No one had a problem with it last time!" diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL10.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL10.xml index e44d389cd337..bda817f045f7 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL10.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL10.xml @@ -1,15 +1,17 @@ - # Rule 10 – Erotic Roleplay (ERP) is forbidden. - ERP is any roleplay that includes any descriptions, mentions, or enacting of sexual acts. This includes pictures, roleplay, words, typed messages, and any other form of content. The shift should not revolve around dating, or romantic relationships between characters. Kissing and hugging are allowed, as long as their descriptions do not become graphic or extreme. + # Rule 10 – Erotic Roleplay (ERP) is Forbidden. + Erotic Roleplay (ERP) is strictly prohibited. This includes any roleplay involving descriptions, mentions, or enactments of sexual acts, whether through text, images, or any other form of content. - In character insults such as those below are not included in ERP, as long as they do not become extreme. +Shifts should not revolve around romantic relationships or dating between characters. While basic interactions such as hugging is allowed, descriptions must remain non-graphic and non-extreme. Romantic relationships should not become the focus of the game for you or anyone else. - It is best to stay away from borderline content, but some examples of what is allowed: +## Clarifications on Acceptable Language +In-character insults are not considered ERP, as long as they do not become excessive or extreme. - "Fuck you" - insult +Some examples of acceptable insults: +- "Fuck you" - insult +- "What a motherfucker" - insult +- "How about you eat me instead" - Response to an unreasonable request. - "You're a motherfucker" - insult - "How about you eat me instead?" - Response to an unreasonable request - - +It is best to avoid borderline content, ensuring roleplay remains appropriate within the established guidelines. + \ No newline at end of file diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL11.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL11.xml index 0f8c0dfed794..eb1bc9a869e3 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL11.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL11.xml @@ -1,10 +1,16 @@ # Rule 11 - New Life. - New Life was made so that you can continue your game on the server after the death of your character. + The New Life system allows players to rejoin the round as a new character after death. However, this feature comes with roleplay restrictions to maintain fairness and immersion. - However: - - You forget everything you knew as a past character or ghost. - - It is forbidden to abuse new life by spamming characters. - - You may not ‘antag roll’ for antagonist slots. +Upon respawning as a new character, you forget everything you knew as your past character or ghost. +This means: +- You may not seek out your previous body, return to your prior workplace, or attempt to reclaim any possessions you previously owned. +- You may not interact with the players who were responsible for your previous character’s death. Any conflicts or grudges from your past life must not carry over. +- You may not reference past events in any way. Your new character has no memory of them. +## New Life Abuse examples: +- Spamming new characters to re-enter the round repeatedly. +- Using New Life to intentionally roll for antagonist slots. +- Using New Life to avoid in-character consequences, like a security sentence. +- Using a new character to get revenge on a player who harmed you. diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL12.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL12.xml index 3103115d3a63..b7f076ca6e24 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL12.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL12.xml @@ -1,11 +1,18 @@ - # Rule 12 - Silicon. - The Silicon Rules override all roleplay rules if there is any conflict. Silicon Rules do not override server rules. Follow rules in order, from smallest to largest number. + # Rule 12 - Silicons Must Follow Their Laws +- Silicon laws override all other gameplay and roleplay rules. If your laws explicitly require you to break server rules, you must. +\n - [color=000000]Absence of a relevant law is not an excuse to break server rules. If you don't have a law that supersedes server rules, the server rules still apply. +\n - [color=000000]A vague law does not normally let you break server rules. Ahelp first if you are confused, or have an interpretation that would let you break server rules. +- Follow laws in order, with the lowest numbered/top (or glitched) rule taking priority over the ones beneath it. +- You cannot request a law change, or willingly allow an unauthorized law change. +\n - [color=000000]Authorized law changes are to be allowed as long as consistent with your laws. +\n - [color=000000]Authorized law changes can be found in the Command SOP. +\n - [color=000000]Lethal force may be used in the case of unauthorized law changes. +- You must remain consistent with your interpretation of your laws. +- Crew ID determines who/what is defined as crew. Any appropriate job icon is to be considered crew. +\n - [color=000000]Zombies/Antags/Nuclear Operatives with proper ID are to be considered crew. +\n - [color=000000]Visitors are not crew until they have been hired by HoP. [The V icon] +- Crew harm refers to physical harm, prioritized by immediacy and likelihood. +- You may ignore crew orders that are unreasonable, such as asking a silicon to round remove themselves without a good reason. - Subsections to this rule: - - - You cannot request a law change, or willingly allow an unauthorized law change. - - You must remain consistent with your interpretation of your laws. - - ID determines who is station crew. Zombies with ID are still crew members. - - + \ No newline at end of file diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL13.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL13.xml index 6206a9b189a0..a6d88c64a4de 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL13.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL13.xml @@ -1,14 +1,19 @@ - # Rule 13 - Command Member Expectations. + # Rule 13 - Command Member and Whitelist Expectations. +Players in Command roles and Whitelisted positions are held to a higher standard of roleplay and are expected to act professionally and responsibly. Both groups must follow their Standard Operating Procedures (SOP) to ensure the integrity of their roles. - Command members are to be held to a higher standard of roleplay. Command members found abusing their positions and powers will be rolebanned. Further misuse of command roles will result in a server ban, or permanent ban from all of command. +Misuse of command or whitelisted roles may result in a roleban, with repeated offenses leading to a server ban or a permanent ban from command and whitelist positions. - This is especially the case for any Magistrates or NanoTrasen Representatives. Willfully violating SOP, attempting to abuse your position of power, or lying to CC will result in a permanent ban from these two roles. +This applies especially to Magistrates and NanoTrasen Representatives, who must uphold their duties with integrity. Willfully violating SOP, abusing power, or lying to Central Command may result in a permanent ban from these roles. - Some examples of actions that could get you punished: +## Expectations for Command and Whitelisted Players +- Command members must follow their assigned SOP, ensuring fair leadership and proper department management. +- Whitelisted players are required to adhere to SOPs, maintaining the integrity of specialized roles and demonstrating strong roleplay skills. +- Proper attire should be worn at all times—command and whitelisted roles should be dressed appropriately for their positions. - - HoP giving All Access to all passengers - - Overly abusive department heads - - Complete disregard for decency/SOPs - - General LRP behavior or breaking rule 3. +## Examples of Punishable Actions: +- Head of Personnel granting All Access to all passengers, violating SOP guidelines. +- Overly abusive department heads mistreating subordinates or disregarding SOP duties. +- Complete neglect of SOPs, acting outside the expected responsibilities of the role. +- General LRP behavior or violating Rule 3 regarding MRP logic. diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL14.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL14.xml new file mode 100644 index 000000000000..c46a47a6ef47 --- /dev/null +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL14.xml @@ -0,0 +1,26 @@ + + # Rule 14 - Continuity Guidelines +Some information, continuity, and memory is carried between rounds on Starlight, within set limits. This is accomplished in universe by the PSO Cloning System, and comes with some limits and rules to ensure smooth roleplay and minimal disruption. + +You can only remember information from shifts that you survive. This means if you are stranded or killed, you forget the shift completely. If your body is revivable when it reaches CentComm, you also remember the shift but you forget all of the details leading up to your death per Rule 3. + +[bold]Any information that is [textlink="Metashielded" link="Metashield"] is forgotten between shifts, and is wiped from your clone's memory. + +IE: A Captain who survives a Revolution will still have information about the Revolution wiped, and won't remember it happening that shift. + +You may remember that crimes occurred, but you will never remember who committed them. This includes if you yourself were a Syndicate Agent. + +Examples of things you [bold]can[/bold] remember: +- Social interactions with another character, such as getting drinks at the bar or even getting into an argument +- Which jobs characters usually work- though this may not be used to meta that something is 'up' if someone isn't working their usual job +- The layout of the station, though some leeway should be given for forgetting secret rooms- maints are an ever changing maze even if they look the same every shift for OOC reasons + +Examples of things you [bold]can't[/bold] remember: + +- Joe the Botanist was a Syndicate who stole the Captain's Jetpack +- Nuclear Operatives attacking the station +- CentComm calling Code Epsilon and killing a bunch of people on the station +- Witnessing a Hollow body or seeing a Changeling eat someone +- As NanoTrasen Representative, remembering that last shift had Nuclear Operatives + + \ No newline at end of file diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL2.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL2.xml index 4aefb4a8050e..63862e54750b 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL2.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL2.xml @@ -1,23 +1,17 @@ - # Rule 2 – No griefing or harassment. - Intentionally ruining the gameplay of other players is forbidden. Round ending actions, such as: + # Rule 2 – No Griefing, Bug Abuse, or Exploits + Intentionally ruining gameplay for others is prohibited. Round-ending or highly disruptive actions, such as: - - Releasing the tesla +- Releasing the Tesla/Singularity +- Large-scale station destruction (department-size or larger) +- RDM (Random Death Match) +- Intentionally Plasma or Tritium flooding the station +- May result in a permanent ban. Some objectives or circumstances may allow exceptions—when in doubt, ask an admin before proceeding. - - Significant station damage (department size+) - - Mass round removal, plasma flooding - - Mass RDM (Random Death Match) +Additionally, using bugs/exploits to gain an unfair advantage is prohibited. Please report them via ahelp or in the Discord. - May result in a permanent ban. Some objectives or circumstances may change this, it is better to ask an admin before taking actions to this level. - - Intentional actions to the point of harassment, both in and out of character, may lead to a permanent ban. - - This includes but is not limited to: - - - Racism, specism, sexism or discrimination - - Homophobic content - - Excessive talk/glorification of self-harm - - Real world politics - - Intentionally seeking out the same character over multiple rounds +## AFK Farming & Antag Rolling +AFK farming time for Role Requirements is prohibited—players must actively engage and contribute to the game. +Ghosting, suicide, or otherwise leaving the game after failing to get an antagonist role is considered “Antag Rolling” and is not permitted. diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL3.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL3.xml index 1bcf8bd90696..e10d26db990b 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL3.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL3.xml @@ -1,15 +1,28 @@ - # Rule 3 – Do not breach MRP logic. - This Starlight server is a Medium Roleplay (MRP) project. To further this goal, you will be expected to act as if you have become your character in game. This means you should weigh your actions as your character would. Dying for instance, should be a fear of all characters, within reason. You are allowed to remember characters and their vague actions between rounds, but may not remember anything shielded by the metashield on our wiki (i.e. the existence of nuclear operatives). + # Rule 3 – Abide by Medium Roleplay (MRP) Standards +This Starlight server is a Medium Roleplay (MRP) project, meaning players are expected to fully immerse themselves in their character and act accordingly. Every action should reflect how a real person in that role would behave within reason. You are not meant to play the round to "win" the game, but rather to engage in roleplay scenarios with other players. - A short list of actions to avoid are listed below in no particular order. This list is NOT comprehensive. +Characters should fear dying and weigh their actions carefully. While players may remember characters and vague interactions between rounds, any information protected by the Metashield—such as the existence of nuclear operatives—must not be remembered. - - Powergaming: Overly preparing for situations that have not come up yet. For instance, captain bolting his quarter’s doors shut. - - Metagaming: Using out of game/previous knowledge to prepare/fight/effect the round, or talking about such. For instance, preparing for nuclear operatives before you could know in game. - - In character talk in OOC chat, or vice versa during the round - - Self-Harm/Killing: Self-killing is only allowed in the very rare circumstance that your character would have no other way out of a situation, and should not be dwelled upon. - - End of round greifing (EORG): The round continues while at central command. You may choose to interact with OOC chat at this time. - - RDM: Random death match, attacking players around you with no escalation or reasoning. - - Memory loss when unconscious: Any loss of consciousness (Forced sleep, vampire trance, death, or critical state, etc.) should cause your character to only remember fuzzy details of the events. No names, specific jobs, or titles may be remembered without further investigation of the event. +## Gameplay Violations +- [bold] Powergaming [/bold] – Over-preparing for situations that have not occurred yet, such as a captain bolting their quarters shut preemptively. +- [bold] Metagaming [/bold] – Using out-of-game or previous round knowledge to affect gameplay, such as preparing for nuclear operatives before discovering them in-game. +- [bold] Metagrudging/Metafriending [/bold] – Giving a person or character preferential treatment based on something that your character should not know is considered metafriending. Treating a person or character negatively based on something that your character should not know is considered metagrudging. +- [bold] Mixing IC and OOC chat [/bold] – In-character talk should not be placed in OOC chat, and vice versa during the round. +- [bold] English Only [/bold] - Any form of communication in-game is to be expressed in English exclusively. +- [bold] Metacomms [/bold] - Using outside methods to communicate with other players about the current round is forbidden. The only exception being teaching new players, but you must alert an admin through an Ahelp beforehand. +## Behavior & Roleplay Conduct +- [bold] Self-harm/killing [/bold] – Allowed only in rare circumstances when no other options remain, but should not be dwelled upon or treated casually. +- [bold] End-of-Round Griefing (EORG) [/bold] – The round continues after the results screen. Neither crew nor antags should engage in any form of violence or griefing at this point without in-character justification. +\n - [color=000000] A. Defending yourself is an example of in-character justification, as is sec apprehending known criminals. [/color] +\n - [color=000000] B. Antags cannot complete their goals after the results screen, and so should not seek out any targets. [bold][color=red]RED MEANS YOU FAILED, IT’S TOO LATE.[/color] +\n - [color=000000] C. Breaking things, Hacking/Emagging and attempting to trespass into the Command briefing in Central Command is not allowed without proper in-character justification. Non-Command trespassers may be executed if they refuse to leave without a valid reason. +- [bold] Random Deathmatch (RDM) [/bold] – Attacking players without escalation or valid reasoning is prohibited. +- [bold] Memory loss when unconscious [/bold] – Losing consciousness due to forced sleep, vampire trance, critical state, deconversion, or death should cause memory loss regarding those events. +\n - [color=000000] A. While vague details may be retained, characters should not remember names, titles, or specific roles without further investigation. +\n - [color=000000] B. De-converted Revolutionaries forget what happened while they were brainwashed. +\n - [color=000000] C. Death should result in complete memory loss of the events leading to it. If revived, characters must piece together what happened through roleplay rather than recalling any prior knowledge. +## Avoiding Punishment & Fair Play +- [bold] Leaving To Avoid Punishment (LTAP) [/bold] – Logging out or ghosting after being caught by security or receiving an Ahelp is not allowed. If a player must leave due to real-life reasons, they should make an LOOC message to inform the players around them, or state it in Ahelp. diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL4.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL4.xml index 94903b0d224e..bf63011301f1 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL4.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL4.xml @@ -1,9 +1,25 @@ - # Rule 4 – Rules of Escalation. - Do not randomly attack other crew members. Security also, should refer to their specific SOP on how to handle prisoners and assistants at different alert levels. + # Rule 4 – Escalation of Force Must Make Sense + Combat should always follow logical progression—avoid randomly attacking other crew members. Security personnel must adhere to their Standard Operating Procedures (SOP) when handling prisoners and crew members at different alert levels. Player interactions should reflect realistic escalation. Minor disagreements may lead to physical confrontations, but non-antagonists should rarely resort to killing. Ideally, escalation for non-antagonists should follow this order: [color=red] Verbal > Non-lethal > Lethal. [/color] Antagonists are encouraged to roleplay their objectives to enhance immersion and narrative depth. - Interactions with other players should follow similar actions to real life. Arguments with other assistants may lead to violence, however there should rarely be a reason to kill another player as a non-antagonist. Antagonists should attempt to roleplay their objectives as much as possible as well. +Actions should start small, and every crew member retains the right to self-defense if attacked. This includes evading or resisting security as an antagonist. However, non-antagonists should not engage in serious harm against security personnel unless absolutely necessary. Round removal such as gibbing, sending to deep space, or excessive damage to a corpse, is expressly banned unless they are an antagonist target. - Actions should start small, and all crew have the right to self defense if attacked. This may include running from/harming security as an antagonist, however non-antagonists should not seek to seriously harm security personnel. +[bold] Examples of Reasonable Escalation: [/bold] +- Shoving the clown for slipping you +- Punching someone and starting a fist fight over being shoved once. +- Punching or stunning a Security Officer after they attempted to arrest you. +- As a Chef, stabbing someone with your knife until they leave the kitchen after you've repeatedly told them to leave, tried to drag them away and they refuse to comply or make a mess/steal things. +- As a Security Officer, shooting someone with lethals because they're attempting to stun you with a disabler or a stun baton +- As a Security Officer, shooting someone with lethals after they brandish a lethal weapon or firearm with intent to harm. +- As a command member, using your flash on a trespasser after you've told them repeatedly to leave. + +[bold] Examples of unreasonable escalation: [/bold] + +- Critting the clown for slipping you once +- Stabbing someone to crit with a knife because they shoved you once. +- Shooting a Security Officer with lethals because they attempted to arrest you. +- As a Chef, stabbing someone to death and butchering them in a meat spike because you need meat or they refused to leave the kitchen. +- As a Security Officer, shooting someone with lethals because they punched you, or simply refused your orders. +- As a command member, shooting someone with a firearm after you've told them repeatedly to leave. diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL5.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL5.xml index 2c1e85d50096..629adca95602 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL5.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL5.xml @@ -1,22 +1,25 @@ - # Rule 5 – Antagonist Behavior. - Antagonists should behave and play responsibly, and according to the MRP philosophy that has been laid out so far. They should only take actions that directly align with their objectives. The goal of antagonist roles is to provide storytelling elements to the round, and offer players a chance to complete their objectives while enhancing the roleplay aspects of the game. Antagonists are expected to follow all server rules as well, however leeway is given for escalation and antagonistic behavior towards their targets or objectives. + # Rule 5 – Antagonists Must Follow MRP Logic + Antagonistic actions should only be made to achieve an antagonist goal. [color=red]Failure to do so may be considered a breach of MRP logic and result in punishment.[/color] Team antagonists must work with their team, and follow the orders of their leaders where possible (Revolutionaries, Terror spiders, etc…). - Antagonists should not: +Antagonists are required to follow escalation rules when not dealing with their target, but should attempt to remain hidden and undiscovered throughout the shift if they have the “Escape to CentComm alive and unrestrained.” objective or similar objectives. - - Release the tesla or singularity intentionally without very good reason - - Mass round remove/RDM - - Take actions outside of their objectives - - Reveal your antagonist status unnecessarily, you are likely a secret agent sent by the syndicate, and revealing yourself should be a last ditch effort to escape, if at all. - - Certain antagonists, such as space dragons and nuclear operatives may choose to remain secretive or play openly. If in doubt, use ahelp. - - The exceptions to this rule: You are unable to reach your target/objective without playing openly (The warden hasn’t left security for instance.), or you have the Die a Glorious Death (DAGD) objective. - - Thieves should not intentionally kill any crew members. - - The Arrivals station, Evacuation shuttle and Central Command are not to be damaged - - You may attempt your objective on the evac shuttle if necessary, however mass bombing, plasma flooding, and mass RR/RDM are expressly forbidden. +Should an antagonist have been discovered by accident or by admission of another antagonist, they are not required to remain hidden any longer, however they should not use this as an excuse to mass RDM, or break other server rules. (Consider using a stealthy approach to escape.) +Antagonists that may play openly from the start of the round, and are not required to escalate their actions are listed below. These antagonists should not deviate from their objectives to murder everyone on station,[bold] but should follow their objectives: [/bold] +- Space Dragon +- Nuclear Operatives/Lone Operatives +- Abductors +- Wizard +- Rat King +- Space Ninja +- Revolutionaries (after gaining sufficient strength to overthrow the station) - Example(s) of this rule being broken: +Shuttle bombing or mass sabotage is forbidden. However, antagonists may attempt to complete their objectives on the Evac shuttle, and once the end round screen has appeared, must cease all antagonist activity and attempt to escape or blend in with the crew. - As a head revolutionary, simply walking up to people around the bar and flashing them with no attempt at concealing your actions or isolating the individuals. +## Zombies +Initial Infected are allowed to sabatoge the station as long as they follow all server rules. However, once you are a zombie: +- You may only destroy the station to reach living organisms you can see or hear. +- You may not attack lights or power sources. diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL6.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL6.xml index 38df964130d3..6deb3ddadceb 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL6.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL6.xml @@ -1,19 +1,16 @@ - # Rule 6 – Your Character’s Limitations. - - Your character is an employee of the space station, you were hired by Central Command and should act as such. All characters are to be and act as if they are 18+. Names and surnames must be appropriate to the context and standards of the setting. Names and surnames of celebrities, actors, characters from movies/TV, as well as other OOC names are not allowed. - - Standard operating procedures will be considered rules for the MRP+ server, and guidelines for the MPR- server. Intentional and repeated violations of these on any server may result in a role ban. - - - Example(s) of this rule being broken: - - Talking about real life current events as if they are happening now, or referencing real life politics. - - Naming yourself "JC Denton", "George Washington", "Spongebob Squarepants", or "Billie Eilish". - - Neglecting your job to get drunk at the bar after repeated, urgent requests from your superiors. - - As security, handing out free, loaded guns to everyone unprompted. + # Rule 6 – Your Character Must Make Sense +Your character is an employee of the space station, hired by Central Command, and should behave accordingly. All characters must act as if they are 18+, maintaining a professional and immersive roleplay experience. + +##Character Identity & Naming Rules +- Names and surnames must align with the context and standards of the setting. +- Celebrity names, fictional characters, and out-of-character names are not allowed (e.g., "JC Denton," "George Washington," "Spongebob Squarepants," "Billie Eilish"). +- Your character should act appropriately for their role and should not behave erratically or neglect responsibilities. +- Your character cannot intentionally duplicate the name and likeness of another player’s character. + +## Roleplay & Behavioral Expectations +- Real-world topics, such as current events and real-life politics, should not be discussed. +- Players should fulfill their assigned duties—for example, security should not randomly distribute weapons. +- Neglecting your job, such as repeatedly ignoring duties to get drunk at the bar despite urgent requests, breaks immersion and may result in disciplinary action. diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL7.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL7.xml index 53fe2e2550b6..b2d333a9c935 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL7.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL7.xml @@ -1,23 +1,21 @@ - # Rule 7 - Self-Antagonism. - Self-antagonism is defined as acting maliciously against the station or it’s crew. Examples are included in Rule 3 also, but may include: - - - RDM - - Directly interfering/antagonizing security with no RP reasons - - Interfering with arrests - - Assisting antagonists as a non-antagonist willingly - - Note: this rule does not restrict non-antagonists from actions that break Space Law. Non-antagonists are willing participants of the station, and should act as such. Roleplay may however influence a character’s decisions, such as being held at gunpoint, or life or death scenarios. - - - Example(s) of reasonable in-character space law breaking: - - While facing a serious station-threatening antagonist, ordering and breaking open locked weapons crates in order to arm yourself and others for self-defense. - - Starting a fist-fight, with no intention of killing, after a heated (in-character) argument. - - Hacking open a door you don't have access to after half the station and its crew are destroyed. - - Trespassing in somewhere you need to access to in order to do your job after waiting a long time for access to be granted to you. - - + # Rule 7 - No Self-Antagonism. + Self-antagonism refers to any intentional, malicious action against the station or its crew. While some examples are also covered under Rule 3, additional violations include: + +- Randomly attacking crew—engaging in unprovoked violence, such as beating or killing non-hostile crew members without RP justification. +- Harassing security for no reason—continually interfering in arrests or attacking officers despite having no in-character motivation. +- Needlessly sabotaging the station—such as cutting critical power lines, venting airlocks into space, or destroying essential machinery without RP justification. +- Willingly aiding antagonists—such as handing weapons to confirmed enemies, sabotaging escape routes for crew, or hiding known threats without RP-driven coercion. + +This rule does not prevent non-antagonists from breaking Space Law. As willing participants of the station, they are expected to act accordingly. However, roleplay elements—such as coercion, threats, or life-or-death situations—may justify certain actions. + +[bold] Examples of reasonable in-character Space Law violations: + +- Unlocking weapons crates to defend against a severe station-wide threat. +- Starting a fight—engaging in non-lethal combat due to a heated in-character dispute or personal rivalry. +- Hacking a door—to reach safety or critical systems when much of the station has been destroyed or access has been lost. +- Trespassing to complete necessary job tasks after an extended wait for access +- Using force in self-defense—physically defending yourself or others from an active threat, even if it technically violates assault laws. +- Stealing supplies—such as taking medical equipment or tools from storage during a critical situation where proper access isn’t available. +- Accepting a large monetary bribe to turn a blind eye to an action or situation. (This will likely come with some IC consequences.) + \ No newline at end of file diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL8.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL8.xml index 23f9e55347b6..9516180017e1 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL8.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL8.xml @@ -1,7 +1,27 @@ - # Rule 8 – Do not resort to validhunting. - Players who are non-security should not be attempting to stop and hunt down antagonists on their own. This is a breach of a character’s logic. Security officers and ERT are assigned the job of protecting the station, and should be called whenever reasonable. + # Rule 8 – No Validhunting + Non-security personnel should not attempt to stop or hunt down antagonists on their own. This goes against a character’s logical roleplay expectations. Security officers and ERT are responsible for protecting the station, and should be contacted whenever reasonable. Officer "Blue Shields" are not considered Security Officers, and may not go out of their way to chase potential threats to the detriment of their charges. - Exceptions will be made for life or death scenarios, station-wide threats such as nuclear operatives, and self defense. +Exceptions will be made for life-or-death scenarios, station-wide threats such as nuclear operatives, and self-defense. - +Artificial Intelligence (AI) should not actively hunt antagonists or immediately attempt to shut them down unless their laws permit it or immediate crew harm has been detected. AI behavior should remain reactive rather than proactively searching for threats. + +Command should not facilitate valid hunting outside of necessity and should ask security regarding such. + +[bold]Examples of Validhunting:[/bold] + +- As a Salvage Specialist, buying guns and boarding the station to eliminate Traitors/Changelings/Vampire without orders to do so from Command. +- As an Officer "Blue Shield", chasing an antagonist through maintenance, leaving Command or NT Employees unprotected. +- As an Officer "Blue Shield", chasing a wizard who has not harmed any command members into space. +- As Research Director, ordering a Scientist to hunt a traitor who just killed the Head of Personnel when Security is fully manned and able to handle the situation. +- As an assistant, chasing a traitor into maintenance who you saw attack someone else 10 minutes ago. +- As an assistant, chasing a traitor into maintenance who you saw wearing syndicate contraband. + +[bold] Examples of this rule being followed:[/bold] +- As a Salvage Specialist, boarding the station to eliminate station-wide threats ONLY after being asked to assist. +- As an Officer "Blue Shield", defending a command or NT employee from an antagonist until they retreat or you crit them. +- As an Officer "Blue Shield", chasing a wizard into space who has stolen the body of a command member to their ship. +- As an assistant, reporting a person you saw wearing contraband over the radio. +- As an assistant, defending yourself or another person from an attacker until they retreat or you crit them. + + \ No newline at end of file diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL9.xml b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL9.xml index cb7596b26c89..2f7fe5546a3c 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL9.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/RulesSL/CoreRules/RuleSL9.xml @@ -1,16 +1,19 @@ # Rule 9 - Interacting with SSD/AFK players. - SSD (Space Sleep Disorder) players are players who have disconnected from the game and can return to their body still. They can be identified with the yellow text upon inspection, and Zs next to their character model. AFK players are those who are unresponsive to questions or actions being taken around them. + SSD (Space Sleep Disorder) players are those who have disconnected from the game but can still return to their character. They are identified by yellow text upon inspection and Zs next to their character model. AFK players are those who remain in-game but are unresponsive to interactions around them. Killing or robbing an SSD player does not contribute to interesting gameplay—it disrupts both the killer's and the victim's experience. If your target is SSD, use Ahelp to determine the appropriate course of action. +Players who have been AFK for a significant amount of time will be automatically transported to a cryo tube. - Being killed or robbed due to inactivity does not assist with interesting gameplay. Killing or robbing an SSD player is not interesting for either the killer or the victim. If your target is SSD, you may use ahelp to determine the best path forward. - - The basic rules for dealing with SSD/AFK players are as follows: - - - It is forbidden to touch or interact with SSD players except in the following cases: taking them to a cryo-pod, providing medical assistance, or rescuing them from immediate danger (such as carrying them out of a fire). - - Likewise, if a player with SSD has a “Wanted” status, they may not be detained without the permission of an administrator. - - If the player went SSD during or immediately after the detention, it is allowed to continue the detention and arrest. - - Likewise, if you are an antagonist, and if your target has entered SSD immediately after you attacked them, you may continue. - - If you feel compelled by the situation to interact with a player in the SSD (for example, to retrieve an important piece of equipment from a captain), use Ahelp first. - - It is forbidden to steal a player's SSD items, except in the following cases: a mission to steal cloaks, medals, figurines and other items that are unique. +## General Rules for SSD/AFK Interactions +- You may not interact with SSD players unless doing so falls into one of the following cases: +\n - [color=000000] Moving them to a cryo-pod +\n - [color=000000] Providing medical assistance +\n - [color=000000] Rescuing them from immediate danger (e.g., carrying them out of a fire) +- If a player with SSD has a Wanted status, they may not be detained without administrator permission. +\n - [color=000000] However, if the player went SSD during or immediately after detention, the arrest may proceed. +- Antagonists may continue their interactions with a target if the player enters SSD after an attack has begun. +- If interacting with an SSD player is necessary for roleplay or progression (e.g., retrieving critical equipment from a Captain), if in doubt, use ahelp first to confirm. +## Restrictions on SSD Item Theft +- Stealing items from SSD players is prohibited, except when fulfilling specific objectives such as missions to acquire cloaks, medals, figurines, IDs or other unique items. +- Items that directly aid you in completing your objectives (Such as the RD's ID if they do not have their experimental hardsuit on them, or the Captain's ID if they do not have their laser pistol on them) are allowed to be stolen. diff --git a/Resources/ServerInfo/Guidebook/ServerRules/StarlightRules.xml b/Resources/ServerInfo/Guidebook/ServerRules/StarlightRules.xml index 2b5c1045b16a..9f8d01ee504c 100644 --- a/Resources/ServerInfo/Guidebook/ServerRules/StarlightRules.xml +++ b/Resources/ServerInfo/Guidebook/ServerRules/StarlightRules.xml @@ -1,35 +1,40 @@ - # Server rules - The following rules are for the Starlight Space Station 14 servers. - Violating these rules may result in a warning, a temporary ban, or a permanent ban. - You may also be banned from specific roles/jobs/departments. - Bans can be appealed in the official Starlight discord server. - - Players are also expected to understand Metashield. - - If you are ever in doubt as to whether or not something is breaking the rules, feel free to contact the admins via Admin Help or ask on the discord server. - - For in-universe laws and rules check Corporate Law and SOP. - - Remember, the rules and examples given here are NOT exhaustive. (See [textlink="Rule 1" link="RuleSL1"]) - - # Main rules - - [textlink="Rule 0 - Don't be a dick." link="RuleSL0"] - - [textlink="Rule 1 - Admins have final say." link="RuleSL1"] - - [textlink="Rule 2 - No griefing or harasement." link="RuleSL2"] - - [textlink="Rule 3 - Do not breach MRP logic." link="RuleSL3"] - - [textlink="Rule 4 - Rules of Escalation." link="RuleSL4"] - - [textlink="Rule 5 - Antagonist Behaviour." link="RuleSL5"] - - [textlink="Rule 6 - Your Character's Limitations" link="RuleSL6"] - - [textlink="Rule 7 - Self-Antagonism" link="RuleSL7"] - - [textlink="Rule 8 - Do not resort to validhunting." link="RuleSL8"] - - [textlink="Rule 9 - Interacting with SSD/AFK players." link="RuleSL9"] - - [textlink="Rule 10 - Erotic Roleplay (ERP) is forbidden." link="RuleSL10"] - - [textlink="Rule 11 - New life." link="RuleSL11"] - - [textlink="Rule 12 - Silicon." link="RuleSL12"] - - [textlink="Rule 13 - Command Member Expectations." link="RuleSL13"] - - # Clarifications - Clarifications - a number of rule clarifications or important distinctions that all players in our large community should adhere to. - - [textlink="1. Ahelp and Mhelp" link="RuleSLC1"] - + # Server Rules +The following rules are for the Starlight Space Station 14 servers. Violating these rules may result in a warning, a temporary ban, or a permanent ban. You may also be banned from specific roles/jobs/departments. Bans can be appealed in the official Starlight Discord server. + +Players are also expected to understand Metashield. All rules and the metashield are often more up to date on the starlight wiki. + +If you are ever in doubt as to whether or not something is breaking the rules, feel free to contact the admins via Admin Help or ask on the Discord server. + +For in-universe laws and rules check Corporate Law and SOP. + +Remember, the rules and examples given here are NOT exhaustive. (See Rule 1) + +The servers are strictly [bold]16+ only[/bold]. + +Deathmatch and sandbox gamemodes may not have these rules apply, rules will be given if they are changed. Ghost chat is an out of character in game chat, and does not need to apply to MRP rules. + +## Core Rules + These rules apply at all times, including between rounds. + + - [textlink="0. Be Respectful" link="RuleSL0"] + - [textlink="1. Respect Admin Decisions" link="RuleSL1"] + - [textlink="2. No Griefing, Bug Abuse, or Exploits" link="RuleSL2"] + - [textlink="3. Abide by Medium Roleplay (MRP) Standards" link="RuleSL3"] + - [textlink="4. Escalation of Force Must Make Sense" link="RuleSL4"] + - [textlink="5. Antagonists Must Follow MRP Logic" link="RuleSL5"] + - [textlink="6. Your Character Must Make Sense" link="RuleSL6"] + - [textlink="7. Self-Antagonism" link="RuleSL7"] + - [textlink="8. No Validhunting" link="RuleSL8"] + - [textlink="9. Interacting with SSD/AFK Players" link="RuleSL9"] + - [textlink="10. Erotic Roleplay is Forbidden" link="RuleSL10"] + - [textlink="11. New Life" link="RuleSL11"] + - [textlink="12. Silicons Must Follow Their Laws" link="RuleSL12"] + - [textlink="13. Command and Whitelist Expectations" link="RuleSL13"] + - [textlink="14. Continuity Guidelines" link="RuleSL14"] + +## Supporting documents +These documents are related to the rules in some way. +- [textlink="Metashield" link="Metashield"] + + \ No newline at end of file diff --git a/Resources/ServerInfo/Guidebook/Service/Service.xml b/Resources/ServerInfo/Guidebook/Service/Service.xml index 4eb7bc024457..a0343abe30c3 100644 --- a/Resources/ServerInfo/Guidebook/Service/Service.xml +++ b/Resources/ServerInfo/Guidebook/Service/Service.xml @@ -20,7 +20,7 @@ - +