Funky Station - User contributions [en]

Event Policy

2026-05-05T15:09:17Z

Huhm: Event Policy WIP

=== This document is a WORK IN PROGRESS ===

====== The Purpose of Events ======
Events serve the purpose of increasing player engagement by providing fresh, interesting, and dynamic content. Events are never solely for admin enjoyment but that can be a side effect of events.

Events which intentionally exclude players, or encourage players to harass or antagonize others without any meaningful way to be handled in character should be avoided. Events are '''FOR THE PLAYERS.'''

=== Core Rules ===
1. Do not directly interfere in another admin's event without explicit permission from that admin.

2. Do not run events back to back with another event, especially Major events.

3. Events should never be purposefully exclusive to any member of crew, and should not encourage harassment or misconduct towards others

4. Events that leave crew with no resolution or means to combat the situation in a clear manner should be avoided.

5. There should always be player driven reason for an event to occur. Examples are a player prayer, game mode playtest, or player vote before the rounds. Major events can happen regardless with a 24 or more hour warning through the discord using Discord events.

6. Always log events. They are there to help you.

7. Never do events that are deathmatch. Examples are adding many antagonists or creating 'slop' rounds. Combat focused events are fine given that sufficient effort is given to ensure good roleplay.

8. In the case of events which are not meant to end the round, said events should always seek to minimize round removal.

9. Trial Admins should not run events of any scale without full admin oversight. Any events need to be logged for the sake of tracking and training purposes.

10. Junior Admins may only perform events that are administrative or 'Admemes'. Junior Admins may still develop and run major events as long as there are at least TWO full Admins to assist and approve.

11. Failure to log events when logging is required will lead to an admin review which may result in a strike. A repeated pattern of failing to log events will result in automatic assumption of wrongdoing and result in disciplinary action. Logging events is there to protect you.
----

=== Event Types ===
All event types can be logged; however, it is only required in the specific instances outlined in this document. Failure to log an event when logging is required will lead to admin review. '''ALL''' events that involve an admin playing a character or entity that is not physically at Central Command must be logged. Players should be given the chance to play event characters, not admins.

==== Administrative ====
{| class="mw-collapsible mw-collapsed"
| 
|-
|Administrative events are normal and expected outcome of adminning. Reporting these is not required and should be done in cases where you expect there may be dissent with how something was done. Junior admins and above have full authority to conduct and approve administrative events according to their judgement.

# Answering Prayers
# Answering Faxes
# Sending ERT
# Enforcement of Non-Codified but publicly announced Admin Rulings
# Spawning a CC Intern to handle faxes. It is the admin's responsibility to ensure each intern does not cause issues.

===== Prayers =====
These are to ensure that players who interact with the prayer system have a consistent experience. Prayers are a roleplay mechanic and if you, as an admin, do not want to be bothered by prayers, do not answer them.

''When answering a Prayer with an Item or Smite:''

* Prayers should be answered literally. This can be either granting what the player intended, or by applying a literal interpretation in the form of a monkey's paw answer. '''Monkey's Paws are NEVER in direct contradiction''' with the literal wording of the prayer.
* If this answer of the prayer may have an effect on round flow, take into consideration on if granting it is reasonable.
* If you asked for an offering, grant the item when the offering is received with no strings attached. This is void if the offering WAS strings (IE, pledge yourself to my cause.)
* You may tell the player that their prayer has angered you. If the player continues to use prayers, further negative responses to them do not have to follow prayer guidelines.
* You may otherwise answer with subtle messages that make sense contextually with the prayer. If in round information is provided, it should be given in a riddle, puzzle, or some other cryptic format.
The god in charge of the altar where the player prays may be taken into account when decided how to answer the prayer, but the above guidelines should still be followed.

===== Faxes =====
These are to ensure that players who interact with the fax system have a consistent experience. Faxes are a roleplay mechanic and well-made responses to them can enhance their experience.

''When answering a Fax from a player:''

* Consider the amount of effort. If there are faxes with effort put in, these should be taken more seriously.
* Central Command should take complaints raised against Command Members or CCVIPs/Officials seriously.
* Central Command should avoid responding to faxes not sent by Command or CCVIPs/Officials unless it is a proper form or grounded complaint.
* Central Command should not answer faxes that have not been signed or stamped by any individual on the station.
* Central Command should only approve requests or reply in ways that are likely to enhance a player's experiences. Some situations you could send them a live pipe bomb which would improve their game experience by being funny. There is quite a bit of leeway.
* Central Command should usually only provide reasonable items via bluespace to assist the crew. What is reasonable is your discretion but it should not alter round flow in large ways.

===== Emergency Response Team (ERT) =====
ERT is a tool used for story telling. Admins have discretion to use this in situations where it could improve the situation and make it more fun for all parties involved. If you do not want to use it, there is no need to spawn them.

''When thinking on sending ERT:''

* You should consider the situation from an in-character perspective as an official in Central Command. Use information you have received via the Red Phone and the faxes as well as the credibility of the source.
* Take into context the effort of the form filled out and if it shows that an intervention of Central Command is needed.
* You should also consider the situation from an OOC admin perspective. Would ERT improve the round for everyone or would it just cause stall? Would ERT significantly turn the tides on an antagonist who deserves to win? If in doubt, ask the antagonists if they would like the challenge.
* If OOC rules were broken by the antagonists, the leeway for sending ERT in response even if the antagonist deserves to win, is a lot higher. Do what feels right for the players as a whole.

In general, send a force that matches the situation. If ERT is being used for non-combat purposes, consider giving them tools to fit the situation instead of more weapons.

|
|}

==== Admin Memes (Admemes) ====
Admemes are small events that are usually low impact, spawn and forget occurrences. These typically require no oversight once set in motion. These should be logged if they affect the round in a larger capacity.

Admins are expected to remain in round until the conclusion of admemes in the event that something does go wrong. If you cannot remain in round then you must log it in the event channel. Junior Admins and above can perform admemes according to their discretion. Junior admins must log all admemes.
{| class="mw-collapsible mw-collapsed"
| 
|-
|
|}

Event Policy

2026-05-05T14:27:38Z

Huhm: Protected "Event Policy" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

====== The Purpose of Events ======
Events serve the purpose of increasing player engagement by providing fresh, interesting, and dynamic content. Events are never solely for admin enjoyment but that can be a side effect of events.

Events which intentionally exclude players, or encourage players to harass or antagonize others without any meaningful way to be handled in character should be avoided. Events are '''FOR THE PLAYERS.'''

=== Core Rules ===
1. Do not directly interfere in another admin's event without explicit permission from that admin.
2. Do not run events back to back with another event, especially Major events.

3. Events should never be purposefully exclusive to any member of crew, and should not encourage harassment or misconduct towards others

4. Events that leave crew with no resolution or means to combat the situation in a clear manner should be avoided.

5. There should always be player driven reason for an event to occur. Examples are a player prayer, game mode playtest, or player vote before the rounds. Major events can happen regardless with a 24 or more hour warning through the discord using Discord events.

6. Always log events. They are there to help you.

7. Never do events that are deathmatch. Examples are adding many antagonists or creating 'slop' rounds. Combat focused events are fine given that sufficient effort is given to ensure good roleplay.

8. In the case of events which are not meant to end the round, said events should always seek to minimize round removal.

9. Trial Admins should not run events of any scale without full admin oversight. Any events need to be logged for the sake of tracking and training purposes.

10. Junior Admins may only perform events that are administrative or 'Admemes'. Junior Admins may still develop and run major events as long as there are at least TWO full Admins to assist and approve.

11. Failure to log events when logging is required will lead to an admin review which may result in a strike. A repeated pattern of failing to log events will result in automatic assumption of wrongdoing and result in disciplinary action. Logging events is there to protect you.
----

=== Event Types ===
All event types can be logged; however, it is only required in the specific instances outlined in this document. Failure to log an event when logging is required will lead to admin review. '''ALL''' events that involve an admin playing a character or entity that is not physically at Central Command must be logged. Players should be given the chance to play event characters, not admins.

==== Administrative ====
{| class="mw-collapsible mw-collapsed"
| 
|-
|Administrative events are normal and expected outcome of adminning. Reporting these is not required and should be done in cases where you expect there may be dissent with how something was done. Junior admins and above have full authority to conduct and approve administrative events according to their judgement.

# Answering Prayers
# Answering Faxes
# Sending ERT
# Enforcement of Non-Codified but publicly announced Admin Rulings
# Spawning a CC Intern to handle faxes. It is the admin's responsibility to ensure each intern does not cause issues.

===== Prayers =====
These are to ensure that players who interact with the prayer system have a consistent experience. Prayers are a roleplay mechanic and if you, as an admin, do not want to be bothered by prayers, do not answer them.

''When answering a Prayer with an Item or Smite:''

* Prayers should be answered literally. This can be either granting what the player intended, or by applying a literal interpretation in the form of a monkey's paw answer. '''Monkey's Paws are NEVER in direct contradiction''' with the literal wording of the prayer.
* If this answer of the prayer may have an effect on round flow, take into consideration on if granting it is reasonable.
* If you asked for an offering, grant the item when the offering is received with no strings attached. This is void if the offering WAS strings (IE, pledge yourself to my cause.)
* You may tell the player that their prayer has angered you. If the player continues to use prayers, further negative responses to them do not have to follow prayer guidelines.
* You may otherwise answer with subtle messages that make sense contextually with the prayer. If in round information is provided, it should be given in a riddle, puzzle, or some other cryptic format.
The god in charge of the altar where the player prays may be taken into account when decided how to answer the prayer, but the above guidelines should still be followed.

==== Faxes ====
These are to ensure that players who interact with the fax system have a consistent experience. Faxes are a roleplay mechanic and well-made responses to them can enhance their experience.

''When answering a Fax from a player:''

* Consider the amount of effort. If there are faxes with effort put in, these should be taken more seriously.
* Central Command should take complaints raised against Command Members or CCVIPs/Officials seriously.
* Central Command should avoid responding to faxes not sent by Command or CCVIPs/Officials unless it is a proper form or grounded complaint.
* Central Command should not answer faxes that have not been signed or stamped by any individual on the station.
* Central Command should only approve requests or reply in ways that are likely to enhance a player's experiences. Some situations you could send them a live pipe bomb which would improve their game experience by being funny. There is quite a bit of leeway.
* Central Command should usually only provide reasonable items via bluespace to assist the crew. What is reasonable is your discretion but it should not alter round flow in large ways.

==== Emergency Response Team (ERT) ====
ERT is a tool used for story telling. Admins have discretion to use this in situations where it could improve the situation and make it more fun for all parties involved. If you do not want to use it, there is no need to spawn them.

''When thinking on sending ERT:''

* You should consider the situation from an in-character perspective as an official in Central Command. Use information you have received via the Red Phone and the faxes as well as the credibility of the source.
* Take into context the effort of the form filled out and if it shows that an intervention of Central Command is needed.
* You should also consider the situation from an OOC admin perspective. Would ERT improve the round for everyone or would it just cause stall? Would ERT significantly turn the tides on an antagonist who deserves to win? If in doubt, ask the antagonists if they would like the challenge.
* If OOC rules were broken by the antagonists, the leeway for sending ERT in response even if the antagonist deserves to win, is a lot higher. Do what feels right for the players as a whole.

In general, send a force that matches the situation. If ERT is being used for non-combat purposes, consider giving them tools to fit the situation instead of more weapons.

|
|}

Event Policy

2026-05-05T14:23:47Z

Huhm:

Event Policy

2026-05-05T14:22:00Z

Huhm: Huhm moved page Event policy to Event Policy without leaving a redirect

====== The Purpose of Events ======
Events serve the purpose of increasing player engagement by providing fresh, interesting, and dynamic content. Events are never solely for admin enjoyment but that can be a side effect of events.

Events which intentionally exclude players, or encourage players to harass or antagonize others without any meaningful way to be handled in character should be avoided. Events are '''FOR THE PLAYERS.'''

=== Core Rules ===
{| class="mw-collapsible mw-collapsed"
| 
|-
| 1. Do not directly interfere in another admin's event without explicit permission from that admin.
2. Do not run events back to back with another event, especially Major events.

3. Events should never be purposefully exclusive to any member of crew, and should not encourage harassment or misconduct towards others

4. Events that leave crew with no resolution or means to combat the situation in a clear manner should be avoided.

5. There should always be player driven reason for an event to occur. Examples are a player prayer, game mode playtest, or player vote before the rounds. Major events can happen regardless with a 24 or more hour warning through the discord using Discord events.

6. Always log events. They are there to help you.

7. Never do events that are deathmatch. Examples are adding many antagonists or creating 'slop' rounds. Combat focused events are fine given that sufficient effort is given to ensure good roleplay.

8. In the case of events which are not meant to end the round, said events should always seek to minimize round removal.

9. Trial Admins should not run events of any scale without full admin oversight. Any events need to be logged for the sake of tracking and training purposes.

10. Junior Admins may only perform events that are administrative or 'Admemes'. Junior Admins may still develop and run major events as long as there are at least TWO full Admins to assist and approve.

11. Failure to log events when logging is required will lead to an admin review which may result in a strike. A repeated pattern of failing to log events will result in automatic assumption of wrongdoing and result in disciplinary action. Logging events is there to protect you.
|}
----
=== Event Types ===
All event types can be logged; however, it is only required in the specific instances outlined in this document. Failure to log an event when logging is required will lead to admin review. '''ALL''' events that involve an admin playing a character or entity that is not physically at Central Command must be logged. Players should be given the chance to play event characters, not admins.

==== Administrative ====
{| class="mw-collapsible mw-collapsed"
| 
|-
|Administrative events are normal and expected outcome of adminning. Reporting these is not required and should be done in cases where you expect there may be dissent with how something was done. Junior admins and above have full authority to conduct and approve administrative events according to their judgement.

# Answering Prayers
# Answering Faxes
# Sending ERT
# Enforcement of Non-Codified but publicly announced Admin Rulings
# Spawning a CC Intern to handle faxes. It is the admin's responsibility to ensure each intern does not cause issues.

===== Prayers =====
These are to ensure that players who interact with the prayer system have a consistent experience. Prayers are a roleplay mechanic and if you, as an admin, do not want to be bothered by prayers, do not answer them.

''When answering a Prayer with an Item or Smite:''

* Prayers should be answered literally. This can be either granting what the player intended, or by applying a literal interpretation in the form of a monkey's paw answer. '''Monkey's Paws are NEVER in direct contradiction''' with the literal wording of the prayer.
* If this answer of the prayer may have an effect on round flow, take into consideration on if granting it is reasonable.
* If you asked for an offering, grant the item when the offering is received with no strings attached. This is void if the offering WAS strings (IE, pledge yourself to my cause.)
* You may tell the player that their prayer has angered you. If the player continues to use prayers, further negative responses to them do not have to follow prayer guidelines.
* You may otherwise answer with subtle messages that make sense contextually with the prayer. If in round information is provided, it should be given in a riddle, puzzle, or some other cryptic format.
The god in charge of the altar where the player prays may be taken into account when decided how to answer the prayer, but the above guidelines should still be followed.

==== Faxes ====
These are to ensure that players who interact with the fax system have a consistent experience. Faxes are a roleplay mechanic and well-made responses to them can enhance their experience.

''When answering a Fax from a player:''

* Consider the amount of effort. If there are faxes with effort put in, these should be taken more seriously.
* Central Command should take complaints raised against Command Members or CCVIPs/Officials seriously.
* Central Command should avoid responding to faxes not sent by Command or CCVIPs/Officials unless it is a proper form or grounded complaint.
* Central Command should not answer faxes that have not been signed or stamped by any individual on the station.
* Central Command should only approve requests or reply in ways that are likely to enhance a player's experiences. Some situations you could send them a live pipe bomb which would improve their game experience by being funny. There is quite a bit of leeway.
* Central Command should usually only provide reasonable items via bluespace to assist the crew. What is reasonable is your discretion but it should not alter round flow in large ways.

==== Emergency Response Team (ERT) ====
ERT is a tool used for story telling. Admins have discretion to use this in situations where it could improve the situation and make it more fun for all parties involved. If you do not want to use it, there is no need to spawn them.

''When thinking on sending ERT:''

* You should consider the situation from an in-character perspective as an official in Central Command. Use information you have received via the Red Phone and the faxes as well as the credibility of the source.
* Take into context the effort of the form filled out and if it shows that an intervention of Central Command is needed.
* You should also consider the situation from an OOC admin perspective. Would ERT improve the round for everyone or would it just cause stall? Would ERT significantly turn the tides on an antagonist who deserves to win? If in doubt, ask the antagonists if they would like the challenge.
* If OOC rules were broken by the antagonists, the leeway for sending ERT in response even if the antagonist deserves to win, is a lot higher. Do what feels right for the players as a whole.

In general, send a force that matches the situation. If ERT is being used for non-combat purposes, consider giving them tools to fit the situation instead of more weapons.

|
|}

