Toggle menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

User:Harryob: Difference between revisions

1,185 editsJoined 13 May 2022
No edit summary
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Getting started with the code =
===Rule 0. Admins===
{| style="width: 100%; border: none"
|style="width: 100%; vertical-align: top;" | <tabs>
<tab name="Staff Powers">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Information
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
!<div align="center">Rule 0 - Override</div>
| Admins and Above retain the authority to ignore or alter the enforcement of specific rules at their discretion should they feel it is in the best interest of the current round, the server or the player base at large. In the absence of an Admin or higher ranking member of staff, Moderators may exercise this power following their own chain of authority. Any use of Rule 0 holds it’s user fully accountable for the actions taken due to their change of the rulings.
|-
!<div align="center">Rule 0.1 - Intent</div>
| Rules are enforced as intended. Every example of a rule break cannot be defined as written, therefore, enforcement of the rules is subject to staff interpretation of the rule's intention. Staff may choose to handle minor rule breaks by utilizing in-game tools to correct improper behavior. Staff retain discretion on when a minor rule break can be handled via "In-Character" consequences in place of warning notes and/or bans. Minor rule breaks such as OOC in IC/Netspeak cannot be handled "In-Character." Staff members shall not use "In-Character" consequences for major rule breaks such as Mass Grief/ERP/Multikeying. If staff use "In-Character" behavior adjusment, no warning notes and/or bans shall be issued, unless further rule violations take place. Players shall not request a staff member to handle things "In-Character" and the final decision rests solely on the staff member conducting the investigation
|-
|-
!<div align="center">Rule 0.2 - Authority</div>
| If a staff member gives you an instruction or makes a ruling, do not argue with the staff member and follow the instruction/accept the ruling. You may file a staff report on the forums or take it up with their manager directly if you do not agree with the decision made after the round ends. Arguing with a staff member may lead to you being punished. Staff members are volunteers and will not tolerate toxicity or hostility during the course of their duties.
|-
|}
</tab>
</tabs>
|}


== Setting up your Coding Environment ==
===Rule 1. No Erotic Role Play (ERP), erotic content, or 18+ sexual content===
Roleplay intended to elicit a sexual response from the receiver(s), including but not limited to writing stories (WGW) or posting links to adult content. Doing so will almost always result in an instant permaban from our server. However, these actions could still be susceptible to Marine Law. A good rule of thumb for whether an interaction crosses this line would be to consider if the action would be allowed in a PG-13 rated movie in the USA.
{| style="width: 100%; border: none"
|style="width: 100%; vertical-align: top;" | <tabs>
<tab name="Examples">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Example
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
Staff reserve the right to make judgement calls on situations to determine if they constitute a breach of 18+ or erotic conduct. If something is overly disgusting or crosses a line in a way that becomes an 18+ situation, it may be punished for regardless of nature.
* If you are not sure whether something you wish to say or do is okay, AHelp first. We would rather you ask and be told no, than have it happen and a ban become necessary.
!<div align="center">Sexual Acts</div>
|
* No character should ever engage in any form of sexual intercourse in the game, whether alone or with another player.
* No sexual act or genitalia should ever be given explicit description. If a sexual act must be referenced, there should never be a description of how particular body parts made contact or interacted in any way, nor should any particular act be named.
** Distasteful but non-sexual bravado do not apply to this. A marine scratching their nuts, for example, is fine.
|-
!<div align="center">Euphemisms</div>
|
* Euphemisms that also have a sexual meaning are allowed in non-sexual contexts. Common terms or phrases like "Suck my dick" are fine, as long as saying such is not a literal invitation or solicitation to do so.
|-
|}
The above are guidelines for reference, and it is highly recommended not to straddle the line along what is and is not allowed when dealing with erotic/18+ content.
</tab>
</tabs>
|}


Though you can use DreamMaker, and external Git software, for modifying your code and maps, all modern SS13 tooling is set up for Visual Studio Code, so it is highly recommended. You can jump to variable definitions, procs and atoms with ease.
===Rule 2. Roleplay===
CM-SS13 is intended to be a Medium Roleplay server. Play a reasonably realistic character. Treat your character as a separate entity from you, the player. Your character's actions, feelings, and knowledge in-game should be based solely on the character's experiences and not your own as the player. Low roleplay actions that have no regard for your character or the setting (Memes, silly copypaste spam IC) are not acceptable. Character development can occur over rounds but each round is a soft-reset, meaning you can have previous mission experience but your character will never have died or fled the ship in the past. Follow the Roleplay Standards.
* Major shenanigans that may disrupt the normal flow of the round at roundstart, (This includes but is not limited to; big or lethal fights, briefing brawls, riots, massive equipment restrictions and tackling players trying to reach their prep room.), are not tolerated.
{| style="width: 100%; border: none"
|style="width: 100%; vertical-align: top;" | <tabs>
<tab name="Human Roleplay Standards">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Standard
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Expectation
|-
!<div align="center">Pre-Drop Arrests and Riots</div>
|
* Causing riots on the dropship over an arrest before first drop will be considered round start shenanigans and staff members will intervene with OOC punishments. You shouldn’t lynch a MP and risk your career because they are arresting a marine who has entered the dropship.  If you are wanted and enter the dropship to try and avoid arrest you will be held accountable if issues arise with MPs.
* You cannot initiate a jailbreak before first drop.
|-
!<div align="center">Sanity</div>
|
* All personnel employed by the USCM are mentally stable and physically fit for duty. They would not desert their post or go against the USCM without a good reason. Marriages are forbidden, no two people employed by the USCM on the same ship may be married. The USCM has knowledge of most threats, including all human forces (UPP, CLF, PMC, etc) and general knowledge of the Xenomorph hive structure. The USCM does not know there is a Xenomorph threat on the planet of operation unless that information is given in a custom event.
|-
!<div align="center">Deployment</div>
|
* All personnel deployed should be following their role requirements. A doctor would not deploy to fight Xenos on the front line, a Squad Medic would not only be healing themself, and a Squad Leader would not ignore the orders of command just to do their own thing.
* Higher ranking squad marines (such as the squad-leader, specialist, smart-gunner and RTO) should be following the orders assigned to them by the commander instead of running off to go fight alone. Special circumstances exclude this requirement, but players should be prepared to justify their actions if contacted by staff.
* You cannot refuse to deploy until someone is released from jail, or in order to break them free.
* Heads of Departments (CE, RO, CMP and CMO) should not be leaving the ship barring exceptional circumstances.
* All marines should be deploying where possible, refusing to deploy because someone got arrested is not allowed.
* Shipside Crew, where authorised to deploy, must remain in secure areas.
|-
!<div align="center">Ship Modifications</div>
|
* Deconstruction of the ship should not be occuring before first drop & confirmed contact. The marines would not immediately resort to taking their warship to pieces for a random unconfirmed distress call.
** This includes deconstruction of things like chairs in briefing, however does not include the barrels and crates scattered around maintenance.
* Modifications to the ship should not be made with meta-purposes, no building a maze or bunker on the ship intended to help secure the ship for hijack before you even know hijack is a thing.
|-
!<div align="center">Synthetics</div>
|
* Synthetics are cold and do not feel emotions as strongly as humans, though they may fake them. They serve the USCM and may not turn against them. Synthetics must adhere to the [https://forum.cm-ss13.com/t/synthetic-programming-and-guidelines Synthetic Programming] and Guidelines.
* Synthetic Survivors have altered Programming which can also be found there.
* Synthetic Guideline breaches are dealt with by the Synthetic Whitelist Council, who can be contacted on discord or through Player Reports.
|-
!<div align="center">Survivors</div>
|
* Survivors have more leeway than marines with their mental stability due to the trauma they may have experienced during the xenomorph attack. They may be suffering PTSD, paranoia or similar conditions for roleplaying purposes. Survivors may '''NOT''' be hostile unless they have been spawned as hostile survivors (CLF).
|-
!<div align="center">ID Cards</div>
|
* These should only be taken for a roleplay reason, such as from a dead XO to call for help on a computer in the ship’s bridge. If you take an ID or find one from a living player (or a dead player that has since been revived), you should make every attempt to return it unless your character has a good reason not to.
* You should not grant yourself or others increased access to areas of the ship unless there is a personnel shortage or exceptional reason to do so.
** Death or absence of any senior officers is suitable reason to grant yourself needed access to run the operation.
** Requisitions missing personnel is a valid reason to give other people or yourself access to Requisitions etc.
|-
!<div align="center">Language</div>
|
* Spamming chat (Local or Radio) with non-english characters, symbols or other gibberish is considered LRP, and a violation of Rule 2
|-
!<div align="center">Aliens & Predators</div>
|
* Marines know what Xenos are and have encountered them before. They have a basic knowledge of how the hive works.
** They '''do not''' know there are Xenos on the colony.
* Marines have not encountered Predators before. Any encounters are to be considered the first of their kind. Marines are permitted to roleplay "I've heard stories and/or legends" in regards to Predators, but metagaming knowing everything about them is a violation. Nicknames that are realistic such  as "Jamaicans" "Dreadlock Lizards" "Spooks" "Phantoms or Ghosts" are acceptable. Avoid meme/gaming terminology such as "maicers"
|-
|}
</tab>
<tab name="Xeno Roleplay Standards">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Standard
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Expectation
|-
!<div align="center">Freedom</div>
|
* Aliens have no free will. They are a hivemind, and their purpose is to enforce the will of the Queen and expand the Hive.
* They are not friendly and will not negotiate.
|-
!<div align="center">Language</div>
|
* Xeno hivemind is an English translation of their thoughts, so words such as “hydro” or “shuttle” are acceptable.
* Spamming "Reeeee" and similar such behaviour in Hivemind or Local Chat is not allowed.
* Calling the Runner caste a "Rooner" is acceptable.
|-
!<div align="center">Marines</div>
|
* Due to the Hivemind, xenos know everything every xeno learns and know the basics of human equipment.
* At the start of the round, the Xenos can sense the human's ship looming above their hive and are aware that human forces will be visiting the colony shortly.
|-
!<div align="center">Larva</div>
|
* Larva should typically remain within the Hive, this is especially the case for roundstart larva, and avoid the frontlines.
* Larva cannot sneak onto dropships to get to the marine ship.
* Larva are not recon castes, and should not be seeking out survivors.
|-
!<div align="center">Queen</div>
|
* The Queen can banish Xenos who fail to uphold these standards and expectations.
* Abuse of banish for memes or other reasons that would not be applicable may result in punishment.
|-
|}
</tab>
<tab name="Predator Roleplay Standards">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Standard
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Expectation
|-
!<div align="center">Predators</div>
|
* Predators are honorable hunters. They must follow the [https://forum.cm-ss13.com/t/predator-honor-code/575 Honor Code] and act like a serious predator, not a prankster.
* The USCM does not hold any information about these beings, meaning each contact is unknown regarding them.
* Predator Honor Code breaches are handled by the Predator Whitelist Council, who can be contacted on Discord or through Player Reports.
|}
</tab>
</tabs>
|}


