imported>Imblyings |
imported>Imblyings |
| (4 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| == Main Rules- read these if nothing else. ==
| | =Main Rules= |
| <ol start=0> | | <ol start="0"> |
| <li>Enforcement of these rules is at the discretion of admins. Admins are fully accountable for any consequences should they invoke this rule. Admins are also allowed to intervene in rounds when it is in the best interest of the playerbase.
| |
| </ol>
| |
| # Don't be a dick. We're all here to have a good time, supposedly. Going out of your way to seriously negatively impact or end the round for someone with little IC justification is against the rules. Legitimate conflicts where people get upset do happen however, these conflicts should escalate properly and retribution must be proportionate."
| |
| # Do not use information gained outside of in character means, i.e.. metagaming. This especially refers to communication between players outside of the game via things like Skype, known as metacomms. Characters are otherwise allowed to know everything about ingame mechanics or antagonists, as well as keep persistent friendships or relationships with other characters when not for the purpose of unfair advantage by teaming up together for little IC reason.
| |
| # Non-consensual erotic/creepy stuff is not allowed.
| |
| # Do not say in character (IC) things in the out of character (OOC) chat channel, do not say OOC things in IC either. There is an exception for OOC in IC where terms like 'clickdrag X to Y, or look for the tab' is used to help a player.
| |
| # Lone antagonists can do whatever they want, short of metagaming/comms, bug/exploit abuse, erotic/creepy stuff, OOC in IC or IC in OOC, and spawn-camping arrivals. Team antagonists can do whatever they want as per lone antagonists, as long as it doesn’t harm their team. Non-antagonists can do whatever they want to antagonists as per lone antagonists, but non-antagonists are not allowed to pre-emptively search for antagonists without reasonable prior cause. Non-antags acting like an antag can be treated as an antag.
| |
| # Players in a head of staff, AI role or team antag role require a minimum amount of effort, generally considered to be not logging out at or near roundstart. Notify admins if you cannot play these roles and must leave near round start, and make an attempt to inform other players IC as well for head of staff or AI roles. Abuse of a job position, particularly Rule 1 breaking abuse, is not allowed.
| |
| # In-game administration rulings are final. Incidences of admin abuse, negligence or disputed rulings can be taken to the forums or the #supportbus IRC channel on the Rizon network. If an admin says something was 'looked into, handled, resolved' etc, regarding an issue, it is unlikely an admin will provide any further information. Admins are under no obligation to reveal IC information. Deliberately lying or misrepresenting facts in adminhelps will be dealt with harshly.
| |
| # If you regularly come close to breaking the rules without actually breaking them, it will be treated as the rules being broken. Repeated instances of the same rules being broken may be met with harsher consequences. Baiting people into escalations or situations where you can report them to admins will be dealt with harshly.
| |
|
| |
|
| | ;<li id="0">'''Admins can do what they want as long as it is in the best interest of the server. They are fully accountable for the consequences of invoking this rule.''' |
|
| |
|
| == Security Policy/Precedents ==
| | ::Grey McKilleveryone the traitor has murdered his way through most of a lowpop station and continues to recall the shuttle several times, just so he can kill everyone off despite only have a steal plasma objective. The admins see this and spawn ERTs to kill Grey, since admins may prioritize keeping players ingame over one persons desire to depopulate the server. |
|
| |
|
| # Rule 1 of the main rules apply to security. The only exception is that security is generally considered to be armed with non-lethal methods to control a situation. Therefore, where reasonably possible, security is expected to use non-lethal methods first in a conflict before escalating to lethal methods.
| | ::A player uses a ghost role in a lavaland ruin to move to an alien ruin to try and introduce xenos to the round. Admins notice this and delete the xeno-infected ghost role mob. There are several factors at play here but the driving justification behind this is that admins have the discretion to shape a round like this (or avoid a round from being shaped by xenos spawned from a ghost role). |
| # Rule 5 of the main rules also apply to security. Security are not exceptions to the rule where non-antagonists can do anything they want, as per rule 5, to antagonists.
| |
| # The 'act like an antag, get treated like one' part of Rule 5 of the main rules also apply to security. Stunning an officer repeatedly, using lethal or restricted weapons on them, disrupting the arrests or sentences of dangerous criminals, or damaging the brig, are examples of behaviour that may make you valid for security under Rule 5. Make sure players deserve it when you treat them as an antag, when in doubt, err on the side of caution as poor behaviour on the part of security will not be tolerated.
| |
| # For arrested players, timed sentences up to a total of 10 minutes, buckle-cuffing, and stripping, are considered IC issues and are not actionable by admins. Brig sentences totaling more than 10 minutes can be adminhelped, as can be gulag or perma sentences or a pattern of illegitimate punishment. However, security should refrain from confiscating items not related to any crimes, especially important department-specific items like hard suits. Obvious exceptions to this are things like radio headsets, if players use it to harass security over the radio while being arrested.
| |
| # Don’t kill asimov borgs for trying to stop harm, unless they are being excessively disruptive, for example, locking down all of security despite only one security staff member causing harm.
| |
| # While it is up to the discretion of the security player, lethal force may be used on a mob of players trying to force entry into the brig. Additionally, lethal force may be used immediately on anyone trying to enter the armoury, is in the armoury, or is leaving it
| |
|
| |
|
| | ::''Consider factors like server pop, amount of shuttle recalls etc when spawning ERTs but also do not be overly swayed by salt from ghosts when clicking buttons. A gradual increase in response may be appropriate- a centcom inspector to act surprised that the station is nearly all dead, then a small ERT team to check things out, then a larger ERT team etc.'' |
|
| |
|
| == Precedents/exceptions- Examples and exceptions to the main rules. == | | ;<li id="1">'''Don't be a dick. We are all here to have a good time. Going out of your way to dick over other players for little IC reason will get you removed.''' |
|
| |
|
| '''Read for detailed clarification on each main rule. Players are subject to precedents but depending on how much of a dick they were, they can be either advised of the precedent to being banned for it.''' | | ::''Players do not have access to the information we have. They can only act on what they know and sometimes, it may be justified from what they know, even if we have information that changes the situation. Be aware, the lack of information a player has can be complicated further by a player’s personal bias. What may seem like dick behaviour may in fact be justified from one players point of view.'' |
|
| |
|
| ===== Rule 0 Precedents. ===== | | ;<li id="2">'''Shit happens. Let it go, move on, hop onto another server (we have two!), play another game, go outside for some fresh air.''' |
| - Rule 0 should only be invoked by admins when it is in the best interests of the server.
| |
|
| |
|
| - Admins have intervened before and will do so again in situations where a player regardless of antag status has repeatedly delayed round-end by recalling the shuttle when most other players are dead or want to leave.
| | ;<li id="3">'''Start shit get hit. If you start dicking over players, accept the reaction you fish for with humility and grace.''' |
|
| |
|
| ===== Rule 1 Precedents. =====
| | ::An assistant breaks into medbay but gets arrested for it. The CMO follows the assistant to the brig and gives him 50cc of cyanide for his troubles. The CMO is warned because hostilities have ended and the assistant has already had his comeuppance by being arrested. |
| - Random murders are not acceptable nor is the killing of other players for poor or little reasoning such as ‘My character is insane’. Each unjustified kill is normally met with one 24 ban.
| |
|
| |
|
| - Acceptable escalation is defined as not using an excessive amount of force to control a situation. Proportionate retribution is defined as a relatively equal amount of force applied to someone in revenge for an earlier attack. Multiple factors are considered here, including but not limited to methods of force available to the involved players, who instigated the conflict and why, the state/general situation of the station, how the players involved end up. Excessive escalation or retribution, depending on the situation, may result in admin intervention, to warnings, to bans.
| | ::Honk Mcwasteofoxygen starts slipping the mime in the hopline. The mime has had enough, breaks his bottle over the clowns head and nearly crits the clown, but the clown slips the mime and crits him. The clown started it but since the clown drags the mime to medbay to fix his silent buddy up ''and doesn't have a history of starting fights'', the clown is a-ok. Be careful, making a habit of starting fights to crit people and then heal them will get you banned. |
| | |
| - Spamming any channel is not allowed, this goes for radio spam, AI vox announcement spam, paper at camera spam and other forms of spam. Non-antagonists doing so may not defend themselves and may suffer from IC or OOC consequences. Antagonists can to a certain extent, moreso with reading things like WGW over the radio, but may be told by admins to stop if it becomes excessive. Spamming can result from ingame admin intervention ending in you dying, to admin warnings, to bans for excessive or repeated spamming.
| |
| | |
| - Rules still apply until the emergency escape shuttle has reached Centcom and the round-end antagonist report has appeared. When the shuttle has reached Centcom, players are free to act as per lone antagonists, detailed in Rule 5. Non-antagonist grief upon the shuttle, from spamming flashbangs for no reason to spraying space lube, can be met with instant 5 (five) minute bans or more.
| |
| | |
| - Unprovoked grief (occasionally known as greytiding), repeated cases of minor unprovoked grief, and unprovoked grief targeted towards specific players or groups (i.e. metagrudging) fall under rule 1. Admins may follow up on grief with allowing the affected parties to ignore normal escalation policy or measures such as warnings or bans.
| |
| | |
| ===== Rule 2 Precedents. =====
| |
| - Metacomms, the use of methods of communication outside of SS13 IC channels, is a very serious rule violation and may be met with permanent bans for all related accounts. If players are sharing the same IP or know each other in real life or the like, inform the admins first, otherwise it may look suspicious. Players are allowed to introduce new players that they know to the game but all communication and explanations should be done in game if possible. Admins can also help in these situations if requested.
| |
| | |
| - Similar to how characters are allowed to know everything about ingame mechanics or antagonists under rule 2, characters are allowed to have persistent knowledge/relationships/friendships with the caveat that knowledge of a character being an antagonist from a previous round is not used.
| |
| | |
| - Character friendships should not be exploitative in nature or be used to gain an unfair advantage. Having an IC friendship with another player does not, for example, justify giving them all-access each round.
| |
| | |
| - Atmos techs are not allowed to edit atmos at roundstart so that the AI cannot use it for malicious purposes. While this might not make sense IC, it's a necessary OOC precedent for some game mechanics to work. Atmos techs are allowed if they have any reasonable suspicion of the AI being rogue.
| |
| | |
| - Station crew are currently not allowed to board or search for the syndicate shuttle during nuke op rounds, unless they specifically follow an operative or a pinpointer onto the shuttle. It is better to adminhelp first in this situation, so admins can confirm that you found it legitimately.
| |
| | |
| ===== Rule 4 Precedents. =====
| |
| - Excessively OOC names fall under rule 4. Make a minimum effort to have your name fit in a setting involving a wacky space station in the future. Admins may get involved if your name is dumb.
| |
| | |
| ===== Rule 5 Precedents. =====
| |
| - Non-antagonists are allowed to assist antagonists given sufficient IC reasoning but assisting an antagonist doesn't mean you get to act like one . If in doubt, ask an admin if a particular action is okay. Depending on the level of assistance, sufficient IC reasoning could be simply treating everyone who goes into medbay regardless of them being a murderer or not, all the way to being threatened under pain of death by an antagonist to do something.
| |
| | |
| ===== Rule 6 Precedents. =====
| |
| - Minimum levels of effort for heads of staff and silicon roles generally include not logging out/going afk at or near round start as well as not being deliberately incompetent or malicious. Constant logging out/going afk may be given warnings by admins, and may progress to jobbans. Deliberate incompetence or malice will be treated the same way, depending on severity, for example, a chemist constantly abusing the position to make space lube and lube hallways, may be warned and then jobbanned if further abuse happens.
| |
| - If you are an antagonist, let an admin know if you cannot or do not want to play the role. Admins will transfer the role to someone else. Obviously, if an admin does so for a player, the player must not use knowledge of that antagonist position existing.
| |
| | |
| ===== Rule 7 Precedents. =====
| |
| - Incidents of admin abuse or negligence should be reported along with a date and time, along with details to pinpoint the incident in the logs, to any full admin via IRC or forum PM or posted on the admin complaints subforum located at https://tgstation13.org/phpBB/viewforum.php?f=23 or taken to the #supportbus IRC channel on the Rizon network. Incidents of poorly conducted admin events may also be taken to https://tgstation13.org/phpBB/viewforum.php?f=37 in their respective feedback threads, for less serious complaints.
| |
| | |
| - Lying in adminhelps, misrepresenting facts deliberately, or logging off when an admin has asked a question may result in permabans. Admins will not automatically place bans for players logging off however, and will generally wait a while in case real life situations caused a player to disconnect or go afk.
| |
| | |
| | |
| == The Secret <span style="text-decoration: line-through;">Rules</span> Facts of Life ==
| |
| | |
| '''For experienced users only. Don't quote these at admins. If you're in a position where you need to defend yourself using this, you've done something wrong. This is about the personal freedom and responsibility an experienced player will have when they have the interests of others first.''' | |
| | |
| This is a game that allows a lot of potential for great things to happen, and naturally the rules restrict a lot of that to ensure the minority don't ruin every round for everyone else. If you push the limits in the pursuit of something interesting for reasons other than your own personal entertainment, breaking the rules may be excused to allow for that freedom. This will always be at the admin's discretion of course, but if you want a large amount of freedom to make great things happen, you'll have to take on the responsibility for them. You won't be faulted if they go wrong in ways beyond your control, but this is a difficult line to tread so use it well. It's almost always better to consult an admin on this as they are more equipped to taking on that responsibility.
| |
| | |
| Everyone has a license to grief to a very limited extent. You can likely get away with borderline antagonistic behaviour (Never random murder, but stealing from the brig and triggering a manhunt, for example) occasionally, but it's when this becomes a frequent occurrence that people get frustrated and admins start to get involved.
| |