Repository: Goob-Station/Goob-Station
Pull request #2491: RULES UPDATES(merge with upstream)
Author: login: Sarahon
Labels: name: size/M
description: Denotes a PR that changes 100-999 lines.
name: Changes: No C#
Created: 2025-04-22T05:40:22Z | Merged: 2025-05-25T06:15:24Z

<!--
SPDX-FileCopyrightText: 2021 Pieter-Jan Briers <pieterjan.briers+git@gmail.com>
SPDX-FileCopyrightText: 2021 Swept <sweptwastaken@protonmail.com>
SPDX-FileCopyrightText: 2021 mirrorcult <lunarautomaton6@gmail.com>
SPDX-FileCopyrightText: 2022 AJCM-git <60196617+AJCM-git@users.noreply.github.com>
SPDX-FileCopyrightText: 2022 Kara <lunarautomaton6@gmail.com>
SPDX-FileCopyrightText: 2023 DrSmugleaf <DrSmugleaf@users.noreply.github.com>
SPDX-FileCopyrightText: 2023 Kevin Zheng <kevinz5000@gmail.com>
SPDX-FileCopyrightText: 2024 Vasilis <vasilis@pikachu.systems>
SPDX-FileCopyrightText: 2024 lzk <124214523+lzk228@users.noreply.github.com>
SPDX-FileCopyrightText: 2025 Aiden <28298836+Aidenkrz@users.noreply.github.com>

SPDX-License-Identifier: AGPL-3.0-or-later
-->

<!-- Guidelines: https://docs.spacestation14.io/en/getting-started/pr-guideline -->
<!-- NOTE: All code submitted to this repository is ALWAYS licensed under the AGPL-3.0-or-later license. 
The REUSE Specification headers or separate .license files indicate a secondary license (e.g., MPL or MIT) solely to facilitate 
integration for projects that do not use the AGPL license. This secondary license does not replace the fact that AGPL-3.0-or-later remains the primary and binding license. 
Uncomment and modify the following line if you wish to change the license from the default of AGPL.-->
<!--- LICENSE: AGPL -->
## About the PR
<!-- What did you change? -->

## Why / Balance
Rules cleanup and updates.


