Политика безопасности: различия между версиями

Материал из SS220 Skyrat Wiki (SS13)
Перейти к навигации Перейти к поиску
imported>Ironhawk
Нет описания правки
imported>Ironhawk
(Initial Creation, added the Basic Guiding Principles to Start)
Строка 5: Строка 5:
|Color=#F00
|Color=#F00
}}
}}
== Basic Guiding Principles ==
# Follow the Action-RP Lawset and escalate appropriately. Roleplay whenever possible. Failure to do so will result in punishment.
# As strongly stated in our Guiding Principles, the main goal of this server is to create a fun roleplaying experience, not to win. If you are concerned about how to win instead of the story experience, this is not the server for you.
# Whenever you are given the green light to use lethals or "shoot to kill", this is not a license to execute them when they are downed or are surrendering without due cause.
# Handle a hostage situation with extreme caution. The preservation of civilians and your comrades should be your #1 priority over arresting someone. Acting as if the hostage does not matter will be punished OOCly for poor roleplay.
# Be aware of the meta protection placed around antag items. Non-obvious items are meta-protected where other obvious items like an energy crossbow and grenades are not. Typically, if the item is disguised, you don’t know of it.
# Being a bully as a security officer is acceptable. Being corrupt as a security officer is acceptable. However, if it comes to the point that the way you're playing shuts down roleplaying opportunities for others, that means you are doing it wrong. You want to create conflict to generate roleplay, not destroy the possibility of it. Furthermore, as a security officer, you cannot ignore obviously antagonistic behavior that is a threat to the station. If you know someone is not a threat to the station, taking a bribe is acceptable.
# Antagonists are an essential part of the game. Unless it is unsafe to do so, players are encouraged to use methods of punishment that do not remove antagonists from the round such as gulag or perma. Calling for the execution of a non-violent and cooperative antag may be marked as failrp. However, this is entirely up to the Captain, acting captain, or HoS, and their ruling (in order of the CoC) is final.
# Corporate Regulations is a suggestion, and is never a substitute for thought, intent, and context. Being unnecessarily harsh is generally frowned upon, even if it's in the regulations.
# Work with traitors to create a fun and engaging story, don't just shut them down to win.
# ERP is allowed as security as long as you are not needed. Red Alert and higher you should end your ERP and return to your job. (With an exception regarding non-con against security staff)
# Use the minimum required equipment to handle a situation, you should not be preemptively equipping yourself for threats.
# Do not go around screaming out the game mode the second you see something. Keep meta-knowledge in mind (detailed below), and never, EVER go and scream out stuff like “traitor”, “ling/changeling”, “malf”, “revs”, and the like. It’s completely LRP behavior and does nothing but encourage validhunting.
# If you are being demoted, role-play out the scenario and realize that it can happen. Do not attempt a one person coup, doing so will be considered failrp. Do not drop all context of Roleplay and start acting like shit-tide.
# The head of your department is the “Head of Security” . If the captain finds this person problematic or demotes them, you are to remember that you work for Nanotrasen, not the Head of Security. Please keep this in mind during Head removals.
# Remember to use CI, you are in a role that will make use of this far more than most players and has the most related impact.
# Handle unknowns as if they are unknown, don't rely on metaknowledge to guide your decision making. What would your character think for the first time.

Версия от 17:54, 29 марта 2021

Paper.png Notice

This document is in development and may be changed often. Please ensure you check for updates periodically to keep up-to-date.


Basic Guiding Principles

  1. Follow the Action-RP Lawset and escalate appropriately. Roleplay whenever possible. Failure to do so will result in punishment.
  2. As strongly stated in our Guiding Principles, the main goal of this server is to create a fun roleplaying experience, not to win. If you are concerned about how to win instead of the story experience, this is not the server for you.
  3. Whenever you are given the green light to use lethals or "shoot to kill", this is not a license to execute them when they are downed or are surrendering without due cause.
  4. Handle a hostage situation with extreme caution. The preservation of civilians and your comrades should be your #1 priority over arresting someone. Acting as if the hostage does not matter will be punished OOCly for poor roleplay.
  5. Be aware of the meta protection placed around antag items. Non-obvious items are meta-protected where other obvious items like an energy crossbow and grenades are not. Typically, if the item is disguised, you don’t know of it.
  6. Being a bully as a security officer is acceptable. Being corrupt as a security officer is acceptable. However, if it comes to the point that the way you're playing shuts down roleplaying opportunities for others, that means you are doing it wrong. You want to create conflict to generate roleplay, not destroy the possibility of it. Furthermore, as a security officer, you cannot ignore obviously antagonistic behavior that is a threat to the station. If you know someone is not a threat to the station, taking a bribe is acceptable.
  7. Antagonists are an essential part of the game. Unless it is unsafe to do so, players are encouraged to use methods of punishment that do not remove antagonists from the round such as gulag or perma. Calling for the execution of a non-violent and cooperative antag may be marked as failrp. However, this is entirely up to the Captain, acting captain, or HoS, and their ruling (in order of the CoC) is final.
  8. Corporate Regulations is a suggestion, and is never a substitute for thought, intent, and context. Being unnecessarily harsh is generally frowned upon, even if it's in the regulations.
  9. Work with traitors to create a fun and engaging story, don't just shut them down to win.
  10. ERP is allowed as security as long as you are not needed. Red Alert and higher you should end your ERP and return to your job. (With an exception regarding non-con against security staff)
  11. Use the minimum required equipment to handle a situation, you should not be preemptively equipping yourself for threats.
  12. Do not go around screaming out the game mode the second you see something. Keep meta-knowledge in mind (detailed below), and never, EVER go and scream out stuff like “traitor”, “ling/changeling”, “malf”, “revs”, and the like. It’s completely LRP behavior and does nothing but encourage validhunting.
  13. If you are being demoted, role-play out the scenario and realize that it can happen. Do not attempt a one person coup, doing so will be considered failrp. Do not drop all context of Roleplay and start acting like shit-tide.
  14. The head of your department is the “Head of Security” . If the captain finds this person problematic or demotes them, you are to remember that you work for Nanotrasen, not the Head of Security. Please keep this in mind during Head removals.
  15. Remember to use CI, you are in a role that will make use of this far more than most players and has the most related impact.
  16. Handle unknowns as if they are unknown, don't rely on metaknowledge to guide your decision making. What would your character think for the first time.