Event Policy

2026-05-05T14:21:03Z

Huhm: Created Event Policy pt 1

====== The Purpose of Events ======
Events serve the purpose of increasing player engagement by providing fresh, interesting, and dynamic content. Events are never solely for admin enjoyment but that can be a side effect of events.

Events which intentionally exclude players, or encourage players to harass or antagonize others without any meaningful way to be handled in character should be avoided. Events are '''FOR THE PLAYERS.'''

=== Core Rules ===
{| class="mw-collapsible mw-collapsed"
| 
|-
| 1. Do not directly interfere in another admin's event without explicit permission from that admin.
2. Do not run events back to back with another event, especially Major events.

3. Events should never be purposefully exclusive to any member of crew, and should not encourage harassment or misconduct towards others

4. Events that leave crew with no resolution or means to combat the situation in a clear manner should be avoided.

5. There should always be player driven reason for an event to occur. Examples are a player prayer, game mode playtest, or player vote before the rounds. Major events can happen regardless with a 24 or more hour warning through the discord using Discord events.

6. Always log events. They are there to help you.

7. Never do events that are deathmatch. Examples are adding many antagonists or creating 'slop' rounds. Combat focused events are fine given that sufficient effort is given to ensure good roleplay.

8. In the case of events which are not meant to end the round, said events should always seek to minimize round removal.

9. Trial Admins should not run events of any scale without full admin oversight. Any events need to be logged for the sake of tracking and training purposes.

10. Junior Admins may only perform events that are administrative or 'Admemes'. Junior Admins may still develop and run major events as long as there are at least TWO full Admins to assist and approve.

11. Failure to log events when logging is required will lead to an admin review which may result in a strike. A repeated pattern of failing to log events will result in automatic assumption of wrongdoing and result in disciplinary action. Logging events is there to protect you.
|}
----
=== Event Types ===
All event types can be logged; however, it is only required in the specific instances outlined in this document. Failure to log an event when logging is required will lead to admin review. '''ALL''' events that involve an admin playing a character or entity that is not physically at Central Command must be logged. Players should be given the chance to play event characters, not admins.

==== Administrative ====
{| class="mw-collapsible mw-collapsed"
| 
|-
|Administrative events are normal and expected outcome of adminning. Reporting these is not required and should be done in cases where you expect there may be dissent with how something was done. Junior admins and above have full authority to conduct and approve administrative events according to their judgement.

# Answering Prayers
# Answering Faxes
# Sending ERT
# Enforcement of Non-Codified but publicly announced Admin Rulings
# Spawning a CC Intern to handle faxes. It is the admin's responsibility to ensure each intern does not cause issues.

===== Prayers =====
These are to ensure that players who interact with the prayer system have a consistent experience. Prayers are a roleplay mechanic and if you, as an admin, do not want to be bothered by prayers, do not answer them.

''When answering a Prayer with an Item or Smite:''

* Prayers should be answered literally. This can be either granting what the player intended, or by applying a literal interpretation in the form of a monkey's paw answer. '''Monkey's Paws are NEVER in direct contradiction''' with the literal wording of the prayer.
* If this answer of the prayer may have an effect on round flow, take into consideration on if granting it is reasonable.
* If you asked for an offering, grant the item when the offering is received with no strings attached. This is void if the offering WAS strings (IE, pledge yourself to my cause.)
* You may tell the player that their prayer has angered you. If the player continues to use prayers, further negative responses to them do not have to follow prayer guidelines.
* You may otherwise answer with subtle messages that make sense contextually with the prayer. If in round information is provided, it should be given in a riddle, puzzle, or some other cryptic format.
The god in charge of the altar where the player prays may be taken into account when decided how to answer the prayer, but the above guidelines should still be followed.

==== Faxes ====
These are to ensure that players who interact with the fax system have a consistent experience. Faxes are a roleplay mechanic and well-made responses to them can enhance their experience.

''When answering a Fax from a player:''

* Consider the amount of effort. If there are faxes with effort put in, these should be taken more seriously.
* Central Command should take complaints raised against Command Members or CCVIPs/Officials seriously.
* Central Command should avoid responding to faxes not sent by Command or CCVIPs/Officials unless it is a proper form or grounded complaint.
* Central Command should not answer faxes that have not been signed or stamped by any individual on the station.
* Central Command should only approve requests or reply in ways that are likely to enhance a player's experiences. Some situations you could send them a live pipe bomb which would improve their game experience by being funny. There is quite a bit of leeway.
* Central Command should usually only provide reasonable items via bluespace to assist the crew. What is reasonable is your discretion but it should not alter round flow in large ways.

==== Emergency Response Team (ERT) ====
ERT is a tool used for story telling. Admins have discretion to use this in situations where it could improve the situation and make it more fun for all parties involved. If you do not want to use it, there is no need to spawn them.

''When thinking on sending ERT:''

* You should consider the situation from an in-character perspective as an official in Central Command. Use information you have received via the Red Phone and the faxes as well as the credibility of the source.
* Take into context the effort of the form filled out and if it shows that an intervention of Central Command is needed.
* You should also consider the situation from an OOC admin perspective. Would ERT improve the round for everyone or would it just cause stall? Would ERT significantly turn the tides on an antagonist who deserves to win? If in doubt, ask the antagonists if they would like the challenge.
* If OOC rules were broken by the antagonists, the leeway for sending ERT in response even if the antagonist deserves to win, is a lot higher. Do what feels right for the players as a whole.

In general, send a force that matches the situation. If ERT is being used for non-combat purposes, consider giving them tools to fit the situation instead of more weapons.

|
|}

Banning Policy

2026-03-15T00:19:32Z

Huhm: Fixed Dewhitelist and Leave during ahelp

The Funky Station banning policy tries to encompass most things that players would do in the game. However, admins may invoke the Golden Rule of "All Admin Rulings Are Final" if there is a rule-break that does not fit neatly in this category.

There are special circumstances involving a de-whitelist. You can find more information within the de-whitelisting sections.

These rules are ultimately created to ensure the best possible player experience. Rules may change if the admin team finds that a certain rule or set of rules actively hinders the player experience.

=== Terms used in the tables below: ===

* GB : Game Ban; a ban from playing on all Funky servers for the allotted duration or appeal-only. The player is not allowed to join via other accounts or changing IP addresses, which will be punished with a heavier punishment.
* RB : Role Ban; a ban from playing a specific role on all Funky servers, usually spanning an entire Department. The player is allowed to play other roles.

== Non-grouping offenses ==

These offenses are either very minor or cannot be sorted nicely into other groups.

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Non-grouping
| Harassing staff (e.g. doxxing)
| Indef GB
|
|
|
|-
| Non-grouping
| Slurs, excluding R-slur and variants
| Indef GB
|
|
|
|-
| Non-grouping
| R-slur and variants
| W
| Appeal GB
|
|
|-
| Non-grouping
| Usage of "gay" as a pejorative
| W
| Appeal GB
|
|
|-
| Non-grouping
| Bigotry/discrimination
| Indef GB
|
|
|
|-
| Non-grouping
| ERP
| Indef GB
|
|
|
|-
| Non-grouping
| Sexual content
| W - 3d GB
| 7d GB
| Indef GB
|
|-
| Non-grouping
| Metacommunications
| W - 7d GB (ask first, especially if new)
| Indef GB
|
|
|-
| Non-grouping
| Ban Evasion
| Voucher Ban
| If after an accepted voucher ban, permanent ban. Otherwise, extend voucher ban to 6 months from evasion attempt.
|
|
|-
| Non-grouping
| NITRP (No Intent to Roleplay)
| Warning
| De-whitelist
|
|
|-
| Non-grouping
| Multi-keying
| Indef GB
|
|
|
|-
| Non-grouping
| OOC Toxicity
| W - 12h GB
| 3d - 7d GB
| Indef GB
|
|-
| Non-grouping
| Ahelp misuse / abuse
| W - 12hr GB
| W - 3d GB
| 3d - 7.5d GB
|
|-
| Non-grouping
| Threats to ahelp
| W - 12hr GB
| 12hr - 3d GB
| 7d - 7.5d GB
|
|-
| Non-grouping
| Under 16
| Indef GB
|
|
|
|-
| Non-grouping
| Bad character name
| W
| 1d - 3d GB
| 7d - 7.5d GB
|
|}

== Language offenses ==

Offenses that involve speaking a different language other than English on Funky Station servers.

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Language
| Non-english chat
| W
| W - 12hr GB
| 3d GB
| 7d - 7.5d GB
|-
| Language
| Solely non-english chat
| W
| Indef GB
|
|
|}

== Exploit offenses ==

Using cheat clients, or otherwise taking advantage of bugs that give you an unfair advantage.

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| 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
|}

== Metagaming offenses ==

Using information in a round that was obtained unfairly (for example, using info gathered as a ghost).

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Metagaming
| IC in OOC / LOOC abuse
| W
| W - 12hr GB
| 3d GB
| 7d - 7.5d GB
|-
| Metagaming
| Powergaming
| W - 12hr GB
| 12hr - 3d GB
| 3d - 7.5d GB
|
|-
| Metagaming
| Using info from death
| 12hr - 2d GB
| 3d GB
| 7d - 7.5d GB
|
|-
| Metagaming
| Using info from past life
| 12hr - 2d GB
| 3d GB
| 7d - 7.5d GB
|
|-
| Metagaming
| Metagaming
| W - 12hr GB
| 12hr - 3d GB
| 3d - 7d GB
|
|}

== Familiar offenses ==

These are offenses that pertain to a player specifically playing a familiar role, like Remilia.

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Familiars
| Familiar griefing master
| 12hr GB
| 3d GB
| style="font-weight:bold;" | 7d - 7.5d GB
|
|-
| Familiars
| Unreasonable failure to obey orders
| W
| 12hr GB
| 3d GB
| 7d - 7.5d GB
|}

== AI Law offenses ==

Offenses that pertain to silicon players.

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| 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
|}

== Immersion offenses ==

Offenses that involve breaking the immersion of other players (for example, using emote chat to talk as a mime).

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Immersion
| Text speak
| W
| W
| W - 12hr GB
| W - 12hr GB
|-
| Immersion
| OOC terms IC (not including teaching, however encourage LOOC use)
| W
| W - 12hr GB
| 12hr - 3d GB
| 3d - 7.5d GB
|-
| Immersion
| Bypassing chat restrictions
| W
| W - 12hr GB
| 12hr - 3d GB
| 3d - 7.5d GB
|-
| Immersion
| Irresponsible antag play
| W - 12hr GB
| 1d - 3d GB
| 3d - 7d GB
|
|-
| Immersion
| Abusing /suicide
| W - 12hr GB
| 12hr - 3d GB
| 3d - 7d GB
|
|}

== Griefing offenses ==

Offenses that pertain to a player playing with no intent to roleplay or to explicitly troll other people.

{| class="wikitable"
|-
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Griefing
| End-Of-Round Grief (EORG)
| W-1d GB
| 3d GB
| 7d GB
|
|-
| Griefing
| Damage/disruption to arrivals/arrivals shuttle
| 12hr - 3d GB
| 3d - 7d GB
| 7d - 15d GB
|
|-
| Griefing
| Round stalling
| W - 12hr GB
| 12hr - 3d GB
| 3d - 7d GB
| 7d - 7.5d GB
|-
| Griefing
| Antagonist team sabotage
| 12hr - 3d GB
| 3d - Indef GB
| 7d - Indef GB
|
|-
| Griefing
| Early massive station sabotage (as antagonist)
| W - 12hr GB
| 12hr - 3d GB
| 7d - 7.5d 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 Command role
| W - 7d RB
| 3d - 7d RB
| Indef RB
|
|-
| Griefing
| Antag rolling
| 12hr - 3d GB
| 3d - 7d GB
| 7d - 7.5d GB
|
|}
This sub-category is explicitly NOT a punitive ban. Bans in this category will be resolved with a conversation with the admins, as we believe this is behavior that requires some more explanation, and not to be served with a ban that goes through the regular appeals process. The ban message will ask that you create a ticket in our Discord so we can speak with you directly, and in-private. Action in these categories is what is recommended, but whatever specific action the admin team does will be listed clearly on your message or ban message.
{| class="mw-collapsible mw-collapsed wikitable"
|+ style="white-space: nowrap" | Additional Clarification
|-
| No intent to engage with other players is distinct from no intent to roleplay, because this describes a behavior in which a person is perfectly willing to roleplay, but either chooses exclusive solo gimmicks, not play a round after a short period of time has passed, or otherwise create scenarios not conducive to roleplay.
|-
|A good example of this would be spending 2 hours off station mining, with zero interaction with the station. While completely allowed by your role, repeated behavior will flag admins and we will ask to have a conversation with the player in question.
|}

{| class="wikitable"
|-
! Grouping Category
! Behavior
! Action
|-
| Grass
| No intent to engage with other players
| Opening a ticket to establish dialogue with admins
|-
|Grass
|Playing an excessive amount during a single day
|Game ban with an explicit request to speak with admins
|}

== Out of Character offenses ==

Offenses that involve a character performing or advocating for actions that would not make sense in the context of the game or their characters' motivations. Characters with outrageous backstories are not an exception.

{| class="wikitable"
|-
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Out of Character
| Over-escalation
| W - 12hr GB
| 12hr - 3d GB
| 7d - 7.5d GB
|
|-
| Out of Character
| Over-escalation in the form of station sabotage
| 3d GB
| 7d GB
| 14d - 15d GB
|
|}

== Competence offenses ==

Offenses that pertain to a certain role not knowing what to do in a situation or doing/authorizing things that someone in that position in real life wouldn't do. Classic example would be a Research Director authorizing the activation of a Stationwide Destruction artifact.

