From f7a6be6b48d8cbea274b01b41848ed1da64c7d60 Mon Sep 17 00:00:00 2001 From: Baptr0b0t Date: Fri, 17 Jul 2026 03:02:06 +0200 Subject: [PATCH] first draft banning policy --- .../admin/goob-station-banning-policy.md | 391 ++++++++++++++---- 1 file changed, 302 insertions(+), 89 deletions(-) diff --git a/src/en/community/admin/goob-station-banning-policy.md b/src/en/community/admin/goob-station-banning-policy.md index 03725b8..18ec38e 100644 --- a/src/en/community/admin/goob-station-banning-policy.md +++ b/src/en/community/admin/goob-station-banning-policy.md @@ -1,20 +1,18 @@ # Goob Station Banning Policy ```admonish info -This is the ban policy for Goob Station. It applies only to our Goob Station servers. The admin policy can be found at [Admin Policy](https://docs.goobstation.com/en/community/admin/banning-policy.html) +This is the ban policy for Goob Station. It applies only to our Goob Station servers. The admin policy can be found at [Admin Policy](https://docs.goobstation.com/en/community/admin/goob-station-admin-policy.html) ``` # Definitions - **Indefinite:** Refers to a ban with no defined end time. This type of ban generally requires a successful appeal for it to be removed. Indefinite bans which have no extra requirements are sometimes called *appeal bans*. - **Voucher:** Confirmation from the admin team of another well known SS14 or SS13 server that you have played on that server for a significant amount of time without any recent major issues. A voucher is required when appealing a *voucher ban*. -- **Voucher ban:** A ban which requires a *voucher* to appeal. These bans can also typically only be appealed after at least 6 months from the date of the ban. They are often used as an alternative to a *permanent ban* that allows players to return if they can demonstrate an ability to follow a server's rules. +- **Voucher ban:** A ban which requires a *voucher* to appeal. These bans are often used as an alternative to a *permanent ban* that allows players to return if they can demonstrate an ability to follow a server's rules. See [Extended And Strict Voucher Bans](#extended-and-strict-voucher-bans) for details. - **Warning:** A warning is a clear communication from an admin that some behavior is not acceptable. Warnings should always be paired with an account note making note of the warning and behavior. - **Permanent ban:** A ban which cannot be appealed. These bans are sometimes called *perma bans*. - **Game ban:** A ban from the servers. A player who is *game banned* cannot connect to the servers during the ban. These bans are sometimes called *server bans*. - **Role ban:** A ban from a specific role or roles. - **Ban evasion:** Attempting to circumvent an active ban. -- **Soft Voucher Ban:** A ban usually applied due to repeat offenses and are only appealable after two months. -- **Ban evasion:** A ban usually applied due to repeat offenses after a Soft Voucher Ban or Ban Evasion and are only appealable after six months. ## Special Banning Requirements @@ -22,13 +20,13 @@ This is the ban policy for Goob Station. It applies only to our Goob Station ser Permanent bans should typically only be placed as the result of an unsuccessful appeal of an indefinite ban or a voucher ban. Except for cases of ban evasion after an accepted voucher ban, a vote by the admin team is required to place a permanent ban. Placing a permanent ban may be an option in a vote for the appeal. It is recommended that any indefinite ban after a prior voucher ban within 6 months of the date of the current ban be upgraded to a permanent ban. -### Soft And Hard Voucher Bans +### Extended And Strict Voucher Bans -**Voucher Bans** usually occur if a player is too problematic and must get a voucher (Prove of good behavior.) from another server in order for their appeal to be accepted. +**Voucher Bans** usually occur if a player is too problematic, or as a modification following an appeal. They require a voucher (proof of good behavior) from another server in order for their appeal to be accepted. -**Soft Voucher Bans** are done if the player receives multiple offenses after an appeal ban. Soft Voucher Bans are only appealable after 2 months and the banned player appeals with a voucher from a well known Space Station 13 or 14 server. +**Extended Voucher Bans** are applied if the player receives multiple offenses after an appeal ban, or if the player evades an ongoing ban. They are only appealable after 2 months and require a voucher **from a well known** Space Station 13 or 14 server. -**Hard Voucher Bans** are applied if the player receives multiple offenses after being Soft Voucher banned or if the player evades an ongoing ban. Hard Voucher Bans are only appealable after 6 months and require a voucher from a well known Space Station 13 or 14 server. +**Strict Voucher Bans** are applied if the player receives multiple offenses after an Extended Voucher Ban, or if the player evades a ban a second time. They are only appealable after 6 months, with the timer resetting on each ban evade attempt, and require a voucher **from a well known** Space Station 13 or 14 server. # Banning Guidelines @@ -69,6 +67,22 @@ If a player evades an ahelp: In most cases, ban reasons should clearly communicate the reason for the ban to the banned player whenever they are not evading a ban. Admins should be able to easily identify the reason for a ban through either the ban or account's notes. +Ban reasons should follow this format for standard offenses: + +``` +Grouping Category | Offense | Sanction (W, RB, GB) | Offense Tier +Explanation +``` + +When multiple offenses are stacked, the following format is also valid: + +``` +Grouping Category, Grouping Category | Sanction +- Offense (Offense Tier) +- Offense (Offense Tier) +Explanation +``` + Alternate account bans should typically be in the form `Alt of OriginalUsername` or `AltUsername alt of OriginalUsername`. Bans of additional non-username information should typically include the GUID of the targeted player as a ban detail and should have a reason with just the account username. The earliest placed ban's reason will appear for the player when trying to connect. @@ -80,7 +94,7 @@ Game admins may dewhitelist a player at their discretion in any case where an is ## Offense Table ```admonish info -First, second, third, and fourth offense refers to the amount of offenses in the grouping category in the last 6 months. Suggestions for subsequent offenses are double the last defined suggestion. +First, second, third, and fourth offense refers to the number of offenses in the same grouping category in the last 6 months. Suggestions for subsequent offenses are double the last defined suggestion. Warnings are independent of grouping categories. ``` ```admonish info @@ -95,49 +109,55 @@ Rule violations not in the offense table can still have bans applied, but have n Any player who requests to be banned from a department or from the server may be banned indefinitely until appealed or requested to be unbanned via ingame admin help. ``` -| Abreviation | Meaning | -|-------------|------------| -| W | Warning | -| RB | Role ban or department ban | -| GB | Game ban | -| Indef | Indefinite | +| Abbreviation | Meaning | +|--------------|----------------------------| +| W | Warning | +| RB | Role ban or department ban | +| GB | Game ban | +| Indef | Indefinite | ----------------------------- | Grouping Category | Offense | First Offense | Second Offense | Third Offense | Fourth Offense | -|-------------------|------------------------------------------------------------------------------------------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------|---------------|----------------| -| Non-grouping | Harassing staff through the game | Indef GB | | | | +|----------|---------|---------------|----------------|---------------|----------------| +| Non-grouping | Harassing staff through the game | W - **Indef GB** | | | | +| Non-grouping | Harassing staff outside of the game | Strict Voucher Ban | Vote for permanent ban | | | | Non-grouping | Slurs, excluding "retard" and variants | Indef GB | | | | | Non-grouping | "Retard" and variants | W | 1d - 3d GB | Indef GB | | | Non-grouping | Bigotry/discrimination[^discrimination] | Indef GB | | | | | Non-grouping | ERP | Indef GB | | | | | Non-grouping | Sexual content | W - 3d GB | 7d GB | Indef GB | | -| Non-grouping | Metacommunications | W - week GB | Indef GB | | | -| Non-grouping | No Intent to Roleplay(NITRP) | W - **12h** GB | 1d GB | 3d GB | Indef GB | -| Non-grouping | Ban Evasion | Hard Voucher Ban | If after an accepted hard voucher ban, permanent ban.
Otherwise, extend hard voucher ban to 6 months from evasion attempt. | | | +| Non-grouping | Metacommunications | W - 7d GB | Indef GB | | | +| Non-grouping | No Intent to Roleplay (NITRP) | W - **12h** GB | 1d GB | 3d GB | Indef GB | +| Non-grouping | Ban Evasion | Extended Voucher Ban | Strict Voucher Ban | | | +| Non-grouping | Role ban evasion[^roleBanEvasion] | W - 12hr GB | 1d - 3d GB | 7d GB | Indef GB | | Non-grouping | Multi-keying | W - **Indef** GB | Indef GB | | | | Non-grouping | Ahelp misuse in bad faith[^badFaith] | **W** - 12hr GB | 12hr - 3d GB | **7d** - 7.5d GB | | | Non-grouping | Threats to ahelp | **W** - 12hr GB | 12hr - 3d GB | **7d** - 7.5d GB | | -| Non-grouping | Under 16, or acts under 16. | Indef GB | | | | +| Non-grouping | Under 16, or acts under 16 | Indef GB | | | | | Non-grouping | Bad character name[^requiresIntent] | **W** - 12hr GB | **12hr** - 3d GB | **7d** - 7.5d GB | | -| Non-grouping | Mini-modding | W | W-**1d** GB | 1d-2d GB | 2d-**4d** GB | 4d-**8d** GB | +| Non-grouping | Mini-modding[^miniModding] | W | W - **1d** GB | 1d - 2d GB | 2d - **4d** GB | | Language | Non-english chat | W | W - 12hr GB | 3d GB | **7d** - 7.5d GB | | Language | Solely non-english chat | W | Indef GB | | | | Exploits | Bugs/exploits | **W** - 7d GB | 12hr - 7d GB | 3d - 15d GB | 7d - 15d GB | | Exploits | Use of macros | W | W - 12hr GB | 3d GB | **7d** - 7.5d GB | -| AI Laws | Major failure to follow silicon laws | W - 5d RB | 3d - 7.5d RB | Indef RB | | -| AI Laws | Minor failure to follow silicon laws | W | W - 5d RB | 3d - 7.5d RB | Indef RB | +| AI Laws | Failure to follow silicon laws[^droneInclude] | W | W - 5d RB | 3d - 7.5d RB | Indef RB | | Familiars | Familiar griefing master | 12hr GB | 3d GB | **7d** - 7.5d GB | | | Familiars | Familiar unreasonable failure to obey orders | W | 12hr GB | 3d GB | **7d** - 7.5d GB | | Immersion | Text speak | W | W | **W** - 12hr GB | W - 12hr GB | | Immersion | OOC terms IC[^teachingException] | W | **W** - 12hr GB | **12hr** - 3d GB | 3d - 7.5d GB | -| Immersion | Bypassing chat restrictions | W | W - **4hr** - 12hr GB | 12hr - 3d GB | 3d - 7.5d GB | -| Metagaming | Using info from death[^infoFromDeath] | W - 12hr GB | 12hr - 3d GB | 3d - 7.5d GB | | -| Metagaming | Using info from past life | 12hr - 48hr GB | 3d GB | **7d** - 7.5d GB | | +| Immersion | Bypassing chat restrictions | W | W - **4hr** GB | 12hr - 3d GB | 3d - 7.5d GB | +| Metagaming | Using info from unconscious | W | 6hr - 12h GB | 1d - 3d GB | 7d - 12d GB | +| Metagaming | Using info from ghost | W - 12hr GB | 12hr - 3d GB | 3d - 7.5d GB | | +| Metagaming | Using info from previous life[^previousLife] | 12hr - 48hr GB | 3d GB | **7d** - 7.5d GB | | +| Metagaming | Violation of new life rule | **W** - 12hr GB | 12hr - 3d GB | **6d** - 8d GB | | | Metagaming | Metagaming round type | W - 12hr GB | 12hr - 3d GB | 3d - 7.5d GB | | | Metagaming | IC in OOC[^positiveException] | W | W - 12hr GB | 3d GB | **7d** - 7.5d GB | +| Metagaming | Metagrudging | W | 12hr - 3d GB | 3d - 7.5d GB | | +| Metagaming | Metafriending | W | 12hr - 3d GB | 3d - 7.5d GB | | | Powergaming | Preparing items not needed IC | W | W - 12hr GB | 12hr - 3d GB | 3d - 7.5d GB | -| Self-antag | Self-antag[^excludingEscalationIssues] | W - 1d GB | 1d - 3d GB | **3d** - 7d GB | 7d - 9d | Indef GB | +| Powergaming | Validhunting[^validhunting] | W | 12hr - 1d GB | 3d GB | 7d GB | +| Self-antag | Self-antag[^excludingEscalationIssues] | W - 1d GB | 1d - 3d GB | **3d** - 7d GB | 7d - 9d GB | | Self-antag | Station sabotage[^stationSabotage] | W - 3d GB | 12hr - 7d GB | 14d - 15d GB | | | Self-antag | Cults/riots/revolutions | **12hr** - 3d GB | 12hr - **3d** - 7d GB | **7d** - 7.5d GB | | | Self-antag | Cooperating with known antags | 12hr GB | 3d GB | **7d** - 7.5d GB | | @@ -145,58 +165,85 @@ Any player who requests to be banned from a department or from the server may be | Griefing | Friendly antag[^antagOnly] | **W** - 12hr GB | 12hr - 3d GB | **7d** - 7.5d GB | | | Griefing | Antagonist team sabotage[^antagOnly] | 12hr - 3d GB | 3d - Indef GB | 7d - Indef GB | | | Griefing | Early massive station sabotage[^antagOnly] | **W** - 12hr GB | 12hr - 3d GB | **7d** - 7.5d GB | | +| Griefing | Abductor sabotage[^abductorSabotage] | **W** - 12hr GB | 12hr - 3d GB | **7d** - 7.5d GB | Indef GB | | Griefing | Unreasonable failure to follow an order from a team leader | W - 5d RB | 3d - 7d RB | Indef RB | | | Griefing | Harassing a player/role/department with no IC conflict | W - 12hr GB | 12hr - 3d GB | **7d** - 7.5d GB | | -| Griefing | Abandoning a role[^abandoningRole] | W - 5d RB | 3d - 7d RB | Indef RB | | -| Griefing | Antag rolling | 12hr - 3d GB | 3d - 7d GB | **7d** - 7.5d GB | | | Griefing | Damage/disruption to arrivals/arrivals shuttle | 12hr - 3d GB | 3d - 7d GB | 7d - 15d GB | | -| Escalation | Validhunting[^validhunting] | W | 12hr - 1d GB | 3d GB | 7d GB | | +| Commitment | Antag rolling | 12hr - 3d GB | 3d - 7d GB | **7d** - 7.5d GB | | +| Commitment | Abandoning a role[^abandoningRole] | W - 5d RB | 3d - 7d RB | Indef RB | | | Escalation | Over escalation[^eachVictim] | W | 12hr GB | 3d GB | **7d** - 7.5d GB | | Escalation | RDM[^eachVictim] | **1d** - 3d GB | 5d GB | **9d** - 9.5d GB | Indef GB | | Escalation | Over escalation or RDM that is a secondary result of station sabotage[^stationSabotageRDM] | 12hr GB | 3d GB | **7d** - 7.5d GB | | -| Competence | Unreasonable incompetence in Command | W - **5d** - 9d RB | 9d - 16d RB | Indef RB | | -| Competence | Unreasonable incompetence in Security | W - **5d** - 9d RB | 9d - 16d RB | Indef RB | | -| Competence | Unreasonable incompetence in Engineering | W - **4d** - 8d RB | 8 - 15d RB | Indef RB | | -| Competence | Unreasonable incompetence in Medical | W - **4d** - 7d RB | 7d - 14d RB | Indef RB -| Competence | Unreasonable incompetence in Cargo | W - **4d** - 7d RB | 7d - 14d RB | Indef RB -| Competence | Unreasonable incompetence in Science | **W** - 3d - 6d RB | 6d - 14d RB | 14d - 21d RB | Indef RB | | -| Competence | Unreasonable incompetence in Service | **W** - 2d - 5d RB | 5d - 10d RB | 10d - 15 RB | Indef RB | | -| Competence | Abuse of a position of authority | 3d - 7d RB | 7d - 15d RB | Indef RB | | -| Competence | Taking actions a reasonable person would view as to be to the detriment of the station as security/command | 3d - 7d RB | 7d - 15d RB | Indef RB | | -| Competence | Unreasonable failure of security/command to follow space law | W - **3d** - 7d RB | 7d - 15d RB | Indef RB | | - -[^eachVictim]: Guideline is multiplied by the number of victims. +| CC Competence | Unreasonable incompetence in Centcomm[^centcomm] | W - **6d** - 11d RB | 11d - 19d RB | Indef RB | | +| Command Competence | Unreasonable incompetence in Command | W - **5d** - 9d RB | 9d - 16d RB | Indef RB | | +| Sec Competence | Unreasonable incompetence in Security | W - **5d** - 9d RB | 9d - 16d RB | Indef RB | | +| Engi Competence | Unreasonable incompetence in Engineering | W - **4d** - 8d RB | 8d - 15d RB | Indef RB | | +| Med Competence | Unreasonable incompetence in Medical | W - **4d** - 7d RB | 7d - 14d RB | Indef RB | | +| Cargo Competence | Unreasonable incompetence in Cargo | W - **4d** - 7d RB | 7d - 14d RB | Indef RB | | +| Sci Competence | Unreasonable incompetence in Science | **W** - 3d - 6d RB | 6d - 14d RB | 14d - 21d RB | Indef RB | +| Service Competence | Unreasonable incompetence in Service | **W** - 2d - 5d RB | 5d - 10d RB | 10d - 15d RB | Indef RB | +| Conduct | Abuse of a position of authority[^authorityAbuse] | 3d - 7d RB | 7d - 15d RB | Indef RB | | +| Conduct | Taking actions a reasonable person would view as to be to the detriment of the station as command[^detrimentStation] | 3d - 7d RB | 7d - 15d RB | Indef RB | | +| Conduct | Unreasonable failure of security/command to follow space law | W - **3d** - 7d RB | 7d - 15d RB | Indef RB | | -[^stationSabotageRDM]: This should be used in cases where there are deaths that result from a station sabotage offense, like people being killed by an AME being overloaded or dying in a loosed singularity. -[^excludingEscalationIssues]: Does not include escalation issues. - -[^stationSabotage]: Acts that result in station wide, or near station wide disruption. Spacing a hallway is not station sabotage, but cutting HV or destroying substations likely is. Arrivals or arrivals terminal sabotage is not sufficient to apply the station sabotage offense. +[^discrimination]: Includes IC racism and using a character's appearance or name to caricature or demean a real-world group. -[^discrimination]: Includes IC racism/speciesism. +[^roleBanEvasion]: 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. [^badFaith]: To qualify as bad faith, there should be no *reasonable* way that something is being done with good intentions. It is not required for the person to *actually* be acting in bad faith, only that it is *unreasonable* for them to think that they are. -[^antagOnly]: Only applies to antagonists and free agents. +[^requiresIntent]: Offenses where the admin does not believe a violation to have been intentional may be reduced to a warning and do not need to be considered a past offense when evaluating guidelines for future offenses. -[^stackEscalation]: Should be combined with an escalation offense from the perspective of the offender. Typically RDM if an execution occurs for no reason, or over escalation if there is a poor reason. +[^miniModding]: Includes suggesting punishments to staff in ahelp or OOC. + +[^droneInclude]: Also applies to Maintenance Drones interfering with beings. [^teachingException]: Use of admin discretion to not enact penalties is highly recommended in cases where the offending player only commits an offense after attempting and failing to teach a new player appropriately. +[^previousLife]: A "life" ends when a player takes a different role, such as a ghost role. Information learned in a previous life may not be carried over. A "life" does not end on cloning. + [^positiveException]: Use of admin discretion to not enact penalties is highly recommended in cases where the offending player is not negatively impacting players, and is attempting to ensure players have a positive experience. For example, using LOOC to get permission to perform an IC act which would be allowed even without that permission. -[^infoFromDeath]: This includes any information that a character should have not known from the same "life". Depending on server rules, this may include information like the information leading to your death. A "life" ends when a player takes a different role, like a ghost role. For the purposes of banning guidelines, a "life" does not end on cloning. +[^validhunting]: Validhunting constitutes a non-security player actively seeking antagonists with the intent to fight/kill them. Bartenders seeking out lings constitutes validhunting; chaplains hunting heretics does not. + +[^excludingEscalationIssues]: Does not include escalation issues. + +[^stationSabotage]: Acts that result in station wide, or near station wide disruption. Spacing a hallway is not station sabotage, but cutting HV or destroying substations likely is. Arrivals or arrivals terminal sabotage is not sufficient to apply the station sabotage offense. + +[^antagOnly]: Only applies to antagonists and free agents. + +[^abductorSabotage]: Includes intentional killing, sabotaging the station, or stealing unique items. [^abandoningRole]: This includes frequently disconnecting in an important role, disconnecting in an important role without notification when there is reason to believe that the disconnection was not urgent, and failing to attempt to perform the duties of a role. -[^requiresIntent]: Offenses where the admin does not believe a violation to have been intentional may be reduced to a warning and do not need to be considered a past offense when evaluating guidelines for future offenses. +[^eachVictim]: Guideline is multiplied by the number of victims. -[^validhunting]: Validhunting constitutes a non-security player actively seeking antagonists with the intent to fight/kill them. Bartenders seeking out lings constitutes validhunting; chaplains hunting heretics does not. +[^stationSabotageRDM]: This should be used in cases where there are deaths that result from a station sabotage offense, like people being killed by an AME being overloaded or dying in a loosed singularity. + +[^centcomm]: Includes NanoTrasen Representative, Blueshield Officer, Emergency Response Team, and Deathsquad. + +[^authorityAbuse]: **Intentionally** using a position of power for personal gain or to maliciously target individuals. Examples include an illegal execution, siccing security on a specific player without IC cause, or brigging someone without justification. + +[^detrimentStation]: **Intentional** decisions by command that harm the station. Examples include ordering security to ignore active threats, using early launch without valid reason, or sabotaging their own department. + + + +## Minor and Major Offenses + +At admin discretion, an offense may be classified as **minor** or **major**. + +- **Minor:** The offense is at the edge of rule-breaking and had no negative, or a positive, impact on other players or the round. It does not count as a full offense and does not accumulate toward the next tier for that specific offense. +- **Major:** The offense has had a significant impact on the round or other players, and the standard punishment is clearly insufficient. The admin may apply the punishment of the next tier directly, skipping the current one. + +```admonish warning +Administrators who classify an offense as minor or major are required to be able to justify the decision to the admin team. +``` ## Modifiers Tables ```admonish info -> Modifiers can be applied to each offense that meets their conditions. They are typically in the form of multipliers. +Modifiers can be applied to each offense that meets their conditions. They are typically in the form of multipliers. ``` ```admonish info @@ -222,22 +269,26 @@ These mitigating modifiers are applied at the discretion of the admin and may be | Admin intervention | Any reduction, including to nothing, may be applied for any offense which is plausibly the result of admin intervention. | | Self report | Reduce to warning. Applies to any offense where the player reports themselves as long as the offense was unlikely to be identified otherwise. | | Valid Rule Clarification | No more than a warning should be given to a player that justifies the offense with a reasonably cited active rule clarification, even if it is not up to date with current rules. | + ### Aggravating ```admonish info -Aggravating modifieres are applied at the discretion of the admin and may be partially applied. +Aggravating modifiers are applied at the discretion of the admin and may be partially applied. ``` | Modifier | Modification | |----------|--------------| | Repeat game bans | A multiplier equal to 1 plus the number of game bans in the last 6 months which resulted from offenses from other grouping categories. | -| Metagrudging | **2x** multiplier if the offense is the result of metagrudging by the offender. | | Prior indefinite ban | **7d** can be added to the total game ban length if the player has had any prior indefinite ban in the last 6 months. Excluding bans used only for contact and ones where they were found to be not at fault. | | Round removal | **2x** multiplier for any offense which results in someone being permanently removed from a round, including an attempt to do so and actions likely to result in permanent round removal. | -| Lying in ahelp | **24h + 3x** multiplier if the offender maliciously lies in the ahelp. You should be certain that they have lied. The multiplier is applied after the 24h addition is made. | -| Command/Security | **2x** multiplier if the offender is in command or security | +| Lying in ahelp | **24h + 3x** multiplier if the offender maliciously lies in the ahelp. You should be certain that they have lied. The 24h is added after the 3x multiplier is applied. | +| Command/Security | **2x** multiplier if the offender is in command or security. Only applies to Griefing, Escalation, Metagaming, Powergaming, and Self-antag offenses. | | Intentional rule breaking | **3x** multiplier. Includes any rule breaking where the player intentionally breaks a rule knowing they are breaking a rule, knowing they will get banned, or claims to not care if they get banned. Any reasonably clear rule violation can be presumed to be intentional if the player was told to read the rules in the last 12 hours. | -| Role specific | Any issue that is likely to be prevented by a role ban should include a role ban if a game ban is applied. The role ban can be applied in addition to or as an alternative to the suggested game ban. Game ban suggestions can be converted to role ban suggestion times by doubling the time. | +| Role specific | Any issue that is likely to be prevented by a role ban should include a role ban if a game ban is applied. The role ban can be applied as an alternative to the suggested game ban. Game ban suggestions can be converted to role ban suggestion times by doubling the time. | + +```admonish warning +Role bans and game bans run concurrently. To ensure a role ban takes effect after a game ban expires, the game ban duration must be added to the role ban duration when applying. +``` ## Grouping and Stacking @@ -250,37 +301,199 @@ Aggravating modifieres are applied at the discretion of the admin and may be par [^ahelpDelimited]: This means that if two otherwise grouped offenses occur within the same round, but the player is ahelped between the two offenses occurring about the first offense, the second offense does not need to be grouped with the first. The second offense may also be considered as a prior offense for determining suggested ban times. -## Role Ban Rounding - -The total time of a role ban may be rounded to the nearest available autofill. - ## Examples -```admonish info -These examples may be outdated due to a banning policy update. Please point out any issues if you notice them. -``` - ### AME Sabotage A technical assistant sets the AME to 50. Their offenses are: -- Self antag -- Station sabotage -- Unreasonable incompetence in role -Self antag and station sabotage are part of the same grouping category, so are treated as only station sabotage. Both remaining offenses can have the new player modifier applied if the player is new to the game, which would allow the offenses to result in only a warning and an instruction to read the rules. The station sabotage offense may optionally have the role specific modifier applied. Any of the following total suggestions are valid: -- With new player modifier - - W - 3d GB + W - 7d RB -- With role specific modifier - - W - 3d GB + W - 13d RB if the role ban is applied in addition to the game ban, or - - W - 13d RB if the role ban is applied as an alternative - -### RDM + Lying -A player RDMs another. When asked why they killed the other player, they say they haven't done anything all round other than walk around, despite having just beaten the victim to death with a bat. Their offenses are: -- 1x RDM - -The lying in ahelp modifier applies. The resulting guideline is: -- 36hr - 4.5d GB - -### Over escalation with history of issues -A player over escalates in a way unlikely to result in the victim's round removal. They have a prior offense of RDM, a prior offense of self-antagging, and a prior offense of griefing the arrivals terminal. They have no prior bans. The offenses in this case are: -- 1x over escalation - -No modifiers apply. Only the prior RDM offense is relevant because it is the only one in the same grouping category. The prior RDM offense means that for the current over escalation incident, second offense guidelines are used. +- Self-antag [Self-antag] +- Station sabotage [Self-antag] +- Unreasonable incompetence in Engineering [Engi Competence] + +Self-antag and station sabotage share the Self-antag grouping category and occur within the same round, so they are grouped. Station sabotage is the most specific offense; self-antag is discarded. The two remaining offenses are in different grouping categories and are stacked: +- Station sabotage (first offense): W - 3d GB +- Unreasonable incompetence in Engineering (first offense): W - **4d** - 8d RB +- Total game ban: **W - 3d GB** +- Total role ban: W - **4d** - 8d RB + +Since GB and RB run concurrently, the GB duration is added to the RB so it takes effect after the GB expires (W - **4d** - 8d + 3d = W - **7d** - 11d RB): **W - 3d GB + W - 7d - 11d RB** + +The admin may also apply the following options: +- New player modifier (both offenses reduced to warning): **W** +- Role specific modifier on station sabotage (game ban converted to role ban at 2x, replaces game ban): (3d × 2 = 6d RB) + (W - **4d** - 8d RB) = W - **10d** - 14d RB + +### RDM + Lying in Ahelp +A player kills a crew member without reason. When asked in ahelp, they claim to have been AFK and nowhere near the victim, despite logs proving otherwise. Their offenses are: +- 1x RDM [Escalation] + +The lying in ahelp modifier applies (3x first, then +24h): +- RDM (first offense): **1d** - 3d GB +- After lying modifier: 1d × 3 + 24h = 4d; 3d × 3 + 24h = 10d → **4d - 10d GB** + +### Security Officer With Prior Offense Categories +A security officer is killed during an arrest. While observing as a ghost, they identify where the crew member who overpowered them is hiding. After being revived, they use that information to track them down and beat them to death. They also made repeated errors processing prisoners throughout the shift. They have a prior IC in OOC [Metagaming] offense from two months ago. Their offenses are: +- Using info from ghost [Metagaming] +- Unreasonable incompetence in Security [Sec Competence] +- New Life Rule Violation [Metagaming] + +Using info from ghost and the NLR violation share the Metagaming grouping category. Using info from ghost is the more specific offense; the NLR violation is discarded. The two remaining offenses are in different grouping categories and are stacked. The Command/Security modifier (2x) applies to Metagaming, but not to Sec Competence. The prior IC in OOC [Metagaming] makes the ghost info use a second offense: +- Using info from ghost (second offense): 12hr - 3d GB → C/S (×2): **24hr - 6d GB** +- Unreasonable incompetence in Security (first offense): W - **5d** - 9d RB + +Total game ban: **24hr - 6d GB** +Total role ban: W - **5d** - 9d RB + +Result (RB starts after GB): W - **5d** - 9d + 6d = **24hr - 6d GB + W - 11d - 15d RB** + +### Station Sabotage With Casualties +A non-antagonist assistant, furious at being demoted, cuts the HV cable network in the engineering department. Two engineers are electrocuted and killed before power is restored. Their offenses are: +- Station sabotage [Self-antag] +- Over escalation or RDM resulting from station sabotage × 2 victims [Escalation] + +These offenses are in different grouping categories and are stacked. The victim multiplier applies to the escalation offense: +- Station sabotage (first offense): W - 3d GB +- Station sabotage RDM × 2 (first offense): 12hr × 2 = 24hr GB +- Total: **1d - 4d GB** + +### Metacommunications With Compounding Modifiers +Two players in an external voice call share a round — one is assigned as a Syndicate traitor, the other joins as a security officer and warns the traitor of active security patrol positions. When confronted in ahelp, the security officer claims to have had no outside contact with the other player, which evidence disproves. Their offenses are: + +Traitor: +- Metacommunications [Non-grouping]: W - 7d GB + +Security officer: +- Metacommunications [Non-grouping]: W - 7d GB +- Lying in ahelp modifier (3x then +24h): W × 3 = W + 24h = 24h; 7d × 3 + 24h = 22d → **24h - 22d GB** +- Command/Security modifier: does not apply to Non-grouping offenses + +Traitor's resulting guideline (first offense): **W - 7d GB** +Security officer's resulting guideline (first offense): **24h - 22d GB** + +### Grouping With Round Removal +A Captain, bearing a personal grudge, orders the HoS to arrest the Research Director without reason, strip their PDA and headset, and brig them indefinitely. The Captain's offenses are: +- Abuse of a position of authority [Conduct] +- Taking actions to the detriment of the station as command [Conduct] +- Unreasonable failure to follow space law [Conduct] — stripping a headset and PDA without valid charges violates space law +- Metagrudging [Metagaming] + +The three Conduct offenses share the Conduct grouping category so they are grouped. The most specific offense is abuse of a position of authority; the other two are discarded. Metagrudging is in a different category and is stacked: +- Abuse of a position of authority (first offense): 3d - 7d RB +- Metagrudging (first offense): W - 12hr GB (×2, Captain is Command): W - 24hr GB + +The Research Director is detained for the rest of the shift, permanently removing them from the round. The round removal modifier applies to the Conduct offense (2x): 3d × 2 = 6d; 7d × 2 = 14d → **6d - 14d RB** + +Total game ban: **W - 24hr GB** +Total role ban: **6d - 14d RB** + +### Extended to Strict Voucher Ban +A player under an Extended Voucher Ban evades the ban again using an alternate account. The alternate account receives a ban in the form `Alt of [OriginalUsername]`. Because this is a second evasion, the original account is upgraded from an Extended Voucher Ban to a Strict Voucher Ban. The player cannot appeal for 6 months, and this timer resets with each ban evade attempt. + +### Warning Independence +An abductor kills a crew member for personal reasons rather than to conduct an abduction. They have a prior warning for friendly antag and a prior warning for round stalling from earlier rounds. Their offense is: +- 1x Abductor sabotage [Griefing] + +Both priors resulted in warnings. Warnings do not count as prior offenses toward the next tier, so despite having two Griefing category priors, this is a first offense: +- Abductor sabotage (first offense): **W** - 12hr GB + +### Warden Stacking With Prior Category Offense +A Warden re-arrests a crew member immediately after they have served their full sentence and strips their PDA without any valid legal basis. The Warden has a prior non-warning offense of unreasonable failure to follow space law from three months ago. Their offenses are: +- Unreasonable incompetence in Security [Sec Competence] — failing to correctly track sentence completion is a basic security competence failure +- Unreasonable failure to follow space law [Conduct] — stripping a PDA without valid charges is a direct space law violation + +These offenses are in different grouping categories and are stacked. The prior is in the same Conduct grouping category as the current Conduct offense, making it a second offense. The Command/Security modifier does not apply to Sec Competence or Conduct offenses: +- Unreasonable incompetence in Security (first offense): W - **5d** - 9d RB +- Unreasonable failure to follow space law (second offense): 7d - 15d RB +- Total: **7d - 24d RB** + +# Appeals + +## Appeals Team + +The Appeals Team is a group of admins within the Admin Team specifically tasked with handling ban appeals. Members are appointed and removed via Admin Team votes. Any member of the Appeals Team may handle an appeal on their own. Head game admins are always members of the Appeals Team. + +An Appeals Team vote is required before placing a Voucher Ban as the outcome of an appeal. An absolute majority of its members must vote in favor for it to be applied. If this threshold is not met but the voucher option holds a relative majority, the ban shall be reduced to 6 months instead. + +Any Appeals Team member may put an appeal to a vote within the Appeals Team or the Admin Team as a whole instead of handling it individually. The Admin Team is competent to decide on anything a singular member or the Appeals Team as a whole is competent to decide. A vote within the entire Admin Team is required where a Permanent Ban is considered. + +## Appeals of Incorrect Bans + +Unless the ban was an upgrade resulting from an unsuccessful appeal, if an appeal disputes the events used to justify the ban, the first appeal of a voucher or permanent ban may only be declined after it has been verified that the ban was appropriately placed. + +## Appeal Hijacking + +If an appeal is currently assigned to someone, it is generally best to let them finish processing it. Cases where it may be acceptable to hijack an appeal are: + +- The processor has not responded to the appeal recently. +- The processor has indicated they are not going to process the appeal. +- A head game admin has authorized you to process the appeal. + +## Processing by Non-Appeals Team Members + +Game Admins and Trial Game Admins may not process appeals without the supervision of an Appeals Team member. Before an outcome can be made it must be approved by the supervising Appeals Team member. The only exception is when an admin reduces or removes their own ban. + +## Appealing the Same Ban Multiple Times + +After an appeal, a banned player with a correctly handled appeal is only entitled to appeal again if the ban is an Indefinite Ban or a Voucher Ban. The typical wait period between attempts is 1 months. + +A player with a temporary ban may be told when they can appeal again by the processing admin. This is at the processing admin's discretion, but is typically 2 weeks or double the waiting period of the previous appeal. + +A player may have their appeal reviewed or submit a new appeal regardless of any waiting period if their appeal was handled improperly (e.g. the handling Appeals Team member relied on incorrect facts). This may only be authorized by a head game admin following a successful complaint. + +If a ban appeal is handled by the banning admin and the ban is not fully removed, the banned player may appeal again immediately. + +## Appeal Procedure + +1. Check for ban evasion. If found, deny the appeal and issue a extended or strict voucher ban. +2. If the ban has expired, you may, but are not required to, change the appeal into a [note appeal](#note-removal). +3. If you are not the banning admin and the appeal is extremely low effort, or a "troll appeal", deny the appeal. An appeal is considered to be low effort if it meets any of the following criteria: + - The appeal is clearly the output of an LLM such as ChatGPT. + - The appellant is clearly not expecting their appeal to be accepted, and made it simply to troll. + - The appeal is incomprehensible or written in a language other than English. + - The appeal has such little effort put into it that no other outcome can be derived from it but to close it. + - The appeal is unable to be accepted for reasons outside the administrative team's control; for example, the appeal was clearly intended for a different fork or server host. +4. If you placed the ban, you are only allowed to process the appeal, but not vote on it. +5. Collect information: + - Check the player's history of appeals, if they have relevant history post it in the appeal. + - Make a reasonable attempt to verify any claims made in the appeal by the player, or accept them to be true. + - Check the player's note and ban history to see if there is evidence of a pattern of behavior. + - Read and link to the AHelp that led to the ban if it exists. +6. Run a vote: + - Votes must run at least 3 days, if there is a tie or insufficient votes you may rerun a vote for the appeal. + - Votes must be made in a thread for the appeal inside the designated Discord appeals discussion channel. + - If an admin is to vote for "voucher" or "other" on an appeal, they should give sufficient explanation as to why they chose voucher and/or what they intend by choosing "other". +7. Post a response on the appeal which must be a summary of the following: + - The outcome of the appeal. + - If applicable, when the player is able to reappeal. +8. Mark the thread as solved using your response and approved or denied respectively, then lock the thread. +9. Implement the outcome. + +## Appeal Format + +**Title** + +`Username - Ban Reason` (additionally add in if there is notable info on the ban, such as it being a Discord ban, Note Appeal, or a Community Approval) + +**Text Body** + +- Link to the ban appeal forums post. +- Banning Admin: Username or @ the user on Discord +- Additional Info: In here goes any additional information that may be important to the ban, such as it being out of policy, previously attempted to appeal, a noticed pattern of behavior, etc. +- Relevant AHelps: Link to the AHelps directly involved in the ban through the admin Discord. Not required, however highly encouraged so that we do not post AHelps publicly and so that the information and context is readily available and on hand. + +Send the first message, then a vote for the unban or note appeal. Unban votes should include options for "Approve", "Deny", "Voucher", and "Other". + +# Note Removal + +Note removal requests follow the same procedure as the Appeal Procedure. Notes serve to describe a player's past behavior and help admins contextualize future interactions — they are not punishments in themselves. + +When evaluating a note removal request, the standard for removal is not whether the behavior was minor or the player has since improved, but whether the note **does not faithfully describe what actually happened** or is **entirely out of context** (e.g. the note records an outcome that was later proven incorrect, or references an incident the player was not actually involved in). + +A note that accurately reflects a real event, even a minor one, should generally be kept. + +# Self Requested Bans + +A player may request a ban for any reason, for any duration of time. Such bans are not considered a ban for further administrative actions. Self-requested bans may only be requested through AHelp or admin messages on the forum. Requests through other channels should be met with instructions to submit them through the proper channels. At the player's request, the ban may be lifted before the requested time via a ban appeal. While admins are not required to honour ban requests, they should be honoured unless there are compelling reasons against placing a ban. + +## Self Requested Ban Appeal Procedure + +Self-requested bans may be removed upon request by the player they were issued to unless the user has specifically requested to not be unbanned while requesting said ban. If this is the case, they may run a regular appeal for their self imposed "grass ban." +