=== Step 1: Downloading Visual Studio Code ===
===Rule 3. Community Expectations===
The general behavioural expectations for members of the community. Unless explicitly stated these rules apply to all areas of the community.
* Don't be a dick.
* This is not a complete list and only includes the most important elements.


Visual Studio Code is a free code editor (from Microsoft) that you can use to edit, test and publish your code to GitHub.  
{| style="width: 100%; border: none"
|style="width: 100%; vertical-align: top;" | <tabs>
<tab name="Expectations">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Expectation
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Details
|-
!<div align="center">Malicious Compliance (Marine Law)</div>
|
* Malicious Compliance with Marine Law is detailed under Rule 11 (Marine Law)
|-
!<div align="center">English Only</div>
|
* All communications within the server (IC and OOC) should be done in English only. Phrases from other languages are fine but should not make up the majority of your conversations.
*  This extends to the use of Netspeak in-character. You should not be using LOL, WTF,
|-
!<div align="center">Profane RP</div>
|
* Roleplaying hostile actions, beliefs or emotions through the use of profanity is permitted. However staff reserve the right to make calls on situations if a player has crossed the line. If a staff member tells you to stop, you stop.
|-
!<div align="center">Racism and Bigotry</div>
|
* Usage of slurs IC/OOC on the server '''will result in a 7 day ban''', automatically.
* Racism, the use of slurs and other targeting terms or phrases is strictly forbidden and will not be tolerated.
* Being Homophobic, Sexist or a general bigot is not ok, and action will be taken to rectify such behaviour.
*BYOND ckey/usernames that are deemed racist, homophobic, sexist, etc... by staff are not permitted. You will be given a chance to create a new CKEY and you must request our staff to transfer any notes.
|-
!<div align="center">Stereotypes</div>
|
* Playing a character that is based upon a specific stereotype is permitted however playing to a racial, religious or cultural caricature is not.
* Management staff, or the highest ranking alternative available, reserve the right to make calls on specific stereotypes being racially, religiously or culturally offensive.
|-
!<div align="center">No Advertising</div>
|
* Don’t post byond://, Discord, Twitch, etc, links to other servers purely for the sake of advertising. If you wish to share links to these kinds of places, either ahelp for permission or do so off the server (IE: over Byond messages or Discord).
|-
!<div align="center">Media Spoilers</div>
|
* Giving out plot spoilers to any media with malicious intent is not allowed, but the general discussion of plot that contains spoilers about media released 1 year ago or longer is fine.
|-
!<div align="center">Spam</div>
|
* Spamming chat ICly or OOCly including LOOC and Deadchat is not allowed.
** This includes copypastes, macro spam or anything else intentionally producing large amounts of message content or duplicate inputs/logs.
* You cannot use Egyptian Hieroglyphics in game.
|}
</tab>
</tabs>
|}


You can download it from https://code.visualstudio.com/ and run the installer.
===Rule 4. No griefing===
Griefing is the intent of one player wanting to cause grief or annoyance to other players or the server without a valid roleplay reason. If Staff believes that the player’s intent is to grief, then action will be taken whether or not it was the player’s intent. Any damage to the station or players caused by griefing can be repaired at an Admin's discretion. If you are being griefed, don’t retaliate - Adminhelp it and you’ll get healed. Shooting a griefer can cause you to get in trouble as well, and the combat logs you’re generating make it harder for Staff to prove who the real griefer is.


=== Step 2: Forking the Repository ===


Go to https://github.com/cmss13-devs/cmss13, and at the top right, hit “Fork” - you’ll need a GitHub account for this.
{| style="width: 100%; border: none"
|style="width: 100%; vertical-align: top;" | <tabs>
<tab name="Griefing">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Example
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
!<div align="center">Typical Griefing</div>
|
* Shooting up medbay at round start.
* Deliberately OBing the marine frontline.
* Taking a role, such as Executive Officer, and putting marines at a deliberate disadvantage. This includes not building a FOB or leaving the primary LZ defenceless.
* Sabotaging areas of the ship.
|-
!<div align="center">End of Round Grief (EORG)</div>
|
* End of Round Grief (EORG) is fighting and generating any combat logs with friendly players after the round ends and is an immediate 3-hour ban without warning. Exceptions are between normal enemies, such as Marines and Aliens, Marines and UPP, etc.
** This includes suicide at the end of the round without a valid RP reason.
|-
|}
</tab>
</tabs>
|}


Follow the prompts that come up, and you’ll have your own copy of the code on GitHub.
===Rule 5. Mechanical Exploits===
Do not abuse bugs or unintended features to gain an unfair advantage for yourself or your team.


