SCP-RP Rules

Civil Networks SCP RP Rules

Discord Link: https://discord.gg/5M3ZwhQkev
Teamspeak Address: ts3.civilgamers.com

All decisions made in game by staff are to be respected. If you feel that your punishment was unjust then speak to an Admin+ in game or make a forum complaint or a ban appeal. Arguing back will simply result in a mute, gag, warn or ban.

The Staff Rulings thread gives examples of situations that have been deemed to break rules such as FailRP.

Section 1: Basic Rules

1.1 Don’t RDM - You need a valid RP reason to kill someone. Reasons for shooting/attacking someone are:

You or someone else is in a life-threatening situation, e.g. you are shot at or held at gunpoint and threatened.
You see a someone hacking a door or a hostile is trespassing.
Giving someone verbal commands to stop what they are doing and continue their actions.
You are a D-class starting a riot with a weapon. It is FailRP to start a riot (e.g. punching security guards) unless you have found a weapon (knife, gun) that you can use.
You have committed a major offence such as Murder or Treason and are about to be arrested, however this doesn’t give you permission to start mass killing people.

1.2 Don’t FailRP - FailRP stands for "Fail Roleplay". It's when someone acts in a very unrealistic way that their character would not do. Decisions must be realistic and players must stay in character. For example, in a hostage situation if the negotiator kills the hostage to resolve the situation that would be unrealistic and FailRP. Other Examples of FailRP would be:

Speaking as an SCP that does not speak (see section 4).
Suiciding for no RP reason.
Using items while stripped other than cyanide pills (this counts as 'biting a cyanide tooth', requires a valid RP reason).
Playing as an SCP and doing inappropriate actions such as dancing as 106.
Using SCP-914 as a CI Juggernaut.
B-Hopping around.
Holstering a weapon in RP.

1.3 Don’t VDM - Running people over with your vehicle without an RP reason.

1.4 Don’t break NLR - New Life Rule means that you can not remember or use any information from a previous life in RP.

Players unless part of their duties may not return to their location of death when in player combat for 5 minutes, unless their job relies on them being in that location: Ex: GENSEC in D-Block.
MC&D, Rangers and Parawatch after death may not re-enter the facility for 15 minutes.
MTFs who die to SCPs during a breach are exempt from any rules preventing their return to a location.

1.5 Don’t RDA - You must have a valid RP reason to arrest someone.

If you’re arrested with a valid RP reason however feel it’s unjust, you should report it to someone of appropriate rank in-character.

1.6 Don’t Metagame - Using information gained from an out-of-character source to gain an advantage against others and using out-of-character sources to give information and influence roleplay negatively. Some examples of third-party/OOC sources are:

Discord
OOC & LOOC chat
Using the names above the heads of enemy players to identify who they are (This does not include ranks)

1.7 Don’t ERP - We have a zero-tolerance policy on Erotic Roleplay. Going out of your way to ERP is unacceptable and will be met with serious consequences.

1.8 Don’t hitbox abuse - Spamming crouch, jump or crouch jump. You must act realistically during combat.

1.9 Don’t Job Abuse - Do not abuse your job; this is where you change jobs to give yourself benefits/advantages under certain circumstances. For example, you are playing Chef and see a D-Class escaping so you switch jobs to security to shoot the D-Class.

1.10 Disrespectful Conduct - Derogatory Language designed to target players in a disrespectful manner is prohibited, this includes Racism, Homophobia and other derogatory slurs; jokingly being racist is not an exception to this rule.

1.11 Don’t Powergame - Powergaming is when you use /me for unrealistic RP actions, examples are;

/me punches the man opposite him in the head and kills him.
Powergaming is also defined as forcing an RP situation or action onto somebody without giving them a chance via /roll (Whoever gets the highest number wins). An example would be breaking someone's leg against their will. Both sides will roll and if the person who wants to break the other person's leg gets the higher roll then the victim who lost the roll will have to RP having a broken leg as they lost the roll in that RP scenario.
/its that place an advantage on the player in a way that prevents RP in an unrealistic fashion.

1.12 Mixing - Mixing is the term used for mixing IC and OOC-related topics together in character. Bringing up rules in character is classed as mixing and it will not be tolerated. Keep everything in character and professional. Examples of OOC topics:

Discord
Rules
Teamspeak
Saying when you're going offline or online
Saying your going AFK

If you wish to relate your IC words to OOC topics you may hint at those OOC topics by using more realistic words such as email instead of Discord. Furthermore, if you wish to speak out of character use the /looc command.