{| class="mw-collapsible mw-collapsed wikitable"
|+ style="white-space: nowrap" | OOC Clarification
|-
| We specify OOC in both the unreasonable incompetence in role offense and abuse of a position of authority because there are scenarios where a command member or other member of a fairly important department could abuse their authority to gain an advantage that is not properly based in-character.
|-
|For example, a Quartermaster accepting a 1 speso bribe is considered OOC abuse and OOC unreasonable incompetence. Accepting a bribe for favors with the syndicate or for 20,000 spesos is explicitly allowed however, and encouraged to keep shifts dynamic and interesting.
|}

{| class="wikitable"
|-
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Competence
| OOC unreasonable incompetence in role
| W - 7d RB
| 7d - 15d RB
| Indef RB
|
|-
| Competence
| OOC 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¹
| 3d - 7d RB
| 7d - 15d RB
| Indef RB
|
|}

== Additional Clarification ==

¹Space Law is to be used as a guideline similar to this policy, however if something is egregious enough (like a 20 minute timer for trespassing) it is justification for OOC admin intervention.

=== Modifiers ===
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.

=== 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.

=== New player ===
If there is no prior warning for the same issue, and if the minimum suggestion is not an indefinite ban, reduce to warning at admin discretion and instruct to read the rules.

=== Caught before round effects ===
If there are no earlier similar issues, any issue caught before it affects the round and other players can be reduced to a warning at admin discretion.

=== Admin intervention ===
Any reduction, including to nothing, may be applied for any offense which is plausibly the result of admin intervention.

=== 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.
=== Offender is Command/Security ===
Apply a roleban that is twice the length of the ban.

=== Intentional rule breaking ===
Indefinite ban. 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.

=== Ban request/demand ===
Any player who demands or requests a ban can be banned indefinitely.

=== EORG ===
End-of-Round Grief (EORG) is classified, generally, as being needlessly violent or acting out-of-character once the round has literally or functionally ended, to the detriment of other players' enjoyment or immersion.
To list specifics, instances of EORG can include the following:

* Random deathmatch (usually abbreviated as RDM)

* Violence that was not mentioned in an ahelp prior to engaging in it. For instance, if you had an ongoing grudge with another character during the round, you should ahelp for permission before escalating it to End-of-Round violence, otherwise we will deem it as EORG.¹

* Destruction, deconstruction, or gross defacing of any CentComm assets, or of the Evacuation shuttle. This includes using an RCD or tools to tear down walls or spam the light fixtures, or using any kind of explosives at CentComm or on the shuttle.

* Any form of incredibly bothersome behavior, especially of which one could reasonably deem as uncharacteristic of how you have been roleplaying up until then. This means, for instance, you should not slip security as they're taking a prisoner to the CentComm brig, and you should not be stun-batoning people without reason.

Centcomm is a place for people to destress, roleplay, and talk about the shift. While you do not have to engage in this, it is expected that you allow others to.

Note that this rule does not apply to round-ending or rule-skirting antagonists such as: Zombies, Space Dragons and their carps, and ASCENDED Heretics.

¹Attacking someone at CentComm because they were your kill objective, or because you found out they killed your friend through the post-game results screen, will still be seen as EORG.

=== De-whitelist ===
'''When should de-whitelisting occur?'''

* During permabans.
* When a game ban offense would total more than 2 weeks, issue a 7-day game ban and de-whitelist as punishment instead of a 2-week game ban.
* Any 4x offenses without a guideline or 5x offenses should be treated as a permanent game ban along with a de-whitelist.
'''What if a player is already de-whitelisted and misbehaves on the new player weekend?'''

* Issue a voucher ban

'''What does de-whitelisting mean?'''

* Players cannot play Funky Station regularly except on new player weekends.
* Players will need to go through the whitelist application again via a different template on the forum.

''If a permaban or offense is appealed and accepted, the whitelist will be reissued.''

''Whitelists can be easily added or removed via the Funky Station Admin site. Just press remove (or add when adding it back).''

=== Leaving during an Ahelp ===
Indefinite appeal ban and open a ticket with the player to bring up the situation. Once the situation is handled, remove the ban and add the punishment ban, if any. If the player can be verifiably proven to have intentionally left an Ahelp in progress, becomes a permanent appeal ban.

Banning Policy

2026-03-15T00:00:30Z

Huhm: Added new de-whitelisting clause

The Funky Station banning policy tries to encompass most things that players would do in the game. However, admins may invoke the Golden Rule of "All Admin Rulings Are Final" if there is a rule-break that does not fit neatly in this category.

There are special circumstances involving a de-whitelist, and are only given out for 3-day or longer game bans, or for 1 week or longer role bans. The process to get re-whitelisted is explained below.

These rules are ultimately created to ensure the best possible player experience. Rules may change if the admin team finds that a certain rule or set of rules actively hinders the player experience.

=== Terms used in the tables below: ===

* GB : Game Ban; a ban from playing on all Funky servers for the allotted duration or appeal-only. The player is not allowed to join via other accounts or changing IP addresses, which will be punished with a heavier punishment.
* RB : Role Ban; a ban from playing a specific role on all Funky servers, usually spanning an entire Department. The player is allowed to play other roles.

== Non-grouping offenses ==

These offenses are either very minor or cannot be sorted nicely into other groups.

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Non-grouping
| Harassing staff (e.g. doxxing)
| Indef GB
|
|
|
|-
| Non-grouping
| Slurs, excluding R-slur and variants
| Indef GB
|
|
|
|-
| Non-grouping
| R-slur and variants
| W
| Appeal GB
|
|
|-
| Non-grouping
| Usage of "gay" as a pejorative
| W
| Appeal GB
|
|
|-
| Non-grouping
| Bigotry/discrimination
| Indef GB
|
|
|
|-
| Non-grouping
| ERP
| Indef GB
|
|
|
|-
| Non-grouping
| Sexual content
| W - 3d GB
| 7d GB
| Indef GB
|
|-
| Non-grouping
| Metacommunications
| W - 7d GB (ask first, especially if new)
| Indef GB
|
|
|-
| Non-grouping
| Ban Evasion
| Voucher Ban
| If after an accepted voucher ban, permanent ban. Otherwise, extend voucher ban to 6 months from evasion attempt.
|
|
|-
| Non-grouping
| NITRP (No Intent to Roleplay)
| Warning
| De-whitelist
|
|
|-
| Non-grouping
| Multi-keying
| Indef GB
|
|
|
|-
| Non-grouping
| OOC Toxicity
| W - 12h GB
| 3d - 7d GB
| Indef GB
|
|-
| Non-grouping
| Ahelp misuse / abuse
| W - 12hr GB
| W - 3d GB
| 3d - 7.5d GB
|
|-
| Non-grouping
| Threats to ahelp
| W - 12hr GB
| 12hr - 3d GB
| 7d - 7.5d GB
|
|-
| Non-grouping
| Under 16
| Indef GB
|
|
|
|-
| Non-grouping
| Bad character name
| W
| 1d - 3d GB
| 7d - 7.5d GB
|
|}

== Language offenses ==

Offenses that involve speaking a different language other than English on Funky Station servers.

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Language
| Non-english chat
| W
| W - 12hr GB
| 3d GB
| 7d - 7.5d GB
|-
| Language
| Solely non-english chat
| W
| Indef GB
|
|
|}

== Exploit offenses ==

Using cheat clients, or otherwise taking advantage of bugs that give you an unfair advantage.

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| 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
|}

== Metagaming offenses ==

Using information in a round that was obtained unfairly (for example, using info gathered as a ghost).

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Metagaming
| IC in OOC / LOOC abuse
| W
| W - 12hr GB
| 3d GB
| 7d - 7.5d GB
|-
| Metagaming
| Powergaming
| W - 12hr GB
| 12hr - 3d GB
| 3d - 7.5d GB
|
|-
| Metagaming
| Using info from death
| 12hr - 2d GB
| 3d GB
| 7d - 7.5d GB
|
|-
| Metagaming
| Using info from past life
| 12hr - 2d GB
| 3d GB
| 7d - 7.5d GB
|
|-
| Metagaming
| Metagaming
| W - 12hr GB
| 12hr - 3d GB
| 3d - 7d GB
|
|}

== Familiar offenses ==

These are offenses that pertain to a player specifically playing a familiar role, like Remilia.

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Familiars
| Familiar griefing master
| 12hr GB
| 3d GB
| style="font-weight:bold;" | 7d - 7.5d GB
|
|-
| Familiars
| Unreasonable failure to obey orders
| W
| 12hr GB
| 3d GB
| 7d - 7.5d GB
|}

== AI Law offenses ==

Offenses that pertain to silicon players.

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| 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
|}

== Immersion offenses ==

Offenses that involve breaking the immersion of other players (for example, using emote chat to talk as a mime).

{| class="wikitable"
|- style="font-weight:bold;"
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Immersion
| Text speak
| W
| W
| W - 12hr GB
| W - 12hr GB
|-
| Immersion
| OOC terms IC (not including teaching, however encourage LOOC use)
| W
| W - 12hr GB
| 12hr - 3d GB
| 3d - 7.5d GB
|-
| Immersion
| Bypassing chat restrictions
| W
| W - 12hr GB
| 12hr - 3d GB
| 3d - 7.5d GB
|-
| Immersion
| Irresponsible antag play
| W - 12hr GB
| 1d - 3d GB
| 3d - 7d GB
|
|-
| Immersion
| Abusing /suicide
| W - 12hr GB
| 12hr - 3d GB
| 3d - 7d GB
|
|}

== Griefing offenses ==

Offenses that pertain to a player playing with no intent to roleplay or to explicitly troll other people.

{| class="wikitable"
|-
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Griefing
| End-Of-Round Grief (EORG)
| W-1d GB
| 3d GB
| 7d GB
|
|-
| Griefing
| Damage/disruption to arrivals/arrivals shuttle
| 12hr - 3d GB
| 3d - 7d GB
| 7d - 15d GB
|
|-
| Griefing
| Round stalling
| W - 12hr GB
| 12hr - 3d GB
| 3d - 7d GB
| 7d - 7.5d GB
|-
| Griefing
| Antagonist team sabotage
| 12hr - 3d GB
| 3d - Indef GB
| 7d - Indef GB
|
|-
| Griefing
| Early massive station sabotage (as antagonist)
| W - 12hr GB
| 12hr - 3d GB
| 7d - 7.5d 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 Command role
| W - 7d RB
| 3d - 7d RB
| Indef RB
|
|-
| Griefing
| Antag rolling
| 12hr - 3d GB
| 3d - 7d GB
| 7d - 7.5d GB
|
|}
This sub-category is explicitly NOT a punitive ban. Bans in this category will be resolved with a conversation with the admins, as we believe this is behavior that requires some more explanation, and not to be served with a ban that goes through the regular appeals process. The ban message will ask that you create a ticket in our Discord so we can speak with you directly, and in-private. Action in these categories is what is recommended, but whatever specific action the admin team does will be listed clearly on your message or ban message.
{| class="mw-collapsible mw-collapsed wikitable"
|+ style="white-space: nowrap" | Additional Clarification
|-
| No intent to engage with other players is distinct from no intent to roleplay, because this describes a behavior in which a person is perfectly willing to roleplay, but either chooses exclusive solo gimmicks, not play a round after a short period of time has passed, or otherwise create scenarios not conducive to roleplay.
|-
|A good example of this would be spending 2 hours off station mining, with zero interaction with the station. While completely allowed by your role, repeated behavior will flag admins and we will ask to have a conversation with the player in question.
|}

{| class="wikitable"
|-
! Grouping Category
! Behavior
! Action
|-
| Grass
| No intent to engage with other players
| Opening a ticket to establish dialogue with admins
|-
|Grass
|Playing an excessive amount during a single day
|Game ban with an explicit request to speak with admins
|}

== Out of Character offenses ==

Offenses that involve a character performing or advocating for actions that would not make sense in the context of the game or their characters' motivations. Characters with outrageous backstories are not an exception.

{| class="wikitable"
|-
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Out of Character
| Over-escalation
| W - 12hr GB
| 12hr - 3d GB
| 7d - 7.5d GB
|
|-
| Out of Character
| Over-escalation in the form of station sabotage
| 3d GB
| 7d GB
| 14d - 15d GB
|
|}

== Competence offenses ==

Offenses that pertain to a certain role not knowing what to do in a situation or doing/authorizing things that someone in that position in real life wouldn't do. Classic example would be a Research Director authorizing the activation of a Stationwide Destruction artifact.

{| class="mw-collapsible mw-collapsed wikitable"
|+ style="white-space: nowrap" | OOC Clarification
|-
| We specify OOC in both the unreasonable incompetence in role offense and abuse of a position of authority because there are scenarios where a command member or other member of a fairly important department could abuse their authority to gain an advantage that is not properly based in-character.
|-
|For example, a Quartermaster accepting a 1 speso bribe is considered OOC abuse and OOC unreasonable incompetence. Accepting a bribe for favors with the syndicate or for 20,000 spesos is explicitly allowed however, and encouraged to keep shifts dynamic and interesting.
|}

{| class="wikitable"
|-
! Grouping Category
! Offense
! First Offense
! Second Offense
! Third Offense
! Fourth Offense
|-
| Competence
| OOC unreasonable incompetence in role
| W - 7d RB
| 7d - 15d RB
| Indef RB
|
|-
| Competence
| OOC 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¹
| 3d - 7d RB
| 7d - 15d RB
| Indef RB
|
|}

== Additional Clarification ==

¹Space Law is to be used as a guideline similar to this policy, however if something is egregious enough (like a 20 minute timer for trespassing) it is justification for OOC admin intervention.

=== Modifiers ===
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.

=== 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.

=== New player ===
If there is no prior warning for the same issue, and if the minimum suggestion is not an indefinite ban, reduce to warning at admin discretion and instruct to read the rules.

=== Caught before round effects ===
If there are no earlier similar issues, any issue caught before it affects the round and other players can be reduced to a warning at admin discretion.

=== Admin intervention ===
Any reduction, including to nothing, may be applied for any offense which is plausibly the result of admin intervention.

=== 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.
=== Offender is Command/Security ===
Apply a roleban that is twice the length of the ban.

=== Intentional rule breaking ===
Indefinite ban. 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.

=== Ban request/demand ===
Any player who demands or requests a ban can be banned indefinitely.

=== EORG ===
End-of-Round Grief (EORG) is classified, generally, as being needlessly violent or acting out-of-character once the round has literally or functionally ended, to the detriment of other players' enjoyment or immersion.
To list specifics, instances of EORG can include the following:

* Random deathmatch (usually abbrieviated as RDM)

* Violence that was not mentioned in an ahelp prior to engaging in it. For instance, if you had an ongoing grudge with another character during the round, you should ahelp for permission before escalating it to End-of-Round violence, otherwise we will deem it as EORG.¹

* Destruction, deconstruction, or gross defacing of any CentComm assets, or of the Evacuation shuttle. This includes using an RCD or tools to tear down walls or spam the light fixtures, or using any kind of explosives at CentComm or on the shuttle.

* Any form of incredibly bothersome behavior, especially of which one could reasonably deem as uncharacteristic of how you have been roleplaying up until then. This means, for instance, you should not slip security as they're taking a prisoner to the CentComm brig, and you should not be stun-batoning people without reason.