=== Step 3: Download Git ===  
{| style="width: 100%; border: none"
|style="width: 100%; vertical-align: top;" | <tabs>
<tab name="Marine Exploits">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Example
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
!<div align="center">Not Exploits</div>
|
* A standard marine deconstructing a wall.
|-
!<div align="center">Exploits</div>
|
* A standard marine creating Ordnance Tech Grenades or Explosives.
* An Ordnance Tech stacking multiple C4 on one entity or object.
* A Specialist not selecting a kit, allowing them to use multiple existing kits.
* Stacking mini turrets and M56Ds.
|}
</tab>
<tab name="Alien Exploits">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Example
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
!<div align="center">Not Exploits</div>
|
Using fuel tanks as explosive traps by acid spitting.
|-
!<div align="center">Exploits</div>
|
* Banishing xenos on the Almayer so they can be killed for free larva.
* Banishing AFK xenos to reclaim larva.
* Walling off bodies to they cannot be recovered/revived.
* * Where bodies fall within natural defense lines this is acceptable.
|}
</tab>
</tabs>
|}


You’ll need Git installed to make any changes to the repository. Download it from https://git-scm.com/downloads.  
===Rule 6. No Metagaming or Metacommunication===
Acting upon knowledge your character would not have or providing unknowable information to another player. Should you be in a voice call with other players, you are still expected to relay information through IC channels (talking, radio, etc) to preserve in-game roleplay. IC information should not be posted to any public location where other parties can be given an advantage. Any form of cheating via metacomms will result in a permaban. All public chat on the CM Discord should refrain from talking about any ongoing round information until the round ends.


Then, on Visual Studio Code, under the Source Control tab on the left bar - the third option down, you should be presented with the option to “Clone Repository”.  
{| style="width: 100%; border: none"
|style="width: 100%; vertical-align: top;" | <tabs>
<tab name="Metagaming">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Example
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
!<div align="center">Not Metagaming</div>
|
* Xenos destroying colony assets prior to Marine landing, such as APCs, lights, vendors, etc.
* Xenos & Marines building traps to catch and kill the other side.
* Marines killing themselves after becoming infected or captured by the Xenos.
|-
!<div align="center">Metagaming</div>
|
* Wordlessly following a friend around without having any IC communications or interactions.
* Building defenses on the ship before a hostile force is en route.
* Xenos sitting next to the dropship landing pad to attack right as the Marines open the doors.
* Xenos melting every colony wall in a specific location to remove a building/defensive point.
* Killing small hosts as survivor before marines land.
** This is explicitly a rulebreak exclusively due to the extensive impact this has on roundstart balance.
* Xenos targetting critical shipside equipment or personnel before hijack to render marines ineffective without an IC justification.
* Surrounding a comms tower entirely with reinforced walls to prevent Xenos attacking it without T3s.
** Walls can be used to cover most of the tower, however there must remain access for other xenos IE barricades.
|}
</tab>
<tab name="Metacommunication">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Example
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
!<div align="center">Not Metacommunication</div>
|
* Teaching someone how to play the game and various mechanics through Voicechat, LOOC or other external communication methods.
|-
!<div align="center">Metacommunication</div>
|
* Telling someone where the enemy are, event details or other In-Character information, that would otherwise be inaccessible, through Voicechat, LOOC or other external communication methods.
|}
</tab>
</tabs>
|}


Paste the URL of your fork into the box that pops up - this should be in the format of https://github.com/[YOURUSERNAME]/cmss13. Select a folder to download the repo into, and let it run. It may take awhile.
===Rule 7. No Ban Evading / Multi-Keying===
Logging in with different accounts at different times, logging in with another account because you died (or were banned), or logging into two separate accounts at the same time. If you have multiple accounts tied to CM-SS13, please ahelp regarding them. Players caught breaking this rule may receive permabans from the server.


=== Step 4: Download Extensions ===
{| style="width: 100%; border: none"
|style="width: 100%; vertical-align: top;" | <tabs>
<tab name="FAQ">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Question
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Answer
|-
!<div align="center">Can I use a VPN?</div>
| Yes, the use of VPNs is not forbidden, however you may become captured in other people's bans.
|-
!<div align="center">Can other people play at my house?</div>
| Yes, but please ahelp beforehand so staff are aware and can make a note of it.
*Your account is held responsible if someone other than you physically plays on your account and violates any of our rules. "My little brother did it, or my friend did it." are not valid excuses or justification.
|-
!<div align="center">Can I change my ckey?</div>
| You can create a new account at your discretion, but you will need to ahelp ingame with both accounts to transfer your notes and bans. Failure to do this you may result in a ban.
* Changing your ckey will mean you will not be allowed to use your previous account. Doing so may result in a ban.
|}
</tab>
</tabs>
|}


These extensions to Visual Studio Code will allow the program to read DreamMaker code intelligently and allow you to navigate through the code faster.  
===Rule 8. Suicide, Rage-Quitting, and Logging off===
If you are a marine and need to leave the game, go to Cryo on the ship and put yourself in a cryotube. This will release your job slot and allow another player to join with your job. If you are unable to get to cryo, send an Adminhelp to staff. If you are the Queen, Adminhelp to let staff know. If you leave without cryo-ing yourself or informing staff, you risk a job ban, especially if your job is an important one. Suicide is permitted if you have a reasonable roleplay reason why, such as you are infected with a xenomorph and there is no hope of rescue, or you are the last xenomorph alive and there is no queen. Committing suicide without a valid reason will result in a ban and/or jobban.


You can get them by clicking on the extensions tab - probably the fourth or fifth option, it looks like three boxes with a fourth being added - and downloading all the “Recommended” extensions.
{| style="width: 100%; border: none"
|style="width: 100%; vertical-align: top;" | <tabs>
<tab name="Ghosting and Logging Out">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Example
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
Some roles carry the risk of punishment for logging out or ghosting without notice.
* This is particularly strict at the start of the round (roughly the first 20 minutes)
!<div align="center">High Risk Roles</div>
|
These are some example roles that are likely to be punished for logging out/ghosting without notice.
* Executive Officer
* Vehicle Crewman
* Squad Specialist
* Queen
|-
!<div align="center">Medium Risk Roles</div>
|
These are some example roles that might be punished for logging out/ghosting without notice.
* Requisitions Officer
* Cargo Technician
* Doctor
* Xeno
|-
!<div align="center">Low Risk Roles</div>
|
These are some example roles that are unlikely to be punished for logging out/ghosting without notice.
* Squad Marine
* Maintenance Technician
|-
|}
</tab>
<tab name="Suicide">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Example
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
!<div align="center">Mid-Round Suicide</div>
|
Suicide in the round is to be limited to critical situations. For example;
* When you have been abandoned on the Colony after Evacuation.
* When Xenos are confirmed to have hijacked the shuttle and are inbound.
* When you are infected and have little to no chance of being saved.
|-
!<div align="center">Round-End Suicide</div>
| Suicide at the end of the round is usually considered EORG and will land an automatic 3 hour ban.
|-
|}
</tab>
</tabs>
|}


=== Step 5: Finishing Up ===
===Rule 9. Character names===
Use a reasonable, unique, lore-friendly character name that has a first name and surname. Short reasonable nicknames are allowed inside the name (e.g. Derek 'Double-D' Donahue, Jane 'Crusher' Sanchez). Other character names should not be used, this includes ckeys. Nicknames should not be considered a meme. You may be a sibling or cousin of another player's character, however you cannot play another player's character unless it's part of a staff event. References can be made to characters in the Official CM-SS13 lore. Staff retain rights to make the final judgement if a name or Xenomorph prefix is acceptable or unacceptable.