## Requirements
<!-- Confirm the following by placing an X in the brackets [X]: -->
- [x] I have read and am following the [Pull Request and Changelog Guidelines](https://docs.spacestation14.com/en/general-development/codebase-info/pull-request-guidelines.html).
- [x] I have added media to this PR or it does not require an ingame showcase.
<!-- You should understand that not following the above may get your PR closed at maintainer’s discretion -->

**Changelog**

:cl:
- tweak: Rules clean up. Space law updates.





Diff:
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml
index e746844fbc3a..191b30e16db6 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml
@@ -9,20 +9,20 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 <Document>
   # Core Rules
-  These rules apply at all times, including between rounds.
+  These rules apply at all times, including between rounds. Zero Tolerance(ZT). Any rules marked as zero tolerance, if broken will result in an immediate permanent ban as the name suggests.
 
   - [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="3. No Hate Speech or Discriminatory Language(ZT)" link="RuleC3"]
+  - [textlink="4. No sexual or shock content(ZT)" link="RuleC4"]
+  - [textlink="5. Do not use out of game methods to communicate with other players(ZT)" link="RuleC5"]
+  - [textlink="6. Do not attempt to evade bans(ZT)" 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="8. Do not exploit the game, use cheats, or macros(ZT)" link="RuleC8"]
+  - [textlink="9. Do not use multiple accounts, or alt accounts, and do not share accounts(ZT)" 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="12. Players must be and act at least 16 years old(ZT)" 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"]
 </Document>
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml
index 3f78fdaa32dc..5938f8a62fa3 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml
@@ -7,19 +7,22 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 <Document>
   # 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.
+  - Admin help, or "ahelp"(f1), is the system used by admins to communicate with specific players in the game.
+  - Anything that is ahelped, then becomes an admin involved issue.
+  - When being ahelped, you're expected to respond to the admin. Leaving after you have been ahelped may result in a ban.
+  - Admins like you are also human, we can't be everywhere at once, we are not omniscient, and we are not perfect. We are here to help you, so please be respectful.
+  - Bwoink.
 
   ## 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.
+  All ahelps are welcome. Even if you believe it's for something silly, a false-positive is better than not reporting it. If you are unsure if something is ahelpable, you can always ask in the ahelp or Discord.
 
   # 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.
+  - Names of the characters involved if possible.
+  - A clear description of the issue.
+  - Any additional information that may help the admin identify the issue faster.
+  - Bwoink.
 
-  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.
+  Don't worry about knowing everything, admins are able to check the logs to verify what has happened even if we don't have all the details.
 
   # Examples
   Appropriate uses of ahelp:
@@ -27,10 +30,13 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   - asking questions about rules,
   - asking for a temporary exemption from a rule, and
   - request a minor gimmick, like a TC trade or item spawn.
+  - Bwoink.
 
   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,
+  - lying
   - requesting events, and
   - spamming messages about the same issue.
+  - Bwoinked.
 </Document>
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12MinAge.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12MinAge.xml
index 1c43bfa5cc06..aa3501039848 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12MinAge.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12MinAge.xml
@@ -9,7 +9,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 <Document>
   # 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.
+  Additionally, all players must act at least as mature as 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.
 </Document>
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC14ICinOOC.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC14ICinOOC.xml
index 3563cdf717ba..7bdd00133ffa 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC14ICinOOC.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC14ICinOOC.xml
@@ -7,7 +7,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 -->
 
 <Document>
-  # Core Rule 14 - Do not use LOOC or OOC to share current round information
+  # Core Rule 14 - Do not use LOOC or OOC to share current round information(Ick Ock)
   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
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml
index 54294b83ab88..4a56c67040ea 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml
@@ -19,6 +19,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   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.
+  - Telling someone you just shit yourself out of fear
 
   Prohibited:
   - Emoting sexual acts.
@@ -26,5 +27,5 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   - 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.
+  - Emoting detailed or gross explanations of defecation or related acts.
 </Document>
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6BanEvasion.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6BanEvasion.xml
index f28a93e597bf..1e1815acb2cc 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6BanEvasion.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6BanEvasion.xml
@@ -9,7 +9,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   # 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.
+  Almost all bans may be appealed on our forums at discord.gg/goobstation 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 inappropriate, including mistaken bans.
 
   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.
 
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR10Subordination.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR10Subordination.xml
index 658a2216f04a..12358cd1c5f5 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR10Subordination.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR10Subordination.xml
@@ -15,10 +15,11 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   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 antagonist ignores orders from the head of their department.
+  - An engineer tells the Chief Engineer that they don't think it's a good idea to set up the singularity, but does so anyway when ordered to.
+  - An engineer tells the Chief Engineer that they don't know how to set up 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 doctor refuses an order from the Chief Engineer about whom 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.
@@ -29,5 +30,6 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   - 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 department crew member refuses an order from their department head to do something that is not dangerous or unreasonable.
   - 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.
 </Document>
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-1AnimalEscalation.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-1AnimalEscalation.xml
index 425af656c3ba..6ff7bb2c6371 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-1AnimalEscalation.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-1AnimalEscalation.xml
@@ -9,11 +9,29 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   # 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.
+  Each station has what's considered "Station pets" and non-pets.
+
+  Station pets usually have names and spawn every round in their respective departments, these pets are protected under Spacelaw and considered crew:
+
+  Some notable pets are:
+  - Hamlet
+  - Ian
+  - Renault
+  - Alexander
+  - McGriff
+  - Shiva
+  - Smile
+
+  Other animals on the station however, are not protected under the same rules, but may become an IC pet with the appropriate roleplay. They don't usually have a name and spawn randomly.
 
-  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.
+  This includes animals like:
 
-  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.
+  - Mice
+  - Monkeys
+  - Mothroaches
+  - Gorillas
+
+  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.
 
   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.
 
@@ -23,8 +41,6 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
   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.
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR4Metashield.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR4Metashield.xml
index 873857f5124b..bbef2baab4d4 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR4Metashield.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR4Metashield.xml
@@ -116,9 +116,9 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   - You are the Blueshield Officer (BSO)
   - A Central Command Official (Non-NTR/BSO) mentions Deathsquad as a [bold]Killsquad[/bold]
 
-  ## Implanted Implants
+  ## Implanted implants
 
-  Implanted implants are shielded.
+  Implanted, implants are shielded.
 
   Implanters themselves and un-implanted implants are not shielded. This prohibits implant checking.
 
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml
index cfc6f6d196ff..5f7a32bc44b0 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml
@@ -11,7 +11,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   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.
 
   ## Seasonal Exemptions
-  Self-antagonism is allowed if you get a DEBUG or ADMEME weapon from a Christmas tree during Goobmas. A chinalake, a python, etc. doesn't count. A gibstick does, for example.
+  Self-antagonism is allowed if you get a DEBUG or ADMEME weapon from a Christmas tree during Goobmas. A chinalake, a python, etc. doesn't count. A gibstick does, for example. Other exceptions you may ask the admin for, but if you doubt it's fine, then it's probably not.
 
   ## Examples
   These examples assume that you are not an antagonist.
@@ -22,9 +22,8 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   - 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.
+  - Low-effort or low-roleplay gatherings to disrupt the round (IC revolutions or cults that have no development or make no sense).
+  - Mutinying the captain because they didn't give you want you wanted.
   - Randomly smashing lots of station lights.
   - Disrupting station power.
   - Spacing parts of the station.
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR8NoFriendlyAntag.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR8NoFriendlyAntag.xml
index d4ef903ee7cc..a70cbcbaac40 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR8NoFriendlyAntag.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR8NoFriendlyAntag.xml
@@ -25,5 +25,8 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   - 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.
+  - Making or trying to make the station uninhabitable as a revolutionary.(Plasma flooding, loosing, mass destruction)
+
+  Grey area:
+  - Buying or providing syndicate gear to security during a nuclear operative round. Possibly acceptable if you have a "survive" objective.
 </Document>
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml
index 0037e6d545e0..ae71b5ec06cd 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml
@@ -19,20 +19,23 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   As an antagonist, do not make the Emergency Shuttle uninhabitable or otherwise cause excessive death, damage, or destruction to the Emergency Shuttle.
 
   ## Exemptions
-  The "die a glorious death" objective allows antagonists to ignore this rule entirely.
+  The "die a glorious death"(DAGD) objective allows antagonists to ignore this rule entirely. You can do practically anything you want with DAGD.
 
   ## 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.
   - Permanently round removing many people who have demonstrated a persistence and a capability to either kill you or interfere with the completion of your objectives.
+  - Causing massive station damage and chaos as an antagonist with the "die a glorious death" objective.
 
   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.
+
+  Grey area:
+  - Evacuation shuttle bombing. It is recommended you at least attempt to complete your objective on station before you consider evac bombing.
 </Document>
diff --git a/Resources/ServerInfo/Guidebook/ServerRules/SpaceLaw/SpaceLaw.xml b/Resources/ServerInfo/Guidebook/ServerRules/SpaceLaw/SpaceLaw.xml
index 4fc566111fbc..158517ba33d8 100644
--- a/Resources/ServerInfo/Guidebook/ServerRules/SpaceLaw/SpaceLaw.xml
+++ b/Resources/ServerInfo/Guidebook/ServerRules/SpaceLaw/SpaceLaw.xml
@@ -39,11 +39,12 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
   - [bold]Mind Shields[/bold]: Shields can be administered to any inmate who has been clearly mind controlled, lost control of themselves, or a suspect charged with unlawful control. Unlike standard implantation you may hold a prisoner until you finish issuing Mind Shields, so long as it's done in a timely fashion. If a suspect refuses cooperate or the implant fails to function they can be charged with Refusal of Mental Shielding.
 
-  - Usage of contraband implanters is a detainable offense, but it's not reasonable to detain someone solely for having an unidentified implant inside them.
-
-  ### Removal
+  ## Removal
   - A suspect can be forced to receive implant removal if there is strong reasonable proof that they have been implanted, such as an officer seeing them use one or their prints being on a discarded injector. Unlike implantation procedure a prisoner can have their sentence entirely delayed or extended until they comply with the procedure, as long as security are actively making attempts to preform it. Akin to implanting, if an inmate gives their clear permission, implant removal can proceed without proof.
 
+  ## Blood testing
+  - Blood testing is a procedure that can be used to determine if a person is a [textlink="Changeling" link="Changelings"]. Blood testing may only be forced when there has been confirmation of changelings existence on the station.
+
   ## Sentencing
   - All sentencing is to be handled by the Warden, if no Warden is available the HoS is to take over that duty, if there's no HoS it falls onto the highest ranking command member.
 
@@ -59,7 +60,12 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 
   # Execution
-  - [bold]All executions are to be confirmed and overseen by the Captain. A prisoner may request a specific execution method, if reasonable. Otherwise the most humane method is prefered. Refer to Standard Operating Procedure to further understand any guidelines applied to execution.[/bold]
+  - [bold]All executions are to be confirmed and overseen by the Captain. Exceptions to this rule exist. A prisoner may request a specific execution method, if reasonable. Otherwise the most humane method is prefered. Refer to Standard Operating Procedure to further understand any guidelines applied to execution.[/bold]
+
+  # Exceptions
+  - [bold]If a changeling is discovered they are kill on sight.[/bold]
+  - [bold]Any unauthorised magic use should be treated seriously and may be kill on sight[/bold]
+  - [bold]Any cases of weapons of mass destruction,extreme terrorism or clear intention to destroy the station are kill on sight[/bold]
 
   ## SOP guidelines
   - [textlink="Legal" link="Legal SOP"] refer to, for more in-depth guidelines.


Reviews:
user: login: deltanedas
state: COMMENTED
author_association: NONE
submitted_at: 2025-05-08T14:11:12Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 2**

<details>
<summary>🧹 Nitpick comments (19)</summary><blockquote>

<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6BanEvasion.xml (1)</summary><blockquote>

`12-12`: **HARK, USER!** To preserve the arcane uniformity of our link conjurations, consider transforming the raw URL into a [textlink] glyph. This will align with other scrolls in the Grimoire.  
Proposed incantation:
```diff
-Almost all bans may be appealed on our forums at https://forums.goobstation.com/ in the ban appeals section.
+Almost all bans may be appealed on our forums in the ban appeals section: [textlink="forums.goobstation.com" link="https://forums.goobstation.com/"].
```

</blockquote></details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml (1)</summary><blockquote>

`12-12`: **HARK! A NITPICK FOR THE SCRIBE.** The proclamation “Zero Tolerance(ZT)” lacks its terminal period. Add “.” to ensure grammatical completeness:
```diff
- These rules apply at all times, including between rounds. Zero Tolerance(ZT)
+ These rules apply at all times, including between rounds. Zero Tolerance(ZT).
```

</blockquote></details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml (1)</summary><blockquote>

`22-22`: **HARK! A NITPICK FOR THE SCRIBE.** The new example reads “you just shit yourself(fear)” but requires a space before the parenthesis. Correct thusly:
```diff
- Telling someone you just shit yourself(fear)
+ Telling someone you just shit yourself (fear)
```

</blockquote></details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12MinAge.xml (1)</summary><blockquote>

`12-12`: **Behold the missing article, mortal!** The phrase “act at least as mature as 16-year-old” requireth an “a” before “16-year-old” to read properly. Insert “a” to become “as mature as a 16-year-old.”

</blockquote></details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR8NoFriendlyAntag.xml (2)</summary><blockquote>

`28-29`: **Arcane spelling be corrected!** The word “loosing” in the parenthesis is wrong—it should be “losing.” Also add a space before the opening parenthesis and ensure a period at sentence end for clarity:
```diff
- - Making or trying to make the station uninhabitable as a revolutionary.(Plasma flooding, loosing, mass destruction)
+ - Making or trying to make the station uninhabitable as a revolutionary (plasma flooding, losing, mass destruction).
```

---

`30-31`: **Consistency in quotation marks, user!** The inner double quotes may vex the parser. Either escape them or switch to single quotes around “survive”:
```xml
- Buying or providing syndicate gear to security during a nuclear operative round. Possibly acceptable if you have a "survive" objective.
+ Buying or providing syndicate gear to security during a nuclear operative round. Possibly acceptable if you have a 'survive' objective.
```

</blockquote></details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml (2)</summary><blockquote>

`22-22`: **Methinks a dash is missing, mortal!** This exemption should be a bullet under “## Exemptions” for consistency. Prepend “- ” and add a space before “(DAGD)”:
```diff
-   The "die a glorious death"(DAGD) objective allows antagonists to ignore this rule entirely.
+ - The "die a glorious death" (DAGD) objective allows antagonists to ignore this rule entirely.
```

---

`39-40`: **Grey Area must be uniform!** Consider capitalizing “Area” in “Grey Area:” to match other rules, and ensure punctuation consistency at sentence end.

</blockquote></details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml (1)</summary><blockquote>

`14-14`: **Lo, the Goobmas exemption is wordy, mortal!** Consider tightening for clarity:
```diff
- Self-antagonism is allowed if you get a DEBUG or ADMEME weapon from a Christmas tree during Goobmas. A chinalake, a python, etc. doesn't count. A gibstick does, for example. Other exceptions you may ask the admin for, but if you doubt it's fine, then it's probably not.
+ Self-antagonism is allowed only with a DEBUG or ADMeme weapon from a Goobmas tree. Other exceptions require admin approval.
```

</blockquote></details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/SpaceLaw/SpaceLaw.xml (3)</summary><blockquote>

`47-49`: **Beware the missing apostrophe, mortal!** “changelings existence” lacks possessive form and an article. Proffer “a changeling’s existence” to clarify.

---

`65-65`: **Oft thy spelling errs!** “prefered” is missing an “r”: write “preferred.” Also consider hyphenating “kill-on-sight” for consistency.

---

`67-70`: **The exceptions require reforging!** The bullets read awkwardly and omit head revolutionaries from our lore. Fix grammar and confirm whether head revolutionaries or failed mental shield cases should be added per SpaceLawCrimeList. Example diff:
```diff
- # Exceptions
- - [bold]If a changeling is discovered they are kill on sight.[/bold]
- - [bold]Any unauthorised magic use should be treated seriously and may be kill on sight[/bold]
- - [bold]Any cases of weapons of mass destruction,extreme terrorism or clear intention to destroy the station are kill on sight[/bold]
+ ## Exceptions
+ - **If a changeling is discovered, they are to be killed on sight.**
+ - **Any unauthorised magic use may be treated as kill-on-sight.**
+ - **Any cases of weapons of mass destruction, extreme terrorism, or clear intent to destroy the station are kill-on-sight.**
+ - **Head revolutionaries are also kill-on-sight.**  <!-- Verify inclusion with SpaceLawCrimeList -->
```

</blockquote></details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR10Subordination.xml (2)</summary><blockquote>

`18-22`: **ARCANE SUBORDINATION EXAMPLES SHINE!**  
THE NEW ACCEPTABLE RUNES CLARIFY WHEN TRAITORS AND ENGINEERS MAY IGNORE THEIR LIEGE’S ORDERS!  
  
FOR UNIFORMITY AND READABILITY, CONSIDER BREAKING THE LONG ENGINEER EXAMPLE INTO TWO SENTENCES OR ABBREVIATING IT TO AVOID A RUN-ON INCANTATION.

---

`33-33`: **UNHOLY DOUBLE NEGATIVE DETECTED!**  
THE PROHIBITED EXAMPLE “…TO DO SOMETHING THAT IS NOT DANGEROUS OR UNREASONABLE” MAY BE CONFUSING TO MORTALS.  
  
REPHRASE AS “…TO DO SOMETHING THAT IS NEITHER DANGEROUS NOR UNREASONABLE” TO BANISH THE DOUBLE NEGATIVE.

</blockquote></details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-1AnimalEscalation.xml (3)</summary><blockquote>

`12-14`: **BEHOLD THE ANIMAL CLASSIFICATION ENCHANTMENT!**  
THE DISTINCTION BETWEEN “STATION PETS” AND NON-PETS IS NOW WRITTEN IN RUNES.  
  
FOR A SMOOTHER INCANTATION, CHANGE “Each station has what's considered 'Station pets' and non-pets.”  
TO “Each station categorizes animals as 'Station pets' or non-pets.'”

---

`16-24`: **ANIMAL ROSTER SUMMONED!**  
THE LIST OF NOTABLE PETS ADDS PRECISION TO THE SPELLBOOK.  
  
FOR MAINTAINABILITY, CONSIDER SORTING THIS LIST ALPHABETICALLY OR EXTRACTING IT INTO A SHARED RESOURCE TO AVOID DUPLICATION ACROSS THE TOME.

---

`25-34`: **NON-PETS, A FAERIE TALE OF CRUELTY AND ROLEPLAY!**  
THE NEW NON-PET SECTION DISTINGUISHES WILD FAUNA FROM SPOKEN CREW-PETS.  
  
BANISH THE COMMA SPLICE IN “Other animals on the station however, are not protected under the same rules, but may become an IC pet with the appropriate roleplay.”  
REWORK TO “Other animals on the station, however, are not protected under the same rules but may become IC pets with appropriate roleplay.”

</blockquote></details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml (2)</summary><blockquote>

`10-14`: **BULLET LIST TRANSFIGURATION COMPLETE!**  
THE CONVERSION TO RUNIC BULLETS CLARIFIES ADMIN COMMUNICATION.  
  
UNIFY THE FORMAT BY UPPERCASING THE HOTKEY: CHANGE “ahelp"(f1)” TO “ahelp (F1)”, AND REMOVE THE SUPERFLUOUS COMMA IN “Anything that is ahelped, then becomes…”.

---

`39-44`: **INAPPROPRIATE AHELP ABERRATIONS!**  
THE PROHIBITED BEHAVIORS ARE CLEAR, YET PUNCTUATION SORCERY NEEDS ALIGNMENT.  
  
ENSURE EACH BULLET ENDS CONSISTENTLY—ADD COMMAS OR SEMICOLONS WHERE NEEDED (E.G., “- lying,”) AND HARMONIZE THE FINAL CONJUNCTION.

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between edcdca924e195ff3359f9747ce4223f493809459 and dee3196c04bdce38d3acff9757730f47c014f746.

</details>

<details>
<summary>📒 Files selected for processing (13)</summary>

* `Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml` (1 hunks)
* `Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml` (1 hunks)
* `Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12MinAge.xml` (1 hunks)
* `Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC14ICinOOC.xml` (1 hunks)
* `Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml` (1 hunks)
* `Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6BanEvasion.xml` (1 hunks)
* `Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR10Subordination.xml` (2 hunks)
* `Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-1AnimalEscalation.xml` (1 hunks)
* `Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR4Metashield.xml` (1 hunks)
* `Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml` (2 hunks)
* `Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR8NoFriendlyAntag.xml` (1 hunks)
* `Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml` (1 hunks)
* `Resources/ServerInfo/Guidebook/ServerRules/SpaceLaw/SpaceLaw.xml` (2 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🧠 Learnings (1)</summary>

<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/SpaceLaw/SpaceLaw.xml (1)</summary>

```
Learnt from: Sarahon
PR: Goob-Station/Goob-Station#1483
File: Resources/ServerInfo/Guidebook/ServerRules/SpaceLaw/SLCrimeList.xml:1045-1045
Timestamp: 2025-01-19T01:38:54.629Z
Learning: In Space Law, while Captain's approval is generally required for executions, there are specific exceptions where approval is not needed:
1. Failed mental shielding cases
2. Head revolutionaries (Kill On Sight)
3. Changelings
These cases can proceed with expedited execution without Captain's oversight.
```

</details>

</details>

</details>

<details>
<summary>⏰ Context from checks skipped due to timeout of 90000ms (4)</summary>

* GitHub Check: build (ubuntu-latest)
* GitHub Check: YAML map schema validator
* GitHub Check: build (ubuntu-latest)
* GitHub Check: YAML Linter

</details>

<details>
<summary>🔇 Additional comments (9)</summary><blockquote>

<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC14ICinOOC.xml (1)</summary>

`10-10`: **HARK, MORTAL!** Thou hast appended “(Ick Ock)” to the decree, matching the pattern of other Core Rules. Thy change is consistent and may remain as-is.

</details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml (1)</summary>

`16-22`: **BY MY BEARD!** The marking of items 3, 4, 5, 6, 8, 9, and 12 with “(ZT)” is a masterful alignment with the root edict. This stylization cements their zero-tolerance status.

</details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml (1)</summary>

`30-30`: **WELL WROUGHT!** The refinement to forbid only “detailed or gross explanations of defecation” instead of all defecation emotes sharpens the rule’s focus.

</details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml (1)</summary>

`32-32`: **Well done, apprentice!** The example granting DAGD disciples the freedom of chaos is clear and fits the “Acceptable” list.

</details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/SpaceLaw/SpaceLaw.xml (1)</summary>

`43-43`: **Thou hast leveled the heading correctly!** The promotion to “## Removal” aligns with other sections. Well met.

</details>
<details>
<summary>Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml (4)</summary>

`17-17`: **AHELPS EMBRACED BY ALL WHO SEEK LIGHT!**  
THE INVITATION “All ahelps are welcome” SHINES WITH TRUE SORCERY.

---

`20-23`: **WEAVER OF AHELP CONTENT CLARITY!**  
THE BULLETS DEPICT PRECISELY WHAT MORTALS MUST INCLUDE.

---

`25-25`: **NO APPREHENSION IN LOGS ARCANA!**  
THE REASSURANCE THAT ADMINS CAN CHECK LOGS EASES PLAYER FEARS.

---

`35-35`: **BWOINK SPELL CAST IN APPROPRIATE EXAMPLES!**  
THE THEMATIC “Bwoink.” ENRICHES THE LIST’S ATMOSPHERE.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-08T15:06:39Z
user: login: SX-7
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-10T20:09:35Z
user: login: gluesniffler
body: leaving blanket approval so SX can merge whenever he feels like it
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-25T00:39:27Z
user: login: SX-7
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-25T06:15:13Z

Review comments:
diff_hunk: @@ -9,20 +9,20 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 <Document>
   # Core Rules
-  These rules apply at all times, including between rounds.
+  These rules apply at all times, including between rounds. Zero Tolerance(ZT)
 
   - [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="3. No Hate Speech or Discriminatory Language(ZT)" link="RuleC3"]
+  - [textlink="4. No sexual, adult or shock content(ZT)" link="RuleC4"]
path: Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml
user: login: deltanedas
body: no alcohol allowed :(
created_at: 2025-05-08T14:11:12Z
author_association: NONE
diff_hunk: @@ -116,9 +116,9 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   - You are the Blueshield Officer (BSO)
   - A Central Command Official (Non-NTR/BSO) mentions Deathsquad as a [bold]Killsquad[/bold]
 
-  ## Implanted Implants
+  ## Implanted implants
 
-  Implanted implants are shielded.
+  Implanted, implants are shielded.
 
path: Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR4Metashield.xml
user: login: coderabbitai[bot]
body: _🛠️ Refactor suggestion_

**HARK! ESSENTIAL REFACTOR REQUESTED.** The heading and first sentence bear awkward casing and punctuation. Let the spell read smoothly:
```diff
- ## Implanted implants
+ ## Implanted Implants

- Implanted, implants are shielded.
+ Implanted implants are shielded.
```  
This restores title‐case consistency with other shields and corrects the stray comma. 


<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
  ## Implanted Implants

  Implanted implants are shielded.
`````

</details>

<!-- suggestion_end -->

<details>
<summary>🤖 Prompt for AI Agents (early access)</summary>

```
In Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR4Metashield.xml
around lines 119 to 122, the heading "Implanted implants" and the sentence
"Implanted, implants are shielded." have awkward casing and an unnecessary
comma. Change the heading to title case consistent with other shields, such as
"Implanted Implants," and remove the comma in the sentence to read smoothly as
"Implanted implants are shielded."
```

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-08T15:06:38Z
author_association: CONTRIBUTOR
diff_hunk: @@ -22,9 +22,8 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   - 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.
+  - Low effort or low roleplay gatherings to disrupt the round.(IC revolution or cults that had no development or make no sense)
+  - Mutinying the captain because they didn't give you want you wanted.
path: Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml
user: login: coderabbitai[bot]
body: _⚠️ Potential issue_

**Your grammar betrays you!** The prohibition reads “make no sense” but the subject “gatherings” requires “makes.” Also insert a space before the parenthesis. Apply this diff:
```diff
- - Low effort or low roleplay gatherings to disrupt the round.(IC revolution or cults that had no development or make no sense)
+ - Low-effort or low-roleplay gatherings to disrupt the round (IC revolutions or cults that have no development or make no sense).
``` 



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
  - Low-effort or low-roleplay gatherings to disrupt the round (IC revolutions or cults that have no development or make no sense).
  - Mutinying the captain because they didn't give you want you wanted.
`````

</details>

<!-- suggestion_end -->

<details>
<summary>🤖 Prompt for AI Agents (early access)</summary>

```
In Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml
around lines 25 to 26, fix the grammar by changing "make no sense" to "makes no
sense" to agree with the singular subject "gatherings." Also, insert a space
before the opening parenthesis to improve readability.
```

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-08T15:06:39Z
author_association: CONTRIBUTOR
diff_hunk: @@ -9,20 +9,20 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 <Document>
   # Core Rules
-  These rules apply at all times, including between rounds.
+  These rules apply at all times, including between rounds. Zero Tolerance(ZT)
path: Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml
user: login: SX-7
body: Explain what zero tolerance exactly means
created_at: 2025-05-10T19:55:45Z
author_association: CONTRIBUTOR
diff_hunk: @@ -9,20 +9,20 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 <Document>
   # Core Rules
-  These rules apply at all times, including between rounds.
+  These rules apply at all times, including between rounds. Zero Tolerance(ZT)
 
   - [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="3. No Hate Speech or Discriminatory Language(ZT)" link="RuleC3"]
+  - [textlink="4. No sexual or shock content(ZT)" link="RuleC4"]
path: Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml
user: login: SX-7
body: Especially in case of these, it can be somewhat up to the admin how close a player steps to the line of it being such content. Either un-ZT, or explain ZT more - perhaps repeat/point to rule 1.
created_at: 2025-05-10T19:57:39Z
author_association: CONTRIBUTOR
diff_hunk: @@ -7,30 +7,36 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 <Document>
   # 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.
path: Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml
user: login: SX-7
body: loss of info: no info that it's relayed to discord, no info not to admincheck, or ahelp etiquette in general
I feel like some acknowledgement of IC admin methods of messaging is important, not every player might know that such things can be used to contact admins
created_at: 2025-05-10T19:59:51Z
author_association: CONTRIBUTOR
diff_hunk: @@ -7,30 +7,36 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 <Document>
   # 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.
+  - Admin help, or "ahelp"(f1), is the system used by admins to communicate with specific players in the game.
+  - Anything that is ahelped, then becomes an admin involved issue.
+  - When being ahelped, you're expected to respond to the admin. Leaving after you have been ahelped may result in a ban.
+  - Admins like you are also human, we can't be everywhere at once, we are not omniscient, and we are not perfect. We are here to help you, so please be respectful.
+  - Bwoink.
 
   ## 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.
+  All ahelps are welcome. Even if you believe it's for something silly, a false-positive is better than not reporting it. If you are unsure if something is ahelpable, you can always ask in the ahelp or Discord.
path: Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml
user: login: SX-7
body: I'd love a sentence or two more that encourages players to ahelp more. Old version had more of that, so maybe that?
created_at: 2025-05-10T20:01:20Z
author_association: CONTRIBUTOR
diff_hunk: @@ -7,30 +7,36 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 <Document>
   # 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.
+  - Admin help, or "ahelp"(f1), is the system used by admins to communicate with specific players in the game.
+  - Anything that is ahelped, then becomes an admin involved issue.
+  - When being ahelped, you're expected to respond to the admin. Leaving after you have been ahelped may result in a ban.
+  - Admins like you are also human, we can't be everywhere at once, we are not omniscient, and we are not perfect. We are here to help you, so please be respectful.
+  - Bwoink.
 
   ## 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.
path: Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10AHelp.xml
user: login: SX-7
body: this feels missing
created_at: 2025-05-10T20:01:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -19,12 +19,13 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   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.
+  - Telling someone you just shit yourself(fear)
path: Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4NoERP.xml
user: login: SX-7
body: ```suggestion
  - Telling someone you just shit yourself out of fear
```
idk not english native, but parentheses look weird
created_at: 2025-05-10T20:02:58Z
author_association: CONTRIBUTOR
diff_hunk: @@ -9,11 +9,29 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   # 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.
+  Each station has what's considered "Station pets" and non-pets.
+
+  Station pets usually have names and spawn every round in their respective departments, these pets are protected under Spacelaw and considered crew:
+
+  Some notable pets are:
+  - Hamlet
+  - Ian
+  - Renault
+  - Alexander
+  - McGriff
+  - Shiva
+  - Smile
path: Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR11-1AnimalEscalation.xml
user: login: SX-7
body: Add pun-pun, or mention it as such, as I believe it's the most important example. 
Alternatively, acknowledge it in another section due to it being a ghostrole
created_at: 2025-05-10T20:05:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -19,20 +19,23 @@ SPDX-License-Identifier: AGPL-3.0-or-later
   As an antagonist, do not make the Emergency Shuttle uninhabitable or otherwise cause excessive death, damage, or destruction to the Emergency Shuttle.
 
   ## Exemptions
-  The "die a glorious death" objective allows antagonists to ignore this rule entirely.
+  The "die a glorious death"(DAGD) objective allows antagonists to ignore this rule entirely. You can do practically anything you want with DAGD.
 
   ## 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.
   - Permanently round removing many people who have demonstrated a persistence and a capability to either kill you or interfere with the completion of your objectives.
+  - Causing massive station damage and chaos as an antagonist with the "die a glorious death" objective.
 
   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.
+
+  Grey area:
+  - Evacuation shuttle bombing. It is recommended you at least attempt to complete your objective on station before you consider evac bombing.
path: Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR9MassSabotage.xml
user: login: SX-7
body: FYI, next upstream which I hope will be finished within a day or few, will make most "kill" objectives "kill and maroon" objectives, which *should* make it way more clear
created_at: 2025-05-10T20:07:32Z
author_association: CONTRIBUTOR
path: Resources/ServerInfo/Guidebook/ServerRules/SpaceLaw/SpaceLaw.xml
user: login: SX-7
body: another implant-related thing, all implants will be named (`storage implant implanter` instead of `syndicate implanter`) IC in the next upstream, just mentioning it cuz it was talked about in the context of IC implant knowledge
created_at: 2025-05-10T20:09:20Z
author_association: CONTRIBUTOR

PR comments:
user: login: pheenty
created_at: 2025-04-22T05:45:33Z
body: Same rules, other wording, I don't see much difference 
author_association: CONTRIBUTOR
user: login: Sarahon
created_at: 2025-04-22T06:53:54Z
body: > Same rules, other wording, I don't see much difference

Crazy how you completely miss the point of "want input" - things need to be added, removed and edited. It's not all the same words.
author_association: CONTRIBUTOR
user: login: pheenty
created_at: 2025-04-22T07:14:32Z
body: > > Same rules, other wording, I don't see much difference
> 
> Crazy how you completely miss the point of "want input" - things need to be added, removed and edited. It's not all the same words.

Oh nevermind I've read it as feedback
author_association: CONTRIBUTOR
user: login: pheenty
created_at: 2025-04-22T07:16:43Z
body: Well one thing I can propose is getting rid of implants metashield, how wizden handles it. I discussed it with sx-7 already and it makes no sense for them to be metashielded with how they work now, though that requires bringing back their wizden damage too
author_association: CONTRIBUTOR
user: login: OnsenCapy
created_at: 2025-04-22T16:39:41Z
body: For all that is holy I beg of thee, put in that heretics are KOS and can be executed without captain permission, and similar for wizard.
author_association: CONTRIBUTOR
user: login: yahay505
created_at: 2025-04-23T15:04:07Z
body: I would like to see death amnesia added, ahelpable if violated to reduced the amount of gibbing, stealing brain or dead and left to rot in maints/unpowered disposals units situations. I dont think many people like being forced to wait as a ghost because they were in the wrong place at the wrong time. It will also make antags life easier as they can just kill and revive to remove evidence.

Also I think "8. Do not exploit the game, use cheats, or macros(ZT)" should not be zero tolerance. It would include generally permissible things like atmos subframes, med reviving hollow corpses, chat macros for emotes and stuff. What is a feature and what is exploit is not very black and white and there should be nuance.
author_association: CONTRIBUTOR
user: login: pheenty
created_at: 2025-04-23T15:21:31Z
body: > I would like to see death amnesia added, ahelpable if violated to reduced the amount of gibbing, stealing brain or dead and left to rot in maints/unpowered disposals units situations. I dont think many people like being forced to wait as a ghost because they were in the wrong place at the wrong time. It will also make antags life easier as they can just kill and revive to remove evidence.

Massive admin workload for no real reason. And come on, this is just a game, sometimes you just die and it's fine. Imo this would make the game only more awful to play

> Also I think "8. Do not exploit the game, use cheats, or macros(ZT)" should not be zero tolerance. It would include generally permissible things like atmos subframes, med reviving hollow corpses, chat macros for emotes and stuff. What is a feature and what is exploit is not very black and white and there should be nuance.

Atmos subframes is legit a feature, it's literally explicitly defined in the code and even commented if i'm not mistaken.
Reviving hollow corpses is also intended
Macros for emotes don't give you any advantage so it's also fine. Use common sense.
author_association: CONTRIBUTOR
user: login: GoobBot
created_at: 2025-05-04T16:38:26Z
body: This pull request has conflicts, please resolve those before we can evaluate the pull request.
author_association: MEMBER
user: login: coderabbitai[bot]
created_at: 2025-05-08T15:06:30Z
body: <!-- This is an auto-generated comment: summarize by coderabbit.ai -->
<!-- walkthrough_start -->

## Walkthrough

BEHOLD! The sacred tomes of the ServerInfo Guidebook have been meticulously updated by the arcane scribes. Core Rules now brandish the "Zero Tolerance (ZT)" sigil upon chosen edicts, whilst the minimum age decree hath shifted focus from mere years to the maturity of a 16-year-old soul. The mystical "ahelp" scroll has been reformed into a bulleted incantation, adorned with the reverberating chant of "Bwoink." Roleplay laws now boast refined examples and clarifications concerning subordination, animal escalation, self-antagonism, friendly antagonism, and mass sabotage. The venerable SpaceLaw codex hath gained new rites for blood testing and exceptions to execution protocols for dire threats. Thus, the laws stand clearer, more structured, and enchanted with newfound detail!

## Sequence Diagram(s)

```mermaid
sequenceDiagram
    participant Player
    participant Admin
    participant Rulebook

    Player->>Rulebook: Consults rules (Core, Roleplay, SpaceLaw)
    Note right of Rulebook: Updated rules with ZT, clarified examples, new exceptions
    Player->>Admin: Sends ahelp (now with clear instructions and Bwoink)
    Admin->>Player: Responds, expects reply (ban if ignored)
    Player->>Rulebook: Checks animal, subordination, self-antag, sabotage rules
    Rulebook-->>Player: Provides explicit guidance and examples
    Admin->>Rulebook: Enforces rules, applies exceptions (e.g., execution, blood testing)
```

```mermaid
sequenceDiagram
    participant Security
    participant Captain
    participant Rulebook

    Security->>Rulebook: Consults SpaceLaw for execution procedure
    Rulebook-->>Security: Provides standard procedure and new exceptions
    Security->>Captain: Requests confirmation for execution
    alt Exception applies (e.g., changeling, WMD, extreme terrorism)
        Security->>Rulebook: Checks exceptions
        Rulebook-->>Security: Permits kill-on-sight
    else No exception
        Captain->>Security: Oversees execution as per law
    end
```

```mermaid
sequenceDiagram
    participant Player
    participant Rulebook

    Player->>Rulebook: Reads animal escalation rule
    Rulebook-->>Player: Distinguishes station pets vs. non-pets, lists notable pets
    Player->>Rulebook: Checks if escalation applies
    Rulebook-->>Player: Provides explicit pet/non-pet guidance
```

THUS, THE FLOW OF LAW AND ORDER HATH BEEN ENCHANTED WITH NEW CLARITY AND STRUCTURE, O USER OF THE CODE!

<!-- walkthrough_end -->

<!-- announcements_start -->

> [!TIP]
> <details>
> <summary>⚡️ Faster reviews with caching</summary>
> 
> - CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure `Review - Disable Cache` at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the `Data Retention` setting under your Organization Settings.
> 
> Enjoy the performance boost—your workflow just got faster.
> 
> </details>

<!-- announcements_end -->

---

<details>
<summary>📜 Recent review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between dee3196c04bdce38d3acff9757730f47c014f746 and d099f092d3bda5d049dde8b736e548e6a12f2c53.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml` (2 hunks)

</details>

<details>
<summary>🚧 Files skipped from review as they are similar to previous changes (1)</summary>

* Resources/ServerInfo/Guidebook/ServerRules/RoleplayRules/RuleR6SelfAntag.xml

</details>

<details>
<summary>⏰ Context from checks skipped due to timeout of 90000ms (1)</summary>

* GitHub Check: Label

</details>

</details>
<!-- internal state start -->


<!-- DwQgtGAEAqAWCWBnSTIEMB26CuAXA9mAOYCmGJATmriQCaQDG+Ats2bgFyQAOFk+AIwBWJBrngA3EsgEBPRvlqU0AgfFwA6NPEgQAfACgjoCEYDEZyAAUASpETZWaCrKNwSPbABsvkCiQBHbGlcSHFcLzpIACIbAFUAGQBRAGVIOKsAEQBBaFSACgBJADkrOOhIAHVs4rzMgEpoyAB3NGQHAWZ1Gno5SGxESkgU5zRYfCwCMNgPAHF8QTAU3Gp4Cb8SbnxEdXwXSHzbSDMAJgAWAE4ARnqNGBnrOyVEBgp4bnF1+AwGL2xn+wrDC0Zz0FJZAAaCm4sjeRFgoUw9C88AYZEGkBmaCUFGQSJ4XjQaPGXhxyAAZnt7KJPhh2tgGLB0MhotkBPg8NMPLYADRNaKVWDyAD0kAAQmhCT8SHz0MCYgBhWCYUhefBEWUCTm0fDSSAYfChXj4CTwJSQJQreCRejfSkUZirdZUxDcUTwcmoxjKjCkRB3dyA6hRbjYChbDGoKZuij25joPzePW/EiYbDcOX0dMgmj2bhEjyE5o8lrqJlob0qkhqoiQdj7A3iX0xGxJ5ApzD9bh3FL5tGQItdnPSDRNQNHVC8aTsKJtBP+IIhSD2hSsbAYdTyb6h0LrY0RqLZ4PIKa4B5ENBsRORRAl760VGrZtn6joWgP2m3jbME2Sr/4uh1DxfwUAwGhgToEszw5eF9XwBQfn8XMKCTSAfwfT0GCdOl+D4JhzUZKtgI8S1tBtUCuXsbBOiQHYJg0cxLAVFg2DA+knBcNwHgfF4BjorB1jPbk7G+CR8C8KR2hIKQqF8Jg1w3XB5DYZgBEoZBjVNB9m3JEg6AEIkAGtMyoog/U/DYLwobTayEngKHwA96BQm8h2DEtnm4dQPDswkGGM/ByQtEgrXIpgwPYCi7InXBBi8ckGIMKAACpku4GZ2FkVLQPUeBJS8eR/EdChDJPZVQjs/dtiiQjfT1NBuDdZwwngtTKMQS8PBcvVmjLC0PV0/wwJaPYbJLEgAA8p0QHZm0QQzNnEBgkHjFQOQqh4diIDdMMwftAsoo8aESlLkpGKhxgwbLfmcD14D1F8NuElBkG+cClHoKZEHE1F1FAncTMeyjuuQBdsHgEDsQ/NY6RLIrfy8f95UA2KS0bNDKGrQqSGaUbviIE7IFS9K9LArLkvQfyDWaG0/UoroHAg3EgTGzE0FNZtvly/LsexSijjnCswaXFddP0oy/GoGY+BfLAKywnxlxdajECBcQpH+vBCeJjKyeyqrBlBkgfw52yHmieBmG4KVYoxlZEAQataCabq4ZIQayGW5txmaSjol6gAvJQMCaQYKBktngVcy3rcwWKAxmZT2Bh/reJm/HplQXqzzlQ1pf6MODkQCawAAdnqEznCIYJplfOyGDDIbQjYe3HdJINcAGJW+Bjm3Xtenx1UfXwiEkMguQhjHatRL9oOwWCzyzjl2/INF05WZCSDehzaAZDPA+DsBVdkSILUvNBSBalArb77XkoAeTpMgFQa8nAQc30Co2RdVbKuuHhBnWKaKJloRHkKrYMtdQjSxCjPdAIFwo7BxFEaIABpe+KQmj5EMtaXw6wtoIgrviLCWA2qTVEHgKI2dxiciwh8bQWAYwM34iWahCYdhdEJHwbq6BGoFQzlMQOoJ/RGFOrIMYaBZAAFYAAMUjsoODMiEPE74M5C1QmtTk0QlBS3QMwcgOw0CymaAgRkI1vC9A8ELTYewVgCFPoFXST8UBBVNOJYMtAE6oB4doZgJ54L+F3v2HYndsLIBMZjAkkj1LwI8KPVQkE2YayEpPAQVBvjtAIJEDAJYqTOELO7UIOjbRYEdG9Mge0PBUnXFsZomN6A8QjJKfoikvz2i9mbY2V9Wh/TnPCbY8d7geHKcNKM8FHQLUoheK8P4QL2lHqbQG8E2g7FVnKFYRAJhIFtn0fK+BerPhmPGKYODFb4n8KaDWpoxCW38d+E0HhpJmk9iQO42RVG0h5lBBAyABhDCrsEP+T1rweGiJkeC6NJrW3wH9Oy0yZQFw8IyVMqNcJoSJA5ZA+QABa0BGj2BoSvQ0kA2oB0oPBLJyhpQktEGgP5KBQhMAsXWH4LB8wzQHCQUe4hHS5nhbHeQulqBhj1A4MxgtcA/ldNLL0HRyRUDYF+NgD4FYbEuRnA6JI1S+yYOGQ2JZiHlXRa8bY3c6w/hoP6IZ8gFa+BXBgbAlSKI8SbNXJACBmxqVwHU8eUK1RARMiMj6y4UUipEUlImaVdZKWuhyCKuJKI6JzpeAxeVTLmRTn0CBrqGXmPbq8FFVj0Xpw1tiLoG5VZUHVh4XGJU1R82oetDGmB8bkm8DS8gnpETyiBrQWQGdUAVgNA6Zp+YKC7iCnCzqQCYz3WlHcGwXLQQCIeGShyLVIhUGpTw9YfqYWopJplRgXC7oPSNdQKVJM3gMCogIeVnViJylAuBT5drQ0gT9b9MBwVPTkBKZRfCCKLmSAzlq/ZCg9V6lQEGqI/LCSyANcjC1HhHQmuQDqOCjKJiDSfdiCQccL6vOtW+MSWFcwrnkj+LAgxnHfBZe0427A77zEEGKQ02VGxnv/h4UMithZrOVO2bDIDbZA2YAMUIbV/DfQklENS9pHn4b+NhRgnZjRojoIle+Ml8rfKRSxdgRtySRDEAmSj65NypwbundYlJrNRHWDdN45J+2HOGRFYaB1oo2A8iQAyObXTukwiCysdUjaEh6FfAVQxwpBO7fQeFU8fQz0Q/QY26U2jwADiujw5AogUciM4caGAGMqEiKlklkpKnOTbCdMAhgDAmCgGQegB06UEGIGQZQkXKPsC4LwfgwgaRjxkDaxQyhVDqC0DofQjXwBQDgNBvEcs8CEFIOQKtNUDNgS4FQX2DgOLyD6IBqgk3NDaF0PVowc3TAGEXd9MMa9hQpEoDJQoJX8DClmODJQ7J8CGWe69ygrYbzCmYv4EH0hhSQ4VDIjQE1mBeA4AYaIqODAWEgNkQonWNseKood/gQVap+i4iRfADdWK4AAOSvTAjvBkBB9jZsY8NVovzuDDk+vBb4vx/g+QeOlKgGJojYvJTAcSVK0Q4rxU0NA5IaB8EbCu7jEGuptl4dbeQr58phEttIO8Pw/g2Rpd60mfg420CtS9nTvhAvLWC4A/IABmEsZwSxSJLAANhLAADhLBcCrVwTgVzqSBdCp7eha8ai1jO0Rpf4tPDMSezxXjvE/ONYBX6v7FRwW5jEgC5xropRLrd+1yROMNgnLqS4vMAPV/iFJfAUQYFKt+BhLTieaeu+jyw2QvAK7CVfOySgnOD4OlC2xDm+ChnsV6ZO4hpBGGKBMV5KO0dJVu/djkFAnsvfDpQd7lIvs/b8wsAHe+ZKQ8QGDvYJAr/Q6TAqK4MjsgAAlqzdgR0jtf0Qe+Y+x+tt1lEAdsVPIAdJ3ogKThaOTo4JFGzhsJWgziKvQPKiwAmMaBiHGK+G9MsiSt4JEJFiiGssfKfAVrdEpCZOloJkgFXjOlKCpgdNEGMB/k0PAVCkiFEFMJ+qAl/MzlAnKFrjMF4G6LaDNDXGpPJPVHLLQOWmAKJOJFIPQLygroDEatFgmvkjOjSJwQEtIFsD2ssjIRkhaGGGonLEIdwKwn1IVoslsC+nlD4NjA4P3gOnLJVhgLQQQOQC0HON9PLl1pHm+MbtYuWjiPwWWsYZobAI4J2OcoEICjmtJm6GILQYLm0KCmKLjN8IZKwYLO+FEOJi4dbD5HrniHiICCfNsl6FSEJLynPpEJTolIGG6iCNSusBEpMMshYT4e0L3BHlfJ7NvoRugHxjYuOl+DzkbiutVPwV0PCKEIMF0rgG8KaJKBVlMG0MZB6C0g4P4G7CbDlvZE8hyOhiFGRFEFWjDJKFYuyJyBEZMHrpXGBBfFsmssiv5OGoGIMDcs6FgCYnXNzobnzhRLEd0fAeFDJJFjgQmFqD4CFFEEQQsckR6K5rWIRFQGIEMBgA+iWB2D3GISRNIKnh8DDEjPQFDLlBMM0hYW2r4HaHsHURMFYTnP4CsmGE6kDPce2J2DJCicFKFMgKsQOOqOGkkBNJeMUcgG1o1A5LwHlLmPiN8A1PuG8JAswcIYiuEpEv4FgbgFCWBPBIiV+GwnZBSbSITjEPwr6LLstqBMqbKaqbmPSg3g8BkpQOaYwZkTCi3k0FSNEF6dkXQDaRsE1JFrUasDetWCzoMoGMaAgGoB6dIeWt6KILnrWOCSep6DoaBLzuaDRsboqh1HTI2pyLRDXPSSOrSFpjbl4HpqFnTHZl3I5oVv4BQCWLMiRBDDSKBIgT8ThPiBWPKnOrQCiEMF4Qimwv4KGYeBiJ6VkT6cyOwkpIiV6DnpQIlIxJjv3t1qSUPtxKIFwmPkFBPuOlPp4LPpGWBLlIvhGsvvWQ9PBCeZFlSDPiAiyuEPdIgFTsFKPhZKHihtiCQAANyJoDT8AYDZ6KCnplT6YeYToJg6gU7sAqYQgACyCQy41oq+qOv+G+YARgW+j2UOF+B+H2x+zyf25+QOFA9+4Od+bYD+kQT+JwqF3w2QpA8OiOyOOFf+WOOOQB9AIBzgYBROPoJOBggYNAE0oQ8B4eWZXO9yySDw3Bf0zOlOMQfevg6hyA4maybUr4hWayVwnukAsgqYCa4kniY4ACxsDCGcNG4E/Y8BU5sAQu2ZfBnJis2laEEmlMiIoQhliIOlwqkM5RxlYAZlzgYAllzJTI0Qxlpl5l/ApITQneCl8VnuEV5l0VKVZqRACqdRqquq/gYgBiVqgYPitxiIRhOEBkGAG4zY3lRIOaN4wVncIEssCY4VkVFAOVtAbsVkI50gUpQUzVjqvghG+xDCvyPwYlmmQy/ANZzaDVtY1MSs9m7QEuX86wvKphFBVa+cnV7Iyal8+Iu1bwSkG5vF25lxEwdyw+B5owFk4+U0k+rW0+1Eb58+n5S+K+P+oim+0g2+u+1Fh+n232FFZ+gO++NFDFdF9+MOVwZwhQCo3w9898ConF3+PFGOfFgBm2gljgoBFpEBUBnebklqlE4QDiQUdFkAkOkASNJKUebowIhxaRwuRQ/kkA98/kCeFKylE0VRzYKebwJJ9EC10m8F9cEwL6BuuZhxfqmAKmAE4pN8+ubexh64aVV1uNN1g+iehJv5u5L1Wwp57155X1V5C+kBt58EEBAxr15taKr5c+1tn5IFEwX88s22uAwo1NPkk0zcUFu05pGSzylEaFGFiFsBYEDEPFeFBFQNRF1+JFFAYN5Fv2UNadtFt+CNj+Zwy+SQNgVgWN3FaOuNABXWBN+OxN4Bc1ttgYR0Vi74tpk0Epp8htIx2qCJ2yx6t0LmyuFU1YzetY30bAK+MQsgHIkAQgvlDsf009YYcU5IwZnYUK0m/EFpQq+JPAlAXQep817y0MVJjhdZcZ8ACZKcu6FqGcSgukZG193C1YeOzV/cGwv67lyJu0jh3cagrWEF8gpEWFFt+V2wyASt2Jz1QUYq5YYgX4B1Y5Po3d5qhoGqQU99tKVZ9wqA5N2JFADkzQMF9gTAboFpdkUt16iZP6WDMMYA/gEWUQxshoI43eetA+FkXdI+h50DM6b1Ltn1btH5N5y+5A/1idd2ydO+xFoNZFENWd/20Nl+cNedDFMOnuEoGASQ+G/EZd/1ld/FNdQl+w9dREUBcQNgGFK4dk9ojgLQMC7hGuqYiMqmpCAF5o4Jc1KBDk8Y0QtjzAGgM0SNGgawTQUw0QCIuA3AiAHAwowo/j/omygg2aMMGg8kwo0QtBtaxu/gg1hxypzj9k5Ow1PR9gKI8xX8LlblKBVI4Uy0NGw1uJYlse2xf00G2JMpjkjpCKkx/wA6QUbTOl2yaAC0gDGuo5zsV8FsAzHTKp8pPTQJBZwzoz7h/oTQd5ecMWstkUVIgC/5IxCuXe127DO5d1e5RtPDJtx5Ttz5H1F57515ttojJA4jEA+FkjD20jqdsjR+8jp+ijOdajEuAq+dkQNgz+KQ1EeMUDqTX+5dv+Bj+NeOxjIl95jdDwDtzdQCHdUGkwACwL8GIWuTy6c0UL1kSp5pUwhWZItBrIDAaI9C9iJATQ7d6tyAa1vT5onJcszxmyFazckiKA20t+uEZIy4PjlEWIrWk6SefA+yWASgY6kq7AbsscHSlEU4biXcrLxR9jkSsRvLrxoQ8Awr0morMSqBxyGLDUVoHhkArFw6I05LzYxVw2Zz+zjoXL8E0QgwoQ6YWC3q8E2TiAFcGSNAfMjBvr/rBwk92TobWAOr0cGAYkEkGcZAo8eWGhPam0+M3g5BsgqRrl6RMQJixekACyKGgEqqyxKK6lUwnozMuRQmBD2h6Vpbxy8EFbGMKqzSNbF6kU9bEMqsTQdGw+5OjO2L6tbyHyVxZ9CY5AvsF9CZTDatur8BUMwBG8Q9CFmwzgyrw0BavsKkakz9bas0tYnYo0QwlrE8fAire76lUrV8GG49IUHqZs2B7LxKrRpADkTZfA64rJ302JTLL0mG3d+y817gGIDtOp3w/OSKJ6FB+ILwjkVSo19Li0ZWVi8oS73kliyobiCaxLzrtYlIg8BytYV7Ca1CdG9746lOy25Jhr/LYQqYfiutve+tnDAtFzT1VzfDztL5gjl5wjTzK+8d6+bzSdnzINMNGdfzlFSjwOQLkQILajSY4LVwYAVw2QG4joXgSQLwVWVZcL+jveVduOkWKLJNDdUBPCUlMlc47BEEClKl36Lqub7qJuPqWA0QywKmbosUsu8oBoGAYAQXUpeLHgKTEtAX5pkXsSP68H5J7LnUzHlsf4/BroaAzQCbMkhUFuFEdud0N69H+7qKmhxoNAmJWYTMwwfYL9xYJkiCzygSjA/gzQIFFYiJFpjY2He9ts67+R9A+Qr+l4BBJYhQmAJYi62J3guAJYfe7dTMJYqFDAswzm5IJYKQCA+GO3nCJAtwkAojEXIUj6otl9s4M12JyqcomXLjQMOXeXkswILA3t8omh6M1XrbLSYRdkHUV4gCWoArR2ogLAHgKNg3ZUf7sEDkan8GdwYpOLI1cE4XiX+zG7o3XQaI7ZEwC0sgSqecDkRIMwX4mybwPgbQx3gYewJrSptuG80Z/BYXZ3tsKIkyOPOHSh+PJAhPrjNK4rekX8py5EbCmA8gUPQH7Rc4Jss48o5S+VeO0Ji87LOM/d6codqTC1mrawXclO19QUiXYMEMabxnEWKcUwbUovVCc48MihJkU5fkcm8gdkC778SB7XkD2EqRowSv6U6AVVHX6v2IjkOarPiX5yBLkiaiCEq8lL8Ec9qsfJRJJnKc8BSgBBTDV5DDBbktNeMrjy5vKmBeyMq7rkRU7e2tXjnHW5HDu5XDj1t1OEpt/Dwn9z31N5UAd5DtXBNzZ5rtonjzaKje9gJrUDYaLQkSnr7mmc6GA0knuF0nHzwNMj8ncjJ+SngLoONg0fsgoLd+ZwqFZxC9TsejONFnhjyLRNwltnZjElGLc1aEIdn5krqYwR2bHgDbxBM4bRhfMQhQG+HHCiCADY4bEUOG61IRa4bqGcOhOoElBZYVauHbWqEmwaBgpWsAhuuKzQLRBQBNsEAUAPAFTM8BwA20IQOC4HAe6O+YthbHIGIBogNPTaL/37C4DyBUQXuHHEfSn9SQmmEdu2C8bEC2B/Va+GANtiaFuBH0UcKWBzh2Q3S46Q3mZhYgVg5cKhVgaIN4End4ImzPCFgKpZDwGAuJWWvD2XDapckfASgA5D4A+gRyGqelmGFr5956+ZzRvsbTOat8hOdzK2mJ1+piME6y/Qil82U7p0N+kNAFtRQRp78D+NgT3C9nih6cNk5/CupfyRbWcb+JjUSvfy+KphgOzSchFbHNI3R6UK4FemAAIx8sVoJhN4M2BYydA5wbBKaBwQUqct+cr4byo6Gxg/xdwQkcwRNAZYWQb2XJWKmZnayW8jU2xdcLsR6bGtkAHPLGOBz2R1JPEC1XrgdDw6RZE2PUO3k8kGCBF7eabTPKAlWbgUYgECeQc2HlgLcQu9AH1isDOEXs1U4kPADDCuEhk/IOWeMOLxJQk8wiaw6+n521RgB3Y9oXcE3n2T0M9+5bKWJQHxh3IeIKED4MDAtyygSuP9L+ErmbBS9pIjw56nhAW4zCjId9aSNWEcjqUXQ6IIjIGHExNh5AGw0pp1yvbeMcBEhOlBiCEjyBcYzKdGAQVMoz0JCEPADI7CCjKph4hOTCJQDCa4EOy5baus0miDMj6UbI/qLQAwBU5QgXbJej4WGgajWgEUKyvnzWS14eMDkeMvh0riYdGWp8DYUbDKRYBq+VYTxGwy45OCcILgy5m4OuZm1bmltIRo8x8HYUpOgNWTmvzewhCFGVFGGhEIR6SIohPuZfAADE3gLWAqPEIviJCEWyQmUakIJymMws9nVCL8ObATINUMsFwAInGQjMEOHcFOBZgwDKgEyA3QWA8L+CfJ9gGZAevdECIUlmwVoiiGOnYBk9pAXAaIFYEJCIBHQJghYKzDVDbB8Y7ZFZMFF7JVkmgx9SktiTnZDp1e0QTbnz1iRoAIBfZUptvEUAMhEkKI1EvwS1DniXyDkLSPZVkBs0yMcSJKl9AoQXUgGphc4fqAZAtl+AMYVYBrD/byh2hgvCMDsHsRa5zRdiU+NsUqjwYhggmBMD6zDCXJmWg2EQDcikBeIVEluL8RyV45HEtWiAb2gIBkyUIimJo80hfGmqSZsA54lIPeJ7a5hvIfiM1N8T2oFtHRdfU5i6PwncN+O7owTl6MH4PMbaoiTQWi0dqeiB+InESR7XApfxwoL6aQR6nnAQjAEUdaAkhVZyy8X+XePwYGNX7fN1+vzTftnXCGqdNg8GKIRcFQorIRgx1QjGmN4qWcBKtdW/jmPEoVVUIjnUps3QUpOY+SQMOyNonugJgiAaoN4CcWChSwsEOQWYA0DQnDZS0FHZbBsiNZ3Jx+IrChqhGTi58M81sLPOAi3ZuYbUnYDDLwGarDwPusgReM2BNI/JEpGEikYLRxYDg+6zlEgNR2zJy9KItI8AiyIziOgS0MXLdusBBCOhTq8oQiKajYRxTMg2Aq1ihjNBDVzmLKaVn7GyCQTsO+47BiuNfQFQDU+oTcduK1yslUqwYCnuyLnBHigkVCPqBWHPaWjy+1ePJt2PwwNwVMDsPABEA8DshVIs4jYL1jZqHJtcLHbZHiEPr5Cr48kYormFH6CB0J1aKLlWPWDyYRWrXHEBnD+lqA3MdYd6QSm+mRAHB3HBvrxKb5HlBJ0kjvu7S77iTe+j5fvhbWEmd9EAntMZopLgJlg6MFYGOpThQroVMKp8WSrpIdH6T3mAQuTiGJMmhDwxyjUHL2ALAJBcuz2RrkrOaBOTEWmY4AmkNRak0H+ZOLSdTgpAMlqAOaYbkn0izHZmmn4jATpAlYPT8Yp8QTEyHyCWBF0JsSUBXA2LQFPqHgZ2QcAxzuyEYFcCjHdW2Sew8+2QI6ftkgG64fp1wsUNOM+ghB8YTbIIoeHq4cDniCXByGiF3jSYSwZ47dvYknFsdk+LrTsG1D+RNDg44gFzJACVBVhR6THdFGATGZtQGMtoDIXVGblJJfpZucKA2zu6CRNoo0u1oGHIQNxzS3xc0sLIwgdjoZmZV3kahMRYUUGk8p4Wc10qSZYKQ8+Xq1hkiLEoBlEF+PQm+AZ4+hu5SaNsjeTRyYgYpS+XdVDgqxY58BG6SeORDC0zY/gDwKL2irhcCEWGNmp+C4A8QmABXC0vLDmqj0Sw64drOMDeBkolCF8L0H8gqxYRDYoEFNosjqQNQBJQ004ouJhgZ4a2V4BXJYJWhmDj0SVEZBVHgjPBli+AZeSNJ95DIYOWAqGEUzznslfAwDCamX0fk8SgEX8kFOEjLBNpJQCuQ4rqkLD6CLSDlT2MWJEE2wfenExwdxPur7lXBLfD0W308E+jRJBgZ5ovwBoNYmsa0yBativ49Zfau2XLm5P2DHZxsp2BMtNkuyGBzFlGdQAAH0zQiAbxcBhxh0BvFpw0ILNhuxQAlAJAJ3FcAuCe4GAMiM4AIFoBogncPuWgE7iJDl4LgpcKRKXFLhO4ZE5IM4KXASVI1yQpcM4CZVmzmLaAMiC4BcHJD1KTgGS5JWgCkR1LLg+RH3AIAKWe4SAUiM4D7hICe40AQeckCcAYBSInc7i4wPNlXAH1fFluAJU8iCW0BvFLWdxUAA=== -->

<!-- internal state end -->
<!-- tips_start -->

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

<details>
<summary>❤️ Share</summary>

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai)
- [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai)
- [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai)
- [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

</details>

<details>
<summary>🪧 Tips</summary>

### Chat

There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai?utm_source=oss&utm_medium=github&utm_campaign=Goob-Station/Goob-Station&utm_content=2491):

- Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  - `I pushed a fix in commit <commit_id>, please review it.`
  - `Generate unit testing code for this file.`
  - `Open a follow-up GitHub issue for this discussion.`
- Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples:
  - `@coderabbitai generate unit testing code for this file.`
  -	`@coderabbitai modularize this function.`
- PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.`
  - `@coderabbitai read src/utils.ts and generate unit testing code.`
  - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.`
  - `@coderabbitai help me debug CodeRabbit configuration file.`

### Support

Need help? Create a ticket on our [support page](https://www.coderabbit.ai/contact-us/support) for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

### CodeRabbit Commands (Invoked using PR comments)

- `@coderabbitai pause` to pause the reviews on a PR.
- `@coderabbitai resume` to resume the paused reviews.
- `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
- `@coderabbitai full review` to do a full review from scratch and review all the files again.
- `@coderabbitai summary` to regenerate the summary of the PR.
- `@coderabbitai generate docstrings` to [generate docstrings](https://docs.coderabbit.ai/finishing-touches/docstrings) for this PR.
- `@coderabbitai generate sequence diagram` to generate a sequence diagram of the changes in this PR.
- `@coderabbitai resolve` resolve all the CodeRabbit review comments.
- `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository.
- `@coderabbitai help` to get help.

### Other keywords and placeholders

- Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed.
- Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description.
- Add `@coderabbitai` anywhere in the PR title to generate the title automatically.

### CodeRabbit Configuration File (`.coderabbit.yaml`)

- You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository.
- Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information.
- If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json`

### Documentation and Community

- Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit.
- Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback.
- Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

</details>

<!-- tips_end -->
author_association: CONTRIBUTOR
user: login: GoobBot
created_at: 2025-05-08T17:03:48Z
body: This pull request has conflicts, please resolve those before we can evaluate the pull request.
author_association: MEMBER