1.13 FearRP - You must fear for your life as if you were put into that situation yourself in real life. Grounds for FearRP are:

Being unarmed and at gunpoint no matter the number of aggressors.
Having your weapon out but still being surrounded and outnumbered 2:1.
Armoured vehicles can be put under FearRP if they are unarmed vehicles.
Vehicles in transit cannot be put under FearRP. The vehicle must be stationary.
You may not purposefully expose yourself to virulent SCPs (008, 049) unless ordered to at gunpoint by CI or Foundation.

1.14 LTAP & LTARP - Leaving to avoid punishment is when a player leaves the server to avoid punishment from a staff member or in character and it will result in a ban.

1.15 Spawn Camping - You can not kill someone directly outside their spawn unless they interact with you within combat or RP, MTF cannot shell with a LAV/BTR past Chaos Insurgency's Garage unless an active CI member is engaged in combat with the armed vehicle. (e.g shooting at you within their spawn or trying to capture you.)

1.16(b) Base Camping - You can not kill someone directly outside their base or within their compounds unless they interact with you within combat, RP, or unless you are raiding.

1.17 Body Blocking - You may not body-block if you are unarmed or playing an immortal SCP.

1.18 Body Boosting - This is allowed but only if one person is boosting you. Using multiple people as a ladder is not acceptable and is punishable.

1.19 Baiting - Baiting is not allowed, below are some examples for what Baiting is or can be classified as;

Getting yourself intentionally kidnapped, in order to allow your friendlies to open fire on the capturing team.
Informing someone to commit an action that would justify you, or any faction, arresting or killing them due to said action.
Intentionally opening fire close to, or near someone in order for them to open fire on you or others, to justify you killing them.

1.20 Naming Conventions - Names used when creating a character must be realistic and not contain any special characters, unnecessary letters, numbers, or resembling a famous celebrity or character - An exception is made for identifying squadrons, such as [LDR]

1.21 Impersonating Staff - Impersonating staff is not allowed. Simply mimicking or pretending to be a specific member of staff for the purpose of gaining a rank or purely out of spite will not be tolerated.

1.22 Bug/Script Abuse - Don’t hack, script, or abuse glitches. Don’t do anything that can be seen as giving you an unfair advantage over other players.

1.23 Self Supplying - Gun Dealers may not self-supply except for 1 gun for self-protection.

1.24 Scamming - Taking/stealing anyone's belongings, that being for material gain is not allowed. This also includes deception. Any bartering between players must be respected, meaning you must deliver what you promised. You cannot steal chemicals from other people.

1.25 Killcams - Knowledge gained from a killcam may not be used in RP or shared with others.

1.26 Real World Trading - The buying, selling or trading of vpoints, items, money or ranks for real-life monetary value between other players is prohibited. Players are allowed to trade vpoints for items or in-game money.

1.27 Chat/Mic Spam - You may not utilise communications in game in order to cause annoyance which detracts from the roleplay experience by screaming down their microphone or spamming voice lines / messages in chat.
Section 2: Roleplay Rules

2.1 Use equipment realistically - Equipment must be used realistically and not be abused. Enhanced Armoury equipment must not be used against human combatants, a matador can be used against armoured vehicles. This rule does not extend to SCPs, however, there must be 2 or more SCPs breached for Enhanced Armoury equipment to be used.

The 1000lb bomb that the GOC possesses may only be used on SCPs.
Juggernauts cannot use any rare weapon or Sniper Rifles against human combatants and SCPs

2.2 Loyalty to your team - You can't divulge information (unless you get interrogated) or assist the enemy team.

You may only assist the enemy team if there has been a valid RP scenario that has been approved by Server Leadership.

2.3 Combat Cuffing - Do not attempt to cuff someone whilst in a combat scenario, you may only cuff someone in a controlled RP situation.

2.4(a) Kidnapping Rules - When a faction member is kidnapped, they must have intentions for the hostage such as execution, interrogation, or making demands to the opposing faction for profit. The hostage's life should always be valued and the opposing faction must make a good plan to get the hostage back. A hostage may only be kidnapped for a total of 30 minutes if no action is taken. If action is being taken then they may be held for longer (eg. ongoing negotiations)

2.4(b) Negotiation Guidelines - Hostages are to be negotiated for where possible, the Hostage Negotiation Guidelines are to be followed during any scenario whereby a player or SCP is held for ransom.