You’ve now got a complete clone of the CM-SS13 codebase on your local computer - excluding the xenomorph sprites you would see on the main server. Don’t be alarmed if you can’t see them.
{| style="width: 100%; border: none"
|style="width: 100%; vertical-align: top;" | <tabs>
<tab name="Naming">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Example
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
* Ranked, titled, honorific, offensive, famous and pop-culture names are not allowed.
* Roman numerals may be used, but should not be excessive.
* Nicknames should not be written in all Caps Lock
* Nicknames should at the maximum contain two words.
!<div align="center">Acceptable Names</div>
|
* Arthur Walker
* Jeremy Bennett
* Becky Jones
|-
!<div align="center">Unacceptable Names/Prefixes</div>
|
* Adolf Hitler
* Vladimir Putin
* Donald Trump
* Johnny 'Nazi' Johnson
* Mike Rotch
* David Weyland
* Ellen Ripley
*DIK
*FAG
*NIG
*XIG


== Making a Change ==
Names that are sexual puns/references of banned words/topics.
|-
!<div align=center”>Exceptions</div>
|
* A name comprised of extremely common names (I.E John Williams) can be excused for being shared with someone otherwise forbidden, provided the player is not attempting to play as the linked person.
|-
!<div align=center”>Xeno Names</div>
|
* Xeno names cannot be 18+ related, slurs, or abbreviations of other banned words.
|-
|}
</tab>
</tabs>
|}


All changes you make to the code must be done on a new branch.  
===Rule 10. Lethal Force===
Do not attack another player without a legitimate, explainable roleplay reason that could be applied in a similar, real-life scenario. A fist fight does not suddenly escalate into a gun fight. Should one defend themselves from grief or improper escalation, the staff handling the matter decides if a punishment is given out and to who. Staff may also decide to leave things in character. Even if you are justified, you are still susceptible to Marine Law.
{| style="width: 100%; border: none"
|style="width: 100%; vertical-align: top;" | <tabs>
<tab name="Examples">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Example
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
!<div align="center">Escalation</div>
|
* Fists/General melee
* Knives/Dangerous melee
* Lethal Weapons


A branch is another version of your codebase - made from your “master” branch - which should be identical to the “master” branch present on the main repo - which changes can be made to without affecting your “master” branch.
* If at any point combat is disengaged and both parties leave the area, you cannot skip escalation and plunge back into a fight. What's done is done.
|-
!<div align="center">Exceptional Circumstances</div>
|
Some Exceptional Circumstances exist that give cause to bypass typical escalation. These include, but are not limited to the following situations:
* There is one evac pod left and four people are trying to board it. The Hive is closing in on you, in desperation you kill the marine in front of you to take their place.
* You are on the frontlines, another marine is enraged at you because you took one of his ammo magazines. You're engaged in a furious battle with the approaching hive and the fellow marine is attempting to disarm and tackle you to the ground. With no barricades around you, and no safe area to take cover within, you shoot the marine.
|-
!<div align="center">Injuriy & Risk to Life</div>
|
In cases where there is a serious threat to life, such as being punched to the borders of crit, escalation in the linear sense does not apply. The most important part of escalation is appropriate force, this means that you use an appropriate amount of force to the situation.
For example:
* Being punched twice on full health is not a serious threat to your life. It would not warrant you throwing hell to the wind and blasting away your comrades.
* Being punched twice after already being critically injured can be seen as a risk to your life, and you can take appropriate action. This is subject to circumstances however and not a greenlight for any situation.
|-
|}
</tab>
</tabs>
|}


A “commit” is a save of your changes to the code you’ve made. Every time you “commit” your changes to the branch, you are saving all your changes made so far. All code must be “committed” before it can be sent to the main repository.
===Rule 11. Marine Law===


To start with making changes, you must make a new branch on your forked repository, from your master branch. Your master branch should never be committed to, and should be a clean state.
{| style="width: 100%; border: none"
|style="width: 100%; vertical-align: top;" | <tabs>
<tab name="Marine Law">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Information
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
!<div align="center">Malicious Compliance</div>
|
* Malicious Compliance with IC Military Law to impose excessive punishments, make an arrest on a technicality of someone non-disruptive and acting in good faith, or causing intentional delays in processing, release or appeals will fall under rule 3, Community Expectations and are actionable.  


Every PR you make should have a new branch. This allows for commits you make on different branches to not affect your other branches, letting you work on multiple projects at once.
* Malicious Compliance does not apply in any case where IC or OOC provocation is present. (For example, following and taunting/threatening a player, engaging in mundane, but disruptive actions and continuing when asked or told to stop, etc)


=== Step 1: Making a New Branch ===
* Malicious Compliance is determined by Staff and reviewed by Management/Head Staff where necessary.
|-
!<div align="center">Mandatory Obedience</div>
|
The following roles are required to follow Marine Law by the server rules. Breaking Marine Law may result in jobbans or further consequences.
* All Military Police roles
* Senior Enlisted Advisor
* USCM Synthetics
|-
!<div align="center">Exceptions</div>
|
* Military Police may ignore Minor Crimes unless ordered to enforce them, but they may not ignore Major or Capital Crimes.
* Survivor Synthetics are not forced to follow Marine Law, dependent on their chosen alignment (Colony/Survivors/USCM/WY etc.)
* Marine Law can be broken when necessary to preserve the lives and safety of others.
|-
|}
</tab>
<tab name="Mutinies">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Information
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
Mutinies must be Adminhelped by a chosen leader stating the reasoning and the players directly involved. There must be at least 5 members. with MPs not eligible to mutiny.
!<div align="center">Mutinies</div>
|
* If the mutiny does not have a valid reason, it can't happen.
** Staff reserve the right to grant or deny mutinies, and to decide if the reason given is sufficient.
* Mutiny cannot occur during hijack, and any ongoing mutiny must be ended upon hijack.
* Only the Acting Commander can be mutinied against for their decisions, actions, or inactions. They must be given a chance to stand down peacefully.
* During the mutiny, attacking any uninvolved, medical, or surrendered personnel is strictly forbidden, as is perma-killing anyone involved. If you have surrendered during a mutiny, you must remain as such.
** Once you have picked a side, it is permanent. No take-backs unless you surrender.
* Once concluded, all sides must be given medical treatment. Only a Major or higher is able to deny treatment or battlefield execute specific mutineers.
* Mutinies must have 5 members minimum.
** Roles bound to follow Marine Law through Mandatory Obedience are unable to mutiny.
*** The USCM Synthetic is not required to aid Command in a Mutiny situation if this would put themselves at high risk, however their choice to help or not is binding, and they are unable to change their mind afterwards.
|-
!<div align="center">Valid Reason Examples</div>
|
* Commander is thoroughly incompetent, an ineffective leader '''and''' the next person in line would be a better leader.
* Commander is generally noncommunicative and make no effort to lead.
* Commander is refusing evacuation, either of the AO or ship during hijack
** See below for further details
|-
!<div align="center">Invalid Reason Examples</div>
|
* Xenos achieved an early or relatively easy victory, outside the control of command.
* MPs have arrested your specialist.
|-
!<div align="center">Evacuation Mutinies</div>
|
* This applies to both the field and the ship during hijack.
* This is the only permitted mutiny during hijack.
* AO evacuation refusal requires 5 people to mutiny as there may be reasons beyond the knowledge of one person.
* Ship evacuation refusal may be mutinied by a single person.
** MPs are not required to help the Commander in this mutiny, and may join/aide/start the mutiny themselves.
** Ship evacuation mutinies do not REQUIRE ahelps, however it is recommended to ahelp before or after to make intentions known to staff.
* Ship evacuation refusal mutinies must provide '''at least''' one chance for the Commander to authorise evacuation, and must use '''minimum''' force to succeed.
** No terminating the entire CIC because the Commander doesn't want to evacuate.
|-
|}
</tab>
<tab name="Battlefield Executions">
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable"
! scope="col" style="background-color:#EEEEFF;" width=150|Information
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Description
|-
!<div align="center">Battlefield Executions</div>
| Whitelisted Commanding Officers are allowed to instantly kill any player at any time if the player fulfills the conditions found in Marine Law. Excessive or poorly-reasoned battlefield executions (such as BEing MPs over a valid arrest) may end with the Commanding Officers being removed from the whitelist.
|-
|}
</tab>
</tabs>
|}


Press Control + Shift + P to bring up the Command Pallet. This allows you to control Visual Studio Control easily, but we want the command “Create new Branch”. Type that in and press enter to run it. Give your branch a name - like new-helmet. Select which branch to make it from - that will be your master branch.
===Rule Precedents===