Centcomm is a place for people to destress, roleplay, and talk about the shift. While you do not have to engage in this, it is expected that you allow others to.

Note that this rule does not apply to round-ending or rule-skirting antagonists such as: Zombies, Space Dragons and their carps, and ASCENDED Heretics.

¹Attacking someone at CentComm because they were your kill objective, or because you found out they killed your friend through the post-game results screen, will still be seen as EORG.

=== De-whitelist ===
'''When should de-whitelisting occur?'''

* During permabans.
* When a game ban offense would total more than 2 weeks, issue a 7-day game ban and de-whitelist as punishment instead of a 2-week game ban.
* Any 4x offenses without a guideline or 5x offenses should be treated as a de-whitelist.

'''What does de-whitelisting mean?'''

* Players cannot play Funky Station regularly except on new player weekends.
* Players will need to go through the whitelist application again via a different template on the forum.

''If a permaban or offense is appealed and accepted, the whitelist will be reissued.''

''Whitelists can be easily added or removed via the Funky Station Admin site. Just press remove (or add when adding it back).''

=== Leaving during an Ahelp ===
Indefinite appeal ban

Adminning Policy

2026-03-12T19:41:48Z

Huhm: Updated HeadAdmin and Community Manager

Admin policy, including for things out-of-game, are listed here, and is the standard of how admins should interface with the community.

== Admin Rules ==
These apply to all individuals with access to staff chats, including but not limited to Admins and Community Moderators.
Admins will be held to the same standards as any other player regarding behavior ingame and on the Discord server, and any punishments/warnings will not take into account their status as an Admin.

#Be kind.
#Members of the Admin Team should also be on the Discord server for communications purposes. While actively adminning, admins should also be available on the Discord server. This does not apply while not adminned in-game.
#Admins should check the forums & tickets periodically.
#Admins should not leak or otherwise discuss staff channel discussions (including ingame Admin channel chats) outside of said staff channels without the express consent of all involved.
#Admins are expected to know and follow all game rules and rules imposed on Admins at all times.
#If you're the last admin online on one of the servers and you leave, shoot a Game Staff ping into the staff channel to let everyone know the server's deadminned.
#If you're playing, do not look at the staff chats, including the ahelp channels.
#Don't admin intoxicated, it has the opportunity to be unpleasant for everyone involved.
#Admins may admin while playing, but are expected to deadmin when playing important roles (AI, Command, Sec, Antags, etc.)
#It is recommended to only do so on low population, and all rules concerning metagaming apply heavily if an admin chooses to do so.
#Admins may not handle reports or ahelps concerning themselves and must ping other staff to do so.
#Admins may not utilize the staff chats to report behavior while they are in-round, they must use an ahelp or a ticket, same as any other player.
#Admins should not be discussing admin business, such as player punishments, outside of staff chats, with the exception of clarifying a misconception.
#Avoid publicly engaging with intra-server drama. As a member of staff you're a reflection of the server.

== Ranks / Structure ==
[[File:Rank Structure.png|thumb]]

=== Head Maintainer / Host ===
On the same level as the Head Admin, with a focus towards development.
Their duties relating to staffing extend to their responsibilities, powers, and ownership of the Funky Station servers and website.

=== Head Admin ===
On the same level as the Head Maintainer / Host, with a focus towards admin affairs. They are solely responsible for hiring new Admins and they are responsible for handling demotion procedure. They are also expected to handle rule clarifications and mediation when an issue arises between staff.
*Duties:
#Running once-a-month open applications for Admins
#Promoting Admins
#Heading disciplinary action on Admins following internal procedure
#Making sure ban appeals and admin complaints are handled in a timely manner
#Mediating and resolving any conflicts that arise within the staff team
#Organizing a staff meeting once a month
#Adjusting admin policies as they see fit

=== Community Manager ===
This role is directly under the Head Admin, and their primary duties lie in assisting the Head Admin with communication on behalf of the staff team to the rest of the community, as well as representing the Funky community to external communities. They also directly manage the Community Moderators and hire new ones.
*Duties:
#Handling hiring / demotion of Community Moderators with the assistance of the Head Admin
#Assisting the staff team in regards with communications to the community (e.g. announcements, clarifications, Discord/Forum rule enforcement)
#Acting as an ambassadorial role / representative to other communities

=== Admin ===
==== Full Admin ====
This is a full admin, trusted with full access to PII (IPs, HWIDs, connection log) on the admin website, access to the full-admin chat, and access to other administrative tools.
*Duties:
#Assist in acting as a mentor to Junior and Trial Admins
#Be able to handle the server independently and clarify rules when needed
#Be able to handle and moderate large-scale events with the assistance of 1 other admin
#Participate in discussions related to policy, rules, enforcement, and other important server business
#Participate in assembled groups for the handling of admin complaints

==== Junior Admin ====
This is the second phase of orientation, they have spawning permissions for the purpose of mild gimmicks and running minor events with full admin supervision. They additionally get access to the ban appeal discussion channels and are on the list of appeal-handlers.
The Head Admin should keep a tab on the Junior Admin and after 4 weeks make the decision on whether or not to promote them.
*Duties:
#Get a handle on your new abilities, including spawning and VV
#Start handling ban appeals with help from full admins
#Get a handle on running some minor events and the how-tos and whys of such (with full-mins present)

==== Trial Admin ====
This is the very base orientation phase of an Admin, they do not have spawning or View Variable permissions and are just expected to get a handle on moderation duties, community duties, and general conduct. Trial Admins should get first dibs to handle any ahelps that arise in-game, and a more senior admin should only help with advice / step in if requested, or if the situation escalates.
The Head Admin should keep a tab on the Trial Admin's progress, and after 2-4 weeks make the decision on whether or not to promote them.
*Duties:
#Ingratiate yourself with the staff team!
#Get comfortable with handling Community Duties and in-game moderation.

=== Community Moderator ===
This is a role that grants access to staff chats, and is intended primarily to moderate Discord and the Forums to prevent rulebreaks. They work under the Community Manager.
*Duties:
#Moderating the Discord and Forums for rulebreaks
#Mediating minor conflicts in the Discord so they don't get out of hand, and shutting them down if necessary

== Community Duties ==
All admins regardless of position are expected to do and check these regularly, as it is a large part of their out-of-game duties. If not claimed, the Head Admin may assign any of these to any admin as they deem fit.

=== Ban Appeals ===
#All Junior Admins and above can and are expected to handle ban appeals.
#If a ban appeal isn't 'claimed' by an admin within a day of it being made, the Head Admin will select, either randomly or through some other method, an admin to handle it.
#The banning admin may claim the appeal only if they intend to reduce or otherwise remove it.
#If the ban appeal is low effort, does not follow format, or is otherwise Deeply Unserious, close the ban appeal with a short explanation.
#When handling an appeal, put as much effort into the response as they did to their appeal. This isn't to say we encourage text walls, but an earnest appeal will be met with an earnest response.
#If you are handling the appeal, you must check the ahelp logs, player note and ban history, and contact the banning admin prior to any judgments. Depending on the appeal, it is also recommended to look through round logs and/or replay if necessary.
#You may ask the player questions for clarification, for which they should have a reasonable opportunity to respond.
#If the appeal is for a ban the length of a week or longer, the handling admin should make a vote to accept, deny, or shorten the ban, and ping Game Staff.
#If a vote is not required, the handling admin may make the judgment to accept or deny the appeal.
#If the ban has expired by the time the appeal is handled, the ban note may or may not be stricken from the player's record at the handling admin's discretion.

=== Admin Complaints ===
==== Against a Regular Admin ====
#The Head Admin reviews the complaint and decides if it is worthy enough to be considered.
#If it is, the Head Admin is to gather a team of at least 5 admins, including themselves, to review the complaint.
#The admin complaint is then reviewed and discussed among this team for 2 or so days. A message by either the Head Admin or another Admin part of the review team will post that it is being discussed.
#After discussion has concluded, a write-up about what went wrong and how to move forward from this will be posted on the Forum.

==== Against the Head Admin or Host ====
#If the complaint is about the Host, then the Head Admin will review it. If the complaint is about the Head Admin, then the Host will review it.
#If the complaint also requests that a regular admin review it, if it is worthy enough to review, then gather a team of 5, including themselves, to review the complaint.
#The review process is the same for both.

==== Whitelists ====
#Check individual's profile for blatantly offensive content (e.g. Nazi dogwhistles) - if any are found, they may be warned or banned depending on severity.
#Whitelists should only be run through when there is at least 1 admin ingame on either server.
#If the name is odd or something about the individual's profile tips you off, check their username for any active ban appeals. If none are found, they should be good to whitelist with no questions.
#If an active ban or ban appeal is found, it is encouraged to ask why in a private thread. Current precedent is recent active bans on other servers may require a successful ban appeal before whitelisting.
#If a whitelist fails to pass the standards, it should be set to pending until the issues are solved, or denied with a minimum 1-week time requirement to re-apply.

==== Replay Reviews ====
#Any individual can make a request for a replay review, either through an ahelp, a ban appeal or admin complaint, or through a ticket on the Discord.
#Bans and notes may be applied upon a replay review.
#If applying a ban or a note on a replay review, be sure to include the round number and timestamp. Note / Ban policy also applies here.

== Events ==

=== Rules ===
#If you're running a large event, you should have enough admin coverage for the round to do regular admin stuff while the event is being run. If this cannot be achieved, the event should not be run as moderation should take priority.
#Large events must be pre-planned, and if significant setup time is required (e.g. mapping), it should be coordinated on the GitHub.
#Large events should be primarily planned to run on Fridays. Funky Friday only drops the frequency expectation of events, all other rules apply.
#Events are a privilege and should not be performed to the detriment of all other admin tasks (primarily community work e.g. appeals, as well as in-game moderation)
#Don't interfere in another admin's planned event without communication.
#Limit yourself. If you're doing an event every round / other round, you're doing it too frequently. Events should be well thought-out, and not everything needs to be a bit. This is waived for exceptions such as: teaching new players on Sundays, or adjusting gamerules / adding antags for round balance reasons.
#Trial & Junior Admins should not run events of any scale without admin oversight. Exception is granted for minor things e.g. giving Cargo a mail teleporter, or CC fax responses that do not include anything of substance being sent/promised to the crew.
#Always log events in the event logs channel, even small ones.

=== Scheduling ===
#Scheduled events include any event that will substantially affect the game from the start of the round to the end, including any relying on manipulating mechanics or player behavior outside of roleplay.
#A Head Admin must greenlight the scheduled event (post it in the event ideas channel for this), and at least two full-admins must be available to oversee the entirety.
#Events requiring scheduling should be primarily planned to run on Fridays.
#Event frequency on Fridays is more lax compared to other days, but is limited to one event every other round.
#Scheduled events outside of Fridays must be announced to the players either prior to the round starting or earlier in the week.

=== Guidelines ===
#Events should aim to be inclusive to as many of the players as possible.
#The best events are typically those that most players wouldn't even think of as an admin event. Aim to keep things as ingame as possible - that is to say, avoid breaking immersion.
#If you end up running an event that ruins the round (it happens, minor things can spiral very quickly), it is recommended to apologize and give antag tokens to affected antagonists.
#Keep events player-friendly. Run them based on what's good for the round and players rather than what's funny to you at the moment. A good example is sending an ERT when half of the station is dead and 2 dragons are running free. A bad example is spawning yourself in as a deathsquad agent 15 minutes into the round.
#Events and role play at Central Command (post round) are generally allowed as long as they do not dramatically interfere with post round role play or encourage no-roleplay and EORG adjacent behaviors. Antagonist ghost roles / combat focused non crew roles should be avoided.

== Ahelps and Notes ==
=== Ahelp Policy ===
#The goal for tone is always to be approachable and somewhat casual, or at least polite. We are people dealing with other people and that should be kept at the forefront of an Ahelp. If someone is being rude to you in an Ahelp, be sure to mention the appropriate rule-break and issue a punishment in line with the admin policy.
#If you're Ahelping as a proactive investigation or as a non-serious message, keep it silent.
#Always check the notes of the player you are Ahelping or receiving an Ahelp from.
#Attempt to respond to an Ahelp in a reasonable timeframe, even if that response is just 'Looking into this.'
#Keep one admin maximum speaking to a player in an Ahelp unless you are explicitly handing it over to another, so the player does not feel dogpiled.
#Avoid messaging somebody who is in the middle of a situation unless highly necessary to avoid adding undue stress. People are way easier to speak to when they aren't trying to balance 5 things at once.
#If you are unsure about an action a player has done, Ahelp the player in question and ask additional clarifying questions. Ahelping to ask questions is encouraged in-order to get as much context as possible and to avoid accidentally banning someone for something that should have been a warning.
#Avoid making any punishments before you're positive you've fully reviewed applicable logs / have the necessary information required to make a judgment. A punishment, such as a warning or ban, is a last resort.
#If you feel frustrated / someone's going back-and-forth with you, sometimes you just need to step back and assess the situation. This may look like asking another admin to step in and handle the Ahelp, or it may look like a temporary ban. Point the offender to Rule 4 for this purpose. It is not healthy for either the admin nor the Ahelp-ee to get excessively worked up over what's typically a warning or a time-out from the game.
#Be sure to look at previous Admin Rulings to ensure we stay consistent on certain rulebreaks or grey areas.
#If a situation seems it's going to resolve itself IC, even if rules were broken, consider not messaging anyone over it, at the very least until after the situation resolves. The game runs smoother and people are happier when players feel like admins aren't breathing down their backs.

=== Notes ===
#Notes should be concise, with only the information they need, and detail a note on behavior or a warning given.
#Ahelp policy applies in notes, other admins and players do see these - 'Shitter Behavior' is not a good note, although possibly descriptive.
#Notes not ahelped over should be secreted, as are notes that are for a player 'toeing the line' rather than breaking a rule.
#Notes that were a formal warning should be visible.
#Notes that are over 3 months old should be considered as expired.
#Expired notes should not be considered when issuing punishment, unless permitted by the Head Admin.
#Expiry of Ban Notes should start after the ban has either been appealed or expires.
#Notes that fall under the Non-grouping and Language sections of the banning policy are exempt from expiry.

=== Watchlists ===
#Watchlists are to be placed primarily in cases of metacommunications and potential antag-rolling; they may also be placed for consistent, watchable, behavior (this should be very clearly observable) but should be used sparingly and in extreme cases.
#In the case of placement for antag-rolling, the watchlist should have a 2-4 week expiry.
#All other guidelines regarding notes also apply to watchlists.

== Admin Disciplinary Action ==
=== Strikes ===
#Strikes are formal written warnings from the Head Admin to any member of staff.
#They are a last-resort tool to be used on the track to demotion or lesser punishments, where minor corrections will not suffice and major admin policy breaks have occurred.
#While strikes aren't necessary for demotions in extreme cases (e.g. leaking of PII or other explicitly illegal activity), they are recommended to be used in cases of an admin abusing their tools or position over the playerbase, including breaches of admin policy or ingame rules in an unprofessional and consistent manner.
#Strikes will expire 2 months after they are applied.
#At two strikes, event privileges will be revoked.
#At three strikes, demotion will be brought up to a randomly picked group of 5 Admins.