2.4(c) Interrogation Rules - INTEL/MTF/GOC/CI have control over another faction's prisoner within their own base and have the power to delegate interrogation or negotiations. During interrogation they may ask 3 questions; for each question asked an interrogator and the prisoner being interrogated must /roll 100 and the interrogator must use /me to describe the interrogation method. If the interrogator rolls higher the prisoner must tell the truth. If the prisoner rolls higher they may say whatever they wish as long as it does not break server rules.

No codewords/phrases allowed.
Interrogators may not ask the same question more than once, while they are following this rule.
After the 3 questions are asked, with the use of /roll, the interrogation may continue as normal and within the confines of RP.

2.5 Trespassing as Surface Zone - Civilians, Mayor, Gun Dealers, Chefs & Medics are forbidden from entering the Foundation base or UNGOC base in RP, Parawatch, Ranger & MC&D may enter with a valid reason.

2.6 Pausing RP - Only staff have the power to pause RP. If someone in an RP scenario breaks a rule then contact staff and carry on with the RP scenario until staff arrive and deem it appropriate to pause RP. This rule makes RP more enjoyable for everyone and gameplay becomes more fluent.

2.7 Position Limits - You may only, across all your characters:

Hold an MTF position along with either a GOC or CI position. You can not hold a CI and GOC position at the same time.
Hold one 'senior position' (zero if you are a CO on MilitaryRP). These are: O5 Council, Ethics Committee, Site Admin, Departmental Directors & Chiefs, and MTF/CI/GOC COs.
Hold whitelisted and/or MTF positions on one of SCP-RP UK or SCP-RP USA.

2.8 Brainwashing - You may brainwash players when they are kidnapped and in a controlled RP scenario. You may not brainwash inside a base that is being raided. Brainwashed players cannot brainwash others. Brainwashing must be utilised by using the appropriate amnestics.

2.9 Voice Changers - Voice Changers may be used as long as they are fitting for the role and are of good quality i.e. SCP-049 to make your voice more monotonous.

Section 3: Raiding Rules

3.1(a) CI Raiding - CI can raid the facility or UNGOC base when authorized by a CO, once every 45 minutes. A raid starts once CI breaches the fenced off area on both bases or through the foundations vents. Only 8 CI may enter the vents on the foundation base. Once personnel raiding the base die they cannot return. A raid ends when all CI are dead; timers begin counting down once a raid has ended.

3.1(b) CI Raiding - CI Deep Cover may only raid every 30 minutes. If the Deep Cover job is used in the main raid the Deep Cover raid cooldown is used and the player must wait out the remaining time.

3.1(c) CI Raiding - CI must remain in their barracks for 1 minute on death whilst being raided.

3.1(d) Chaos Deep Cover - Chaos Insurgency deep cover may only enter the facility or UNGOC base when authorised by a Chaos Commanding Officer. Entering the either as a deep cover must have valid reasoning e.g., A member of chaos has recovered a foundation keycard allowing the deep cover to enter and retrieve files. Deep cover may not re-enter either locations after death unless a separate infiltration mission is approved by a CO after cooldown.

3.2(a) Foundation Raiding - Foundation MTF personnel can raid the CI and UNGOC Base when authorised by MTF Nu-7 Commander, the Director of Intelligence, B-1 Commander or the Site Administration e.g (O5, Ethics, Site Director/Advisor). They may raid once every 30 minutes. A raid starts once foundation personnel have started hacking the entrance of the CI or UNGOC base. Once personnel raiding the base die, they cannot return. A raid ends when all MTF personnel are dead; timers begin counting down once a raid has ended. Valid reasons for raiding are:

A facility SCP is captured by CI.
CI has kidnapped a foundation member.
Retrieving Stolen Documents.

3.2(b) Foundation Raiding - Alpha-1 may not leave their bunks for 1 minute on death whilst CI are raiding floor 3. Additionally, Omega-1 may not leave their bunks for 1 minute on death whilst CI are raiding the Ethics Committee

3.3(a) GOC Foundation Raiding - The UNGOC may not raid the Foundation base unless approved by a UNGOC CPT+ with justified reasoning, except that Assessment Team operatives may enter for espionage once every hour this cooldown applies to normal raids as well.

3.3(b) GOC CI Raiding - The UNGOC may not raid the Chaos Insurgency unless approved by a UNGOC LT+ to retrieve an SCP, or classified documents belonging to the Foundation or GOC, except that Assessment Team Operatives may enter for espionage once every 45 minutes with approval from a UNGOC LT+.

3.3(c) GOC Raiding - GOC must remain in their barracks for 1 minute on death whilst being raided.