Then, switch to this branch. You can do this at the bottom of the Source Control tab, under the Branches title - you might have to click on it to show all your branches. Right click on your new branch, and select the option to switch to it.
==== Rule 1 ====


Now, you can make whatever changes you like, and you can commit them to this branch without altering your master branch.
1. Can you RP urinating on someone?


=== Step 2: Modifying the Code ===
No. It's LRP & 18+


Now, if you make any change to any file within the repo, Git will notice and add it to the modified files in the Source Control tab.


You can make a simple change - such as altering an item description - just to see your code changes reflected in game. To find an item, use the Search tab on the left - the magnifying glass - and type in the name or description if the item as it is in game.
2. Can I Call The Incendiary OB "Coom OB"?


Once you’ve made this change, it’ll be noticed at the top of the Source Control tab.
No, it's LRP/18+ and a sexual reference meme.


=== Step 3: Testing your Code ===
==== Rule 2 ====


Press F5 - this will start your code with the debugger attached. This will automatically pause the server and tell you when an error - usually known as a runtime - occurs.
1. Can I wear uniforms found on the colony, such as pyjamas?


You can press Control-F5 to start without the debugger.
If you're a PFC, go for it, but you're still susceptible to marine law. SLs are held to higher standards and should not do it.
 
Then, at the bottom right of your Windows interface, click the chevron to view your hidden processes. Click on the green DreamDaemon circle, and you can see the server process that has booted up. Then, on the World tab at the top, press Join. This will log you in to the server, where you will automatically have full Admin permissions.
 
Find your item in game - or spawn it in with the admin game-panel - and it should have the changes you’ve made in the code. If it doesn’t- you probably didn’t save the file. Terminate the server using the stop button on Visual Studio Code or by right clicking on the DreamDaemon process and pressing Stop.
 
=== Step 4: Committing your Changes ===
 
At the top of the Source Control tab, your modified file should be under “Changes”. Hover over the file name you have modified, and press the Plus symbol - or do the same over the Changes button to “stage” your changes.
 
Once your changes have been “staged”, they have been selected to be committed. You can give it a commit message on the box with “Message”, and press the tick at the top to commit those changes.
 
Once this has been completed, you’ve committed your changes locally - but they have not been published to your GitHub fork.
 
=== Step 5: Publishing to GitHub ===
 
This is quite simple. On the Source Control tab, you should now see the “Publish Branch”. This will publish your branch, along with your changes, to your fork on GitHub. You can navigate to it on the web to see these changes.
 
If you make any further changes to this branch and commit them, you will see the “Sync Changes” option instead. This does the same thing - “pushing” all your changes to your fork on GitHub.
 
== Making a Pull Request ==
 
A “pull request” is a *request* for the main repository to *pull* - or more accurately, merge - the contents of your branch into the master branch. This process allows for code to be tested and reviewed by maintainers/developers, before being merged into the master branch.
 
=== Step 1: Navigating the Web Interface ===
 
Head to your repository on GitHub - not the main CM-SS13 repo. Then, click on “master” and type in the name of your branch.
 
Hit “Pull Request” on the right, and it’ll bring up the Pull Request editor - automatically setting the merge as being from your branch to the master branch at the main CM-SS13 repository.
 
=== Step 2: Creating the Pull Request ===
 
Give your PR a good title - this will be the message of the commit to the main branch containing all your code.
 
Then, fill in the PR description, including a descriptive changelog. Put your BYOND username next to the first :cl: to ensure you are accurately credited.
 
Then, hit Create Pull Request (or don’t, if you’re uselessly changing one description as a test).
 
=== Step 3: Code Review ===
 
GitHub will automatically run some tests on your code, which may fail, resulting in you having to change your code. The developers will review your code, and may also request changes.
 
In order to carry out the changes, simply make the changes on your branch on your local repository, and press “Sync Changes”, this will automatically update the PR.
 
If a developer has marked your PR as a draft, you will have to mark it as being ready for review. You can do this at the bottom of the web interface on your PR.
 
== Staying in Sync ==
 
As other PRs are merged into the repository, your branch will slowly become out of date. This will become an issue over time, as you modify code that has been changed by another recent PR, and you find conflicts that didn’t need to happen.
 
To avoid this, regularly go to your master branch of your fork on the web interface, and press “Fetch from Upstream”, to add all the commits recently merged to your fork.
 
Then, on Visual Studio Code, you can “Sync Changes” to update your local copy of the master branch.
 
Do this regularly to ensure you don’t fall out of date with any changes.
 
= Appendix =
 
== Merge Conflicts ==
 
=== Mapping Conflicts ===
 
Install the git hooks in tools/hooks by hitting “Install.bat”. This will help during mapping conflicts by marking areas that are conflicting, allowing you to open an editor (such as StrongDMM), look for the conflict markers and resolve the issue.
 
It will look like the conflict has entirely disappeared - but it *hasn’t* - the MapMerger has just automatically dumped everything from the conflicting branches together in a mess that *you* have to fix.
 
=== Code Conflicts ===
 
Find the conflict markers, indicated with a bunch of >>>>>>>>> and <<<<<<<<<. VSC should make this obvious, and in some cases, deconflict the files itself. Where it fails to do so, you will need to remove the conflict markers and add the code together from both branches, and test it so it works, and merge the changes together.
 
== Glossary ==
 
=== Branch ===
 
A version of your fork that you can freely commit changes to without affecting other branches.
 
=== Commit ===
 
A change to a branch, can be of any size from a single space added to one file to completely rewriting the entire repository.
 
=== Fork ===
 
A copy of the CM-SS13 repository that you own, and can make whatever changes to that you like without impacting the main repo.
 
=== Repository ===
 
Often known as a repo. Ours contains all of the code, maps and assets for CM-SS13 - excluding the xenomorph sprites.
 
=== PR ===
 
Pull Request - a request for the main repository to merge the changes present in one of the branches of your fork into the master branch of the main, upstream repository.
 
=== Merge ===
 
Where all the commits from a branch are applied to another branch. For example, merging your origin branch containing a new feature to an upstream master branch.
 
=== Merge Conflicts ===
 
Where two branches from separate contributors have touched the same code, when one of them is merged, you will have a conflict preventing automatic merging. This involves manually fitting the code together, allowing both changes to exist without overwriting either.
 
=== Remote ===
 
A remote is a version of your repository that is not stored on your computer - such as on GitHub. This includes both your fork and the upstream, main CM-SS13 repo.
 
=== Origin ===
 
This will be your fork of the CM-SS13 repository.
 
=== Upstream ===
 
The upstream of your fork will be the main CM-SS13 repo. Think of changes flowing down a stream from the main repo to your fork when you “Fetch Upstream”.
 
=== Git ===
 
The version control system used by CM-SS13, allowing us to synchronise changes being made by many different contributor - and easily go back if something goes wrong.
 
=== Diff ===
 
Shows the changes between the current copy of the code and the new code that you have committed.
 
=== VSC / VS Code ===
 
Visual Studio Code, the text editor we use for DM development.

Latest revision as of 08:54, 18 May 2023

Rule 0. Admins

Information Description
Rule 0 - Override
Admins and Above retain the authority to ignore or alter the enforcement of specific rules at their discretion should they feel it is in the best interest of the current round, the server or the player base at large. In the absence of an Admin or higher ranking member of staff, Moderators may exercise this power following their own chain of authority. Any use of Rule 0 holds it’s user fully accountable for the actions taken due to their change of the rulings.
Rule 0.1 - Intent
Rules are enforced as intended. Every example of a rule break cannot be defined as written, therefore, enforcement of the rules is subject to staff interpretation of the rule's intention. Staff may choose to handle minor rule breaks by utilizing in-game tools to correct improper behavior. Staff retain discretion on when a minor rule break can be handled via "In-Character" consequences in place of warning notes and/or bans. Minor rule breaks such as OOC in IC/Netspeak cannot be handled "In-Character." Staff members shall not use "In-Character" consequences for major rule breaks such as Mass Grief/ERP/Multikeying. If staff use "In-Character" behavior adjusment, no warning notes and/or bans shall be issued, unless further rule violations take place. Players shall not request a staff member to handle things "In-Character" and the final decision rests solely on the staff member conducting the investigation
Rule 0.2 - Authority
If a staff member gives you an instruction or makes a ruling, do not argue with the staff member and follow the instruction/accept the ruling. You may file a staff report on the forums or take it up with their manager directly if you do not agree with the decision made after the round ends. Arguing with a staff member may lead to you being punished. Staff members are volunteers and will not tolerate toxicity or hostility during the course of their duties.