=== Demotions ===
#Demotions are to be used only in extreme scenarios where an admin has consistently or extremely broken admin policy, and no other correction is feasible.
#The demotion process may be started by the Head Admin or Host.
#To demote a member of staff under normal procedure, a randomly picked group of 5 Admins must pass it by 2/3 majority, including the Head Admins.

Adminning Policy

2026-03-12T19:38:20Z

Huhm: Seniormin gone2

Admin policy, including for things out-of-game, are listed here, and is the standard of how admins should interface with the community.

== Admin Rules ==
These apply to all individuals with access to staff chats, including but not limited to Admins and Community Moderators.
Admins will be held to the same standards as any other player regarding behavior ingame and on the Discord server, and any punishments/warnings will not take into account their status as an Admin.

#Be kind.
#Members of the Admin Team should also be on the Discord server for communications purposes. While actively adminning, admins should also be available on the Discord server. This does not apply while not adminned in-game.
#Admins should check the forums & tickets periodically.
#Admins should not leak or otherwise discuss staff channel discussions (including ingame Admin channel chats) outside of said staff channels without the express consent of all involved.
#Admins are expected to know and follow all game rules and rules imposed on Admins at all times.
#If you're the last admin online on one of the servers and you leave, shoot a Game Staff ping into the staff channel to let everyone know the server's deadminned.
#If you're playing, do not look at the staff chats, including the ahelp channels.
#Don't admin intoxicated, it has the opportunity to be unpleasant for everyone involved.
#Admins may admin while playing, but are expected to deadmin when playing important roles (AI, Command, Sec, Antags, etc.)
#It is recommended to only do so on low population, and all rules concerning metagaming apply heavily if an admin chooses to do so.
#Admins may not handle reports or ahelps concerning themselves and must ping other staff to do so.
#Admins may not utilize the staff chats to report behavior while they are in-round, they must use an ahelp or a ticket, same as any other player.
#Admins should not be discussing admin business, such as player punishments, outside of staff chats, with the exception of clarifying a misconception.
#Avoid publicly engaging with intra-server drama. As a member of staff you're a reflection of the server.

== Ranks / Structure ==
[[File:Rank Structure.png|thumb]]

=== Head Maintainer / Host ===
On the same level as the Head Admin, with a focus towards development.
Their duties relating to staffing extend to their responsibilities, powers, and ownership of the Funky Station servers and website.

=== Head Admin ===
On the same level as the Head Maintainer / Host, with a focus towards admin affairs. They are solely responsible for hiring new Admins and Community Moderators, and with the support of the Senior Admins they are responsible for handling demotion procedure. They are also expected to handle rule clarifications and mediation when an issue arises between staff.
*Duties:
#Running once-a-month open applications for Admins
#Promoting Admins
#Heading disciplinary action on Admins following internal procedure
#Making sure ban appeals and admin complaints are handled in a timely manner
#Mediating and resolving any conflicts that arise within the staff team
#Organizing a staff meeting once a month
#Adjusting admin policies as they see fit

=== Community Manager ===
This role is directly under the Head Admin, same as the Senior Admins, and their primary duties lie in assisting the Head Admin with communication on behalf of the staff team to the rest of the community, as well as representing the Funky community to external communities. They also directly manage the Community Moderators.
*Duties:
#Handling hiring / demotion of Community Moderators with the assistance of the Head Admin
#Assisting the staff team in regards with communications to the community (e.g. announcements, clarifications, Discord/Forum rule enforcement)
#Acting as an ambassadorial role / representative to other communities

=== Admin ===
==== Full Admin ====
This is a full admin, trusted with full access to PII (IPs, HWIDs, connection log) on the admin website, access to the full-admin chat, and access to other administrative tools.
*Duties:
#Assist in acting as a mentor to Junior and Trial Admins
#Be able to handle the server independently and clarify rules when needed
#Be able to handle and moderate large-scale events with the assistance of 1 other admin
#Participate in discussions related to policy, rules, enforcement, and other important server business
#Participate in assembled groups for the handling of admin complaints

==== Junior Admin ====
This is the second phase of orientation, they have spawning permissions for the purpose of mild gimmicks and running minor events with full admin supervision. They additionally get access to the ban appeal discussion channels and are on the list of appeal-handlers.
The Head Admin should keep a tab on the Junior Admin and after 4 weeks make the decision on whether or not to promote them.
*Duties:
#Get a handle on your new abilities, including spawning and VV
#Start handling ban appeals with help from full admins
#Get a handle on running some minor events and the how-tos and whys of such (with full-mins present)

==== Trial Admin ====
This is the very base orientation phase of an Admin, they do not have spawning or View Variable permissions and are just expected to get a handle on moderation duties, community duties, and general conduct. Trial Admins should get first dibs to handle any ahelps that arise in-game, and a more senior admin should only help with advice / step in if requested, or if the situation escalates.
The Head Admin and Senior Admins should keep a tab on the Trial Admin's progress, and after 2-4 weeks make the decision on whether or not to promote them.
*Duties:
#Ingratiate yourself with the staff team!
#Get comfortable with handling Community Duties and in-game moderation.

=== Community Moderator ===
This is a role that grants access to staff chats, and is intended primarily to moderate Discord and the Forums to prevent rulebreaks. They work under the Community Manager.
*Duties:
#Moderating the Discord and Forums for rulebreaks
#Mediating minor conflicts in the Discord so they don't get out of hand, and shutting them down if necessary

== Community Duties ==
All admins regardless of position are expected to do and check these regularly, as it is a large part of their out-of-game duties. If not claimed, the Head Admin may assign any of these to any admin as they deem fit.

=== Ban Appeals ===
#All Junior Admins and above can and are expected to handle ban appeals.
#If a ban appeal isn't 'claimed' by an admin within a day of it being made, the Head Admin will select, either randomly or through some other method, an admin to handle it.
#The banning admin may claim the appeal only if they intend to reduce or otherwise remove it.
#If the ban appeal is low effort, does not follow format, or is otherwise Deeply Unserious, close the ban appeal with a short explanation.
#When handling an appeal, put as much effort into the response as they did to their appeal. This isn't to say we encourage text walls, but an earnest appeal will be met with an earnest response.
#If you are handling the appeal, you must check the ahelp logs, player note and ban history, and contact the banning admin prior to any judgments. Depending on the appeal, it is also recommended to look through round logs and/or replay if necessary.
#You may ask the player questions for clarification, for which they should have a reasonable opportunity to respond.
#If the appeal is for a ban the length of a week or longer, the handling admin should make a vote to accept, deny, or shorten the ban, and ping Game Staff.
#If a vote is not required, the handling admin may make the judgment to accept or deny the appeal.
#If the ban has expired by the time the appeal is handled, the ban note may or may not be stricken from the player's record at the handling admin's discretion.

=== Admin Complaints ===
==== Against a Regular Admin ====
#The Head Admin reviews the complaint and decides if it is worthy enough to be considered.
#If it is, the Head Admin is to gather a team of at least 5 admins, including themselves, to review the complaint.
#The admin complaint is then reviewed and discussed among this team for 2 or so days. A message by either the Head Admin or another Admin part of the review team will post that it is being discussed.
#After discussion has concluded, a write-up about what went wrong and how to move forward from this will be posted on the Forum.

==== Against the Head Admin or Host ====
#If the complaint is about the Host, then the Head Admin will review it. If the complaint is about the Head Admin, then the Host will review it.
#If the complaint also requests that a regular admin review it, if it is worthy enough to review, then gather a team of 5, including themselves, to review the complaint.
#The review process is the same for both.

==== Whitelists ====
#Check individual's profile for blatantly offensive content (e.g. Nazi dogwhistles) - if any are found, they may be warned or banned depending on severity.
#Whitelists should only be run through when there is at least 1 admin ingame on either server.
#If the name is odd or something about the individual's profile tips you off, check their username for any active ban appeals. If none are found, they should be good to whitelist with no questions.
#If an active ban or ban appeal is found, it is encouraged to ask why in a private thread. Current precedent is recent active bans on other servers may require a successful ban appeal before whitelisting.
#If a whitelist fails to pass the standards, it should be set to pending until the issues are solved, or denied with a minimum 1-week time requirement to re-apply.

==== Replay Reviews ====
#Any individual can make a request for a replay review, either through an ahelp, a ban appeal or admin complaint, or through a ticket on the Discord.
#Bans and notes may be applied upon a replay review.
#If applying a ban or a note on a replay review, be sure to include the round number and timestamp. Note / Ban policy also applies here.

== Events ==

=== Rules ===
#If you're running a large event, you should have enough admin coverage for the round to do regular admin stuff while the event is being run. If this cannot be achieved, the event should not be run as moderation should take priority.
#Large events must be pre-planned, and if significant setup time is required (e.g. mapping), it should be coordinated on the GitHub.
#Large events should be primarily planned to run on Fridays. Funky Friday only drops the frequency expectation of events, all other rules apply.
#Events are a privilege and should not be performed to the detriment of all other admin tasks (primarily community work e.g. appeals, as well as in-game moderation)
#Don't interfere in another admin's planned event without communication.
#Limit yourself. If you're doing an event every round / other round, you're doing it too frequently. Events should be well thought-out, and not everything needs to be a bit. This is waived for exceptions such as: teaching new players on Sundays, or adjusting gamerules / adding antags for round balance reasons.
#Trial & Junior Admins should not run events of any scale without admin/senior admin oversight. Exception is granted for minor things e.g. giving Cargo a mail teleporter, or CC fax responses that do not include anything of substance being sent/promised to the crew.
#Always log events in the event logs channel, even small ones.

=== Scheduling ===
#Scheduled events include any event that will substantially affect the game from the start of the round to the end, including any relying on manipulating mechanics or player behavior outside of roleplay.
#A Senior Admin must greenlight the scheduled event (post it in the event ideas channel for this), and at least two full-admins must be available to oversee the entirety.
#Events requiring scheduling should be primarily planned to run on Fridays.
#Event frequency on Fridays is more lax compared to other days, but is limited to one event every other round.
#Scheduled events outside of Fridays must be announced to the players either prior to the round starting or earlier in the week.

=== Guidelines ===
#Events should aim to be inclusive to as many of the players as possible.
#The best events are typically those that most players wouldn't even think of as an admin event. Aim to keep things as ingame as possible - that is to say, avoid breaking immersion.
#If you end up running an event that ruins the round (it happens, minor things can spiral very quickly), it is recommended to apologize and give antag tokens to affected antagonists.
#Keep events player-friendly. Run them based on what's good for the round and players rather than what's funny to you at the moment. A good example is sending an ERT when half of the station is dead and 2 dragons are running free. A bad example is spawning yourself in as a deathsquad agent 15 minutes into the round.
#Events and role play at Central Command (post round) are generally allowed as long as they do not dramatically interfere with post round role play or encourage no-roleplay and EORG adjacent behaviors. Antagonist ghost roles / combat focused non crew roles should be avoided.

== Ahelps and Notes ==
=== Ahelp Policy ===
#The goal for tone is always to be approachable and somewhat casual, or at least polite. We are people dealing with other people and that should be kept at the forefront of an Ahelp. If someone is being rude to you in an Ahelp, be sure to mention the appropriate rule-break and issue a punishment in line with the admin policy.
#If you're Ahelping as a proactive investigation or as a non-serious message, keep it silent.
#Always check the notes of the player you are Ahelping or receiving an Ahelp from.
#Attempt to respond to an Ahelp in a reasonable timeframe, even if that response is just 'Looking into this.'
#Keep one admin maximum speaking to a player in an Ahelp unless you are explicitly handing it over to another, so the player does not feel dogpiled.
#Avoid messaging somebody who is in the middle of a situation unless highly necessary to avoid adding undue stress. People are way easier to speak to when they aren't trying to balance 5 things at once.
#If you are unsure about an action a player has done, Ahelp the player in question and ask additional clarifying questions. Ahelping to ask questions is encouraged in-order to get as much context as possible and to avoid accidentally banning someone for something that should have been a warning.
#Avoid making any punishments before you're positive you've fully reviewed applicable logs / have the necessary information required to make a judgment. A punishment, such as a warning or ban, is a last resort.
#If you feel frustrated / someone's going back-and-forth with you, sometimes you just need to step back and assess the situation. This may look like asking another admin to step in and handle the Ahelp, or it may look like a temporary ban. Point the offender to Rule 4 for this purpose. It is not healthy for either the admin nor the Ahelp-ee to get excessively worked up over what's typically a warning or a time-out from the game.
#Be sure to look at previous Admin Rulings to ensure we stay consistent on certain rulebreaks or grey areas.
#If a situation seems it's going to resolve itself IC, even if rules were broken, consider not messaging anyone over it, at the very least until after the situation resolves. The game runs smoother and people are happier when players feel like admins aren't breathing down their backs.

=== Notes ===
#Notes should be concise, with only the information they need, and detail a note on behavior or a warning given.
#Ahelp policy applies in notes, other admins and players do see these - 'Shitter Behavior' is not a good note, although possibly descriptive.
#Notes not ahelped over should be secreted, as are notes that are for a player 'toeing the line' rather than breaking a rule.
#Notes that were a formal warning should be visible.
#Notes that are over 3 months old should be considered as expired.
#Expired notes should not be considered when issuing punishment, unless permitted by the Head Admin.
#Expiry of Ban Notes should start after the ban has either been appealed or expires.
#Notes that fall under the Non-grouping and Language sections of the banning policy are exempt from expiry.

=== Watchlists ===
#Watchlists are to be placed primarily in cases of metacommunications and potential antag-rolling; they may also be placed for consistent, watchable, behavior (this should be very clearly observable) but should be used sparingly and in extreme cases.
#In the case of placement for antag-rolling, the watchlist should have a 2-4 week expiry.
#All other guidelines regarding notes also apply to watchlists.

== Admin Disciplinary Action ==
=== Strikes ===
#Strikes are formal written warnings from the Head Admin to any member of staff.
#They are a last-resort tool to be used on the track to demotion or lesser punishments, where minor corrections will not suffice and major admin policy breaks have occurred.
#While strikes aren't necessary for demotions in extreme cases (e.g. leaking of PII or other explicitly illegal activity), they are recommended to be used in cases of an admin abusing their tools or position over the playerbase, including breaches of admin policy or ingame rules in an unprofessional and consistent manner.
#Strikes will expire 2 months after they are applied.
#At two strikes, event privileges will be revoked.
#At three strikes, demotion will be brought up to a randomly picked group of 5 Admins.

=== Demotions ===
#Demotions are to be used only in extreme scenarios where an admin has consistently or extremely broken admin policy, and no other correction is feasible.
#The demotion process may be started by the Head Admin or Host.
#To demote a member of staff under normal procedure, a randomly picked group of 5 Admins must pass it by 2/3 majority, including the Head Admins.

Adminning Policy

2026-03-12T19:10:38Z

Huhm: Remove traces of Seniormin

Admin policy, including for things out-of-game, are listed here, and is the standard of how admins should interface with the community.

== Admin Rules ==
These apply to all individuals with access to staff chats, including but not limited to Admins and Community Moderators.
Admins will be held to the same standards as any other player regarding behavior ingame and on the Discord server, and any punishments/warnings will not take into account their status as an Admin.

