Skip to content

Reorder the footnotes in the banning policy to be in the right order #514

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Reorder the footnotes in the banning policy to be in the right order #514

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5a9f98a
Reorder the footnotes to be in the right order
Lyroth001 Sep 9, 2025
cdd26fc
Remove unused footnote
Lyroth001 Sep 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 11 additions & 13 deletions src/en/community/admin/wizards-den-banning-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -145,32 +145,30 @@ Rule violations not in the offense table can still have bans applied, but have n
| 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.
[^discrimination]: Includes IC racism/speciesism.

[^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.
[^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.

[^excludingEscalationIssues]: Does not include escalation issues.
[^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.

[^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.
[^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.

[^discrimination]: Includes IC racism/speciesism.
[^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.

[^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.
[^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.

[^antagOnly]: Only applies to antagonists and free agents.
[^excludingEscalationIssues]: Does not include escalation issues.

[^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.
[^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.

[^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.
[^antagOnly]: Only applies to antagonists and free agents.

[^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.
[^eachVictim]: Guideline is multiplied by the number of victims.

[^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.
[^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.

[^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.

## Modifiers Tables

```admonish info
Expand Down
Loading