Rule 1. No Erotic Role Play (ERP), erotic content, or 18+ sexual content

Roleplay intended to elicit a sexual response from the receiver(s), including but not limited to writing stories (WGW) or posting links to adult content. Doing so will almost always result in an instant permaban from our server. However, these actions could still be susceptible to Marine Law. A good rule of thumb for whether an interaction crosses this line would be to consider if the action would be allowed in a PG-13 rated movie in the USA.

Staff reserve the right to make judgement calls on situations to determine if they constitute a breach of 18+ or erotic conduct. If something is overly disgusting or crosses a line in a way that becomes an 18+ situation, it may be punished for regardless of nature.
  • If you are not sure whether something you wish to say or do is okay, AHelp first. We would rather you ask and be told no, than have it happen and a ban become necessary.
Example Description
Sexual Acts
  • No character should ever engage in any form of sexual intercourse in the game, whether alone or with another player.
  • No sexual act or genitalia should ever be given explicit description. If a sexual act must be referenced, there should never be a description of how particular body parts made contact or interacted in any way, nor should any particular act be named.
    • Distasteful but non-sexual bravado do not apply to this. A marine scratching their nuts, for example, is fine.
Euphemisms
  • Euphemisms that also have a sexual meaning are allowed in non-sexual contexts. Common terms or phrases like "Suck my dick" are fine, as long as saying such is not a literal invitation or solicitation to do so.

The above are guidelines for reference, and it is highly recommended not to straddle the line along what is and is not allowed when dealing with erotic/18+ content.

Rule 2. Roleplay

CM-SS13 is intended to be a Medium Roleplay server. Play a reasonably realistic character. Treat your character as a separate entity from you, the player. Your character's actions, feelings, and knowledge in-game should be based solely on the character's experiences and not your own as the player. Low roleplay actions that have no regard for your character or the setting (Memes, silly copypaste spam IC) are not acceptable. Character development can occur over rounds but each round is a soft-reset, meaning you can have previous mission experience but your character will never have died or fled the ship in the past. Follow the Roleplay Standards.

  • Major shenanigans that may disrupt the normal flow of the round at roundstart, (This includes but is not limited to; big or lethal fights, briefing brawls, riots, massive equipment restrictions and tackling players trying to reach their prep room.), are not tolerated.
Standard Expectation
Pre-Drop Arrests and Riots
  • Causing riots on the dropship over an arrest before first drop will be considered round start shenanigans and staff members will intervene with OOC punishments. You shouldn’t lynch a MP and risk your career because they are arresting a marine who has entered the dropship. If you are wanted and enter the dropship to try and avoid arrest you will be held accountable if issues arise with MPs.
  • You cannot initiate a jailbreak before first drop.
Sanity
  • All personnel employed by the USCM are mentally stable and physically fit for duty. They would not desert their post or go against the USCM without a good reason. Marriages are forbidden, no two people employed by the USCM on the same ship may be married. The USCM has knowledge of most threats, including all human forces (UPP, CLF, PMC, etc) and general knowledge of the Xenomorph hive structure. The USCM does not know there is a Xenomorph threat on the planet of operation unless that information is given in a custom event.
Deployment
  • All personnel deployed should be following their role requirements. A doctor would not deploy to fight Xenos on the front line, a Squad Medic would not only be healing themself, and a Squad Leader would not ignore the orders of command just to do their own thing.
  • Higher ranking squad marines (such as the squad-leader, specialist, smart-gunner and RTO) should be following the orders assigned to them by the commander instead of running off to go fight alone. Special circumstances exclude this requirement, but players should be prepared to justify their actions if contacted by staff.
  • You cannot refuse to deploy until someone is released from jail, or in order to break them free.
  • Heads of Departments (CE, RO, CMP and CMO) should not be leaving the ship barring exceptional circumstances.
  • All marines should be deploying where possible, refusing to deploy because someone got arrested is not allowed.
  • Shipside Crew, where authorised to deploy, must remain in secure areas.
Ship Modifications
  • Deconstruction of the ship should not be occuring before first drop & confirmed contact. The marines would not immediately resort to taking their warship to pieces for a random unconfirmed distress call.
    • This includes deconstruction of things like chairs in briefing, however does not include the barrels and crates scattered around maintenance.
  • Modifications to the ship should not be made with meta-purposes, no building a maze or bunker on the ship intended to help secure the ship for hijack before you even know hijack is a thing.
Synthetics
  • Synthetics are cold and do not feel emotions as strongly as humans, though they may fake them. They serve the USCM and may not turn against them. Synthetics must adhere to the Synthetic Programming and Guidelines.
  • Synthetic Survivors have altered Programming which can also be found there.
  • Synthetic Guideline breaches are dealt with by the Synthetic Whitelist Council, who can be contacted on discord or through Player Reports.
Survivors
  • Survivors have more leeway than marines with their mental stability due to the trauma they may have experienced during the xenomorph attack. They may be suffering PTSD, paranoia or similar conditions for roleplaying purposes. Survivors may NOT be hostile unless they have been spawned as hostile survivors (CLF).
ID Cards
  • These should only be taken for a roleplay reason, such as from a dead XO to call for help on a computer in the ship’s bridge. If you take an ID or find one from a living player (or a dead player that has since been revived), you should make every attempt to return it unless your character has a good reason not to.
  • You should not grant yourself or others increased access to areas of the ship unless there is a personnel shortage or exceptional reason to do so.
    • Death or absence of any senior officers is suitable reason to grant yourself needed access to run the operation.
    • Requisitions missing personnel is a valid reason to give other people or yourself access to Requisitions etc.
Language
  • Spamming chat (Local or Radio) with non-english characters, symbols or other gibberish is considered LRP, and a violation of Rule 2
Aliens & Predators
  • Marines know what Xenos are and have encountered them before. They have a basic knowledge of how the hive works.
    • They do not know there are Xenos on the colony.
  • Marines have not encountered Predators before. Any encounters are to be considered the first of their kind. Marines are permitted to roleplay "I've heard stories and/or legends" in regards to Predators, but metagaming knowing everything about them is a violation. Nicknames that are realistic such as "Jamaicans" "Dreadlock Lizards" "Spooks" "Phantoms or Ghosts" are acceptable. Avoid meme/gaming terminology such as "maicers"
Standard Expectation
Freedom
  • Aliens have no free will. They are a hivemind, and their purpose is to enforce the will of the Queen and expand the Hive.
  • They are not friendly and will not negotiate.
Language
  • Xeno hivemind is an English translation of their thoughts, so words such as “hydro” or “shuttle” are acceptable.
  • Spamming "Reeeee" and similar such behaviour in Hivemind or Local Chat is not allowed.
  • Calling the Runner caste a "Rooner" is acceptable.
Marines
  • Due to the Hivemind, xenos know everything every xeno learns and know the basics of human equipment.
  • At the start of the round, the Xenos can sense the human's ship looming above their hive and are aware that human forces will be visiting the colony shortly.
Larva
  • Larva should typically remain within the Hive, this is especially the case for roundstart larva, and avoid the frontlines.
  • Larva cannot sneak onto dropships to get to the marine ship.
  • Larva are not recon castes, and should not be seeking out survivors.
Queen
  • The Queen can banish Xenos who fail to uphold these standards and expectations.
  • Abuse of banish for memes or other reasons that would not be applicable may result in punishment.