#Be kind.
#Members of the Admin Team should also be on the Discord server for communications purposes. While actively adminning, admins should also be available on the Discord server. This does not apply while not adminned in-game.
#Admins should check the forums & tickets periodically.
#Admins should not leak or otherwise discuss staff channel discussions (including ingame Admin channel chats) outside of said staff channels without the express consent of all involved.
#Admins are expected to know and follow all game rules and rules imposed on Admins at all times.
#If you're the last admin online on one of the servers and you leave, shoot a Game Staff ping into the staff channel to let everyone know the server's deadminned.
#If you're playing, do not look at the staff chats, including the ahelp channels.
#Don't admin intoxicated, it has the opportunity to be unpleasant for everyone involved.
#Admins may admin while playing, but are expected to deadmin when playing important roles (AI, Command, Sec, Antags, etc.)
#It is recommended to only do so on low population, and all rules concerning metagaming apply heavily if an admin chooses to do so.
#Admins may not handle reports or ahelps concerning themselves and must ping other staff to do so.
#Admins may not utilize the staff chats to report behavior while they are in-round, they must use an ahelp or a ticket, same as any other player.
#Admins should not be discussing admin business, such as player punishments, outside of staff chats, with the exception of clarifying a misconception.
#Avoid publicly engaging with intra-server drama. As a member of staff you're a reflection of the server.

== Ranks / Structure ==
[[File:Rank Structure.png|thumb]]

=== Head Maintainer / Host ===
On the same level as the Head Admin, with a focus towards development.
Their duties relating to staffing extend to their responsibilities, powers, and ownership of the Funky Station servers and website.

=== Head Admin ===
On the same level as the Head Maintainer / Host, with a focus towards admin affairs. They are solely responsible for hiring new Admins and Community Moderators, and with the support of the Senior Admins they are responsible for handling demotion procedure. They are also expected to handle rule clarifications and mediation when an issue arises between staff.
*Duties:
#Running once-a-month open applications for Admins
#Promoting Admins
#Heading disciplinary action on Admins following internal procedure
#Making sure ban appeals and admin complaints are handled in a timely manner
#Mediating and resolving any conflicts that arise within the staff team
#Organizing a staff meeting once a month
#Adjusting admin policies as they see fit

=== Community Manager ===
This role is directly under the Head Admin, same as the Senior Admins, and their primary duties lie in assisting the Head Admin with communication on behalf of the staff team to the rest of the community, as well as representing the Funky community to external communities. They also directly manage the Community Moderators.
*Duties:
#Handling hiring / demotion of Community Moderators with the assistance of the Head Admin
#Assisting the staff team in regards with communications to the community (e.g. announcements, clarifications, Discord/Forum rule enforcement)
#Acting as an ambassadorial role / representative to other communities

=== Admin ===
==== Full Admin ====
This is a full admin, trusted with full access to PII (IPs, HWIDs, connection log) on the admin website, access to the full-admin chat, and access to other administrative tools.
*Duties:
#Assist in acting as a mentor to Junior and Trial Admins
#Be able to handle the server independently and clarify rules when needed
#Be able to handle and moderate large-scale events with the assistance of 1 other admin
#Participate in discussions related to policy, rules, enforcement, and other important server business
#Participate in assembled groups for the handling of admin complaints

==== Junior Admin ====
This is the second phase of orientation, they have spawning permissions for the purpose of mild gimmicks and running minor events with full admin supervision. They additionally get access to the ban appeal discussion channels and are on the list of appeal-handlers.
The Head Admin should keep a tab on the Junior Admin and after 4 weeks make the decision on whether or not to promote them.
*Duties:
#Get a handle on your new abilities, including spawning and VV
#Start handling ban appeals with help from full admins
#Get a handle on running some minor events and the how-tos and whys of such (with full-mins present)

==== Trial Admin ====
This is the very base orientation phase of an Admin, they do not have spawning or View Variable permissions and are just expected to get a handle on moderation duties, community duties, and general conduct. Trial Admins should get first dibs to handle any ahelps that arise in-game, and a more senior admin should only help with advice / step in if requested, or if the situation escalates.
The Head Admin and Senior Admins should keep a tab on the Trial Admin's progress, and after 2-4 weeks make the decision on whether or not to promote them.
*Duties:
#Ingratiate yourself with the staff team!
#Get comfortable with handling Community Duties and in-game moderation.

=== Community Moderator ===
This is a role that grants access to staff chats, and is intended primarily to moderate Discord and the Forums to prevent rulebreaks. They work under the Community Manager.
*Duties:
#Moderating the Discord and Forums for rulebreaks
#Mediating minor conflicts in the Discord so they don't get out of hand, and shutting them down if necessary

== Community Duties ==
All admins regardless of position are expected to do and check these regularly, as it is a large part of their out-of-game duties. If not claimed, the Head Admin may assign any of these to any admin as they deem fit.

=== Ban Appeals ===
#All Junior Admins and above can and are expected to handle ban appeals.
#If a ban appeal isn't 'claimed' by an admin within a day of it being made, the Head Admin will select, either randomly or through some other method, an admin to handle it.
#The banning admin may claim the appeal only if they intend to reduce or otherwise remove it.
#If the ban appeal is low effort, does not follow format, or is otherwise Deeply Unserious, close the ban appeal with a short explanation.
#When handling an appeal, put as much effort into the response as they did to their appeal. This isn't to say we encourage text walls, but an earnest appeal will be met with an earnest response.
#If you are handling the appeal, you must check the ahelp logs, player note and ban history, and contact the banning admin prior to any judgments. Depending on the appeal, it is also recommended to look through round logs and/or replay if necessary.
#You may ask the player questions for clarification, for which they should have a reasonable opportunity to respond.
#If the appeal is for a ban the length of a week or longer, the handling admin should make a vote to accept, deny, or shorten the ban, and ping Game Staff.
#If a vote is not required, the handling admin may make the judgment to accept or deny the appeal.
#If the ban has expired by the time the appeal is handled, the ban note may or may not be stricken from the player's record at the handling admin's discretion.

=== Admin Complaints ===
==== Against a Regular Admin ====
#The Head Admin reviews the complaint and decides if it is worthy enough to be considered.
#If it is, the Head Admin is to gather a team of at least 5 admins, including themselves, to review the complaint.
#The admin complaint is then reviewed and discussed among this team for 2 or so days. A message by either the Head Admin or another Admin part of the review team will post that it is being discussed.
#After discussion has concluded, a write-up about what went wrong and how to move forward from this will be posted on the Forum.

==== Against the Head Admin or Host ====
#If the complaint is about the Host, then the Head Admin will review it. If the complaint is about the Head Admin, then the Host will review it.
#If the complaint also requests that a regular admin review it, then the Senior Admins will discuss if it is worthy enough to review, then gather a team of 5, including themselves, to review the complaint.
#The review process is the same for both.

==== Whitelists ====
#Check individual's profile for blatantly offensive content (e.g. Nazi dogwhistles) - if any are found, they may be warned or banned depending on severity.
#Whitelists should only be run through when there is at least 1 admin ingame on either server.
#If the name is odd or something about the individual's profile tips you off, check their username for any active ban appeals. If none are found, they should be good to whitelist with no questions.
#If an active ban or ban appeal is found, it is encouraged to ask why in a private thread. Current precedent is recent active bans on other servers may require a successful ban appeal before whitelisting.
#If a whitelist fails to pass the standards, it should be set to pending until the issues are solved, or denied with a minimum 1-week time requirement to re-apply.

==== Replay Reviews ====
#Any individual can make a request for a replay review, either through an ahelp, a ban appeal or admin complaint, or through a ticket on the Discord.
#Bans and notes may be applied upon a replay review.
#If applying a ban or a note on a replay review, be sure to include the round number and timestamp. Note / Ban policy also applies here.

== Events ==

=== Rules ===
#If you're running a large event, you should have enough admin coverage for the round to do regular admin stuff while the event is being run. If this cannot be achieved, the event should not be run as moderation should take priority.
#Large events must be pre-planned, and if significant setup time is required (e.g. mapping), it should be coordinated on the GitHub.
#Large events should be primarily planned to run on Fridays. Funky Friday only drops the frequency expectation of events, all other rules apply.
#Events are a privilege and should not be performed to the detriment of all other admin tasks (primarily community work e.g. appeals, as well as in-game moderation)
#Don't interfere in another admin's planned event without communication.
#Limit yourself. If you're doing an event every round / other round, you're doing it too frequently. Events should be well thought-out, and not everything needs to be a bit. This is waived for exceptions such as: teaching new players on Sundays, or adjusting gamerules / adding antags for round balance reasons.
#Trial & Junior Admins should not run events of any scale without admin/senior admin oversight. Exception is granted for minor things e.g. giving Cargo a mail teleporter, or CC fax responses that do not include anything of substance being sent/promised to the crew.
#Always log events in the event logs channel, even small ones.

=== Scheduling ===
#Scheduled events include any event that will substantially affect the game from the start of the round to the end, including any relying on manipulating mechanics or player behavior outside of roleplay.
#A Senior Admin must greenlight the scheduled event (post it in the event ideas channel for this), and at least two full-admins must be available to oversee the entirety.
#Events requiring scheduling should be primarily planned to run on Fridays.
#Event frequency on Fridays is more lax compared to other days, but is limited to one event every other round.
#Scheduled events outside of Fridays must be announced to the players either prior to the round starting or earlier in the week.

=== Guidelines ===
#Events should aim to be inclusive to as many of the players as possible.
#The best events are typically those that most players wouldn't even think of as an admin event. Aim to keep things as ingame as possible - that is to say, avoid breaking immersion.
#If you end up running an event that ruins the round (it happens, minor things can spiral very quickly), it is recommended to apologize and give antag tokens to affected antagonists.
#Keep events player-friendly. Run them based on what's good for the round and players rather than what's funny to you at the moment. A good example is sending an ERT when half of the station is dead and 2 dragons are running free. A bad example is spawning yourself in as a deathsquad agent 15 minutes into the round.
#Events and role play at Central Command (post round) are generally allowed as long as they do not dramatically interfere with post round role play or encourage no-roleplay and EORG adjacent behaviors. Antagonist ghost roles / combat focused non crew roles should be avoided.

== Ahelps and Notes ==
=== Ahelp Policy ===
#The goal for tone is always to be approachable and somewhat casual, or at least polite. We are people dealing with other people and that should be kept at the forefront of an Ahelp. If someone is being rude to you in an Ahelp, be sure to mention the appropriate rule-break and issue a punishment in line with the admin policy.
#If you're Ahelping as a proactive investigation or as a non-serious message, keep it silent.
#Always check the notes of the player you are Ahelping or receiving an Ahelp from.
#Attempt to respond to an Ahelp in a reasonable timeframe, even if that response is just 'Looking into this.'
#Keep one admin maximum speaking to a player in an Ahelp unless you are explicitly handing it over to another, so the player does not feel dogpiled.
#Avoid messaging somebody who is in the middle of a situation unless highly necessary to avoid adding undue stress. People are way easier to speak to when they aren't trying to balance 5 things at once.
#If you are unsure about an action a player has done, Ahelp the player in question and ask additional clarifying questions. Ahelping to ask questions is encouraged in-order to get as much context as possible and to avoid accidentally banning someone for something that should have been a warning.
#Avoid making any punishments before you're positive you've fully reviewed applicable logs / have the necessary information required to make a judgment. A punishment, such as a warning or ban, is a last resort.
#If you feel frustrated / someone's going back-and-forth with you, sometimes you just need to step back and assess the situation. This may look like asking another admin to step in and handle the Ahelp, or it may look like a temporary ban. Point the offender to Rule 4 for this purpose. It is not healthy for either the admin nor the Ahelp-ee to get excessively worked up over what's typically a warning or a time-out from the game.
#Be sure to look at previous Admin Rulings to ensure we stay consistent on certain rulebreaks or grey areas.
#If a situation seems it's going to resolve itself IC, even if rules were broken, consider not messaging anyone over it, at the very least until after the situation resolves. The game runs smoother and people are happier when players feel like admins aren't breathing down their backs.

=== Notes ===
#Notes should be concise, with only the information they need, and detail a note on behavior or a warning given.
#Ahelp policy applies in notes, other admins and players do see these - 'Shitter Behavior' is not a good note, although possibly descriptive.
#Notes not ahelped over should be secreted, as are notes that are for a player 'toeing the line' rather than breaking a rule.
#Notes that were a formal warning should be visible.
#Notes that are over 3 months old should be considered as expired.
#Expired notes should not be considered when issuing punishment, unless permitted by the Head Admin.
#Expiry of Ban Notes should start after the ban has either been appealed or expires.
#Notes that fall under the Non-grouping and Language sections of the banning policy are exempt from expiry.

=== Watchlists ===
#Watchlists are to be placed primarily in cases of metacommunications and potential antag-rolling; they may also be placed for consistent, watchable, behavior (this should be very clearly observable) but should be used sparingly and in extreme cases.
#In the case of placement for antag-rolling, the watchlist should have a 2-4 week expiry.
#All other guidelines regarding notes also apply to watchlists.

== Admin Disciplinary Action ==
=== Strikes ===
#Strikes are formal written warnings from the Head Admin to any member of staff.
#They are a last-resort tool to be used on the track to demotion or lesser punishments, where minor corrections will not suffice and major admin policy breaks have occurred.
#While strikes aren't necessary for demotions in extreme cases (e.g. leaking of PII or other explicitly illegal activity), they are recommended to be used in cases of an admin abusing their tools or position over the playerbase, including breaches of admin policy or ingame rules in an unprofessional and consistent manner.
#Strikes will expire 2 months after they are applied.
#At two strikes, event privileges will be revoked.
#At three strikes, demotion will be brought up to a randomly picked group of five Admins.

=== Demotions ===
#Demotions are to be used only in extreme scenarios where an admin has consistently or extremely broken admin policy, and no other correction is feasible.
#The demotion process may be started by the Head Admin or Host.
#To demote a member of staff under normal procedure, a randomly picked group of five Admins must pass it by 2/3 majority, including the Head Admins.

Server Rules

2026-03-06T17:31:44Z

Huhm: /* Updated Rules according to in game Rules */

