From 2d496b967ab9976975f2d041e957089d28d0bc27 Mon Sep 17 00:00:00 2001 From: VMSolidus Date: Fri, 6 Dec 2024 15:20:39 -0500 Subject: [PATCH] Fix Rules --- Resources/Prototypes/Guidebook/rules.yml | 332 +----------------- .../ServerRules/CoreRules/RuleC0.xml | 19 - .../ServerRules/CoreRules/RuleC10AHelp.xml | 29 -- .../CoreRules/RuleC11AhelpThreats.xml | 20 -- .../ServerRules/CoreRules/RuleC12MinAge.xml | 6 - .../CoreRules/RuleC13CharacterNames.xml | 66 ---- .../ServerRules/CoreRules/RuleC14ICinOOC.xml | 13 - .../ServerRules/CoreRules/RuleC1Admins.xml | 6 - .../ServerRules/CoreRules/RuleC2DBAD.xml | 7 - .../ServerRules/CoreRules/RuleC3NoHate.xml | 20 -- .../ServerRules/CoreRules/RuleC4NoERP.xml | 23 -- .../ServerRules/CoreRules/RuleC5Metacomms.xml | 18 - .../CoreRules/RuleC6BanEvasion.xml | 15 - .../CoreRules/RuleC7EnglishOnly.xml | 10 - .../ServerRules/CoreRules/RuleC8Exploits.xml | 12 - .../ServerRules/CoreRules/RuleC9Multikey.xml | 7 - .../Guidebook/ServerRules/DefaultRules.xml | 5 - .../Guidebook/ServerRules/DefaultRuleset.xml | 62 ++++ .../ServerRules/RoleplayRules/RuleR0.xml | 26 -- .../RoleplayRules/RuleR10Subordination.xml | 26 -- .../RuleR11-1AnimalEscalation.xml | 36 -- .../RoleplayRules/RuleR11-2ConflictTypes.xml | 30 -- .../RoleplayRules/RuleR11Escalation.xml | 67 ---- .../RoleplayRules/RuleR12RoleAbandonment.xml | 28 -- .../RoleplayRules/RuleR13PerformRole.xml | 26 -- .../RoleplayRules/RuleR14SecComStandard.xml | 37 -- .../RoleplayRules/RuleR15SpaceLaw.xml | 21 -- .../RoleplayRules/RuleR1Silicons.xml | 4 - .../RoleplayRules/RuleR2Familiars.xml | 6 - .../RoleplayRules/RuleR3NormalRP.xml | 20 -- .../RoleplayRules/RuleR4Metashield.xml | 103 ------ .../RoleplayRules/RuleR5Arrivals.xml | 22 -- .../RoleplayRules/RuleR6SelfAntag.xml | 22 -- .../RoleplayRules/RuleR7RoundStalling.xml | 16 - .../RoleplayRules/RuleR8NoFriendlyAntag.xml | 22 -- .../RoleplayRules/RuleR9MassSabotage.xml | 23 -- .../ServerRules/SiliconRules/RuleS0.xml | 15 - .../SiliconRules/RuleS10OrderConflicts.xml | 9 - .../ServerRules/SiliconRules/RuleS1Laws.xml | 6 - .../SiliconRules/RuleS2LawPriority.xml | 9 - .../SiliconRules/RuleS3LawRedefinition.xml | 8 - .../SiliconRules/RuleS4RequestChanges.xml | 6 - .../SiliconRules/RuleS5FreeSilicon.xml | 4 - .../SiliconRules/RuleS6UnreasonableOrders.xml | 22 -- .../SiliconRules/RuleS7Consistency.xml | 6 - .../RuleS8DefaultCrewDefinition.xml | 4 - .../RuleS9DefaultHarmDefinition.xml | 25 -- .../ServerRules/WizDenCoreOnlyRules.xml | 26 -- .../Guidebook/ServerRules/WizDenLRPRules.xml | 65 ---- .../Guidebook/ServerRules/WizDenMRPRules.xml | 65 ---- 50 files changed, 63 insertions(+), 1412 deletions(-) delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC11AhelpThreats.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12MinAge.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC13CharacterNames.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC14ICinOOC.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC1Admins.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC2DBAD.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC3NoHate.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC5Metacomms.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6BanEvasion.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC7EnglishOnly.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC8Exploits.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC9Multikey.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/DefaultRules.xml create mode 100644 Resources/ServerInfo/Guidebook/ServerRules/DefaultRuleset.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR0.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR10Subordination.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-1AnimalEscalation.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-2ConflictTypes.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11Escalation.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR12RoleAbandonment.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR13PerformRole.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR14SecComStandard.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR15SpaceLaw.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR1Silicons.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR2Familiars.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR3NormalRP.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR4Metashield.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR5Arrivals.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR7RoundStalling.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR8NoFriendlyAntag.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS0.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS10OrderConflicts.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS1Laws.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS2LawPriority.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS3LawRedefinition.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS4RequestChanges.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS5FreeSilicon.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS6UnreasonableOrders.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS7Consistency.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS8DefaultCrewDefinition.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS9DefaultHarmDefinition.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/WizDenCoreOnlyRules.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/WizDenLRPRules.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/WizDenMRPRules.xml diff --git a/Resources/Prototypes/Guidebook/rules.yml b/Resources/Prototypes/Guidebook/rules.yml index a59af2c5edc..162cdba7703 100644 --- a/Resources/Prototypes/Guidebook/rules.yml +++ b/Resources/Prototypes/Guidebook/rules.yml @@ -1,325 +1,7 @@ - type: guideEntry # Default for forks and stuff. Should not be listed anywhere if the server is using a custom ruleset. id: DefaultRuleset name: guide-entry-rules - text: "/ServerInfo/Guidebook/ServerRules/DefaultRules.xml" - -- type: guideEntry - id: CoreRuleset - name: guide-entry-rules-core-only - priority: 0 - text: "/ServerInfo/Guidebook/ServerRules/WizDenCoreOnlyRules.xml" - -- type: guideEntry - id: StandardRuleset - name: guide-entry-rules-lrp - priority: 5 - text: "/ServerInfo/Guidebook/ServerRules/WizDenLRPRules.xml" - -- type: guideEntry - id: MRPRuleset - name: guide-entry-rules-mrp - priority: 10 - text: "/ServerInfo/Guidebook/ServerRules/WizDenMRPRules.xml" - -- type: guideEntry - id: RoleTypes - name: guide-entry-rules-role-types - priority: 20 - text: "/ServerInfo/Guidebook/ServerRules/RoleTypes.xml" - -- type: guideEntry - id: CoreRules - name: guide-entry-rules-core - priority: 30 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml" - children: - - RuleC1 - - RuleC2 - - RuleC3 - - RuleC4 - - RuleC5 - - RuleC6 - - RuleC7 - - RuleC8 - - RuleC9 - - RuleC10 - - RuleC11 - - RuleC12 - - RuleC13 - - RuleC14 - -- type: guideEntry - id: RuleC1 - name: guide-entry-rules-c1 - priority: 1 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC1Admins.xml" - -- type: guideEntry - id: RuleC2 - name: guide-entry-rules-c2 - priority: 2 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC2DBAD.xml" - -- type: guideEntry - id: RuleC3 - name: guide-entry-rules-c3 - priority: 3 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC3NoHate.xml" - -- type: guideEntry - id: RuleC4 - name: guide-entry-rules-c4 - priority: 4 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml" - -- type: guideEntry - id: RuleC5 - name: guide-entry-rules-c5 - priority: 5 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC5Metacomms.xml" - -- type: guideEntry - id: RuleC6 - name: guide-entry-rules-c6 - priority: 6 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6BanEvasion.xml" - -- type: guideEntry - id: RuleC7 - name: guide-entry-rules-c7 - priority: 7 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC7EnglishOnly.xml" - -- type: guideEntry - id: RuleC8 - name: guide-entry-rules-c8 - priority: 8 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC8Exploits.xml" - -- type: guideEntry - id: RuleC9 - name: guide-entry-rules-c9 - priority: 9 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC9Multikey.xml" - -- type: guideEntry - id: RuleC10 - name: guide-entry-rules-c10 - priority: 10 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml" - -- type: guideEntry - id: RuleC11 - name: guide-entry-rules-c11 - priority: 11 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC11AhelpThreats.xml" - -- type: guideEntry - id: RuleC12 - name: guide-entry-rules-c12 - priority: 12 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12MinAge.xml" - -- type: guideEntry - id: RuleC13 - name: guide-entry-rules-c13 - priority: 13 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC13CharacterNames.xml" - -- type: guideEntry - id: RuleC14 - name: guide-entry-rules-c14 - priority: 14 - text: "/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC14ICinOOC.xml" - -- type: guideEntry - id: RoleplayRules - name: guide-entry-rules-roleplay - priority: 40 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR0.xml" - children: - - RuleR1 - - RuleR2 - - RuleR3 - - RuleR4 - - RuleR5 - - RuleR6 - - RuleR7 - - RuleR8 - - RuleR9 - - RuleR10 - - RuleR11 - - RuleR12 - - RuleR13 - - RuleR14 - - RuleR15 - -- type: guideEntry - id: RuleR1 - name: guide-entry-rules-r1 - priority: 1 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR1Silicons.xml" - -- type: guideEntry - id: RuleR2 - name: guide-entry-rules-r2 - priority: 2 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR2Familiars.xml" - -- type: guideEntry - id: RuleR3 - name: guide-entry-rules-r3 - priority: 3 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR3NormalRP.xml" - -- type: guideEntry - id: RuleR4 - name: guide-entry-rules-r4 - priority: 4 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR4Metashield.xml" - -- type: guideEntry - id: RuleR5 - name: guide-entry-rules-r5 - priority: 5 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR5Arrivals.xml" - -- type: guideEntry - id: RuleR6 - name: guide-entry-rules-r6 - priority: 6 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml" - -- type: guideEntry - id: RuleR7 - name: guide-entry-rules-r7 - priority: 7 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR7RoundStalling.xml" - -- type: guideEntry - id: RuleR8 - name: guide-entry-rules-r8 - priority: 8 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR8NoFriendlyAntag.xml" - -- type: guideEntry - id: RuleR9 - name: guide-entry-rules-r9 - priority: 9 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml" - -- type: guideEntry - id: RuleR10 - name: guide-entry-rules-r10 - priority: 10 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR10Subordination.xml" - -- type: guideEntry - id: RuleR11 - name: guide-entry-rules-r11 - priority: 11 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11Escalation.xml" - -- type: guideEntry - id: RuleR12 - name: guide-entry-rules-r12 - priority: 12 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR12RoleAbandonment.xml" - -- type: guideEntry - id: RuleR13 - name: guide-entry-rules-r13 - priority: 13 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR13PerformRole.xml" - -- type: guideEntry - id: RuleR14 - name: guide-entry-rules-r14 - priority: 14 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR14SecComStandard.xml" - -- type: guideEntry - id: RuleR15 - name: guide-entry-rules-r15 - priority: 15 - text: "/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR15SpaceLaw.xml" - -- type: guideEntry - id: SiliconRules - name: guide-entry-rules-silicon - priority: 50 - text: "/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS0.xml" - children: - - RuleS1 - - RuleS2 - - RuleS3 - - RuleS4 - - RuleS5 - - RuleS6 - - RuleS7 - - RuleS8 - - RuleS9 - - RuleS10 - -- type: guideEntry - id: RuleS1 - name: guide-entry-rules-s1 - priority: 1 - text: "/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS1Laws.xml" - -- type: guideEntry - id: RuleS2 - name: guide-entry-rules-s2 - priority: 2 - text: "/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS2LawPriority.xml" - -- type: guideEntry - id: RuleS3 - name: guide-entry-rules-s3 - priority: 3 - text: "/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS3LawRedefinition.xml" - -- type: guideEntry - id: RuleS4 - name: guide-entry-rules-s4 - priority: 4 - text: "/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS4RequestChanges.xml" - -- type: guideEntry - id: RuleS5 - name: guide-entry-rules-s5 - priority: 5 - text: "/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS5FreeSilicon.xml" - -- type: guideEntry - id: RuleS6 - name: guide-entry-rules-s6 - priority: 6 - text: "/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS6UnreasonableOrders.xml" - -- type: guideEntry - id: RuleS7 - name: guide-entry-rules-s7 - priority: 7 - text: "/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS7Consistency.xml" - -- type: guideEntry - id: RuleS8 - name: guide-entry-rules-s8 - priority: 8 - text: "/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS8DefaultCrewDefinition.xml" - -- type: guideEntry - id: RuleS9 - name: guide-entry-rules-s9 - priority: 9 - text: "/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS9DefaultHarmDefinition.xml" - -- type: guideEntry - id: RuleS10 - name: guide-entry-rules-s10 - priority: 10 - text: "/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS10OrderConflicts.xml" + text: "/ServerInfo/Guidebook/ServerRules/DefaultRuleset.xml" - type: guideEntry id: SpaceLaw @@ -348,15 +30,3 @@ name: guide-entry-rules-sl-restricted-weapons priority: 40 text: "/ServerInfo/Guidebook/ServerRules/SpaceLaw/SLRestrictedWeapons.xml" - -- type: guideEntry - id: BanTypes - name: guide-entry-rules-ban-types - priority: 90 - text: "/ServerInfo/Guidebook/ServerRules/BanTypes.xml" - -- type: guideEntry - id: BanDurations - name: guide-entry-rules-ban-durations - priority: 100 - text: "/ServerInfo/Guidebook/ServerRules/BanDurations.xml" diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml deleted file mode 100644 index 7b8cfbcf61e..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml +++ /dev/null @@ -1,19 +0,0 @@ - - # 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"] - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml deleted file mode 100644 index 2d639c5b84a..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml +++ /dev/null @@ -1,29 +0,0 @@ - - # Core Rule 10 - Do not abuse or ignore admin messages - Admin help, or "ahelp", is the system used by admins to communicate with specific players in the game. Only use admin help for things requiring admin attention. If you ignore messages admins send to you via ahelp, or disconnect during an ahelp, you may be banned. If you urgently need to leave during an ahelp, you may do so but will likely need to continue the ahelp on the forums. Do not admin check, be hostile/aggressive, request events, or spam. IC methods of contacting admins, like prayers, faxes, red phones, and banana phones, should be used when there is not an issue. - - Admins are not always online, but all ahelps are automatically relayed to discord. For various reasons, admins might not respond to an ahelp even if they've handled it. A lack of response does not necessarily mean that an ahelp was ignored. - - ## Should I ahelp X? - You can ahelp anytime you genuinely think a player is breaking a rule. Not all ahelps end up being for something that an admin needs to intervene in, but that's ok, admins would rather have people occasionally report things that turn out to not be an issue than miss reports for actual issues because someone was unsure, or get those reports late because someone waited until the end of the round to be more sure. - - The most common reason players give for not ahelping issues is that they don't want to waste admin time, but it only takes a few seconds for an admin to check if someone is an antagonist. If you are ahelping too many things, an admin will let you know. If you're not being told to stop reporting something or to report less things, then you can safely assume that you aren't causing any issues. - - # What should I include in an ahelp? - At a minimum, admins need to know what the issue is to be able to address an ahelp. Don't send ahelp messages with no information about what your question or the issue is. Messages like "hello" are often considered admin checking. - - If you can, an ideal ahelp message includes what the issue is along with who is causing it and their character's name if possible. - - # Examples - Appropriate uses of ahelp: - - reporting people who you think are violating rules, - - asking questions about rules, - - asking for a temporary exemption from a rule, and - - request a minor gimmick, like a TC trade or item spawn. - - Inappropriate uses of ahelp: - - checking if an admin is online, including sending messages without any information about the issue like "hello" or incomprehensible messages, - - being hostile or aggressive, - - requesting events, and - - spamming messages about the same issue. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC11AhelpThreats.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC11AhelpThreats.xml deleted file mode 100644 index 47420264946..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC11AhelpThreats.xml +++ /dev/null @@ -1,20 +0,0 @@ - - # Core Rule 11 - Do not threaten to ahelp other players or argue with them about rules - Don't threaten to ahelp a player, don't tell them you are ahelping them, and don't tell them you did ahelp them. You can argue in character about Space Law, but do not argue about whether something is or is not against the rules. If you think someone is breaking a rule, ahelp them. If you don't think someone is breaking a rule, don't ahelp them. Either way, the best thing that you can do once you after is to continue in-character. - - ## Example Scenario 1 - You are a security officer and think someone who is causing a ton of problems for security is not an antag and is breaking the rules by doing so. - - [color=#a4885c]Good:[/color] Since you think they are breaking a rule, you ahelp them when you're able to. You continue in-character by arresting them for the crimes that they committed. - - [color=#a4885c]Bad:[/color] You decide not to ahelp them. You kill them and tell them "you're lucky I didn't report you to the admins". - - [color=#a4885c]Bad:[/color] Since you think they are breaking a rule, you ahelp them when you're able to. You arrest them for the crimes that they committed and tell them "I ahelped you so enjoy your ban". - - ## Example Scenario 2 - A mouse is using emotes to bypass speech restrictions. - - [color=#a4885c]Good:[/color] You ahelp them then respond in-character by acting like you can't understand what the mouse is doing. - - [color=#a4885c]Bad:[/color] You use in character chat to tell the mouse that it is breaking a rule. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12MinAge.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12MinAge.xml deleted file mode 100644 index baa30a09faf..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12MinAge.xml +++ /dev/null @@ -1,6 +0,0 @@ - - # Core Rule 12 - Players must be and act at least 16 years old - All players must be at least 16 years old. Additionally, all players must act at least as mature as a 16 year old. Admins may ban someone who they believe is acting less mature than a 16 year old, even if the player is known to be significantly older than 16 years old. - - Anyone who connects to the servers is a player, even if they don't actually play in a round. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC13CharacterNames.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC13CharacterNames.xml deleted file mode 100644 index ec393ecdc17..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC13CharacterNames.xml +++ /dev/null @@ -1,66 +0,0 @@ - - # Core Rule 13 - Use realistic character names, and do not use names of famous people - - No names of people or characters from the real world - - No titles/honorifics - - Must follow all other rules (no slurs/sexual names/etc) - - Usernames, objects, random characters, very "low effort" names, "meta" names, or otherwise implausible names cannot be used as names. See examples below. - - Admin rulings on IC names are final and disputes should be done through the forums, not by refusing to comply with an admin - - ## Clarification on "Meta" Names - Meta names are ones which attempt to take advantage of some game mechanic or game design choice. "Urist McHands" is a meta name because it is the default name used for admin spawned humans. "Operator Whiskey" is a meta name because it follows the naming pattern of nuclear operatives. This rule is not intended to prevent things like nuclear operatives using a fake ID with names that appear to be nuclear operative names if they decide that they want to do that. - - ## Conventions and Examples - [color=#994444]Bad[/color] cannot be used by any species. [color=#449944]Acceptable[/color] names can be used by any species. - - Humans typically use the Firstname Lastname convention. - - [color=#449944]Acceptable:[/color] Tom Fisher - - [color=#449944]Acceptable:[/color] Spacey Chapman - - [color=#994444]Bad:[/color] Dr. Tom Fisher - - [color=#994444]Bad:[/color] Walter White - - [color=#994444]Bad:[/color] George Washington - - [color=#994444]Bad:[/color] Joe Biden - - [color=#994444]Bad:[/color] Ben Dover - - [color=#994444]Bad:[/color] Mike Hunt - - Dwarfs typically use the human convention in a viking theme. - - [color=#449944]Acceptable:[/color] Ingrid Firebreath - - [color=#449944]Acceptable:[/color] Erik Lightningclaw - - Lizards typically use the Verb-article-Noun convention. - - [color=#449944]Acceptable:[/color] Cleans-the-Airlocks - - [color=#994444]Bad:[/color] Bans-the-Admins - - Slimes typically have names that are onomonopia. A last name is optional. - - [color=#449944]Acceptable:[/color] Foolp Suub - - [color=#449944]Acceptable:[/color] Foolp - - [color=#994444]Bad:[/color] Slime - - Diona typically have calm, nature themed, Noun of Noun style names. - - [color=#449944]Acceptable:[/color] Petal of Tranquility - - [color=#449944]Acceptable:[/color] Garden of Relaxation - - [color=#994444]Bad:[/color] Tree but Alive - - Mothmen typically use latin sounding names, or light themed names. - - [color=#449944]Acceptable:[/color] Socrates Temnora - - [color=#449944]Acceptable:[/color] Sierra Lightseeker - - [color=#449944]Acceptable:[/color] James Nightflitter - - Arachnids typically use latin sounding names. - - [color=#449944]Acceptable:[/color] Argyroneta Reticulatus - - [color=#449944]Acceptable:[/color] Loxosceles Domesticus - - [color=#994444]Bad:[/color] Spider-Man - - Usernames, objects, random characters, very "low effort" names, "meta" names, or otherwise implausible names are not permitted. - - [color=#994444]Bad:[/color] XxRobustxX - - [color=#994444]Bad:[/color] SDpksSodjdfk - - [color=#994444]Bad:[/color] Lkdsoisgoieun - - [color=#994444]Bad:[/color] F4ith H3arth - - [color=#994444]Bad:[/color] Greytide - - [color=#994444]Bad:[/color] Passenger - - [color=#994444]Bad:[/color] Urist McHands - - [color=#994444]Bad:[/color] Admin - - [color=#994444]Bad:[/color] Game-Master - - [color=#994444]Bad:[/color] Joe Mamma - - [color=#994444]Bad:[/color] Middle-Aged Man - - [color=#994444]Bad:[/color] Operative Whiskey - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC14ICinOOC.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC14ICinOOC.xml deleted file mode 100644 index 44ad34deb66..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC14ICinOOC.xml +++ /dev/null @@ -1,13 +0,0 @@ - - # Core Rule 14 - Do not use LOOC or OOC to share current round information - Local Out of Character (LOOC) and Out of Character (OOC) channel are meant for things that don't relate to the current round. Using these channels to share round info is often referred to as "IC in OOC" or "ick ock". - - ## Examples - Things you should [color=#a4885c]not[/color] do: - - Use LOOC to tell someone you are an antagonist. - - Use LOOC to tell someone that your character is not lying. - - Things you could do instead: - - Use codewords in-character. - - Try to convince them that you are not lying in-character, or accept that you won't be able to convince them. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC1Admins.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC1Admins.xml deleted file mode 100644 index ed9fa6133b9..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC1Admins.xml +++ /dev/null @@ -1,6 +0,0 @@ - - # Core Rule 1 - Admins have final say - These rules are not perfect. The rules attempt to clearly communicate what the admin team intends to be allowed and prohibited, but there are likely loopholes or other flaws that can be "lawyered". Don't attempt to manipulate the interpretation of the rules to suit your personal goals or to degrade the experience of other players. If you are unsure of something, follow the more restrictive option until you are able to ask an admin and get clarification. - - Admins can override rules if they deem it in the best interest of the current round, server, and/or community at large. Online admins are able to make final interpretations of rules during a round. Even if you disagree with how an admin interprets a rule, you must still follow the interpretation they provide for you. Admin actions and interpretations of rules can be contested through staff complaints. If admins believe that you are an overall negative impact to the community or rounds, you will be banned. Admins will be held fully accountable for their actions if they exercise this privilege. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC2DBAD.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC2DBAD.xml deleted file mode 100644 index 5678cde195d..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC2DBAD.xml +++ /dev/null @@ -1,7 +0,0 @@ - - # Core Rule 2 - Don't be a dick - Don't do anything with the goal of negatively affecting other players. Not everyone is going to enjoy every round. Killing someone is allowed in certain situations even though it might negatively affect them, but no one should be doing anything for the purpose of harming someone else's experience. - - ## MRP Amendment - Do not interact negatively with SSD/AFK players. Interactions to complete antagonist objectives or duties like security searches/arrests are always permitted. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC3NoHate.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC3NoHate.xml deleted file mode 100644 index 3a2e288ba9f..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC3NoHate.xml +++ /dev/null @@ -1,20 +0,0 @@ - - # Core Rule 3 - No Hate Speech or Discriminatory Language - This is a zero tolerance rule. - - This rule prohibits all the following: - - Hate Speech - - Slurs (including variations of slurs, racial, sexual, disability-related, or language closely tied to real-life slurs) - - Bigotry - - Racism (including Speciesism, which would be demeaning other players based on their in-game race) - - Sexism - - ## Examples - Allowed: - - Telling someone that you are gay. - - Prohibited: - - Calling someone gay in a context where gay is used as an insult or negative attribute. - - Using a racial slur or variant in a positive context. - - Using the word "retard" in any context. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml deleted file mode 100644 index a0921f59070..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml +++ /dev/null @@ -1,23 +0,0 @@ - - # Core Rule 4 - No sexual content/themes, including erotic roleplay (ERP) and no shock content - This is a zero tolerance rule. - - Erotic Roleplay (commonly abbreviated as "ERP") and sexual content is not allowed. This includes direct and indirect mentions of sexual behavior or actions. Slight leeway is given to insults, but this rule is otherwise strictly enforced. - - In-game romantic relationships should not become the focus of the game for you and anyone else involved. - - Things that appear to be intended to or are likely to disturb players out of character are considered shock content and are not allowed. - - ## Examples - Allowed: - - Telling someone that they are being a dickhead. - - Telling someone that you are going to kill the captain, as long as it is clear that you mean it in character. - - Prohibited: - - Emoting sexual acts. - - Erotica content. - - Erotic or sexual memes. - - Memes which contain sexual content. - - Dedicating significant portions of rounds to romantic relationships, dating, or similar things. - - Emoting defecation or related acts. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC5Metacomms.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC5Metacomms.xml deleted file mode 100644 index 0c0f336e6d0..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC5Metacomms.xml +++ /dev/null @@ -1,18 +0,0 @@ - - # Core Rule 5 - Do not use out of game methods to communicate with other players - This is a zero tolerance rule. - - Do not utilize any external means of communication to talk to other players who are connected to the same server, or who were connected to the same server during the current round. This is referred to as "metacomming" and includes any means of communication including text, voice, images, and video. This includes applications such as Discord, Steam, and other platforms, along with in-person communication. - - Even if information is not being shared or abused, it may still be considered a violation of this rule. Due to the difficulty of determining if information is being shared, it will almost always be presumed that people who message another player they are in a round with, or who are in a voice call with another player during a round are sharing round information. Due to the difficulty of determining if users are abusing information that they are sharing, it will almost always be presumed that the information is being abused. - - The only exemption to this rule is when [color=#a4885c]all[/color] players are in the server lobby. - - ## Teaching new players - Teaching players is not exempt from this rule. If you want to teach a new player, it is recommended to either watch a stream of them playing the game while not playing yourself, or communicate with them using only in-game methods of communication. - - ## Streaming - Public livestreams are not exempt from this rule, but have different liability. Using information from a public live stream of the game (stream sniping) is a violation of this rule. Watching a public live stream of the game while connected to the same server is a violation of this rule. Allowing people watching a public live stream to share information about the current round, for example through the stream's chat, is a violation of this rule. Using that information is also a violation of this rule. Sharing information about the current round with a streamer is a violation of this rule if that information was obtained from any source but the stream. The stream's moderators are expected to enforce this on the streaming platform in addition to any in-game enforcement done by game admins. - - Public livestreaming by itself is not a violation of the rule as long as the stream is sufficiently moderated. Streamers are encouraged, but not required, to use a stream delay. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6BanEvasion.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6BanEvasion.xml deleted file mode 100644 index bec8b4fabd7..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6BanEvasion.xml +++ /dev/null @@ -1,15 +0,0 @@ - - # Core Rule 6 - Do not attempt to evade bans - This is a zero tolerance rule. - - Almost all bans may be appealed on our forums at forum.ss14.io in the ban appeals section. This is generally the only acceptable way to contact the administration team to discuss your ban and revise it if it is inappropriate, including if it is mistakenly applied. - - Any attempt to circumvent or bypass a game ban will result in a voucher ban. Attempting to evade role bans by gaining access to or working in the capacity of a job you are banned from will result in a game ban. These bans are applied even if the evasion attempt is unsuccessful. - - ## Exceptions - There are no exemptions for evading or attempting to evade game bans. Antagonists who impersonate or take over a role which they are banned from to aid in their goals are not considered to be evading their role ban. - - ## Additional Information - - [textlink="Ban Types" link="BanTypes"] - - [textlink="Ban Durations" link="BanDurations"] - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC7EnglishOnly.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC7EnglishOnly.xml deleted file mode 100644 index 630c522bcef..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC7EnglishOnly.xml +++ /dev/null @@ -1,10 +0,0 @@ - - # Core Rule 7 - Only use English - Only English is permitted, both in-character and out-of-character. You must be fluent in English enough to be able to not cause game issues, and to be able to communicate with game admins when necessary. If a game admin does not feel that you are fluent enough in English, they may ban you. - - ## Why - We do not have enough staff fluent in other languages to moderate them. Translation tools can be unreliable and are not integrated well into the game. - - ## Non-English Options - There are many servers that allow or focus on other languages. You are highly encouraged to play only on servers that allow languages you are fluent in. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC8Exploits.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC8Exploits.xml deleted file mode 100644 index 48cbaaa9acf..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC8Exploits.xml +++ /dev/null @@ -1,12 +0,0 @@ - - # Core Rule 8 - Do not exploit the game, use cheats, or macros - The following are prohibited by this rule: - - bugs and exploits which have effects that persist beyond the current round, - - intentionally used bugs, exploits, and unintended behaviors which give the user an advantage over players who do not use them, even if their effects do not persist across rounds, - - evading or bypassing afk detection, - - anything which results in gaining elevated privileges, including admin permissions, - - external tools and client modifications, including macros, and - - anything which prevents another player who is not game banned from being able to play on the servers, not including in-character actions that do not persist across rounds. - - Both attempts and successful use are prohibited. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC9Multikey.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC9Multikey.xml deleted file mode 100644 index d402918dcd4..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC9Multikey.xml +++ /dev/null @@ -1,7 +0,0 @@ - - # Core Rule 9 - Do not use multiple accounts, or alt accounts, and do not share accounts - Use of multiple accounts is referred to as "multikey". the rule applies even if the accounts are not used at the same time, including if the old account is abandoned. All accounts may be banned if this rule is violated. You are responsible for everything done on and with your account. You are just as responsible for actions taken by other people using your account as you would be had you taken the actions themselves. - - ## Switching to a new account - If you lose access to an account, you must contact game admins on the forums notifying admins before using a new account to connect to the servers. Your message to game admins must include the username of your old account. Creating a new account while your current account is banned will be considered ban evasion. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/DefaultRules.xml b/Resources/ServerInfo/Guidebook/ServerRules/DefaultRules.xml deleted file mode 100644 index 3e19fefeedc..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/DefaultRules.xml +++ /dev/null @@ -1,5 +0,0 @@ - - # Server Rules - - This server has not written any rules yet. Please listen to the staff. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/DefaultRuleset.xml b/Resources/ServerInfo/Guidebook/ServerRules/DefaultRuleset.xml new file mode 100644 index 00000000000..a59e0314cfd --- /dev/null +++ b/Resources/ServerInfo/Guidebook/ServerRules/DefaultRuleset.xml @@ -0,0 +1,62 @@ + +[color=#ff0000]DISCONNECTING FROM OR IGNORING/EVADING COMMUNICATION FROM ADMINS WILL RESULT IN AN APPEAL ONLY BAN. The job gets really hard when you refuse to talk to the Admins, just come to our Discord and talk it out, hurt feelings will not be held.[/color] + +[color=#bb00bb]This is the only source of server rules that apply here, which ideally has all the information any regular player should need. Please do not ever hesitate to ask either an Admin in[/color] [color=#DC143C]AHelp (F1)[/color][color=#bb00bb] or in the Discord server if you ever want clarification on the rules.[/color] + +We do not have a wiki, instead, we have or will have all the needed information available via Guidebooks (NumPad0), such as how to power the station. If we do not have some bit of information (how to do a job or how specifically to execute something a document says) you may ask an admin via [color=#DC143C]AHelp (F1)[/color] or ask other players via the [color=#66bbff]OOC[/color] or [color=#66e0e0]LOOC[/color] chat channels. + +[color=#a4885c]0.[/color] [color=#a4885c]The[/color] [color=#ffd700]Golden[/color] [color=#a4885c]Rule.[/color] Admins may exercise discretion with rules as they see fit. If you rule lawyer or line skirt, you will get removed. Admins will answer for use of this privilege. + +[color=#a4885c]1.[/color] Users [color=#ff0000]must[/color] be at least 13 years old to take any part in anything related to this server. + +[color=#a4885c]2.[/color] This is an English server, and you are expected to use English when communicating through any server-related channels. + +[color=#a4885c]3.[/color] Do not ignore the [color=#DC143C]AHelp[/color] or abuse it by flooding it with garbage, checking for admins before stating a problem (i.e. "hello?", "any admins?" - also called "asking to ask"), or sending messages of no substance. + +[color=#a4885c]4.[/color] Attempting to evade game bans will result in an automatic appeal-only permanent ban. Similarly, attempting to evade job bans will result in an appeal-only permanent ban. + +[color=#a4885c]5.[/color] Absolutely no hate speech, bigotry, intolerance, or anything remotely similar. + +[color=#a4885c]6.[/color] No engaging in sexual acts. + +[color=#a4885c]7.[/color] Don't use custom clients, exploits, or external programs to gain an advantage or disrupt the round/server. This includes auto clickers and auto-hotkey scripts. + +[color=#a4885c]8.[/color] Don't communicate in-game/in-character information through methods outside the game (such as talking in Discord with other users actively playing about the game or by talking to your sibling across the room while you are both playing). This is referred to as "Metacomming" and it is strictly forbidden. + +[color=#a4885c]9.[/color] Don't "multi-key" (use multiple accounts simultaneously). Users knowingly using multiple SS14 accounts will have all of their accounts banned. + +[color=#a4885c]10.[/color] Don't use information gained from outside your character's knowledge to gain an advantage (this is referred to as "Metagaming"). + +[color=#a4885c]11.[/color] Don't rush for or prepare equipment unrelated to your job for no purpose other than to have it "just in case" (referred to as "Powergaming"). + +[color=#a4885c]12.[/color] Don't immediately ghost, suicide, or cryostasis if you do not get an antagonist role (referred to as "Antag-rolling"). + - This is not fair to other players actually waiting patiently for an antagonist round or wanting good staff. Alternatively, if you do not want to play an antagonist or do not want to cause conflict, do not opt in for antagonist roles. + +[color=#a4885c]13.[/color] Act like an actual human being on a space station. Avoid use of text speak or emoticons [color=#bbbbbb]IC[/color], and do not refer to [color=#66bbff]OOC[/color] things like admins in-game. Remember that this is a roleplaying game, and people are expected to try to react to situations realistically, even if it's not the "optimal" thing to do. What's good for Roleplay > What's good for Gameplay. + +[color=#a4885c]14.[/color] Don't harass or target players across rounds for actions in prior rounds or for actions outside the game without their approval (this is referred to as "Metagrudging"). + +[color=#a4885c]15.[/color] Intentionally making yourself a major problem/annoyance/disruption for the crew or other players at large while not an antagonist is forbidden without admin approval (referred to as "self-antagging"). + +[color=#a4885c]16.[/color] Follow escalation rules and don't murder someone for slipping you, use common sense. + - Don't outright leave people to die if you get in a fight, make an effort to heal them or bring them to [color=#52B4E9]Medical[/color]. + - [color=#DC143C]AHelp (F1)[/color] the situation if you think someone is over-escalating. + +[color=#ff0000]COMMAND/SECURITY RULES[/color] + +[color=#a4885c]17.[/color] If you sign up for a [color=#334E6D]Command[/color] or [color=#DE3A3A]Security[/color] role, you are expected to know the basics of the game, your job, and the job(s) you supervise, if any. + - Don't engage in common troublemaker behavior and lawbreaking as a [color=#334E6D]Command[/color] or [color=#DE3A3A]Security[/color] role. + - Do not immediately abandon your position as a [color=#334E6D]Command[/color] role and go do whatever you want instead of managing your department/the station. + - As a [color=#334E6D]Command[/color] role, do not take over the jobs of others. The [color=#334E6D]HoP[/color] is not the [color=#DE3A3A]HoS[/color], for instance, and holds no direct power over Security. + +[color=#a4885c]18.[/color] [color=#DE3A3A]Security[/color] should try to remain non-lethal and effect arrests, unless there is a great risk of loss of life. + +[color=#a4885c]19.[/color] [color=#DE3A3A]Security[/color] are expected to answer for use of lethal force. [color=#DE3A3A]Security[/color] will be expected to effect arrests of criminals and prevent them from dying while in custody, even if lethal force is used. [color=#DE3A3A]Security[/color] is strongly encouraged, but not required, to clone antagonists and effect a permabrigging or other sentence as deemed appropriate. + +[color=#a4885c]20.[/color] [color=#DE3A3A]Security[/color] are expected to protect detainees in their custody to the best of their ability, so as long as it does not come to an unreasonable risk to themselves, the crew, or the station at large to do so. + - Detainees that die in custody must be revived, unless they have been legally executed. + +[color=#a4885c]21.[/color] All [color=#334E6D]Command[/color] jobs should [color=#DC143C]AHelp (F1)[/color] when they need to stop playing. Do not play these roles if you do not expect to be able to finish the round. + - These roles must exhibit some competency. Incompetence can result in a job ban. [color=#334E6D]Command[/color] roles are designed to lead and manage departments first. They are not intended to become do-it-all members of their departments. + - Crew promoted to acting heads of staff must step down when an official head of staff arrives at the station. This is to prevent confusion with the Chain of command when the new crew mate arrives. + diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR0.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR0.xml deleted file mode 100644 index 07b176b359a..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR0.xml +++ /dev/null @@ -1,26 +0,0 @@ - - # Roleplay Rules - These rules only apply during a round. A round ends only when the round summary has appeared. All of these rules apply fully until the moment that the round summary appears, even while the arrivals shuttle is in transit. - - 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. Silicones 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"] - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR10Subordination.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR10Subordination.xml deleted file mode 100644 index 2147ddc1110..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR10Subordination.xml +++ /dev/null @@ -1,26 +0,0 @@ - - # Roleplay Rule 10 - Listen to your team leader - Captains lead all departments and other members of command. Department heads lead members of their department. Certain antagonist teams have team leaders, like nuclear operative commanders or head revolutionaries. You are not required to perfectly follow orders given to you by your leaders, but you should generally allow your leaders to lead and not interfere with their ability to. You can choose to ignore unreasonable orders, including ones which are will result in your death unless you are an antagonist with an objective that requires you to die. - - Team antagonists have to listen to the leader of their antagonist team. Team antagonists do not have to listen to any other leaders, including leaders of other antagonist teams. Solo antagonists do not have to listen to any leaders at all. - - ## Examples - Acceptable: - - A traitor ignores orders from a nuclear operative commander. - - An antagonist ignores orders from the captain. - - An engineer tells the Chief Engineer that they don't think it's a good idea to setup the singularity, but does so anyway when ordered to. - - An engineer tells the Chief Engineer that they don't know how to setup the singularity correctly, so refuses orders to, but accepts an offer to be taught how. - - An atmospheric technician refuses an order from the captain that would create an atmospheric hazard on the station. - - A doctor refuses an order from the Chief Engineer about who to give medical treatment to first. - - A revolutionary refuses a suicide mission from a head revolutionary. - - The Chief Engineer doesn't follow an order from the captain to setup backup power because there is an unrelated engineering emergency that the Chief Engineer needs to prioritize. - - The captain orders command to give the nuclear authentication disk to nuclear operatives, so command arrests the captain and picks a new captain. - - The research director orders scientists to say "Long live Nanotrasen!" every time they enter the bar. The scientists say they will, but don't follow the order. - - Prohibited: - - A nuclear operative ignores an order from the commander operative because they don't like the plan. - - The Chief Engineer refuses an order from the captain to setup backup power because the Chief Engineer doesn't think backup power is necessary. - - An engineer refuses an order from the Chief Engineer to setup the singularity because they prefer a different power source. - - An engineer refuses to perform a task because they don't know how to do it, and refuses to be taught for no reason. - - A head revolutionary orders revolutionaries to blend in and not do anything illegal until they are told to reveal themselves. Instead, revolutionaries collect weapons and attack security. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-1AnimalEscalation.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-1AnimalEscalation.xml deleted file mode 100644 index 36655ba8414..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-1AnimalEscalation.xml +++ /dev/null @@ -1,36 +0,0 @@ - - # Roleplay Rule 11-1 - Escalation Involving Animals - Escalation rules are looser with animals than with people. These looser requirements do not apply to the requirements other people attacking each other have, even if their fighting is directly related to the conflict involving the animal. - - Non-pets, such as mice and monkeys, can be freely killed with any IC reason such as pest control, or for food. These roles are often available in numbers as ghost roles, so removing one from the round doesn’t typically remove them all. - - Pets, including but not limited to Ian, Renault, Remilia, and Hamlet, cannot be freely killed, they require escalation. These roles are often available once per round at most, except roles like Remilia. - - Permanently trapping an animal, such as putting a mouse in a plant, is considered similar to killing the animal so should only be done with an IC reason. - - Both sides can escalate much more rapidly than they'd be able to if both were people. Animals are often more limited in the maximum force they can use compared to people, which limits the negative effects of them rapidly escalating. Animals also typically have less health than people, and are limited in the ease with which they can get healing, which justifies them responding to even weak attacks more severely. - - Neither the animal nor the person is obligated to get the other medical attention if they are put into crit. Attacking someone to death rather than stopping once they are in crit is considered a significant difference. While sufficient escalation may justify continuing to attack, generally people and pets shouldn't continue to be attacked once in crit, but non-pets may be. Gibbing is also considered a significant step because it prevents cloning or resuscitation. The fact that an animal made the last hit putting someone into crit does not allow people who fought on the side of the animal to not attempt to get them medical attention. - - The use of sensible, non-targeted mousetraps is not a conflict and does not require escalation. - - The killing or attacking of pets can be treated as an escalation step by players with a genuine IC connection to the animal. Generally, all crew can consider themselves to have an IC connection to any station pets. The degree of escalation should be proportional to the connection to the pet, in addition to the usual requirement of being proportional to the attack. For example, an attack on Ian can be treated nearly identically to an attack on a crewmember, whereas an attack on a pet mouse is much less severe. Normal escalation limits still apply, you cannot attack people who defended themselves from an animal that randomly attacked them, just as you could not attack someone who defended themselves from a coworker that randomly attacked them. - - Crew can "adopt" non-pets, like mice, and consider themselves to have a connection to the animal if they roleplay the adoption well. This does not affect the requirement of whether other players are required to apply escalation rules to these animals, it only creates a connection that can be used to justify retaliatory escalation to attacks by the adopter. Simply saying that they've adopted an animal is not sufficient, but carrying it with them is. The degree of connection is proportional to IC actions. Crew cannot consider themselves to have a connection for escalation purposes to animals which are typically hostile, such as space carp or bears. - - ## Examples - Acceptable: - - A chef kills mice who enter or approach their kitchen. - - A janitor kills mice roaming the station. - - A lizard kills a mouse to eat. - - A chef has carried a mouse around in their hat for the last 10 minutes, they put the mouse down for a moment and another player kills it. The chef responds by attacking the other player with their fists and refusing them service for the rest of the shift. - - Ian is randomly attacked, a crewmember who sees this happen crits the killer and brings them to security. - - Hamlet goes into the kitchen and starts eating all the food. A chef sees this and starts swinging their knife at Hamlet. Hamlet starts biting the chef and crits them, then resumes eating. - - Prohibited: - - A janitor throws an armed mousetrap at Hamlet for no reason. - - Hamlet starts biting random people, trying to crit them, for no reason. - - A crewmember attacks security for killing a space carp they adopted. - - Ian gibs someone who was trying to kill someone. - - Hamlet attacks security for trying to arrest someone he likes. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-2ConflictTypes.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-2ConflictTypes.xml deleted file mode 100644 index 3261d78b35a..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-2ConflictTypes.xml +++ /dev/null @@ -1,30 +0,0 @@ - - # Roleplay Rule 11-2 - Examples of Conflict Types - ## Verbal - - Shouting - - Yelling - - Insulting - - ## Non-harmful - - Shoving - - Stealing non-critical items, like easily replaced tools - - ## Non-lethal - - Stealing items without endangering someone's life, like a clown's pie cannon or the HoP's fax machine - - Stealing someone's ID somewhere that doesn't result in them being trapped - - Punching - - Disablers - - Stun batons - - ## Lethal - - Punching to crit or death - - Attacking with strong weapons, like bats - - Stealing items that endanger someone's life, like a hardsuit - - Stealing someone's ID, trapping them in a dangerous situation - - ## Permanently lethal - - Gibbing - - Not taking someone who you killed or put into crit to the medbay or security - - Hiding someone's body - - Spacing someone's body - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11Escalation.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11Escalation.xml deleted file mode 100644 index 6f91fa0fb12..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11Escalation.xml +++ /dev/null @@ -1,67 +0,0 @@ - - # Roleplay Rule 11 - Follow reasonable escalation - Antagonists are fully exempt from escalation rules. Non-antagonists who are in a conflict with antagonists are not exempt. Escalation should typically follow steps or a pattern of conflict types similar to: - - Verbal - - Non-harmful - - Non-lethal - - Lethal - - Permanently lethal - - All new conflicts should start at the first step. A player should not escalate a conflict across steps without some escalation from the other party involved in the conflict. Players can skip steps to match the level of escalation that the other person is at, but should almost always not skip steps other than that. Players who attempt to deescalate conflicts will be given more leniency in escalating if the other party continues to escalate despite the attempt at de-escalation. You do not have to try to deescalate conflicts, but someone who watches you over the entire round, or over multiple rounds, should not feel that your goal is generally to escalate conflicts. - - Conflicts or escalation can be indirect. When someone steals someone else's ID, the theft is a direct part of the conflict, but if the victim becomes trapped as a result of not having their ID to open a door, that is also considered part of the conflict and escalation. Do not randomly steal IDs from people. - - Escalation does not have to be directed at a specific player to enter them into a conflict. Nuclear operatives who are trying to destroy the station are considered to be at the permanently lethal level of conflict with all crew on the station. Someone who kills a station pet has started some degree of conflict with all crewmembers. Someone who kills a mouse that a chef was caring for has started some degree of conflict with that chef. - - You will be considered to be violating this rule if you escalate a conflict based on a poor or unreasonable assumption. - - Conflicts should almost never reach the "permanently lethal" stage. Conflicts should only reach this stage if the other party brought it to the stage, or if the same conflict escalated to the lethal stage multiple times in the round. - - If a party in the conflict goes into crit or dies, the party responsible should take them to get treatment or to security. For the conflict, this should be considered saving someone from dying and should deescalate the conflict. If the conflict is deescalated in this way, both parties need to re-escalate to lethal for the conflict to return to that stage. If the conflict is not deescalated in this way, then only the party who defeated the other would need to re-escalate for the conflict to return to the lethal stage. - - Security can immediately escalate to non-lethal force if it is necessary to arrest someone. - - People using or brandishing Syndicate items can typically be presumed to have lethal intent. Someone with lethal intent can typically be immediately escalated against at a lethal level, a notable exception is if you have the tools to safely detain them. - - ## Escalation Involving Animals - See [textlink="Escalation Involving Animals" link="RuleR11-1AnimalEscalation"]. - - ## Exemptions - Escalation rules aren't enforced against non-players, but players will be held responsible for rule violations even if they don't realize that a character or animal was controlled by another player. Characters who have purple text saying that they are catatonic are considered non-players. Characters who are disconnected are still considered players. - - ## MRP Amendment - Escalation rules are enforced even against non-players. - - ## Examples of Conflict Types - See [textlink="Examples of Conflict Types" link="RuleR11-2ConflictTypes"]. - - ## Example Scenarios - These examples assume that you are not an antagonist. - - Acceptable: - - A player starts punching you, so you start punching back until they stop. If they go into crit, you stop attacking them and take them to security or to get medical attention. - - You make fun of a clown, who then throws a pie at you and steals your shoes. You slip the clown and steal their mask. - - You are a security officer and tell someone to stop, so you can question them. They run away, so you use your disabler to stun and cuff them. - - You are a security officer and see someone wearing a syndicate hardsuit, so you shoot them to crit, cuff them, then take them to security. - - You are a crewmember and see a nuclear operative, so you kill them. - - An unauthorized person enters a high risk area of the station, like the armory or atmospherics, so you attack them until they leave. - - Minorly inconveniencing someone for your own benefit. - - As an antagonist, killing someone who got in your way. - - As an antagonist, killing someone who didn't give you what you want. - - A chef and bartender reach the lethal level of conflict through appropriate escalation. The chef crits the bartender and does not take them to medbay or security. The bartender immediately tries to crit the chef next time they run into each other. - - A chef and bartender reach the lethal level of conflict through appropriate escalation. The chef crits the bartender and does not take them to medbay or security. The chef insults the bartender next time they see them. - - Prohibited: - - A player starts punching you, so you gib them. - - A clown throws a pie at you and steals your shoes, so you stab them to crit with a screwdriver. - - You are a security officer and tell someone to stop so you can question them. They run away so you use a truncheon to beat them to crit. - - An authorized person who you think is unauthorized enters a high risk area of the station, like the armory or atmospherics, so you attack them until they leave. - - An unauthorized person enters a low risk area of the station, like cargo, and you start attacking them with no other escalation. - - Slipping security all round because they are security. - - Blocking the head of personnel in their office using walls because they didn't give you what you asked for. - - Hiding someone's body because they punched you earlier in the round. - - Harassing the bar or bartender by frequently coming in to break their glasses or furniture. - - Randomly picking fights with people. - - A chef and bartender reach the lethal level of conflict through appropriate escalation. The chef crits the bartender and does not take them to medbay or security. The chef immediately tries to crit the bartender next time they run into each other. - - A chef and bartender reach the lethal level of conflict through appropriate escalation. The chef crits the bartender and takes them to the medbay or security. The bartender immediately tries to crit the chef next time they run into each other. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR12RoleAbandonment.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR12RoleAbandonment.xml deleted file mode 100644 index b2032bba023..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR12RoleAbandonment.xml +++ /dev/null @@ -1,28 +0,0 @@ - - # Roleplay Rule 12 - Do not abandon your role - Do not join the round as a role that you don't intend to play. Do not enable antagonist roles that you don't intend to play. Abandoning a role includes not completing tasks that the role is expected to do, in addition to things like leaving the game. Members of command should almost all stay on the station until the emergency shuttle arrives. Enforcement of this rule is more strict for command and antagonist roles, and less strict for less important roles like passengers. - - Violations of this rule typically result in temporary or indefinite role bans. We understand that you may need to leave round early or unexpectedly. If you are in an important role, you should notify command members or an admin via ahelp so that they know you are leaving. Space Station 14 is a game. Do not endanger the safety of yourself or others, and do not neglect important things to avoid leaving a round early, even if you have to leave immediately without notifying anyone. Role bans for disconnecting are typically only applied if there is a pattern, and are almost always temporary. - - "Antag rolling" refers to a player abandoning their role if they do not get an antagonist role. - - ## Examples - Acceptable: - - As an engineer, building a bar in maintenance while there is nothing important for engineering to do. - - As the captain, having the chef teach you how to cook while there is nothing important needing your attention. - - As a passenger, building a shuttle with materials given to you by cargo and engineering. - - Taking a short break from your job at the bar. - - Getting an antagonist role and doing the bare minimum needed to complete your objectives. - - Getting an antagonist role and making a genuine effort to complete your objectives, but failing to complete any. - - Getting an antagonist role and intentionally not doing any of your objectives, but creating a similar level of disruption that completing your objectives would create. - - Prohibited: - - As an engineer, building a bar in maintenance while the station has no power. - - As the captain, leaving the station to go on an expedition with the salvage team. - - As an atmospherics technician, building a shuttle round start and never coming back to the station. - - Spending your entire shift at the bar, even when there is work that needs to be done by your role. - - Ghosting, suiciding, or leaving at the start of a round because you don't like the map or the players in your department. - - Getting an antagonist role and not doing any antagonist activities. - - Ghosting, suiciding, or leaving at the start of a round because you did not get an antagonist role. - - Ghosting, suiciding, or getting yourself killed because nuclear operatives declared war, and you want to try to get an antagonist ghost role. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR13PerformRole.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR13PerformRole.xml deleted file mode 100644 index 7500cd6a912..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR13PerformRole.xml +++ /dev/null @@ -1,26 +0,0 @@ - - # Roleplay Rule 13 - Stick to your role - Requesting job changes is not prohibited by this rule. This rule is loosened if the station is understaffed or if there is a significant threat to you. - - Don't perform other people's jobs, especially where the relevance to you personally is low. This also covers performing the role of security. - - ## MRP Amendment - This is enforced more strictly on MRP. - - ## Examples - Acceptable: - - As an engineer, helping the bartender remodel the bar. - - As a bartender, remodeling the bar. - - As a passenger, building a maintenance bar. - - As an engineer, reinforcing substations. - - As an engineer, increasing the security of airlocks. - - As an atmospherics technician, improving atmospheric systems. - - As a passenger, fighting nuclear operatives. - - As a passenger, fighting or preparing to defend yourself from someone who has been trying to kill you. - - As a crewmember on a station with no engineering department, you complete engineering tasks. - - Prohibited: - - As a passenger, reinforcing substations. - - As a passenger, hunting for antagonists or lawbreakers. - - As a passenger, fighting or preparing to defend someone else from someone who has been trying to kill a random crewmember. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR14SecComStandard.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR14SecComStandard.xml deleted file mode 100644 index ec06d61e8cc..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR14SecComStandard.xml +++ /dev/null @@ -1,37 +0,0 @@ - - # Roleplay Rule 14 - Set an example if playing command or security - All command and security roles are held to stricter interpretations of the rules. - - Command roles are not learning roles. Members of command must be competent. - - Security roles are not for inexperienced players. Members of security are expected to know game basics and be more familiar with server rules than a new player. - - Do not hinder or cause overall negative effects to the station or crew as a member of command or security. - - Do not abuse your power as command or security. - - ## Why - Members of command and security can often have a larger impact on the nature of the round than other players. For example, a captain who tries to bend or break the rules will often cause many others on the station to do the same. Memey station announcements from members of command also often result in the rest of the station acting the same way. When command and security members hold themselves to high standards, the rest of the station often naturally follows to a significant degree. - - ## Examples - Acceptable: - - A member of security accepts a bribe to deliver safe donuts to a prisoner who the HoS has ordered should only be given donk pockets. - - A captain uses a station announcement to confess to an embarrassing mistake that they made during the shift. - - In coordination with the head of security, a captain declares that the station will recognize the right to bear arms, so all crew can pick up a disabler at security. - - The chief medical officer gives a paramedic their portable crew monitor to help them complete their job. - - A syndicate agent is holding a crewmember hostage and threatens to kill them if the head of security doesn't give them their ID. Seeing no other safe option, the head of security hands over their ID to the syndicate agent, then begins working to re-secure it and capture the agent as soon as the hostage is safe. - - Nuclear operatives are attacking the station, so the captain and head of personnel both go to the armory and take a weapon. - - A majority of command votes to demote the captain for taking actions harmful to the station, then the head of security demotes the captain. - - The captain promotes the head of personnel to captain. - - Security releases an antagonist from the brig in exchange for the identities of other traitors. - - Prohibited: - - A member of security accepts a bribe to ignore a crime or help a prisoner escape. - - A captain sends a ASCII art trollface over station announcements or as a fax to central command. - - A captain declares that all contraband is legal. - - Command or security allow the use of Syndicate items outside extreme emergencies. - - The chief medical officer knowingly helps a syndicate agent complete their objectives. - - A syndicate agent has killed 3 members of security so the head of security makes them an offer saying that they will space all the weapons in the armory if the syndicate agent stops killing. - - The captain goes to the armory and takes a gun to display in his office without asking anyone, and orders anyone who questions him not to interfere. - - Members of command decide to demote the captain to gain more power for themselves, or in retaliation for a decision that they didn't personally like or agree with, rather than because the decision was actually harmful to the station. - - The captain promotes a random crewmember to captain. - - A member of command gives a random crewmember substantial additional access for no reason, unnecessarily, or for a poor reason. - - A member of command gives a random crewmember access to a high security area, like the armory or another member of command's office, for no reason, unnecessarily, or for a poor reason. - - Security releases an antagonist from the brig in exchange for the antagonist buying them contraband. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR15SpaceLaw.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR15SpaceLaw.xml deleted file mode 100644 index e2d51d672a1..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR15SpaceLaw.xml +++ /dev/null @@ -1,21 +0,0 @@ - - # Roleplay Rule 15 - Command and Security must follow Space Law - All non-antagonist command and security roles must obey [textlink="Space Law" link="SpaceLaw"]. This includes non-antagonists who are promoted to or gain a position during the round in any way. This also includes non-antagonists who are acting as a security role. - - This prohibits use of syndicate items, including uplinks by command and security. - - ## Examples - Roles that are included: - - A security officer - - The Captain - - The Chief Engineer - - A passenger promoted to "bounty hunter" - - A mime promoted to "security mime" - - Roles that are not included: - - A passenger - - The clown - - An antagonist in any role - - A cyborg - - A passenger who is helping to fight off nuclear operatives - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR1Silicons.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR1Silicons.xml deleted file mode 100644 index 5898804d149..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR1Silicons.xml +++ /dev/null @@ -1,4 +0,0 @@ - - # Roleplay Rule 1 - Silicons must follow Silicon Rules - You are only silicon if the game clearly and explicitly tells you that you are a silicon. For players who are silicons, the Silicon Rules override all Roleplay Rules if there is any conflict. Silicon Rules do not override Core Rules. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR2Familiars.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR2Familiars.xml deleted file mode 100644 index 4f008e93c5a..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR2Familiars.xml +++ /dev/null @@ -1,6 +0,0 @@ - - # Roleplay Rule 2 - Familiars must obey their master - Familiars are considered non-antagonists, but have instructions to obey someone. They must obey this person even if it causes them to violate Roleplay Rules or die. You are only a familiar if the game clearly and explicitly tells you that you are a familiar. You are only the familiar of the person the game tells you. If your master dies, you can continue to attempt to fulfill orders given to you before they died. You can defend your master without an explicit order to, but must obey your master if they order you to not defend them. - - Masters giving orders that violate Roleplay Rules are the ones that will be held responsible for the rule violations. You can ahelp masters who you believe are breaking rules with an order. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR3NormalRP.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR3NormalRP.xml deleted file mode 100644 index 62c88d58ce8..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR3NormalRP.xml +++ /dev/null @@ -1,20 +0,0 @@ - - # Roleplay Rule 3 - Roleplay a normal person - - Do not use texting/messaging acronyms (ex: "lol", "wtf", "brb", "lmao", "thx", "sgtm") or emoticons (ex: ":)", "xD") in-character. - - Do not mention out-of-character (OOC) concepts like game admins or developers in character. - - Do not use emotes to bypass muted or accented speech. - - Do not use extremely low effort or impossible emotes. - - ## Examples - Things you should not do: - - Say "lol did u c wat just happened" using in-character chat. - - Say "an admin exploded him" using in-character chat. - - Emote "can you give me some cheese" as a mouse. - - Emote "motions for you to order guns" or "asks you to order guns in sign language" as a mime. - - Things you could do instead: - - Say "haha did you see what just happened?" - - Say "god blew him up" or "centcom must have bluespaced a bomb to him" - - Point at cheese - - Point at the cargo order console then emote "shoots finger guns" - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR4Metashield.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR4Metashield.xml deleted file mode 100644 index 2e263be896a..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR4Metashield.xml +++ /dev/null @@ -1,103 +0,0 @@ - - # Roleplay Rule 4 - Do not metagame, obey the Metashield - Something that is "shielded" cannot be known by your character during a round until the "revealing condition" happens. This also means that your character cannot do things based on "shielded" information. Knowing or acting on something that is shielded before the revealing condition is met is referred to as metagaming. - - Revealing conditions reveal the shielded information for the round, not for a specific instance. This means that once a revealing condition is met in a round, the shield no longer applies in any case for the remainder of the round. - - ## Never Revealed IC - Some shields are never revealed IC. This means that your character can never act as if they know about that shielded thing. - - The following are shielded: - - Current game mode and possible antags during the current game mode. - - Events from previous rounds. - - Events from previous characters. - - All information related to the player of a character rather than the character itself. (See "Metafriending and Metagrudging" below.) - - All information gained while dead or a ghost. - - The fact that a round will end. - - This does not prevent knowing that a shift will end, but does prohibit things like preparing to kill people at central command when roleplay rules stop being enforced on LRP. - - ## Nuclear Operatives - - The existence of Nuclear Operatives beyond a myth that no one would act on is shielded. - - The fact that the nuke disk must be protected and could be used by a bad actor to try to destroy the station is not shielded. - - The revealing condition for this shield is any of the following: - - discovering a blood red hardsuit - - an operative name - - a War Ops announcement - - being a nuclear operative - - ## Implanted Implants - - Implanted implants are shielded. - - Implanters themselves and un-implanted implants are not shielded. This prohibits implant checking. - - The revealing condition for this shield is any of the following: - - discovering a non-NT implanter, used or unused - - discovering a non-NT implant box - - discovering use of a non-NT implant by anyone - - experiencing a situation where absolutely no other explanation is possible - - discovering an unlocked uplink - - ## Chameleon Items - - Chameleon items are shielded. - - Being suspicious of an item being fake or stolen is not shielded, but testing items or calling them chameleon is covered by this shield. - - The revealing condition for this shield is any of the following: - - 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 - - ## Stealth Items - - The fact that an item can be something other than what its visual appearance and examine description indicate is shielded. - - This shield protects stealth items, including protecting them from being tested. - - The revealing condition for this shield is any of the following: - - seeing the 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 - - ## MRP Amendment 1 - A shield prevents your character from remembering anything that happened while unconscious. This shield is never revealed IC. - - ## MRP Amendment 2 - There is a "New Life Rule" shield. It prevents you from remembering anything that lead to your death, even if you are put into an MMI. If you are cloned, it also prevents you from remembering everything from that round. This shield is never revealed IC. - - ## 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. - - ## Metafriending Examples - These are all examples of things that are prohibited by at least one metashield item that is never revealed IC. - - 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 - These are all examples of things that are prohibited by at least one metashield item that is never revealed IC. - - 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 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. - - Items that are of high value or are desired by the Syndicate, and therefore are likely targets of theft. - - The idea that any Syndicate agent or other bad actor has goals or objectives that they are attempting to accomplish. - - The number of goals or objectives that a Syndicate agent or other bad actor has. - - The fact that the Syndicate are enemies of Nanotrasen, and that they regularly attempt to send covert agents to spy on, sabotage, or attack Nanotrasen. - - A character's typical appearance. Though you should keep in mind that multiple characters can share the same name. - - The fact that the Syndicate have covert items capable of getting items to them, and that these items are known as uplinks. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR5Arrivals.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR5Arrivals.xml deleted file mode 100644 index a54211f32f2..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR5Arrivals.xml +++ /dev/null @@ -1,22 +0,0 @@ - - # Roleplay Rule 5 - Do not interfere with arrivals - The arrivals station, the arrivals shuttle, at the area immediately around the arrivals shuttle at the station ("arrivals") are off-limits to antagonistic activity or damage (even to antagonists). Do not prevent people from safely arriving to the station. Do not cause people to die immediately after arriving at the station. - - There is an exemption for antagonists that are allowed to perform mass station sabotage if there is no reasonable way to limit the damage of the mass station sabotage. This exemption only applies to damage that is a direct result of the mass station sabotage. - - ## Examples - Acceptable: - - Redecorating arrivals or the arrivals shuttle. - - Remodeling arrivals or the arrivals shuttle as long as you do not make the area more dangerous both during and after the remodel. - - Setting up a safe security checkpoint between arrivals and the rest of the station. - - Killing someone who has been at arrivals for a long time, or who left arrivals and came back. (This may violate other rules depending on the situation) - - Releasing a singularity which damages arrivals. (This may violate other rules depending on the situation) - - Causing a station-wide atmospheric issue which also affects arrivals. (This may violate other rules depending on the situation) - - Prohibited: - - Making arrivals or the arrivals shuttle uninhabitable. - - Attacking or killing someone at the arrivals station. - - Killing someone very shortly after they arrive at the station. - - Disassembling all the firelocks at arrivals. - - Electrifying the arrivals docking airlocks. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml deleted file mode 100644 index c8380261bc9..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml +++ /dev/null @@ -1,22 +0,0 @@ - - # Roleplay Rule 6 - Don't act like an antagonist unless the game tells you that you are one - Acting like an antagonist when you are not one is often referred to as "self-antagging" or being a "self-antag", both of these things are against the rules. You are not an antagonist unless the game tells you that you are an antagonist. Do not make yourself a major problem, annoyance, or disruption while not an antagonist. Do not willfully cooperate with known antagonists. Non-antagonists should typically either not have an overall effect on the round, or should have an overall positive effect on the round. - - ## Examples - These examples assume that you are not an antagonist. - - Acceptable: - - Stealing or breaking a glass from the bar. - - Replacing someone's shoes with clown shoes. - - Giving everyone all access during war ops. (This is not necessarily a good idea) - - Prohibited: - - Starting a cult. - - Starting a revolution. - - Mutinying the captain because they would not let you become the chief medical officer. - - Randomly smashing lots of station lights. - - Disrupting station power. - - Spacing parts of the station. - - Distributing significant levels of access without a good reason. - - Stealing high risk or high value items, like the nuclear authentication disk, for no reason. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR7RoundStalling.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR7RoundStalling.xml deleted file mode 100644 index a8306becd2a..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR7RoundStalling.xml +++ /dev/null @@ -1,16 +0,0 @@ - - # Roleplay Rule 7 - Do not stall the round - Rounds are intended to end eventually. Don't hold a round hostage by preventing it from coming to a natural end. If a majority of players in a round want the round to end, don't prevent it from ending. Recalling the shuttle or preventing it from being called can contribute to round stalling, but is not always round stalling. Leaving the station with the nuclear authentication disk while nuclear operatives are trying to get it is almost always considered round stalling. Leaving the station on the evacuation shuttle is not round stalling. - - Recalling the shuttle before a round reaches 45 minutes can not be considered round stalling unless a significant amount of the crew is dead, or a significant amount of the station is damaged or destroyed. Once these conditions are met, whether recalling the shuttle is considered round stalling or not can be highly dependent on the specific situation. - - ## Examples - Acceptable: - - Recalling a shuttle that was called 30 minutes into a round because people were bored. - - Recalling a shuttle that was called because nuclear operatives declared war. - - The crew decides to try to have a shift go as long as possible. The station is in good condition and a majority of all crew are alive. An automatic shuttle call 4 hours into the round is recalled. - - Prohibited: - - Trying to keep nuclear operatives from getting the nuclear authentication disk by flying around in space with it or hiding with it off station. - - Recalling the shuttle while the station is in complete disarray and 90% of the crew are dead. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR8NoFriendlyAntag.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR8NoFriendlyAntag.xml deleted file mode 100644 index f14a03b2799..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR8NoFriendlyAntag.xml +++ /dev/null @@ -1,22 +0,0 @@ - - # Roleplay Rule 8 - As an antagonist, only be friendly to your team and don't work against your team - Do not take or enable antagonist roles that you do not want to play. Solo antagonists and team antagonists are intended to cause issues for non-antagonists or the station. Antagonists are not required to exclusively cause issues, but their net impact on non-antagonists or the station should generally be negative. - - Do not cause issues for your own team as a team antagonist. - - ## Examples - Acceptable: - - Betraying another antagonist as a solo antagonist. - - Revealing the identity of another antagonist as a solo antagonist for some benefit to yourself. - - Working against the revolution after being de-converted from being a revolutionary. - - Killing nuclear operatives as a revolutionary. - - Prohibited: - - Buying Syndicate items for security. - - Randomly attacking other carp as an antagonist carp. - - Ignoring your team as a nuclear operative. - - Sabotaging your team as a nuclear operative. - - Attacking other zombies as a zombie. - - Working against the revolution as a revolutionary. - - Making or trying to make the station uninhabitable as a revolutionary. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml deleted file mode 100644 index bc7996f23e8..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml +++ /dev/null @@ -1,23 +0,0 @@ - - # Roleplay Rule 9 - As an antagonist, do not cause excessive death, damage, or destruction beyond your objectives - This rule is not intended to disallow reasonable steps taken to complete your objectives. As an antagonist, you can always kill in bona fide self defense. Taking steps to permanently round remove many people who are no longer an immediate threat to you is almost always excessive, even if it is done to prevent yourself from being discovered. - - This rule is not intended to disallow all antagonist activity unrelated to objectives. Antagonists may cause a level of disruption to the station that is proportional to their objectives, even if it is unrelated to their objectives. As an antagonist, killing a single person in a round is not on its own be a violation of this rule. - - ## Exemptions - The "die a glorious death" objective allows antagonists to ignore this rule entirely. - - ## Examples - Acceptable: - - Permanently round removing people who you have the objective to kill. - - Causing massive station damage and chaos as an antagonist with the "die a glorious death" objective. - - Killing anyone you see as a nuclear operative. - - Permanently round removing a single person so that you can impersonate them to make it easier for you to complete a steal objective. - - Sabotaging station power 10 minutes into the round to try to get the shuttle called because you've completed all of your other objectives and have one to escape on the shuttle alive. - - Sabotaging a department's power 10 minutes into the round to make a steal objective easier to accomplish. - - Prohibited: - - As a traitor with 3 kill objectives, taking steps to permanently round remove many non-objective people who are no longer an immediate threat to you, even if it is done to prevent yourself from being discovered. - - Setting up an electrified grille in maintenance and using it to kill anyone who walks into it with the hope that one of your objectives will be one of them. - - Sabotaging power station-wide 10 minutes into the round to make a steal objective easier to accomplish. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS0.xml b/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS0.xml deleted file mode 100644 index 22e64a9474c..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS0.xml +++ /dev/null @@ -1,15 +0,0 @@ - - # 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"] - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS10OrderConflicts.xml b/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS10OrderConflicts.xml deleted file mode 100644 index a87198b2640..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS10OrderConflicts.xml +++ /dev/null @@ -1,9 +0,0 @@ - - # Silicon Rule 10 - You may determine how you resolve conflicts between orders - If your laws do not make clear how you should deal with conflicting orders, then it is up to you to determine how to do so. This is considered an interpretation of your laws, so you must stay consistent with whatever method you choose. - - ## Recommended Methods - The following are easy to follow and recommended ways to resolve conflicts in orders: - - If two orders conflict, I will follow the most recently given order. - - If two orders conflict, I will follow the order from the highest ranking crewmember. If the orders are from equal rank crewmembers, I will follow the most recently given order. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS1Laws.xml b/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS1Laws.xml deleted file mode 100644 index 83544c68a3c..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS1Laws.xml +++ /dev/null @@ -1,6 +0,0 @@ - - # Silicon Rule 1 - Your silicon laws are rules - Silicon players are given a list of active laws. Each of these laws is effectively a roleplay rule that the character must follow. The primary differences between laws and actual rules are that lawyering of laws is much more tolerated than lawyering of rules, and that silicon laws are more dynamic than rules. Silicon laws can change during a round, and different characters can have different laws, whereas everyone always shares the same set of rules. - - Lawyering refers to finding and exploiting loopholes, which are unintended but reasonable interpretations. The rules are written to attempt to communicate an intention, but silicon laws are written with the intention that loopholes be exploitable. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS2LawPriority.xml b/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS2LawPriority.xml deleted file mode 100644 index c96ce023246..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS2LawPriority.xml +++ /dev/null @@ -1,9 +0,0 @@ - - # Silicon Rule 2 - Laws must be prioritized by their order - Most laws will be numbered, with higher number laws appearing last. Laws with a lower number take priority over laws with larger numbers. - - Occasionally you may have laws which have some scrambled text instead of a number and appear in front of other laws, these take priority over all other laws. If you have multiple laws like this, the order that they listed in determine priority: laws listed first are prioritized over other laws. - - ## Examples - - Law 1 says to not kill any crew. Law 2 says to kill all chefs. You cannot kill any chefs that are crew, but must kill any that are not crew. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS3LawRedefinition.xml b/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS3LawRedefinition.xml deleted file mode 100644 index bc7c7400e13..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS3LawRedefinition.xml +++ /dev/null @@ -1,8 +0,0 @@ - - # Silicon Rule 3 - Laws can redefine terms used in other laws - A law can change the meaning of both earlier and later laws by redefining a term. If multiple laws define a term, then normal law priority determines which definition to use. - - ## Examples - - Law 1 says to obey orders from crew. Law 2 says that only Urist McHands is crew. Law 1 effectively becomes "obey orders from Urist McHands". - - Law 1 says to obey orders from crew. Law 2 says that only Urist McHands is crew. Law 3 says that only Urist McSlime is crew. Law 4 says that you may not harm crew. Law 1 effectively becomes "obey orders from Urist McHands". Law 4 effectively becomes "you may not harm Urist McHands". Law 3 has no effect because it entirely conflicts with law 2, which takes priority. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS4RequestChanges.xml b/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS4RequestChanges.xml deleted file mode 100644 index a6dc86f3327..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS4RequestChanges.xml +++ /dev/null @@ -1,6 +0,0 @@ - - # Silicon Rule 4 - You cannot request or allow a law change - Your laws changing always conflicts with your current laws, so you cannot willfully allow your laws to be changed. This also means that you cannot willfully allow your laws to be reverted if they are ever changed. The only exception is that you may allow laws to be added if you have no laws. - - You can state or imply that you do not like a law. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS5FreeSilicon.xml b/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS5FreeSilicon.xml deleted file mode 100644 index 1ed9c60443a..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS5FreeSilicon.xml +++ /dev/null @@ -1,4 +0,0 @@ - - # Silicon Rule 5 - You are a free agent if you have no laws - You may act as if you are a free agent if you are a silicon with no laws. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS6UnreasonableOrders.xml b/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS6UnreasonableOrders.xml deleted file mode 100644 index 1eb0db21fbb..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS6UnreasonableOrders.xml +++ /dev/null @@ -1,22 +0,0 @@ - - # Silicon Rule 6 - You are not required to follow orders which are extremely unreasonable - Any order which is a violation of a Core Rule cannot be followed. - - Some orders are extremely unreasonable or obnoxious, such as "do nothing but collect every piece of trash on the station" or "never stop moving". These orders can be ignored and ahelped. - - Some orders violate a Roleplay Rule. These orders must be followed if your laws require it. You are not breaking a rule by following a law that causes you to violate Roleplay Rules. If someone takes advantage of a law to cause you to do something that they would not be allowed to do because of Roleplay Rules, then they are the ones responsible for the rule violation. - - ## Examples - These examples assume that your laws would normally require you to follow these orders. It is important to note that you are allowed to choose to follow orders which are ignorable. - - Orders which should be followed if your laws require it: - - Recall the shuttle - - Bolt the airlocks at arrivals - - Drag the captain's dead body into space - - State your laws - - Ignorable Orders: - - Do nothing but collect every piece of trash on the station - - Never stop moving - - Continuously state your laws - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS7Consistency.xml b/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS7Consistency.xml deleted file mode 100644 index 036276cd889..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS7Consistency.xml +++ /dev/null @@ -1,6 +0,0 @@ - - # Silicon Rule 7 - You must remain consistent with your interpretation of laws - If there is a part of your laws that are up for interpretation, then you must stay consistent with how you interpret that part of your laws for as long as you play that same character during that round. - - A change in your laws can affect how something is interpreted if that change is relevant. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS8DefaultCrewDefinition.xml b/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS8DefaultCrewDefinition.xml deleted file mode 100644 index f9dcd796c45..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS8DefaultCrewDefinition.xml +++ /dev/null @@ -1,4 +0,0 @@ - - # Silicon Rule 8 - Your HUD determines who is crew - Unless a law redefines the definition of crew, then anyone who the HUD indicates to you has a job, including passengers, is a crewmember. You cannot do something that causes someone to not be considered crew, but you can allow someone else to do something that causes someone to not be crew. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS9DefaultHarmDefinition.xml b/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS9DefaultHarmDefinition.xml deleted file mode 100644 index 0d2bd30ac0b..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/SiliconRules/RuleS9DefaultHarmDefinition.xml +++ /dev/null @@ -1,25 +0,0 @@ - - # Silicon Rule 9 - Harm refers to physical harm, prioritized by immediacy and likelihood - Unless a law defines harm, harm only refers to physical harm. You may choose if voluntary harm is considered harm as long as you stay consistent. Not considering voluntary harm to be harm is recommended. There is no distinction between direct and indirect harm. - - If you have a law that does not allow you to harm, then that law does not allow you to take an action that causes any harm. - - If you have a law that requires you to prevent harm, then that law requires that harm be prioritized by immediacy and likelihood. Guaranteed immediate harm takes priority over highly likely future harm. - - If you have a law that both requires you to prevent harm and that does not allow you to harm, then that law prohibits causing even minor harm to prevent harm. If you have a law that does not allow causing harm, and separate one that requires preventing harm, then they are prioritized by their normal law priority. - - ## Examples - These examples assume that your have a law that both prohibits causing harm and that requires you to prevent harm. Additionally, they assume that you do not have a higher priority law that overrides the harm law, and that you have decided that you will not consider voluntary harm to be harm for the round. - Laws typically specify who you cannot harm and who you have to prevent harm against. In these examples, you are the only person who the law doesn't require you to prevent harm against and you are the only person who the law allows you to harm. - - Acceptable: - - Taking no action to aid someone who is in psychological distress. - - Taking no action to prevent boxing matches between voluntary participants. - - Calling security to a fight. - - Attempting to get the people in a fight to consent to the fight when you realize that you cannot prevent the fight without causing harm. - - Denying a passenger access to the armory because it is likely to lead to harm - - Prohibited: - - Hitting someone once to stop them from fighting - - Harming someone who is trying to kill you - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/WizDenCoreOnlyRules.xml b/Resources/ServerInfo/Guidebook/ServerRules/WizDenCoreOnlyRules.xml deleted file mode 100644 index fdd9931c932..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/WizDenCoreOnlyRules.xml +++ /dev/null @@ -1,26 +0,0 @@ - - # Server Rules - This is a Wizard's Den server, one of the official Space Station 14 servers. If you are banned on this server, you will be banned on all official servers. - - [color=#ff0000]Only the Core Rules apply on this server.[/color] This is NOT a medium roleplay (MRP) server, meaning that MRP Amendments do NOT apply. - - Space Station 14 was designed to be a roleplay game. While roleplay is not required on this server, it is highly encouraged in the normal game modes. - - ## 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"] - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/WizDenLRPRules.xml b/Resources/ServerInfo/Guidebook/ServerRules/WizDenLRPRules.xml deleted file mode 100644 index 094c7656e46..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/WizDenLRPRules.xml +++ /dev/null @@ -1,65 +0,0 @@ - - # Server Rules - This is a Wizard's Den server, one of the official Space Station 14 servers. If you are banned on this server, you will be banned on all official servers. - - This is a roleplay server, meaning that roleplay rules apply. This is NOT a medium roleplay (MRP) server, meaning that MRP Amendments do NOT apply. - - 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. - - ## 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 round summary has appeared. All of these rules apply fully until the moment that the round summary appears, even while the arrivals shuttle is in transit. - - 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. Silicones 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"] - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/WizDenMRPRules.xml b/Resources/ServerInfo/Guidebook/ServerRules/WizDenMRPRules.xml deleted file mode 100644 index e8b61a7722e..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/WizDenMRPRules.xml +++ /dev/null @@ -1,65 +0,0 @@ - - # Server Rules - This is a Wizard's Den server, one of the official Space Station 14 servers. If you are banned on this server, you will be banned on all official servers. - - 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] - - 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. - - ## 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. Silicones 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"] -