Standard Expectation
Predators
  • Predators are honorable hunters. They must follow the Honor Code and act like a serious predator, not a prankster.
  • The USCM does not hold any information about these beings, meaning each contact is unknown regarding them.
  • Predator Honor Code breaches are handled by the Predator Whitelist Council, who can be contacted on Discord or through Player Reports.

Rule 3. Community Expectations

The general behavioural expectations for members of the community. Unless explicitly stated these rules apply to all areas of the community.

  • Don't be a dick.
  • This is not a complete list and only includes the most important elements.
Expectation Details
Malicious Compliance (Marine Law)
  • Malicious Compliance with Marine Law is detailed under Rule 11 (Marine Law)
English Only
  • All communications within the server (IC and OOC) should be done in English only. Phrases from other languages are fine but should not make up the majority of your conversations.
  • This extends to the use of Netspeak in-character. You should not be using LOL, WTF,
Profane RP
  • Roleplaying hostile actions, beliefs or emotions through the use of profanity is permitted. However staff reserve the right to make calls on situations if a player has crossed the line. If a staff member tells you to stop, you stop.
Racism and Bigotry
  • Usage of slurs IC/OOC on the server will result in a 7 day ban, automatically.
  • Racism, the use of slurs and other targeting terms or phrases is strictly forbidden and will not be tolerated.
  • Being Homophobic, Sexist or a general bigot is not ok, and action will be taken to rectify such behaviour.
  • BYOND ckey/usernames that are deemed racist, homophobic, sexist, etc... by staff are not permitted. You will be given a chance to create a new CKEY and you must request our staff to transfer any notes.
Stereotypes
  • Playing a character that is based upon a specific stereotype is permitted however playing to a racial, religious or cultural caricature is not.
  • Management staff, or the highest ranking alternative available, reserve the right to make calls on specific stereotypes being racially, religiously or culturally offensive.
No Advertising
  • Don’t post byond://, Discord, Twitch, etc, links to other servers purely for the sake of advertising. If you wish to share links to these kinds of places, either ahelp for permission or do so off the server (IE: over Byond messages or Discord).
Media Spoilers
  • Giving out plot spoilers to any media with malicious intent is not allowed, but the general discussion of plot that contains spoilers about media released 1 year ago or longer is fine.
Spam
  • Spamming chat ICly or OOCly including LOOC and Deadchat is not allowed.
    • This includes copypastes, macro spam or anything else intentionally producing large amounts of message content or duplicate inputs/logs.
  • You cannot use Egyptian Hieroglyphics in game.

Rule 4. No griefing

Griefing is the intent of one player wanting to cause grief or annoyance to other players or the server without a valid roleplay reason. If Staff believes that the player’s intent is to grief, then action will be taken whether or not it was the player’s intent. Any damage to the station or players caused by griefing can be repaired at an Admin's discretion. If you are being griefed, don’t retaliate - Adminhelp it and you’ll get healed. Shooting a griefer can cause you to get in trouble as well, and the combat logs you’re generating make it harder for Staff to prove who the real griefer is.


Example Description
Typical Griefing
  • Shooting up medbay at round start.
  • Deliberately OBing the marine frontline.
  • Taking a role, such as Executive Officer, and putting marines at a deliberate disadvantage. This includes not building a FOB or leaving the primary LZ defenceless.
  • Sabotaging areas of the ship.
End of Round Grief (EORG)
  • End of Round Grief (EORG) is fighting and generating any combat logs with friendly players after the round ends and is an immediate 3-hour ban without warning. Exceptions are between normal enemies, such as Marines and Aliens, Marines and UPP, etc.
    • This includes suicide at the end of the round without a valid RP reason.

Rule 5. Mechanical Exploits

Do not abuse bugs or unintended features to gain an unfair advantage for yourself or your team.

Example Description
Not Exploits
  • A standard marine deconstructing a wall.
Exploits
  • A standard marine creating Ordnance Tech Grenades or Explosives.
  • An Ordnance Tech stacking multiple C4 on one entity or object.
  • A Specialist not selecting a kit, allowing them to use multiple existing kits.
  • Stacking mini turrets and M56Ds.
Example Description
Not Exploits

Using fuel tanks as explosive traps by acid spitting.

Exploits
  • Banishing xenos on the Almayer so they can be killed for free larva.
  • Banishing AFK xenos to reclaim larva.
  • Walling off bodies to they cannot be recovered/revived.
  • * Where bodies fall within natural defense lines this is acceptable.

Rule 6. No Metagaming or Metacommunication

Acting upon knowledge your character would not have or providing unknowable information to another player. Should you be in a voice call with other players, you are still expected to relay information through IC channels (talking, radio, etc) to preserve in-game roleplay. IC information should not be posted to any public location where other parties can be given an advantage. Any form of cheating via metacomms will result in a permaban. All public chat on the CM Discord should refrain from talking about any ongoing round information until the round ends.

Example Description
Not Metagaming
  • Xenos destroying colony assets prior to Marine landing, such as APCs, lights, vendors, etc.
  • Xenos & Marines building traps to catch and kill the other side.
  • Marines killing themselves after becoming infected or captured by the Xenos.
Metagaming
  • Wordlessly following a friend around without having any IC communications or interactions.
  • Building defenses on the ship before a hostile force is en route.
  • Xenos sitting next to the dropship landing pad to attack right as the Marines open the doors.
  • Xenos melting every colony wall in a specific location to remove a building/defensive point.
  • Killing small hosts as survivor before marines land.
    • This is explicitly a rulebreak exclusively due to the extensive impact this has on roundstart balance.
  • Xenos targetting critical shipside equipment or personnel before hijack to render marines ineffective without an IC justification.
  • Surrounding a comms tower entirely with reinforced walls to prevent Xenos attacking it without T3s.
    • Walls can be used to cover most of the tower, however there must remain access for other xenos IE barricades.
Example Description
Not Metacommunication
  • Teaching someone how to play the game and various mechanics through Voicechat, LOOC or other external communication methods.
Metacommunication
  • Telling someone where the enemy are, event details or other In-Character information, that would otherwise be inaccessible, through Voicechat, LOOC or other external communication methods.

Rule 7. No Ban Evading / Multi-Keying

Logging in with different accounts at different times, logging in with another account because you died (or were banned), or logging into two separate accounts at the same time. If you have multiple accounts tied to CM-SS13, please ahelp regarding them. Players caught breaking this rule may receive permabans from the server.

Question Answer
Can I use a VPN?
Yes, the use of VPNs is not forbidden, however you may become captured in other people's bans.
Can other people play at my house?
Yes, but please ahelp beforehand so staff are aware and can make a note of it.
  • Your account is held responsible if someone other than you physically plays on your account and violates any of our rules. "My little brother did it, or my friend did it." are not valid excuses or justification.
Can I change my ckey?
You can create a new account at your discretion, but you will need to ahelp ingame with both accounts to transfer your notes and bans. Failure to do this you may result in a ban.
  • Changing your ckey will mean you will not be allowed to use your previous account. Doing so may result in a ban.

Rule 8. Suicide, Rage-Quitting, and Logging off

If you are a marine and need to leave the game, go to Cryo on the ship and put yourself in a cryotube. This will release your job slot and allow another player to join with your job. If you are unable to get to cryo, send an Adminhelp to staff. If you are the Queen, Adminhelp to let staff know. If you leave without cryo-ing yourself or informing staff, you risk a job ban, especially if your job is an important one. Suicide is permitted if you have a reasonable roleplay reason why, such as you are infected with a xenomorph and there is no hope of rescue, or you are the last xenomorph alive and there is no queen. Committing suicide without a valid reason will result in a ban and/or jobban.

Some roles carry the risk of punishment for logging out or ghosting without notice.
  • This is particularly strict at the start of the round (roughly the first 20 minutes)
Example Description
High Risk Roles

These are some example roles that are likely to be punished for logging out/ghosting without notice.

  • Executive Officer
  • Vehicle Crewman
  • Squad Specialist
  • Queen
Medium Risk Roles