3.4 Surface Missions - If a mission requires you to enter an enemy base the raiding reason, cooldown and NLR may be ignored.

3.5 Raiding Requirements - There must be 4 MTF/CI/UNGOC combat personnel to raid or infiltrate (Including Deep Cover) either bases. Exceptions are made if a member of your faction is kidnapped, which you can skip the raid cooldown to retrieve those kidnapped.

3.6 Raiding Protections - No parties may destroy documentation, you may only destroy documentation relating to your faction. You can steal important documents for usage.

Section 4: Chain of Command

4.1 Global Base Hierarchy - The following chain of command applies at all times. Foundation Staff in higher positions in this table can give orders to those in lower positions.

Overseer Council | Ethics Committee
O5/Ethics Assistants (when under direct orders from O5/Ethics)
Site Administration (Site Director, Manager and Advisor)
Department Directors | Department Chiefs | MTF Commanders
O5/Ethics Assistants (when not under direct orders from O5/Ethics)
Executive Researchers | Medical Consultants | Ambassadors | Security Captains | MTF Commissioned Officers
Internal Affairs | Intelligence
MTF Operative
Security Staff
All other personnel

4.2 Departmental Hierarchy - If you fall under 'All other personnel in the above hierarchy, then you can give other players an order only if they are in your department and you are playing a more senior job than them. e.g. a Senior Researcher can give a Junior Researcher orders. If you are playing a job listed in the Global Base Hierarchy, then that takes priority and Departmental Hierarchy does not apply.

Section 5: PAC3 Editor Rules

Abusing the PAC3 editor will result in your PAC3 access being revoked

5.1 All PAC3 creations must fit within the lore of SCP-RP. ‘Excessive’ PACs (ones that go far beyond what is considered reasonable in RP) must be justified and approved in the Character Bios section with the PAC request tag. This is designed so that we can ensure you are using your PAC to create roleplay, with an interesting backstory.

5.2 Creations must not contain any items that cause offense or harm.

5.3 You can only change the height of your character using “Size” and the value may only be between 1 and 1.1.

5.4 PACs may have modified body mass, however it must be proportionate to realistic proportions i.e. having extremely thin legs and excessively large arms is not permitted.

5.5 All PACs should fit the role specified, i.e. a D-Class would not wear a tuxedo nor would a researcher wear combat attire.

5.6 PACs may use sound as long as it is conducive to roleplay, is not spammed, does not cause issues with volume or content, and has a reasonable sound distance, there are no instances where a sound should be heard map wide, across floors or through multiple walls.

5.7 PACs may not be massively oversized or have excessive movement of props that contribute to lag.

5.8 Weapons may not be re-skinned or changed to look like a different type of weapon.

5.9 Animations - PAC animations can be used without approval, however they must be appropriate for roleplay, and not contribute to lag or be used excessively.

5.10 Lights - PACs may utilize lights however they must not be excessively bright and they are prohibited from having shadows enabled.

5.11 Authorisations - If a PAC has been approved for one player, this does not automatically approve it for others. ‘Excessive’ PACs must undergo the process in 5.1 again.

5.12 SCP PACs are allowed for RP purposes, however must maintain the logic and integrity of the character being played i.e. SCP-999 cannot look like a humanoid, these must be approved by a member of SL in game for the scenario presented.

Does not require approval	Requires approval
Items that are attached to the player and are outside of the model, such as; Watches, Glasses, PDAs, Weapons, Badges, etc Hair changes Changes of clothes and material that fit the character in RP Ghillie Suits (only permitted for MTFs, CI, GOC)	Animalistic traits (Animal body parts) Animal ear headbands Capes Changing base model (only permitted for non-combative units) Prosthetics and or robotic traits Pets, though they must be statically placed on the person and not be “following” them

Section 6: SCP Rules

SCP Golden Rule: Never kill-farm. Kill-farming is sitting in a spawn area, e.g. D-Block or MTF Bunks, and repeatedly killing people when they spawn. SCPs are not mindless killing machines, remember that you have more objectives than simply killing humans (e.g. reaching the surface).

SCP Silver Rule: Role-play during experiments. Do not instantly kill D-Class introduced to your cell; this is poor roleplay and not fun for other players. All use of your microphone must be in-character for that SCP (see below).

6.2 Surface SCP's may not enter the Foundation,CI or GOC bases unless they have been captured by the relevant personnel. If a Surface SCP enters the facility, it is classed as FailRP.
6.3 Do not accept a surface queue offer in RP; if you cannot leave RP when the timer ends, leave a message in /LOOC to indicate you will be accepting a queue. If you accept a queue in RP without any warning, it is classed as FailRP.
6.4 Surface SCPs may be captured for 30 minutes, and then they must be terminated. The player may leave the SCP job if left alone for more than 5 minutes.
6.5 SCPs cannot team with any human; they can only work with other SCPs