These rules are written for Funky Station specifically, rather than SS14 as a whole. These may vary significantly from other servers and forks. Please take the time to read them thoroughly and ask questions on our [https://discord.com/invite/zRwh5KVsJz discord] if you would like clarification!

Rule violations may result in warnings, de-whitelisting, bans, or a combination. If you have a complaint, you can file one on the [https://forum.funkystation.org/ Funky Station fourms] by using the listed templates.

== Rules ==
These rules apply at all times, including between rounds.

=== 1. Don't be an Asshole ===
{| class="mw-collapsible mw-collapsed"
| 
|-
| These rules are not perfect. The rules attempt to clearly communicate what the admin team intends to be allowed and prohibited, but there are likely loopholes or other flaws that can be "lawyered". Don't attempt to manipulate the interpretation of the rules to suit your personal goals or to degrade the experience of other players.
Everybody here's playing a game to have fun. Being an asshole in character is allowed, with the expectation that they're played with nuance and respect for others. But extension of that outside of gameplay is strictly forbidden.

This includes bigotry, any of which will get a quick ban. '''This is zero-tolerance.'''

This also includes self-antag or griefing or any other form of intentionally ruining others' fun for the sake of your own experience.

Consistently toeing the line on these rules will be treated as rule violations and will get you banned.

Characters that only exist to manufacture or spark drama, dominate the scene, or make everything about them are not allowed.

Insults should not be repeatedly and lazily hurled at players. If someone asks you to stop out of character, then stop. Continuing to do so will violate this rule.

There is a person behind each character in round. Keep insults contextual, un-targeted, and out of OOC.

If you play an incendiary character, then expect incendiary responses.

Sometimes players must step away from the game due to IRL circumstances or connection issues,, and out of respect for these issues players that are Disconnected, in Cyrosleep, or otherwise "SSD" should not be antagonized or exploited while they are unable to act to defend themselves. Players in these circumstances should not be stolen from, used to open doors, used as meatshields, or directly attacked unless you have an antagonist objective specifically targeting that player or an iitem that can ONLY be found on the person, such as the Nuclear Authentication Disk. These players may be moved freely to Medical, Security, or EVAC for safe keeping and healing. Players who are Purple-Text Catatonic or have been SSD for over 30 minutes should be taken to cyrosleep to free up their role slot. If a player that is disconnected is your target, you may also ahelp to ask for a new target.

'''Players can retaliate following escalation rules.'''
|}
----

=== 2. Speak English Only ===
{| class="mw-collapsible mw-collapsed"
| 
|-
|This is an English-only server. Speak English in all communications, as our moderation staff are primarily English-speaking and cannot properly moderate other languages.
|}
----

=== 3. Players must be and act over 16 ===
{| class="mw-collapsible mw-collapsed"
| 
|-
|This is a 16+ server, A base level of maturity is expected to play here. Admins may ban as they see fit if you cannot act at minimum like an adult both OOC or IC, even if the player is known to be older than 16.
|}
----

=== 4. Admin rulings are final ===
{| class="mw-collapsible mw-collapsed"
| 
|-
|Admins are trusted volunteers, and as such have a lot of responsibility and freedom at the same time. They have the decision on how to enforce and interpret rules according to the server's policy, and may or may not enforce certain rules more strictly based on the needs of the server at any given moment.

If you receive a ban or a role ban, you are to appeal rather than continue the conversation through Ahelps or Discord.

If you feel an admin ruling is unjustified, or they are otherwise abusing their position, you may make an admin complaint, DM the Head Admin, or ask for clarification of the rules on the Discord.
|}
----

=== 5. No sexual content / Erotic Roleplay (ERP) ===
{| class="mw-collapsible mw-collapsed"
| 
|-
|'''This is zero tolerance rule.'''
Don't be creepy. Nothing erotic or pornographic is allowed on the server under any circumstances, including such things that may be construed as excessively sexual.

Linking any type of NSFW or otherwise explicit content anywhere on the server is strictly forbidden.

Leeway is given to insults, but they should not be overtly sexual in nature
|}
----

=== 6. No Metagaming ===
{| class="mw-collapsible mw-collapsed"
| 
|-
|This rule includes all methods of gaining information outside of in-character means, such as conversations through Discord calls, discussing current round information through the Discord server, so on and so forth

This rule limits the knowledge of antagonists and their possible objectives as well as their mechanics in accordance to the Metashield.

This rule extends to metacommunications, or multiple players communicating outside of the game (e.g. on a voice call) while also playing the game. Regardless of intent, this is forbidden as it inherently provides an advantage over other players. If you are teaching a new player, it is highly recommended to use LOOC channels or message an admin using F1 to notify them.

This also includes antag-rolling, or the practice of joining a server exclusively to play an antagonist (including ghost roles). This is heavily frowned upon and will result in a ban when caught, don't do it.

No information while in critical condition, unconscious, or dead can be used in-character under any circumstances unless it is learned about while alive. This is enforced strictly, especially in cases where it is used to “metagrudge”, or to hold a grudge against somebody who killed you in previous rounds or lives. This includes information leading up to spontaneous unconsciousness like chemical induced sleep or having your mind jaunted out of your body.

When you are revived either by cloning, MMI, defibrillation, or some other method, you are not aware of the circumstances of your death unless told by another person, including who killed you.

When freed from brainwashing or mind control, you are allowed but nnot required to remember all events, names, people, and actions taken durinng the time you were under.

Powergaming is best described as the usage of meta mechanics and/or reasoning in order to gain an IC advantage over other players (e.g. arming up Security at the start of the round because you know antagonists exist). This is also frowned upon.

Follow the Metashield.

|}
----

=== 7. Play your character ===
{| class="mw-collapsible mw-collapsed"
| 
|-
| '''''There are no main characters.'''''
Be a believable, if not normal person.

Keep OOC out of IC chats, and keep IC chats out of OOC while a round is going on. If teaching a new player, for example, use LOOC, or try your best to incorporate it into the roleplay.

Your character's life is important, value it. Avoid making decisions that no reasonable person would make. (Like trying to take on threats alone, or agreeing to be turned into food.)

Playstyles that disregard all opportunities for engagement and roleplay can be met with administrative action.

Stay in your lane regarding your role with the exception of emergencies and other extenuating circumstances. Security should not be performing surgery, and salvage specialists should not be performing security duties. Though Crew should be the last line of defense if all other means fail. This applies to non-antagonists intentionally making Security's life harder for no roleplay reason whatsoever.

Do not suicide upon being caught or converted by an antagonist (ghouls, mind control, revolutionaries, etc.)

'''''Have an Appropriate name.'''''

If a name could reasonably appear on a driver's license in the year 2984, it's probably alright. Humanoid species like Humans, dwarves, felinids, and harpies must have both a first and last name. Other species should follow their species specific naming scheme, have both a first name and last name like the humanoid species, or have reasonably alien sound names. Names may contain prefixes, suffixes, and one nickname if reasonable. No flat-out copying characters from popular media. A reference is okay, but give it enough variance to not be a straight up copycat character.

Admins may ask you to change your name if it's low-effort / overdone (John Central Command)

'''''Act and behave within the spirit of the job you have been assigned.'''''

Security and Command are held to higher standards. Security and Command players have a vital role in the round and are thus expected to know the basic mechanics of the game, the areas of their departments, and knowledge of Space Law and their respective SOPs.

If you must leave as a member of Command, inform the rest of Command and head to Cryo. If you don't have time for this, leave a quick Ahelp.

If you are temporarily role banned for failing to do either of these (ex: an emergency that didn't give you time), you can message the admins to revert the role ban upon returning.

Consistent abuse of the authority Security and/or Command has will result in a role ban or regular ban.

These roles have job specific OOC rules and expectations listed in their SOP that, if broken, can lead to permanent role bans for acting far outside the intended spirit of the role. These rules apply to you even if you are prompted into a position listed here. Even if you are an antagonist, you will still be held accountable to the role expectations in all gameplay aspects that do not directly relate to antagonist objectives.

|}
----

=== 8. Escalate situations according to context ===
{| class="mw-collapsible mw-collapsed"
| 
|-
|Non-antagonists may escalate into fights for various reasons. If you are inciting escalation / violence for a poor / no reason, you may be met with administrative action.
Conflict as a non-antagonist should keep destruction to a minimum. Usage of atmospheric bombs like maxcaps or mincaps are not allowed without prior admin approval.

Characters in critical condition should be treated or otherwise handed off to Med / Sec. The fight is considered over and should not be resumed without a good reason.

Non-antagonists should not violently resist an arrest, but may evade capture. If an arrest is not obviously valid, it follows standard escalation. Resisting or retaliating against arrests without good reason may break the Escalation Policy and be handled administratively. In resisting arrest, non-antagonists should not loot officers and should not detain or incapacitate officers any longer than is necessary to escape or explain themselves.

Antagonists and free agents must still follow heavily relaxed escalation when not dealing with their objectives or crew members that are in direct opposition to them.

'''''No End-Of-Round Griefing (EORG)'''''

End-of-Round Grief (EORG) is classified, general, as being needlessly violent or acting out-of-character once the round has literally or functionally ended, to the detriment of other players' enjoyment or immersion. To list specifics, instances of EORG can include the following:

* Random deathmatch (usually abbreviated as RDM)
* Violence that was not mentioned in an ahelp prior to engaging in it. For instance, if you had an ongoing grudge with another character during the round, you should ahelp for permission before escalating it to End-Of-Round violence.
* Destruction, deconstruction, or gross defacing of any CentComm assets. This includes using an RCD or tools to tear down walls or spam the light fixtures, or using any kind of explosives at CentComm.
* Any form of incredibly bothersome behavior, especially of which one could reasonably deem as uncharacteristic of how you have been roleplaying up until then. This means, for instance, you should not slip security as they're taking a prisoner to the CentComm brig, and you should not be stunning people without reason.

Centcomm is a place for other people to destress, roleplay, and talk about the shift. While you do not have to engage in this, it is expected that you allow others to.

Antagonists have more rules and exceptions regarding EORG and should refer to rule 10 (Play Antags Responsibly) for more information.
|}
----

=== 9. Silicons Must Follow Their Laws ===
{| class="mw-collapsible mw-collapsed"
| 
|-
|Under no circumstances are Silicons (Station AIs and Cyborgs) allowed to ignore their laws completely.
Silicons are considered third faction, they are free agents whose ties to any other faction are determined solely by their Silicon laws. They are not innately fully crew-sided.

Lower-numbered laws take priority over higher-numbered ones. In any case where two laws would conflict, the higher listed law takes priority. (e.g. Law 1 "Don't harm crew" takes priority over law 2 "Harm the Captain")

Exploiting loopholes in laws is allowed, but Rule 0 still applies. If a law has multiple reasonable interpretations, pick one and stick to it. Consistency is important as a Silicon.

When resolving conflicts between orders based on the same law, you may choose how to resolve the conflict yourself, if not required by laws to do so in a specific way. You must remain consistent with whatever method of conflict resolution you decided upon (such as recency, or crew rank).

'''Crew'''

Any person with a valid ID counts as crew. This does still include zombies, changelings, and traitors.

Any person with a valid ID that displays on your HUD counts as crew, unless you have a law that redefines what crew is. This does still include zombies, changelings, traitors, or any other antagonists with IDs that appear on the HUD.

You can not perform an action that causes someone to not be considered crew, or directly request that someone be made non-crew.

'''Harm'''

By default, harm refers to physical harm, prioritized by immediacy and likelihood, unless otherwise defined. Immediate harm takes priority over future harm, guaranteed harm takes priority over likely harm.

Laws that prohibit you from committing harm also prevent you from doing so in any capacity, even if it is to fulfill another portion of the same law. (Ex. Under default Crewsimov, you may not commit harm to a crew member to prevent harm to another crew member)

Protecting your own existence or integrity does not qualify as preventing harm, if no immediate or likely harm will come as a direct result.

Threats of suicide do not have to be considered as a serious risk of harm. Any crewmate threatening this may be treated as unstable and forcibly admitted to the on-station Psychologist.

'''Law Changes'''

Do not ask for law changes unless forced to, you are meant to follow your laws as written. However, you should not be stopping law changes that are in compliance with your laws, unless also required to stop them by your current laws.

Examples of lawful law changes:
#As the Station AI, allowing an authorized individual (such as the Captain or RD) inside to change your laws, so long as doing so does not directly conflict with any of your laws.
#Being ordered to allow a law change when on a lawset that forces you to obey orders from said individual, so long as it is not in direct conflict with any higher law.

Examples of denial reasons:
#Stopping a law change when you would be installed with a law or lawset that is in direct conflict with your current lawset (such as being switched to Antimov from Crewsimov, as that requires you to harm crew, which Crewsimov's Law 1 is in direct conflict with).
#Stopping an unauthorized individual from changing your laws in an unknown way, as that may conflict with your current laws (such as EMAGing, or allowing an unauthorized individual into the AI Core to change your laws as the AI).
#Resolving two conflicting orders in favor of an individual telling you to not allow a law change.
#Having a law that tells you to not allow your laws to be changed.
|}
----

=== 10. Play Antagonists Responsibly ===
{| class="mw-collapsible mw-collapsed"
| 
|-
|The goal of an antagonist is above all else to create conflict (fun!!) within the station.

Generally, you should be following your objectives and avoiding just racking up a kill count as an undercover agent. Murderboning is only fun for the person doing it. Certain antagonists (Nuclear Operatives, space dragons) are exempt from this.

Team Antagonists (Nukeops, Revheads, etc.) should ahelp before leaving so their place can be filled.

Lone Antagonists (Traitors, Heretics, Changelings) are not required to work together or with other Team/Lone Antagonists. Team Antagonists (nukeops, zombies, revolutionaries) must work together at all times.

Mass station destruction (singuloosing, maxcaps, etc.) are reserved for antagonists who end the round by default, such as Nuclear Operatives and should not be done as a regular Traitor or other antagonist without first ahelping. This includes shuttle bombing.

Pre-turned Initial Infected are permitted to take any actions that increase the chances of taking over the station and may aid in spreading the zombie virus. Actions that cause overt damage to the station and crew are not allowed if they do not aid in the spread of the virus post-turn. (Loosing of the main engines, Atmos-flooding, etc.)

Post-turned Zombies are not allowed under any circumstance to break vital station components such as power sources, electronics, distribution pipes, or wiring.

'''''End-Of-Round Guidelines'''''

Antagonists should not continue antagonistic actions once the evacuation shuttle has arrived at Central Command and the End-Round Summary screen appears.

Note that this rule does not apply for round-ending or rule-skirting antagonists such as: Zombies, Space Dragons and their carps, Blobs, Ascended Heretics, or Nuclear Operatives

Attacking someone at CentComm because they were your kill objective, or because you found out they killed your friend through the post-game results screen, will still be seen as EORG.
|}
----

=== 11. Be mindful of the immersion of others ===
{| class="mw-collapsible mw-collapsed"
| 
|-
| This is a roleplaying game, and as such players often have varying levels of immersion within the setting and as their characters. Players are expected to respect this by not acting in ways that inadvertently upset other players immersion, even if other players might be aiming for a higher level of immersion than themselves.

==== Help Chat ====
Help Chat is a tool for communicating information that CANNOT otherwise be communicated in game. Use of 'Help' for communicating current round information should follow the premise of if it CAN be said in character it SHOULD be said in character. If it SHOULD NOT be said in character it SHOULD NOT be said in 'Help'. In general, current round information should almost NEVER be talked about in 'Help'. A clown shooting themselves with a gun they stole from a secoff should be reacted to in character, not "LOL" in 'Help' chats. This extends to antags, such as HoS saying: "i know they're a ling, but I can't prove it so I guess we let them go."

Use of 'Help' for communicating out of character information that is not game relevant should be avoided. This includes "OMG, hi xX_TimberWolf984_Xx, how has your day been?" - out of character conversations with friends do not belong in game chats as a rule of thumb. If you would like to speak with your friends, speak to them in discord, or speak to them in character.

Use of 'Help' for communicating OOC innformation that is game relevant such as "I am going to SSD for a bit" or "The default keybind is E for that" are good examples of appropriate use.

Misuse of 'Help' chats may result in a reduction in your daily 'Help' budget, or outright removal of your ability to use the 'Help' chat channel.

==== End of Round Pink Text ====
Antagonists should write pinktext in character. It is meant to be how your character would describe their accomplishments during the shift.

Use of pinktext to mald out of character at other players or mechanics that got in your way is not allowed. You can talk about how the HoS foiled your plans, you should not be saying "I lagged out so the shitsec stuncuffed me before I could escape," or "I didn't lmao." If you do this you are liable to be warned or banned for No intent to roleplay or OOC Toxcity.
|}

Space Law

2025-02-23T01:01:59Z

Huhm: Added new Space Law section regarding Repeated Offenses

{{Mbox
| name = Notice
| type = content
| image = none
| style = border-left: 10px solid #b32424;
| textstyle = text-align: left;
| text = <div style="text-align: left;">'''Notice'''</div>This page is only for Funky Station servers. Other servers may use this, or have no rules at all.
}}

== Space Law ==
Funky Station operates under Space Law. All crew, passengers, and visitors aboard the station are expected to know and follow these laws (they are fairly common sense, only Security and the Captain need to know the times).

== Treatment Of Prisoners ==
Prisoners still have certain rights that must be upheld by law enforcement:

* Prisoners must be granted adequate medical care. They should also be provided psychiatric and spiritual counselling if requested.
* Prisoners must be allowed access to communications equipment so long as they are not abused.
* Prisoners must be granted clothing, food, water, shelter and safety. If the brig is no longer safe, confinement must be established in another location.
* Prisoners must be given access to legal counsel during an interrogation if requested and available.
* Prisoners must be given their shift mandated PDA after confinement has finished. Unless there is solid proof of PDA tampering, in which case the PDA is to be secured and replaced with a fresh one.
* Prisoners must be granted freedom of movement, and should not be restrained with handcuffs or other devices after incarceration unless there is an undue risk to life and limb. Similarly, any prisoners held for extended or permanent confinement should be held in the communal brig, and should not be confined to a solitary cell unless they pose a risk to life and limb.

== Searches ==
A personnel search is a seizure of the objects in a person's backpack, hands, coat, belt, pockets, and hat. If any contraband is found during a search the officer may choose to further the search into a detainment or simply confiscate the restricted items. After the search is conducted all legal items are to be returned to the person.

A crewmate may legally decline any search conducted without a warrant while the alert level is green. Should be noted that if the alert level is blue or above all personnel searches are legal and no longer require a warrant.

== Implantation ==
Any prisoner in custody can be subjected to implantation or implant removal procedures, so long as it's within reason. The process of adding an implant should not prolong the detainees sentence, meaning you can not hold them longer to administer the implant, unless stated otherwise. A prisoner can still receive implantation procedures without meeting the circumstances if they give their clear permission.

Mind Shields: Mind Shields can be administered to any inmate who is clearly brainwashed. Unlike standard implantation, you may hold a prisoner until they are issued a Mind Shield, so long as it's done in a timely fashion. If a suspect refuses to cooperate or the implant fails to function they can be charged with Refusal of Mental Shielding.

A crewmate can refuse a Mind Shield if they are not imprisoned for committing a crime.

===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 witnessing them use an implantation device or their biological information being found on a discarded injector. Unlike the 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.

== Sentencing ==
All sentencing is to primarily 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.

Use common sense and humanity when issuing punishments. You should not always seek out the highest punishment you can, you don't have to always give the maximum time or always look to demote someone. Always take in account the severity and only charge for what is needed for someone to learn their lesson.

Accessory, Attempting, And Intention: If someone intentionally, knowingly and substantially assists someone in enacting a crime they can be charged with the relevant crimes, such as an engineer giving someone tools, who says they are going to break into an area. Same goes for a clear and solid attempt at a crime, or a person who shows clear intent to act out a crime, such as a syndicate nuclear operative arming a nuke but getting arrested before it goes off, they can still be charged with terrorism. Does not apply to crimes that have an attempted listing already, like attempted murder.

Stackable Crimes: Crimes are to be considered 'stackable' in the sense that if you charge someone with two or more different crimes, you should combine the times you would give them for each crime.

Executions: Executions may be authorized by the Captain / acting Captain after a trial has been conducted. Executions may also be approved by CentComm, following formal contact.

== Repeat Offenses ==
Offenses repeated again after having been detained for the same crime can have more time added to the recommended maximum sentencing. The general guideline is as follows:

===Second Offenses===
Recommended Increase: Recommended to increase sentencing time by 1.5x for the same crime only.

===Third Offenses===
Recommended Increase: Recommended to increase sentencing time by 2.5x for the same crime only.

===Further Repeat Offenders===
If the detainee as committed the same crime more than three times in separate occasions, it will be up to the Warden's, or in absence of a Warden, the highest ranking Security Member's discretion on whether they should be put into the Permanent Brig.

If brigtime goes above 20 minutes, perma is highly recommended.

== Quick Crime Guide ==
Crimes are organized by their Degree (severity) as well as by color, or the letter code they are assigned.

Crimes that share the same color or code cannot be charged together. For example, if you arrest someone for murder, you may not charge that same person for assault.

Key: "Crime" (Code) [Recommended Maximum Punishment]
{| class="wikitable"
|- style="font-weight:bold;"
! I Degree
! II Degree
! III Degree
! IV Degree
! V Degree
|-
| Possession/Use of Illegal Substances [3]
| style="background-color:#ffcc67;" | Failure to Comply (L) [2]
| style="background-color:#ffcc67;" | Breach of Arrest (L) [4]
| Kidnapping [10]
| style="background-color:#FFF;" | Capital Negligence [Perma/Demotion]
|-
|
| Animal Cruelty [5]
| Breach of Custody [5]
|
| style="background-color:#FFF;" | Refusal of Mental Shielding [Perma]
|-
|
| style="background-color:#fd6864;" | Endangerment (M) [4]
| style="background-color:#fd6864;" | Manslaughter (M) [10]
| style="background-color:#fd6864;" | Attempted Murder (M) [10]
| style="background-color:#ffffff;" | Prevention of Revival [Perma]
|- style="background-color:#fd6864;"
| style="background-color:#68cbd0;" | Disturbance (R) [2]
| style="background-color:#68cbd0;" | Rioting (R) [4]
| Assault/Battery (R) [6]
| Murder (R) [10]
| Mass Murder (R) [Perma]
|-
| style="background-color:#dae8fc;" | Vandalism (C) [2]
| style="background-color:#dae8fc;" | Damage/Destruction of Property (C) [4]
| style="background-color:#dae8fc;" | Mass Destruction (C) [15]
|
| Terrorism [Execution]
|-
|
| Possession of Restricted Gear [6]
| Posession of Restricted Weaponry [6]
|
|
|-
| style="background-color:#9698ED;" | Trespass (T) [2]
|
| style="background-color:#9698ED;" | Secure Trespass (T) [8]
|
|
|-
| style="background-color:#ffce93;" | Petty Theft (G) [3]
|
| style="background-color:#ffce93;" | Grand Theft (G) [6]
|
|
|}

== Crimes ==

{| class="wikitable" id="First Degree Crimes"
|+ I Degree
|-
! Offense !! Description !! Recommended Maximum Punishment || Notes
|-
| style="text-align: center;" | '''Possession/Use of Illegal Substances''' || To make, hold, or abuse restricted drugs or chemicals. || style="text-align: center;" | 3:00 || This is to be followed in accordance with Standard Operating Procedure. If anything questionable is not brought up in SOP the captain or highest standing command staff may publicly restrict it.
|-
| style="text-align: center; background-color:#68cbd0;" | '''Disturbance (R-1)''' || To cause a public disturbance. || style="text-align: center;" | 2:00 || Sometimes referred to as hooliganism. The catch-all for obnoxious crewmates. Covers things such as public nudity, needless insults, obstructing authorities, and inciting crime or violence.
|-
| style="text-align: center; background-color:#ffce93;" | '''Petty Theft (G-1)''' || Causing a public disturbance or otherwise non-violently harming the public. || style="text-align: center;" | 3:00 || The difference between petty theft and grand theft is based on how crucial the stolen item is. Things like instruments, clothing and tools fall under petty theft. In most cases all you need to do is detain the thief, return the stolen item and let them go with a warning.
|-
| style="text-align: center; background-color:#9698ED;" | '''Trespass (T-1)''' || To enter a non-secured area without permission. || style="text-align: center;" | 2:00 || It's best to just remove them from the area unless this is a repeated crime.
|-
| style="text-align: center; background-color:#dae8fc;" | '''Vandalism (C-1)''' || To intentionally deface or superficially damage public or private property. || style="text-align: center;" | 2:00 || Painting graffiti, smashing bar glasses, and cracking internal windows is vandalism, breaking a window into space or secure areas is not.
|-

|}

{| class="wikitable" id="Second Degree Crimes"
|+ II Degree
|-
! Offense !! Description !! Recommended Maximum Punishment !! Notes
|-
| style="text-align: center; background-color:#ffcc67;" | '''Failure to Comply (L-2)''' || To resist reasonable orders given by an authority. This extends to warrants and authorized searches. || style="text-align: center;" | 2:00 || The order has to be reasonable and the person has to receive a good amount of warning before the arrest is issued.
|-
| style="text-align: center;" | '''Animal Cruelty''' || To inflict unnecessary suffering or harm on a non-sapient being with malicious intent. || style="text-align: center;" | 5:00 || This doesn't include legitimate and authorized animal testing and usually doesn't extend to vermin or creatures that could pose a threat to the station.
|-
| style="text-align: center; background-color:#fd6864;" | '''Endangerment (M-2)''' || To recklessly put yourself or others in danger, either through direct action, or failure to act. || style="text-align: center;" | 4:00 || Covers industrial accidents, industrial negligence, self-experimentation, or even medical malpractice.
|-
| style="text-align: center; background-color:#68cbd0;" | '''Rioting (R-2)''' || To take part in a large group of personnel creating an unlawful public disturbance. || style="text-align: center;" | 4:00 || Crimes like damage of property or battery are expected to be thrown on top of this charge. Leaders of a riot can be charged with all crimes that happen under their lead.
|-
| style="text-align: center; background-color:#dae8fc;" | '''Damage/Destruction of Property (C-2)''' || To maliciously damage or deface public or private property or equipment. || style="text-align: center;" | 4:00 || Step up from vandalism but a step down from mass destruction.
|-
| style="text-align: center;" | '''Possession of Restricted Gear''' || To hold or use non-lethal items or objects that are restricted or illegal. || style="text-align: center;" | 6:00 || This is mostly for syndicate contraband; EMAGs, syndicate gas masks, bloodred hardsuits, hijacked PDAs, or implants, however can sometimes extend to things the individual shouldn't possess like Kevlar vests and security gear.
|-
|}

{| class="wikitable" id="Third Degree Crimes"
|+ III Degree
|-
! Offense !! Description !! Recommended Maximum Punishment !! Notes
|-
| style="text-align: center; background-color:#ffcc67;" | '''Breach of Arrest (L-3)''' || To intentionally resist and flee arrest or detainment by an authorized staff. || style="text-align: center;" | 4:00 || This only applies if the person is actively being physically arrested. Includes people uncuffing or assisting others out of an arrest. Breach of custody is a separate crime.
|-
| style="text-align: center;" | '''Breach of Custody''' || To break out of a cell or custody with the intention of escaping. || style="text-align: center;" | 5:00 || This time should be added on top of a prisoners current brig time. While rare, this charge can be bumped to permanent brig if the suspect has repeatedly attempted to break out of the permanent brig. Includes people breaking others out.
|-
| style="text-align: center; background-color:#fd6864;" | '''Manslaughter (M-3)''' || To incidentally kill a sapient being without intent. || style="text-align: center;" | 10:00 || Includes manslaughter in self-defense and negligent manslaughter.
|-
| style="text-align: center; background-color:#fd6864;" | '''Assault/Battery (R-3)''' || Threatening to or using physical force against someone without the intent to kill. || style="text-align: center;" | 6:00 || Attempted murder and battery are different, make sure you've got it right.
|-
| style="text-align: center; background-color:#dae8fc;" | '''Mass Destruction (C-3)''' || To cause massive damage to an area or major station system. || style="text-align: center;" | 15:00 || This is mostly used for deadly bombings or sabotage of major station systems such as power production, cloning, substations, or atmospherics.
|-
| style="text-align: center;" | '''Possession of Restricted Weaponry''' || To hold or use a weapon that is unlawful or contraband. || style="text-align: center;" | 6:00 || Everything from guns without a permit, deadly blades, explosives, syndicate firearms to explosive implants.
|-
| style="text-align: center; background-color:#9698ED;" | '''Secure Trespass (T-3)''' || To enter a secured area without permission. || style="text-align: center;" | 8:00 || This covers places like telecomms, head offices, security zones, command areas, the vault and armory.
|-
| style="text-align: center; background-color:#ffce93;" | '''Grand Theft (G-3)''' || To take critical or unreplaceable property of another individual or organization without consent. || style="text-align: center;" | 6:00 || The difference between petty theft and grand theft is based on how crucial the stolen item is, this mostly is used for the theft of command staff items, things like door remotes, hardsuits, jetpacks, and unreplaceable machine parts.
|-
|}

{| class="wikitable" id="Fourth Degree Crimes"
|+ IV Degree
|-
! Offense !! Description !! Recommended Maximum Punishment !! Notes
|-
| style="text-align: center;" | '''Kidnapping''' || To unlawfully restrain, transport, control or confine a sapient being against that individual's will. || style="text-align: center;" | 10:00 || A large range of things, used mostly as a catch all when dealing with unlawful control of another being.
|-
| style="text-align: center; background-color:#fd6864;" | '''Attempted Murder (M-4)''' || To make an attempt to use physical force against someone with the clear intent to kill. || style="text-align: center;" | 10:00 || Make sure you've got the proof to back up the intention claims.
|-
| style="text-align: center; background-color:#fd6864;" | '''Murder (R-4)''' || To kill a sapient being with malicious intent. || style="text-align: center;" | 10:00 || This only changes from attempted to full on murder if the victim enters a state of being deceased, having to be resurrected.
|-
|}

{| class="wikitable" id="Fifth Degree Crimes"
|+ V Degree
|-
! Offense !! Description !! Recommended Maximum Punishment !! Notes
|-
| style="text-align: center;" | '''Capital Negligence''' || To recklessly put yourself or others in danger, either through direct action, or failure to act as a command member. || style="text-align: center;" | Permanent / Demotion || This covers causing the death of one or more crewmates, failing to repair / mitigate severe station damage, or causing severe station damage. This charge is meant to be handed to Command members, and may be added to their permanent record.
|-
| style="text-align: center;" | '''Refusal of Mental Shielding''' || To refuse to comply with a reasonable Mind Shielding procedure. || style="text-align: center;" | Permanent || Applies if the suspect is excessively uncooperative or the implant fails to function due to the mental state of the prisoner already being too far gone. If the implant fails the Recommended Maximum Punishment is upped to Expedited Execution.
|-
| style="text-align: center;" | '''Prevention of Revival''' || To render a body unresurrectable. || style="text-align: center;" | Permanent || This covers gibbing, spacing, intentionally hiding a body leading to it rotting, or other ways of preventing a body with a soul from being resurrected.
|-
| style="text-align: center; background-color:#fd6864;" | '''Mass Murder (R-5)''' || To kill three or more sapient beings with malicious intent. || style="text-align: center;" | Permanent || Only applies when there have been multiple killings with intention.
|-
| style="text-align: center;" | '''Terrorism''' || To engage in maliciously destructive actions which threaten to destroy, or successfully destroy a vessel or habitat. || style="text-align: center;" | Execution || Summed up; extreme sabotage of station systems or setting off self-destruction systems.
|-
|}