These are some example roles that might be punished for logging out/ghosting without notice.

  • Requisitions Officer
  • Cargo Technician
  • Doctor
  • Xeno
Low Risk Roles

These are some example roles that are unlikely to be punished for logging out/ghosting without notice.

  • Squad Marine
  • Maintenance Technician
Example Description
Mid-Round Suicide

Suicide in the round is to be limited to critical situations. For example;

  • When you have been abandoned on the Colony after Evacuation.
  • When Xenos are confirmed to have hijacked the shuttle and are inbound.
  • When you are infected and have little to no chance of being saved.
Round-End Suicide
Suicide at the end of the round is usually considered EORG and will land an automatic 3 hour ban.

Rule 9. Character names

Use a reasonable, unique, lore-friendly character name that has a first name and surname. Short reasonable nicknames are allowed inside the name (e.g. Derek 'Double-D' Donahue, Jane 'Crusher' Sanchez). Other character names should not be used, this includes ckeys. Nicknames should not be considered a meme. You may be a sibling or cousin of another player's character, however you cannot play another player's character unless it's part of a staff event. References can be made to characters in the Official CM-SS13 lore. Staff retain rights to make the final judgement if a name or Xenomorph prefix is acceptable or unacceptable.

  • Ranked, titled, honorific, offensive, famous and pop-culture names are not allowed.
  • Roman numerals may be used, but should not be excessive.
  • Nicknames should not be written in all Caps Lock
  • Nicknames should at the maximum contain two words.
Example Description
Acceptable Names
  • Arthur Walker
  • Jeremy Bennett
  • Becky Jones
Unacceptable Names/Prefixes
  • Adolf Hitler
  • Vladimir Putin
  • Donald Trump
  • Johnny 'Nazi' Johnson
  • Mike Rotch
  • David Weyland
  • Ellen Ripley
  • DIK
  • FAG
  • NIG
  • XIG

Names that are sexual puns/references of banned words/topics.

Exceptions
  • A name comprised of extremely common names (I.E John Williams) can be excused for being shared with someone otherwise forbidden, provided the player is not attempting to play as the linked person.
Xeno Names
  • Xeno names cannot be 18+ related, slurs, or abbreviations of other banned words.

Rule 10. Lethal Force

Do not attack another player without a legitimate, explainable roleplay reason that could be applied in a similar, real-life scenario. A fist fight does not suddenly escalate into a gun fight. Should one defend themselves from grief or improper escalation, the staff handling the matter decides if a punishment is given out and to who. Staff may also decide to leave things in character. Even if you are justified, you are still susceptible to Marine Law.

Example Description
Escalation
  • Fists/General melee
  • Knives/Dangerous melee
  • Lethal Weapons
  • If at any point combat is disengaged and both parties leave the area, you cannot skip escalation and plunge back into a fight. What's done is done.
Exceptional Circumstances

Some Exceptional Circumstances exist that give cause to bypass typical escalation. These include, but are not limited to the following situations:

  • There is one evac pod left and four people are trying to board it. The Hive is closing in on you, in desperation you kill the marine in front of you to take their place.
  • You are on the frontlines, another marine is enraged at you because you took one of his ammo magazines. You're engaged in a furious battle with the approaching hive and the fellow marine is attempting to disarm and tackle you to the ground. With no barricades around you, and no safe area to take cover within, you shoot the marine.
Injuriy & Risk to Life

In cases where there is a serious threat to life, such as being punched to the borders of crit, escalation in the linear sense does not apply. The most important part of escalation is appropriate force, this means that you use an appropriate amount of force to the situation. For example:

  • Being punched twice on full health is not a serious threat to your life. It would not warrant you throwing hell to the wind and blasting away your comrades.
  • Being punched twice after already being critically injured can be seen as a risk to your life, and you can take appropriate action. This is subject to circumstances however and not a greenlight for any situation.

Rule 11. Marine Law

Information Description
Malicious Compliance
  • Malicious Compliance with IC Military Law to impose excessive punishments, make an arrest on a technicality of someone non-disruptive and acting in good faith, or causing intentional delays in processing, release or appeals will fall under rule 3, Community Expectations and are actionable.
  • Malicious Compliance does not apply in any case where IC or OOC provocation is present. (For example, following and taunting/threatening a player, engaging in mundane, but disruptive actions and continuing when asked or told to stop, etc)
  • Malicious Compliance is determined by Staff and reviewed by Management/Head Staff where necessary.
Mandatory Obedience

The following roles are required to follow Marine Law by the server rules. Breaking Marine Law may result in jobbans or further consequences.

  • All Military Police roles
  • Senior Enlisted Advisor
  • USCM Synthetics
Exceptions
  • Military Police may ignore Minor Crimes unless ordered to enforce them, but they may not ignore Major or Capital Crimes.
  • Survivor Synthetics are not forced to follow Marine Law, dependent on their chosen alignment (Colony/Survivors/USCM/WY etc.)
  • Marine Law can be broken when necessary to preserve the lives and safety of others.
Mutinies must be Adminhelped by a chosen leader stating the reasoning and the players directly involved. There must be at least 5 members. with MPs not eligible to mutiny.
Information Description
Mutinies
  • If the mutiny does not have a valid reason, it can't happen.
    • Staff reserve the right to grant or deny mutinies, and to decide if the reason given is sufficient.
  • Mutiny cannot occur during hijack, and any ongoing mutiny must be ended upon hijack.
  • Only the Acting Commander can be mutinied against for their decisions, actions, or inactions. They must be given a chance to stand down peacefully.
  • During the mutiny, attacking any uninvolved, medical, or surrendered personnel is strictly forbidden, as is perma-killing anyone involved. If you have surrendered during a mutiny, you must remain as such.
    • Once you have picked a side, it is permanent. No take-backs unless you surrender.
  • Once concluded, all sides must be given medical treatment. Only a Major or higher is able to deny treatment or battlefield execute specific mutineers.
  • Mutinies must have 5 members minimum.
    • Roles bound to follow Marine Law through Mandatory Obedience are unable to mutiny.
      • The USCM Synthetic is not required to aid Command in a Mutiny situation if this would put themselves at high risk, however their choice to help or not is binding, and they are unable to change their mind afterwards.
Valid Reason Examples
  • Commander is thoroughly incompetent, an ineffective leader and the next person in line would be a better leader.
  • Commander is generally noncommunicative and make no effort to lead.
  • Commander is refusing evacuation, either of the AO or ship during hijack
    • See below for further details
Invalid Reason Examples
  • Xenos achieved an early or relatively easy victory, outside the control of command.
  • MPs have arrested your specialist.
Evacuation Mutinies
  • This applies to both the field and the ship during hijack.
  • This is the only permitted mutiny during hijack.
  • AO evacuation refusal requires 5 people to mutiny as there may be reasons beyond the knowledge of one person.
  • Ship evacuation refusal may be mutinied by a single person.
    • MPs are not required to help the Commander in this mutiny, and may join/aide/start the mutiny themselves.
    • Ship evacuation mutinies do not REQUIRE ahelps, however it is recommended to ahelp before or after to make intentions known to staff.
  • Ship evacuation refusal mutinies must provide at least one chance for the Commander to authorise evacuation, and must use minimum force to succeed.
    • No terminating the entire CIC because the Commander doesn't want to evacuate.
Information Description
Battlefield Executions
Whitelisted Commanding Officers are allowed to instantly kill any player at any time if the player fulfills the conditions found in Marine Law. Excessive or poorly-reasoned battlefield executions (such as BEing MPs over a valid arrest) may end with the Commanding Officers being removed from the whitelist.

Rule Precedents

Rule 1

1. Can you RP urinating on someone?

No. It's LRP & 18+


2. Can I Call The Incendiary OB "Coom OB"?

No, it's LRP/18+ and a sexual reference meme.

Rule 2

1. Can I wear uniforms found on the colony, such as pyjamas?

If you're a PFC, go for it, but you're still susceptible to marine law. SLs are held to higher standards and should not do it.