SCP	Can Speak?	Other Rules
SCP-049	Using the voice line system, text chat. Can use voice chat only if making a reasonable effort to speak with an ominous in-character style.	N/A
SCP-049-2	Make zombie noises	N/A
SCP-008-2	Make zombie noises	N/A
SCP-096	No	Cannot purposefully look at people Must sit down (crouching) when not in an agro state Must only kill those that look at its face or purposefully block its path, e.g. body blocking a door Whilst breached, SCP-096 may roam when left undisturbed for more than 60 seconds
SCP-076	Yes	N/A
SCP-173	No	N/A
SCP-106	Yes	N/A
SCP-999	No	Cannot enter other SCP’s chambers without an RP reason
SCP-682	Yes	N/A
SCP-457	Using text chat	N/A
SCP-939	Using the voice line system or text chat	N/A
SCP-035	Yes with a host body	Can silent breach if a host is obtained out of the auto breach system
SCP-079	Yes	SCP-079 cannot break other SCPs out of cuffs
SCP-912	Using the voice line system or text chat	Must follow all orders from uniformed security personnel ( Including CI) Must arrest any dangerous individuals that pose a threat, with the exception of security personnel. Must protect itself and other security personnel. Only use lethal force against others using lethal force. Arrest where appropriate Should only enter D-Block during a riot. Should not be used in raids or breaches.
SCP-860-2	No	N/A
SCP-966	No	N/A
SCP-323 (Surface SCP)	May only Grunt / Heavy Breathing Via Voice Communications.	N/A
SCP-9000-A-X	Make zombie noises	N/A
SCP-2295	No	Cannot enter other's SCP chambers without an RP reason Must repair any injured players they see (Foundation, D-Class, C.I...)
SCP-073	Yes	Cannot purposefully get involved in combat Cannot co-operate with GOIs/ D-Class, only foundation staff Cannot purposefully leak info such as A-1, O-1 etc. Foundation is not to use SCP-073 for any combat purposes, E.g. telling SCP-073 to stand in a corridor and let CI shoot him. SCP-073 is not to body block under any circumstance Should not be used in raids or breaches. SCP-073 should only follow reasonable orders(Being ordered to stand in front of CI is not a reasonable order) SCP-073 must attempt to abstain from actions that cause him physical pain or injury
SCP-7722	Yes	Cannot team with anyone (other than SCPs) You are to stand on your podium until your idle state is disturbed (if you are undisturbed for 10 minutes or more, you may move around and then move back to it)
SCP-8854 (Surface SCP)	No	N/A

Section 7: Group Rules

Group rules refer to all MTF units, site command, facility staff and chaos insurgency. All of those categories listed are groups and they can be found in the regiments tab in the F4 menu.

7.1 Rank skips - Are not allowed unless a new commander has been selected and is in need of command staff or they wish to reform the group members. A new commander will have a 2-week rank skip window to rank skip people by 2 ranks who they wish with authorisation from group managers and higher command e.g 05 council or CI commander.

7.2 Paperwork/Document Ownership - Any Documents/Paperwork must be transferred to Ventz. This is to prevent any unauthorised editing or vandalism from taking place. Failure to transfer official documents to Ventz will lead to severe consequences.

7.3 Rank Transfers - Must be authorized by the Site Command eg. (O5 and Ethics) and the person transferring must be at least Command Sergeant. If the transfer is accepted the person transferring will transfer 4 ranks below their original rank.

7.4 Promotion cooldown guidelines:

Group	Foundation Ranks Involved	Cooldown
Enlisted	Private Specialist Lance Corporal	3 days
Non-Commissioned Officers	Corporal Sergeant Command Sergeant	5 days
Commissioned Officer	Lieutenant Captain Major	7 days

Group	Chaos Insurgency Ranks Involved	Cooldown
Chaos Insurgency	Alpha Beta	3 days
Chaos Insurgency NCO	Gamma Delta	5 days
Chaos Insurgency Officers	Delta Commander Brigade Commander Major Commander Lieutenant Commander	7 days

Last edited by a moderator: Feb 27, 2023

Reactions: Bartholemew alen, Ozziejacob, Divisional and 53 others

Click to expand...

Search

SCP-RP Rules

Requis

Super Administrator