Odyssey RP

OdysseyRP SCP Playable Entity Guidelines (Standalone Rule Set) *1* This document serves as the official and updated ruleset for all playable SCPs on the OdysseyRP SCP server. It is separate from general server rules and tailored specifically to individual SCPs and their in-game permissions, behavior, and maintenance. Note: Each SCP has custom permissions. Some entities are peaceful or passive, others are actively hostile. Every SCP player is expected to follow their entity’s behavioral profile. Breaches, containment RP, FearRP behavior, and maintenance cycles are strictly enforced to preserve immersive and serious roleplay. This system replaces prior SCP guidelines and should be referenced by staff, SCP mains, and those interacting with anomalies IC. SCP-131-A/B – “Eye Pods” Object Class: Safe Overview: SCP-131-A and SCP-131-B are small, teardrop-shaped entities with a single large eye each. They are non-hostile, highly mobile, and exhibit curiosity and empathy toward others. They are commonly seen “watching” other anomalies, particularly SCP-173, helping maintain visual contact. Maintenance Guidelines: Does not require direct maintenance. Containment Guidelines: Will willingly follow anyone offering eye drops. Breach Guidelines: Can roam freely without needing to “breach.” Must /advert to be let out of containment. Example: /advert SCP-131 requests to be let out to roam. Abilities & Permissions: Speaks only in high-pitched babbles or meeps. May open non-secured doors by throwing themselves to hit buttons if no Foundation personnel are present. May enter D-Block. May go on surface if following or captured by a GOI If given an order by Foundation it must be followed If no new order is given within 2 minutes of the previous and no one is near 131 it may leave and do something else May not attack or assist in combat. May not breach or team with other SCPs. Notes: These entities are meant to provide lighthearted presence and light support roleplay, especially in observation roles. Chaos Insurgency (CI) and Serpent's Hand (SH) may breach and extract SCP-131 for surface containment, but may not use them for hostile actions. SCP-999 – “The Tickle Monster” Object Class: Safe Overview: SCP-999 is a friendly, orange, gelatinous entity that exudes a calming and euphoric effect. Known for its playful, joyful demeanor, it is popular among personnel and often used to alleviate stress and improve morale. Maintenance Guidelines: Does not require direct maintenance. Containment Guidelines: Will happily follow anyone offering sweets. Breach Guidelines: Can roam freely without needing to “breach.” Must /advert to be let out of containment. Example: /advert SCP-999 requests to be let out to roam. Abilities & Permissions: Does not speak but produces bubbly, excited noises. May open non-secured doors by bouncing against buttons if no Foundation personnel are present. May enter D-Block. May go on surface if following or captured by a GOI May tickle people to boost morale or calm aggression. Can attempt to calm SCP-682 by tickling it (must /roll — 2 attempts max per breach). May not attack, assist in combat, or breach other SCPs. Notes: Primarily used for emotional RP support. Staff may allow SCP-999 to attend events or high-stress zones to reduce tension IC. Chaos Insurgency (CI) and Serpent's Hand (SH) may breach and contain SCP-999 for their own morale purposes, but not use it offensively. SCP-912 – “Autonomous SWAT Armor” Object Class: Safe Overview: SCP-912 is a full set of mobile SWAT-style body armor animated by an unknown force. It mimics law enforcement behavior and attempts to detain those it perceives as breaking the law. It responds only to lawful command and follows policing protocols in an exaggerated but non-hostile manner. Maintenance Guidelines: Does not require maintenance. May request to be let out using /advert. Example: /advert SCP-912 requests to be let out. Containment Guidelines: Can be contained if ordered by someone wearing a police vest. Police vests may be acquired from GENSEC bunks and require an /advert to roleplay equipping. Breach Guidelines: Can roam freely by default. Obeys lawful individuals wearing a police vest, even if their orders contradict Foundation norms. Cannot be hacked, disabled, or killed. Will arrest anyone it deems a lawbreaker, but never its current “handler.” Abilities & Permissions: Does not speak. May open doors. May assist GENSEC in transporting Class-Ds or escorting during tests. May enter D-Block. May not attack SCPs. May detain or engage Foundation, Class-D, or CI/SH personnel based on law-based behavior. Notes: SCP-912 is not hostile but acts on in-universe interpretations of law. May cause unique RP outcomes based on orders received and law enforcement perspective. CI and SH may breach SCP-912 for their own policing needs, but not weaponize it maliciously. SCP-527 – “Mr. Fish” Object Class: Safe Overview: SCP-527, also known as "Mr. Fish," is a human male with the head of a fish (genus unknown). He displays no anomalous behaviors beyond his appearance. SCP-527 behaves like a normal, mild-mannered individual and poses no threat to Foundation personnel or infrastructure. Maintenance Guidelines: Does not require maintenance or feeding beyond standard humanoid procedures. Containment Guidelines: May remain in standard humanoid containment. Will comply with orders and roleplay directions unless directly endangered. Breach Guidelines: Does not breach on his own and cannot initiate breaches. May /advert to leave containment for social RP. Example: /advert SCP-527 requests to roam. Abilities & Permissions: May speak normally. May enter public Foundation spaces and common areas. May visit the surface or D-Block with staff escort or authorization. May not attack, provoke, or assist in breaches. May not team with other SCPs. Notes: SCP-527 is intended for light, comedic, or philosophical RP. He is not a combatant and should not be used in tactical or containment-based RP. CI and SH may breach SCP-527 for recruitment or morale reasons but may not weaponize him. SCP-2295 – “The Bear with a Heart of Patchwork” Object Class: Safe Overview: SCP-2295 is a small, hand-sewn teddy bear made of mismatched fabrics and cotton stuffing. It is animated and possesses anomalous healing properties. When in the presence of an injured human, SCP-2295 attempts to create a rough but functional copy of the injured organ using cloth and stuffing. Maintenance Guidelines: Does not require traditional maintenance. May request a Class-D patient for healing RP every 20 minutes via /advert. Containment Guidelines: Contained in a standard Safe-Class containment room. Will follow staff or personnel requesting assistance with healing. Breach Guidelines: Cannot breach on its own. May /advert to request surface or D-Block access to help with morale or injury RP. Abilities & Permissions: Can speak softly, often with childlike phrases. May roam under escort. May use healing RP on wounded personnel (requires /me and /roll). May not attack, provoke, or assist in breaches. May not team with SCPs unless explicitly scripted by staff. Notes: Primarily designed for medical or morale RP. May not be weaponized or used in combat. CI and SH may extract SCP-2295 during raids for use in humanitarian roleplay but may not forcefully exploit its powers. SCP-049 – “The Plague Doctor” Object Class: Euclid Overview: SCP-049 is a humanoid entity dressed in a traditional plague doctor outfit that appears to be fused with its body. It believes itself to be curing the “Pestilence” and can lethally touch individuals it deems infected, later performing crude surgery to create zombie-like SCP-049-2 instances. Maintenance Guidelines: Must be provided a Class-D “patient” every 25 minutes. First patient: wait full 25 minutes before breaching. After first breach: only 15-minute cooldowns between patients. Must request a new patient using /advert SCP-049 requests a new patient. Each patient must be checked for pestilence via /me and /roll. Success allows surgery to begin. If no pestilence, Class-D may be terminated or returned. Containment Guidelines: All 049-2s in sight must be terminated before recontaining 049. Must have 2 guns pointed at 049 to apply kevlar gloves and lead it back to containment. If a gun is lowered, 049 may resist and remove gloves to resume curing. Putting on/taking off gloves must be /adverted. Breach Guidelines: Can breach if not provided a new patient within required timeframe. Must use /advert: /advert SCP-049 breaches due to lack of patients. Ignores FearRP for 10 minutes post-breach or until it has 3 SCP-049-2s. SCP-049-2s obey 049 for first 10 minutes, then may act independently (or follow SCP-035). May breach SCP-035 six minutes after breaching. Abilities & Permissions: Can speak in-character. Can open doors while breached. May not enter D-Block. May attack Foundation, CI, SH, and Class-D. May breach only SCP-035 and may team with SCP-035. CI and SH may breach SCP-049 (including to surface), but may not contain or use this SCP in their own facilities. SCP-173 – “The Sculpture” Object Class: Euclid Overview: SCP-173 is a statue-like entity made of concrete and rebar that is capable of rapid movement and lethal force when unobserved. It kills by snapping the necks of its victims and must be kept under direct line of sight by at least three observers at all times. Maintenance Guidelines: Requires containment cell cleaning every 20 minutes. If RC'd you must wait 20 minutes before requesting Cleaning Must request cleaning via /advert SCP-173 requires cleaning. Cleaning must be roleplayed using /me and /roll. Each roll must be 50 or higher to succeed. If the roll is under 50, the action fails and must be reattempted. 173 May kill D-Class during cleaning if line of sight is broken If no cleaning occurs within 20 minutes, 173 may breach. Containment Guidelines: Recontainment requires three people maintaining direct line of sight. Must attempt to cage with /me’s and /roll Failed rolls mean you are killed by 173 Once recontained, all personnel must exit the cell together before it is secured. SCP-131-A/B may assist as visual observers but may leave if not given orders for 2 minutes. Breach Guidelines: May breach if cleaning is not performed within 20 minutes. May freely move and attack if fewer than 3 people are looking at it. All kills must follow proper RP procedure and /me actions when possible. Abilities & Permissions: Cannot speak. May open doors when breached. May breach the surface. May not enter D-Block. May attack Foundation, CI, SH, and Class-D personnel. May not attack or team with other SCPs. CI and SH may breach SCP-173 (including to surface) but may not contain or use this SCP at their own facilities. SCP-096 – “Shy Guy” Object Class: Euclid Overview: SCP-096 is a tall, emaciated humanoid that becomes violently hostile when someone views its face. Upon exposure, SCP-096 will enter an emotional distress state, followed by a lethal rage and an unstoppable pursuit of the viewer. Maintenance Guidelines: SCP-096 requires no direct maintenance. Upon spawning, SCP-096 must begin roleplay by announcing its emotional instability via /advert SCP-096 starts becoming sad and paces inside its cell. After 20 minutes of inactivity, SCP-096 may initiate a breach with an advert: /advert SCP-096 begins to cry violently and breaches containment. Containment Guidelines: SCP-096 may only be bagged (to suppress visual triggers) after it has become docile (no active targets). Bagging must be performed using /me and /roll. A failed roll (Counter Roll) results in the player being attacked and killed. Once successfully bagged, SCP-096 can be cuffed and escorted back to its containment cell. If SCP-096 is not returned to containment within 10 minutes of bagging, it may remove the bag and enrage again with /advert SCP-096 removes the bag and screams. Breach Guidelines: When breached from sadness, SCP-096 enters a rage phase and cannot be bagged or contained for the first 5 minutes. SCP-096 will target and kill anyone who has seen its face (direct view, not forced). When not enraged, SCP-096 must alt-walk (no sprinting). SCP-096 may not enter D-Block, interact with SCPs, or attack unless triggered by visual contact. SCP-096 will cry uncontrollably if it sees SCP-682. SCP-096 may not sit down to self enrage Abilities & Permissions: Cannot speak but may perform audio cues (growling, crying). May open doors when breached. May breach the surface. May not enter D-Block. May attack Class-D, Foundation, CI, and SH when enraged. May not team or interact with other SCPs. CI and SH may breach SCP-096 (including to surface), but may not contain or utilize SCP-096 at their facilities. SCP-457 – “The Burning Man” Object Class: Euclid Overview: SCP-457 is a humanoid composed entirely of fire. It grows in size and heat when exposed to flammable materials and becomes more dangerous the longer it is active. Maintenance Guidelines: SCP-457 requires maintenance. Have a D-Class bring him 2 barrels Upon spawning, SCP-457 must begin roleplay by announcing ignition using /advert SCP-457's flame begins to grow. After 30 minutes, SCP-457 may breach containment with an advert: /advert SCP-457's fire overwhelms the containment cell and breaches containment. Containment Guidelines: To recontain SCP-457, at least 3 Foundation personnel must be actively spraying with fire extinguishers. If fewer than 3 extinguishers are active at any point, SCP-457 reignites and resumes breaching behavior. Breach Guidelines: For the first 5 minutes of its breach, SCP-457 is immune to fire extinguishers and does not follow FearRP. SCP-457 must actively seek out flammable objects, heat sources, or personnel to ignite. After 5 minutes, standard containment via fire extinguishers resumes. Abilities & Permissions: May speak, but dialogue must be fire-themed and aggressive. May open doors when breached. May breach the surface. May not enter D-Block. May attack Class-D, Foundation, CI, and SH. May not team or interact with other SCPs. CI and SH may breach SCP-457 (including to surface), but may not contain or utilize SCP-457 at their facilities. SCP-1370 – “Pesterbot” Object Class: Euclid Overview: SCP-1370 is a small, humanoid robot with an oversized ego and delusions of grandeur. Though non-lethal and incapable of actual combat, it constantly declares war on random objects and people, acting out as a self-proclaimed conqueror of all things. Maintenance Guidelines: Requires mechanical diagnostics every 20 minutes if in Foundation custody. May request attention or monologue via /advert SCP-1370 demands maintenance or recognition. Containment Guidelines: SCP-1370 can be lured back into containment with flattery or logic traps. Staff may outwit 1370 using RP dialogue or distraction. Breach Guidelines: 1370 may roam freely if not directly supervised. Must act in a comically aggressive, over-the-top manner — this is not a combatant SCP. Cannot kill, harm, or sabotage anything. Abilities & Permissions: May speak loudly and dramatically (RP voice strongly encouraged). May open unlocked doors. May wander the site but cannot enter armories or classified areas. May interact with D-Class, CI, SH, Foundation staff in-character but cannot instigate violence. May not breach other SCPs or coordinate with anomalies. Cannot be used in combat scenarios. SCP-239 – “The Witch Child” Object Class: Keter Overview: SCP-239 is a young girl with the unconscious ability to alter reality through her imagination and belief. While cooperative and innocent in demeanor, her powers make her extremely dangerous if left unchecked or emotionally unstable. Maintenance Guidelines: SCP-239 must be checked on every 20 minutes via roleplay. Personnel must be briefed and medically cleared before interacting. Sleep-inducing measures must be maintained at all times. Containment Guidelines: 239 must remain sedated unless directly involved in approved experiments. Interaction requires O5 or SD/SDD approval. Only MTF or Research with express clearance may enter her cell. Breach Guidelines: If SCP-239 becomes aware of her powers or awakens unsupervised, she may breach. 239 may bend physics in localized ways (e.g., gravity shifts, illusions, spontaneous forcefields), but must announce major effects via /advert. Recontainment requires either sedation or calm, trust-based roleplay. Abilities & Permissions: Can speak and express thoughts clearly. May use minor telekinetic and environmental effects in RP. May not attack other SCPs. May not breach without significant RP reasoning or emotional instability event. May not breach surface. Unless captured by GOI May not enter D-Block. May be influenced or calmed by SCP-999. CI or SH may attempt to breach SCP-239 only during coordinated events with staff supervision. SCP-106 – “The Old Man” Object Class: Keter Overview: SCP-106 is a decayed humanoid entity capable of passing through matter and creating a corrosive effect on all it touches. It drags victims into a “pocket dimension” for torture or containment, making it highly feared and difficult to detain. Maintenance Guidelines: SCP-106 will always breach. There is no way to permanently maintain it. Upon spawning, SCP-106 must /advert that it is becoming more active (e.g., /advert [RP] SCP-106 paces in its pocket realm.) After 1 hour, SCP-106 may begin its breach with a new advert such as: /advert [RP] SCP-106 breaches the wall. Containment Guidelines: Recontainment requires use of the Femur Breaker protocol with a live Class-D. Required steps (via /advert): Ensure 106 is either in Site or Pocket Dimension /advert [RP] Straps Class-D into the Femur Breaker /advert [RP] Activates sound; femur is broken SCP-106 must begin walking back to its CC once the sequence begins, but may still attack anyone directly in its path. The Femur Breaker becomes active 5 minutes after breach starts. Breach Guidelines: For the first 2 minutes post-breach, SCP-106 is enraged and can attack anyone in sight. After 2 minutes, 106 may only engage those actively targeting or threatening it. Abilities & Permissions: Cannot speak, but may emit eerie breathing or moans. When hit with a Micro HID you must return to Pocket Dimension for 15 seconds May open doors while breached. May reach the surface. May not enter D-Block. May attack Foundation, Class-D, CI, or SH — but not other SCPs. May not team with or breach other SCPs. May only be breached by CI or SH during a coordinated event (NOT used or recontained by them). SCP-939 – “With Many Voices” Object Class: Keter Overview: SCP-939 are red-skinned, blind, quadrupedal predators that lure prey using human vocal mimicry. Their bite induces unconsciousness or death, and they rely on sound to hunt. Maintenance Guidelines: Each SCP-939 must request a Class-D every 5 minutes for 30 minutes using /advert. Example: /advert SCP-939 requests a Class-D. If there are multiple 939s, each will share breach timers. If a 939 is breached before you swap to the job you may not breach 939s must respond to sounds made. If 939 is shot they will not lose sight of the person who shot. Containment Guidelines: SCP-939 can only be recontained via termination. Containment doors must be secured before recontainment to prevent rebreach. Breach Guidelines: If no Class-D is received after 30 minutes, SCP-939 may breach with a /advert. Example: /advert SCP-939 has gone too long without food and breaches. SCP-939 is blind and relies entirely on hearing and sensing movement. It may only break through doors if noise is detected behind them. During breach: May kill anyone they detect. Must passively walk unless actively hearing or sensing movement. Abilities & Permissions: May mimic human voices but only for luring victims. May break down doors only when noise or movement is sensed. May not breach the surface. May not enter D-Block. May attack Class-D, Foundation, CI, or SH — but not other SCPs. May not breach or team with other SCPs, except other 939s. GoI factions like CI/SH may only breach 939 during coordinated events; they may not contain or utilize 939. SCP-682 – “Hard-to-Destroy Reptile” Object Class: Keter Overview: SCP-682 is an enormous, near-indestructible reptilian creature that possesses extreme hatred for all life. It is intelligent, highly aggressive, and incredibly resistant to physical harm, making containment exceptionally difficult. Maintenance Guidelines: SCP-682 will always breach. There is no way to permanently maintain it. Upon spawning, SCP-682 must /advert that it is becoming more active (e.g., /advert [RP] SCP-682 stirs restlessly within the acid containment tank. After 1 hour, SCP-682 may begin its breach with a new advert such as: /advert [RP] SCP-682 breaches the door. Containment Guidelines: SCP-682 becomes docile automatically 20 minutes after breaching unless provoked. SCP-682 also becomes docile when at 10% HP SCP-999 may attempt to calm SCP-682 with tickling. This requires a /roll. If it fails, 999 must wait 3 minutes before reattempting. Breach Guidelines: Upon breaching, SCP-682 must attack any target it sees until it becomes docile. Hostile Actions If attacked while docile, SCP-682 becomes enraged and must attack any target it sees until it becomes docile again. If Disrespected 682 becomes enraged and must attack any target it sees until it becomes docile again. Escort 682 back to his Cell when docile. Requires 3+ people Abilities & Permissions: May speak in a slow, deep, menacing tone. When Docile you must walk back to your Containment Cell May open doors while breached. May breach the surface. May not enter D-Block. May attack Foundation, Class-D, CI, or SH — but not other SCPs. May not breach or team with other SCPs. May be breached by CI or SH during coordinated events, but cannot be used or kept by them. SCP-3199 – “Humans, Refuted” Object Class: Keter Overview: SCP-3199 is a species of extremely dangerous, hairless, humanoid-like creatures capable of rapid reproduction under stress. These creatures are highly aggressive, unpredictable, and extremely hostile toward all other forms of life. Maintenance Guidelines: SCP-3199 does not require traditional maintenance but must be checked every 20 minutes. SCP-3199 must /advert on spawn: /advert [RP] SCP-3199 quietly writhes in its containment. If not checked within 20 minutes, 3199 may breach. Containment Guidelines: SCP-3199 is considered a kill-on-sight (KOS) threat. It cannot be subdued or recontained once breached. Termination is the only method of neutralization. Breach Guidelines: 3199 may breach if not checked on in time. SCP-3199 does not follow FearRP and must be terminated immediately during breach. May /advert upon breaching: /advert [RP] SCP-3199 screeches violently and breaks containment. Abilities & Permissions: May not speak. May open breached doors. May not enter D-Block unless lured. May breach the surface. May attack Class-D, Foundation, CI, or SH — but not other SCPs. May not team with any SCPs. May be breached by CI or SH during events but cannot be kept or controlled. SCP-035 – “The Possessive Mask” Object Class: Keter Overview: SCP-035 is a white porcelain comedy mask that secretes a corrosive black liquid and can possess anyone who wears it. Once worn, it takes full control of the host's body and displays high intelligence, manipulation, and knowledge of Foundation operations. Maintenance Guidelines: A check must be roleplayed by staff or Foundation personnel with /me and /roll. If 3 or more rolls fail under 50, repairs are required and must be roleplayed. Containment Guidelines: To recontain SCP-035: Terminate the current host (035-1). Roleplay securing the mask in a containment box via /me and /roll (must roll 60+). Box must be escorted back to the containment chamber. Breach Guidelines: SCP-035 may attempt to control people via /me RP within range. Targets must roll 50+ to resist (45+ with hazmat). Can attempt 2 control rolls per target with a 2-minute cooldown. May team with SCP-049 after 5 minutes of breach. Abilities & Permissions: May speak freely. May not be worn by SCPs. May open any door. May RP to breach keycard doors. May breach the surface. May not enter D-Block. May attack Class-D, Foundation, CI, or SH — not SCPs. May breach SCP-049 and team up only with it. May be breached by CI or SH but may not be kept or used by them. *1* These rules may be changed at anytime with or without warning it is your responsibility to check frequently to ensure you are up to date with current SCP rules

OdysseyRP – SCP Roleplay Server Rules Welcome to OdysseyRP, a Serious Roleplay (SeriousRP) environment based in the SCP Foundation universe. This server is dedicated to immersive, structured, and lore-compliant roleplay. Every player is expected to conduct themselves professionally, remain in character at all times, and respect the integrity of the world we’ve built. This is not a sandbox. This is not a game where rules are flexible or ignored. Every action you take reflects on the quality of the community as a whole. All rules listed below are mandatory. Violating them may result in removal from the server, temporary suspension, or permanent bans depending on severity. Appeals must be submitted via our forums: https://odysseyrp.xyz Regularly review the rules for changes. 1. Conduct and Behavior 1.1 Respect Is Expected OdysseyRP is built on serious, story-driven roleplay — and that means every player needs to feel respected. Whether you’re IC or OOC, keep interactions civil and professional. You don’t need to like every character, but you do need to respect the player behind them. Discrimination, slurs, or harassment of any kind will result in immediate removal. We’re here to build a strong, immersive community — leave the toxicity at the door. 1.2 English Only All public communication must be in English. This includes in-game chat, voice channels, and /advert. Private IC language is allowed only when all participants consent. Staff must be able to moderate public interactions. 1.3 Disruption is Not Tolerated Spamming, mic abuse, or any form of intentional disruption will result in escalating punishments. Examples include: Repetitive sounds, messages, or emotes Abusing mechanics or tools Deliberate interference with active RP Punishment: Verbal Warning → Written Warning → Temporary Ban → Permanent Ban for repeat/severe cases. 1.4 Staff Directives are Final Staff are authorized to make decisions to maintain the integrity of the server. Their instructions must be followed without resistance. Disputes are handled post-incident via Discord or forums with valid evidence. Failure to comply: Warning → Kick → Ban Falsifying evidence or misleading staff: Minimum 7-day ban. 1.5 No Outside Promotions Promotion of other communities, servers, or platforms without Senior Staff authorization is strictly prohibited. Punishment: 3-day Ban → Permanent Ban for repeat offenses 2. Core Roleplay Standards 2.1 You Must Remain In-Character You are expected to roleplay your assigned character at all times unless using authorized OOC channels. Mixing OOC into IC environments, discussing real-world topics, or treating the world as a game will be classified as FailRP. Punishment: Warning → 24h Ban → Escalation for repeat offenses 2.2 Character Names Must Be Immersive Your name must fit the universe, your faction, and your role. Joke names, pop culture references, and offensive terms are prohibited. Guidelines: Foundation/GOC/SH: Follows Command naming conventions Class-D/SCPs: Steam name, designation, or nickname permitted Failure to comply: Name change required within 5 minutes → Kick → 24h Ban if not corrected 2.3 You Are Not Invincible – FearRP is Mandatory Every character, no matter the faction, is expected to value their life and act accordingly when facing danger. You are not a hero unless the role, backstory, or situation justifies it. FearRP ensures realism — it keeps characters grounded in the world, and it stops powergaming dead in its tracks. You must roleplay fear in any situation where your character’s life is clearly at risk, including but not limited to: Having a weapon aimed at you Being outnumbered or surrounded Being restrained (ziptied, cuffed) Encountering hostile SCPs without proper defense Watching teammates get killed by a threat you can’t handle If your character would reasonably fear for their life — they should act like it. Panic, comply, run, surrender. Don't crack jokes or charge blindly unless you have a lore-justified reason. Exceptions may apply to: Certain SCPs with lore immunity to fear (e.g., SCP-682) Trained GOC/MTF operatives with pre-approved fearless behavior Characters with a documented backstory that includes trauma conditioning or combat desensitization All exceptions must be cleared ahead of time via staff. Failing to follow FearRP breaks immersion and will be treated as FailRP. Punishment: Warning → 24h Ban → Extended Ban for repeat behavior 2.4 Stay Within Your Role – No FailRP Every role in OdysseyRP comes with expectations. Whether you’re a researcher, a Mobile Task Force operative, or an anomalous entity, your actions should make sense for who — and what — you are. This doesn’t mean you have to be serious 24/7. It just means your behavior should always fit the situation and your character’s purpose in the facility. Examples of FailRP: A Class-D joking around during a deadly breach A scientist entering SCP chambers without security or reason SCP-173 using voice chat or "playing nice" Abusing mechanics, like dropping your weapon in combat just to avoid death Note: Dropping a weapon as a form of surrender or FearRP is valid — if it’s done realistically. Doing it just to dodge consequences (e.g., baiting rules to avoid being shot) is not. Punishment: Warning → 24h Ban → 3-day Ban for repeated or intentional violations 2.5 OOC Information Must Stay OOC – No Metagaming Any use of out-of-character knowledge to influence in-character actions is prohibited. You must not act on information your character has not learned through roleplay. Examples: Identifying others using nameplates Using Discord leaks to act IC Broadcasting containment info via /ooc Punishment: 24h Ban → 7-day Ban → Permanent Ban for repeated or coordinated metagaming 2.6 New Life Rule (NLR) When your character dies, they forget everything from that life — where they were, who killed them, and what happened. You are starting fresh. Standard NLR Rules: You may not act on information from your previous life. You may not leave spawn for at least 1 minute unless otherwise instructed. New Life Rule (During Raids): To maintain fairness, pacing, and immersion: All players — attackers and defenders — must wait 5 minutes before returning to the raid zone after death. This applies to the entire active combat area, not just the location where you died. You are not allowed to use the time to scout, coordinate attacks, or influence the outcome while dead. These NLR timers are in place to prevent wave respawning, protect tactical integrity, and ensure death feels impactful. Treat each life during a raid as valuable — once it's gone, you’re on hold. NLR is not just a timer — it’s a mindset. You don’t remember what just happened, so don’t act like you do. Punishment: Verbal Warning → 24h Ban → 3-day Ban for repeated or intentional violations 2.7 RDM Is Not Roleplay – All Kills Must Make Sense In the world of SCP, violence is part of survival — but it must still serve the story. Every kill must have clear, justifiable in-character reasoning. This isn’t a deathmatch server. You are not here to frag people for fun. Random Deathmatch (RDM) is defined as: Killing without RP buildup or clear justification Using lethal force when lower-force options exist Attacking allies or faction members without approved betrayal RP Spawn camping or killing players before they can reasonably react Combat is expected, but it must have purpose. Valid examples of kill scenarios: MTF neutralizing a breached SCP CI eliminating key Foundation personnel during a raid SH freeing a Class-D as part of a planned extraction SCPs acting according to hostile containment lore What matters is context — who your character is, what they know, and how they’re acting within the world. Even a single line of RP can justify a fight. No buildup? No reason? That’s RDM. If it feels like you're playing a shooter and not telling a story — take a step back. Punishment: 24h Ban → 7-day Ban → Permanent Role Ban (for repeated or blatant violations) 2.8 ERP Is Strictly Prohibited – No Exceptions Erotic or sexual roleplay (ERP) is absolutely forbidden in all forms — text, emotes, PAC3, or voice. This rule is non-negotiable and applies to all players regardless of age, context, or intent. ERP will result in a permanent ban without warning. This includes: Suggestive or sexual text-based actions Inappropriate PAC3 avatars or animations Attempting ERP in voice or private messages through server systems This policy protects both the server and its community from serious real-world consequences. If you're here to push boundaries — this isn't the place for you. Appeals may be submitted after 90 days, but will only be reviewed if: The player takes full responsibility They show a clear understanding of the rule and why it exists They demonstrate respectful conduct since the ban (e.g., clean history elsewhere) Reinstatement is extremely rare and never guaranteed. 2.9 Loyalty Matters – Faction Betrayal Must Be Roleplayed Properly Every faction has its own mission, and you're expected to support that mission while you're part of it. That means acting in-character, following orders, and protecting your side’s interests. But betrayal is part of the SCP world — and it’s allowed, if done right. Defections, sabotage, or turncoat arcs must be: Properly built up through RP, not done on impulse Followed through with consequences — once you defect, there’s no going back without a serious IC reason Examples of improper betrayal (FailRP): Randomly releasing Class-D without any RP Sharing Foundation secrets with CI/SH for no reason Swapping teams mid-raid without an approved story arc Examples of valid betrayal: An MTF operative secretly defecting to CI over time A captured Researcher being turned by SH after IC indoctrination A Class-D becoming loyal to the Foundation over several events Punishment (for unapproved betrayal): 24h Ban → Role Blacklist → Permanent Ban from faction roles (for repeat or blatant violations) 3. Faction and Role-Specific Rules 3.1 Class-D Personnel Class-D are prisoners assigned to SCP testing and containment experiments. They are not free agents. Rules: Must comply with Foundation staff during tests unless resistance is approved via backstory or GameMaster. FearRP applies at all times — Class-D must surrender when outnumbered or threatened. Uniforms must remain default (orange jumpsuit). PAC3 use requires prior approval. Escapes and riots must be justified, coordinated, and roleplayed. Random aggression is FailRP. Punishment: Warning → 24h Ban → 3-day Ban 3.2 General Security (GENSEC) GENSEC is responsible for maintaining order within the Light Containment Zone (LCZ). You are the first line of defense and the primary authority over Class-D personnel and test logistics. Expectations: Follow your assigned SOP and orders from Foundation Command, Research Staff, or MTF where applicable Use force only when justified — FearRP and proportional response apply Do not leave the LCZ or interfere with HCZ/EZ activity without a direct order Protect Researchers and enforce site security — but do not overstep authority Punishment: Warning → 24h Ban → Role Restriction / SOP Enforcement 3.3 Mobile Task Force (MTF) MTF units are elite, high-clearance responders deployed for breach containment, CI engagement, and EZ defense. You are trained, tactical, and expected to carry yourself as a professional soldier. Expectations: Follow SOP and command orders precisely; no rogue operations or personal missions Remain mission-focused — RP must reflect your unit’s purpose D-Block access is permitted only for Lockdowns, Uncontrollable Riots. Inactive patrols, misuse of heavy weapons, or non-combat behavior without context is FailRP Punishment: Warning → Role Blacklist → Extended Ban 3.4 Research Division Researchers are responsible for the ethical and procedural testing of SCPs. You are not combatants — you are scientists. You should drive discovery, not chaos. Expectations: Follow Research SOP, request escorts when entering SCP zones All tests must be pre-approved and logged where required Improvisation is allowed within reason — but dangerous SCP exposure without approval is FailRP You may not be armed or engage in combat unless cleared by a GameMaster for a special scenario Punishment: Warning → 24h Ban → Role Restriction 3.5 SCP Entities SCPs are anomalies — you are not “players” in the conventional sense. Your actions should reflect the containment protocols, abilities, and behavioral lore of the specific SCP you are playing. Expectations: Do not speak, team up, or interact outside your SCP’s behavioral patterns unless lore supports it Breaching is only allowed if: It’s staff-approved A breach condition is met (e.g., a door is open or maintenance requirement not met) Use of PAC3, voice, or RP text must be in full compliance with the SCP’s lore SCPs do not use /advert. Instead, Foundation personnel (MTF, GENSEC, or Site Staff) are responsible for announcing breaches via /advert or in-character radio comms Example: ✅ /advert SCP-096 has breached in HCZ (posted by MTF/Staff) ❌ /advert I AM FREE LOL (posted by SCP-096) Abusing mechanics to self-breach (e.g., switching jobs or forcing open doors) is FailRP You may not escape containment just to roam or “look for action” — breaches must serve the story For Containment Procedures please refer to https://odysseyrp.xyz/topic/111-scp-containment-procedures/#comment-286 Punishment: 3-day Ban → SCP Role Blacklist → Permanent SCP Ban 3.6 Chaos Insurgency (CI) The Chaos Insurgency is a splinter paramilitary organization that aims to disrupt Foundation control, extract SCPs, and undermine site operations. CI operatives are trained, tactical, and lethal — but not random killers. Expectations: Follow your CI SOP and chain of command — undisciplined or solo actions are FailRP FearRP applies — you are elite, not unstoppable. Know when to pull back Raids must be objective-driven Do not kill indiscriminately or without reason — every operation must have a narrative motive Use only CI-appropriate gear Punishment: Warning → 24h Ban → 3-day Ban → CI Role Restriction 3.7 Serpent’s Hand (SH) The Serpent’s Hand is a rogue faction of anomalous sympathizers, dedicated to freeing SCPs, resisting control, and protecting the anomalous from human containment. They operate in secret, often using subversion and sabotage over brute force. Expectations: Work covertly — SH is not a raid-heavy faction. Your strength is RP, stealth, and subversion Freeing SCPs and Class-Ds must be meaningful — not random or routine FearRP applies — SH operatives are not combat specialists Use only SH-appropriate weapons and gear, with a focus on agility, stealth, and disruption Punishment: Warning → 24h Ban → Role Restriction → Faction Blacklist 3.8 Raid & Counter-Raid Procedures Raids and counter-raids are major coordinated operations between factions — not spontaneous skirmishes. To ensure balance, immersion, and pacing, strict limits are in place. Raid Rules: Raid Cooldown: Each faction (CI, SH, Foundation) may conduct one raid every 4 hours. Raid Ratio All raids must follow a 2:1 ratio (2 FO to 1 CI/SH) Time Limit: Raids may last a maximum of 30 minutes from the moment the first hostile engagement or breach of perimeter occurs. Objective Required: All raids must have a clear, RP-driven purpose (e.g., extracting an SCP, eliminating a target, recovering intel). Aimless raids or “chaos for chaos’ sake” are not permitted. Initiation: Raids must begin with IC communication — radio chatter, briefings, announcements — not OOC planning or surprise rushes. Staff Notification (Recommended): It is strongly recommended that factions notify a staff member or GameMaster prior to initiating a raid to ensure balance, visibility, and oversight — but this is not required. All Players (Attackers and Defenders): Upon death during a raid, you must wait 5 minutes before returning to the fight or re-entering the raid zone. Counter-Raids: May be launched within 10 minutes of a concluded raid Must have a clear, reactive objective (e.g., recovery, retaliation, rescue) Operate as one-life engagements — no respawns after death All Counter-Raids must follow the same RP and timing rules Raids should create tension, not chaos. One raid, one shot. Make it impactful. Punishment for violations: Verbal Warning → 24h Ban → 3-day Ban → Faction Role Blacklist (for repeated or exploitative behavior) 3.9 GOI/MTF Rules Players must choose one allegiance: Foundation (MTF), Chaos Insurgency (CI), or Serpent’s Hand (SH). Cross-faction roles or split loyalties are not permitted You may not hold officer+ roles in multiple factions simultaneously. Switching factions must be roleplayed properly. See rule 2.9 Failure to comply will result in a warning and potential faction role blacklist. You may not go higher than NCO in your second faction. GSD Chief - CI Officer+ (No) GSD Chief - CI NCO (Yes) 4. Containment and Breach Protocols 4.1 Breach Behavior During SCP breaches, each faction must act in accordance with their role: Foundation Personnel: Must prioritize recontainment and follow lockdown protocol. Class-D: May attempt to escape but must follow FearRP at all times. SCPs: Must act per lore and may not breach without proper triggers or staff approval. See SCP Rules Chaos Insurgency (CI): May intervene to escalate or exploit a breach only as part of a planned operation or raid. Random interference is not permitted. Serpent’s Hand (SH): May attempt to aid in SCP escape or protect anomalies only during pre-approved RP events or coordinated raids. Breaches must be reported using the in-game report system or via Discord, with video or log evidence. Punishment: Warning → 24h Ban → 3-day Ban 5. Tools and PAC3 Usage 5.1 Tool Gun Access The tool gun is restricted. Only staff, GameMasters, or those with forum-approved permissions may use it. Rules: Unauthorized prop spawning, tool usage, or physics manipulation is prohibited. Intentional misuse (e.g., prop griefing, server crashes) results in a permanent ban. Punishment: 7-day Ban → Permanent Ban 5.2 PAC3 Editor Guidelines PAC3 is for cosmetic/lore enhancements only and must not be used to gain mechanical or visual advantages. Rules: Must be submitted for approval via discord ticket, with screenshots and character context. No oversized models, offensive content, or FPS-heavy effects. Max height: 1.1x (combat roles), 0.9–1.1x (non-combat) Punishment: Warning → 7-day PAC3 Ban → Permanent Revocation 6. GameMasters and Events 6.1 GameMaster Authority GameMasters have full control over events, custom scenarios, and test supervision. Their instructions must be followed without question during active events. Failure to comply: Warning → Ban from Event → 24h Ban 6.2 Roleplay Events Participation must be immersive and fully in-character. Using OOC knowledge to manipulate outcomes is Metagaming and will be punished accordingly. 6.3 Player-Created Events Players may propose custom events via the forum or Discord. Proposals must include: Clear theme and objectives Expected factions and players Required tools or GameMaster oversight Events must be approved before execution. 7. Enforcement and Reporting 7.1 Reporting Rule Violations To report: Use the in-game report system or capture valid evidence (video/screenshot). Reports must include: Player Name, Steam ID, time of incident, and context. Submissions must be made within 24 hours. Do not confront rulebreakers directly — let staff handle it. False reports: Warning → 3-day Ban 7.2 Punishment Scaling Punishments escalate based on severity and frequency. Minor Offenses: Verbal → Written Warning Moderate Offenses: 24h → 3-day Ban Severe Offenses: Permanent Ban (e.g., ERP, harassment) Repeat violations within 30 days will automatically escalate to the next level. Staff discretion only applies to judgment of context — not whether the rule applies. 8. Appeals and Feedback 8.1 Ban Appeals Appeals must be submitted via the forum within 7 days of the ban. Include: Steam ID + Discord Description of the incident Any supporting evidence Appeals are reviewed within 72 hours. Messaging staff directly may delay appeal handling. 8.2 Feedback Feedback and suggestions must be submitted respectfully. Use the forum’s Suggestions section or Discord’s feedback channel. Spamming staff or making low-effort submissions will result in a warning. 9. Community Governance 9.1 SD/SDD/SDG Elections Leadership on OdysseyRP is shaped not only by RP but by community voice. Every month, the community will elect its Site Director (SD) and Site Deputy Director (SDD) through a structured debate and vote process. How It Works: One Debate per Month: Held approximately 1 week before the 1st (usually 24th–25th) One Election per Month: Held on the 1st of each month Players vote based on IC leadership, RP quality, and vision Candidates must announce intent prior to debate day Winning candidates will serve as the official IC heads of Foundation operations for that term, unless removed by staff or community vote. This system gives players agency while preserving serious roleplay structure. 9.2 Candidate Requirements To maintain quality leadership and prevent troll nominations, candidates must meet the following criteria: Receive permission from current Site Command or a vote of confidence from the Head of Security (HoS) No active punishments or bans in the past 30 days A clean disciplinary history involving FailRP, Metagaming, or Abuse Must hold (or be eligible for) a Foundation command whitelist or SD whitelist Must submit a brief campaign message or debate statement prior to the debate Failure to meet these conditions will result in disqualification before the debate begins. 9.3 Powers and Limits of Elected Leaders Site Directors (SD) and Deputy Directors (SDD) may: Set internal Foundation policy (IC SOP changes, schedules, command structure) Organize in-character meetings, alerts, and Foundation directives Roleplay as command figures for GENSEC, Research, and MTF (unless contradicted by O5 or staff oversight) However, SD/SDD may not: Override server-wide rules or staff decisions Create rogue policy not grounded in Foundation lore Engage in OOC punishments or authority (e.g., kicking staff, revoking roles) Use the role to harass, silence, or powerplay others All SD/SDD decisions are subject to Senior Admin+ review if abuse is suspected. 9.4 Removal and Emergency Votes If a current SD, SDD, or SDG (e.g., Site Administration team) is failing in their duties, the community may initiate a Vote of No Confidence. To request a removal: Submit a petition signed by 5 unique players with valid reasoning Include video/log evidence if abuse is involved EC will review the request and determine if a removal vote is justified A removal vote must receive ⅔ majority to pass If passed, the current SD/SDD is removed, and either the runner-up is promoted or a special election is held. Conclusion OdysseyRP operates under a strict SeriousRP framework. These rules exist to maintain order, fairness, and immersion. Attempting to exploit loopholes, interpret rules in bad faith, or intentionally bend roleplay mechanics will result in immediate punishment. By playing on this server, you agree to uphold the standards of realism, respect, and structure required for serious roleplay. Secure. Contain. Protect.

Thank you for applying to become a GameMaster for the OdysseyRP community! GameMasters craft immersive roleplay events, storylines, and experiences to enhance our server. Please copy and paste the template below into a new thread in the GameMaster Applications section. Fill out all fields completely and honestly. Our community and staff will review your application to determine if you’re a great fit to shape the future of OdysseyRP. 1. GENERAL INFORMATION In-Game Name: Discord Username (e.g., Username#1234): Steam ID (e.g., STEAM_0:0:12345678): Age: Timezone: 2. SERVER INVOLVEMENT Estimated Playtime on OdysseyRP (in hours): How long have you been part of the OdysseyRP community? (e.g., weeks, months): What roleplay roles or activities are you most involved in? (e.g., jobs, factions, events): 3. GAMEMASTER EXPERIENCE Previous GameMaster or Event Planning Experience (if any): (Include server names, roles, types of events, and duration. If none, state "None.") 4. CREATIVITY AND SKILLS Why do you want to become a GameMaster for OdysseyRP? (Explain your motivation and how you can enrich the server’s roleplay.) What skills or qualities make you a good fit for a GameMaster role? (e.g., storytelling, creativity, knowledge of GMod tools, organization, etc.) 5. EVENT PLANNING Describe an example roleplay event or storyline you would create for OdysseyRP: (Include the theme, objectives, player involvement, and how it enhances roleplay.) How would you handle a situation where an event you’re running goes off track? (e.g., players derail the story or technical issues arise.) 6. AVAILABILITY Weekly Availability: (Describe when you are typically available to plan and run events, e.g., weekdays, weekends, specific hours.) 7. ADDITIONAL INFORMATION Anything else you’d like to add? (Optional: Share extra details, creative ideas, or reasons why you’d be a great GameMaster.) INSTRUCTIONS FOR APPLICANTS Create a new thread in the GameMaster Applications section. Title your thread: “[Your In-Game Name] GameMaster Application”. Copy and paste the template above, filling out all fields. Be honest, detailed, and creative in your responses. Engage with community feedback on your application respectfully. We’re excited to review your application and see how you can bring epic roleplay experiences to OdysseyRP!

Thank you for applying to join the OdysseyRP staff team! Please copy and paste the template below into a new thread in the Staff Applications section. Fill out all fields completely and honestly. Our community and staff will review your application to determine if you’re a great fit to represent OdysseyRP. 1. GENERAL INFORMATION In-Game Name: Discord Username (e.g., Username#1234): Steam ID (e.g., STEAM_0:0:12345678): Age (Minimum Age 16, Exceptions Possible): Timezone: 2. SERVER INVOLVEMENT Estimated Playtime on OdysseyRP (in hours): How long have you been part of the OdysseyRP community? (e.g., weeks, months): What roleplay roles or activities are you most involved in? (e.g., jobs, factions, events): 3. STAFF EXPERIENCE Previous Staff Experience (if any): (Include server names, roles, duration, and responsibilities. If none, state "None.") 4. MOTIVATION AND SKILLS Why do you want to join the OdysseyRP staff team? (Minimum 150 Words) What skills or qualities make you a good fit for our staff team? (e.g., communication, conflict resolution, roleplay knowledge, etc.) (Minimum 150 Words) 5. SCENARIO QUESTIONS (Provide detailed responses to the following scenarios) Scenario 1: A player is breaking roleplay rules (e.g., FailRP) in a public area. How would you handle this? (Minimum 50 Words) Scenario 2: Two players are in a heated OOC argument in chat about a rule violation. What steps would you take? (Minimum 50 Words) Scenario 3: A player reports another for suspected cheating (e.g., aimbot). How would you investigate and proceed? (Minimum 50 Words) 6. AVAILABILITY Weekly Availability: (Describe when you are typically available to moderate, e.g., weekdays, weekends, specific hours.) 7. ADDITIONAL INFORMATION Anything else you’d like to add? (Optional: Share extra details, skills, or reasons why you’d be a great staff member.) INSTRUCTIONS FOR APPLICANTS Create a new thread in the Staff Applications section. Title your thread: “[Your In-Game Name] Staff Application”. Copy and paste the template above, filling out all fields. Be honest, detailed, and professional in your responses. Engage with community feedback on your application respectfully. We’re excited to review your application and see how you can help make OdysseyRP even better!

Introduction Welcome to OdysseyRP, a serious SCP Roleplay (SCPRP) community built around immersive storytelling in the SCP Foundation universe on Garry’s Mod. These community rules apply to all OdysseyRP platforms, including our Garry’s Mod server, Discord server, website (https://odysseyrp.xyz/), and any other official channels. Our goal is to create a respectful, inclusive, and engaging environment for all members. These rules ensure fairness, compliance with platform Terms of Service (ToS), and a high-quality roleplay experience. By participating in OdysseyRP, you agree to follow these rules, as well as the Discord ToS, Steam Community Guidelines, and Garry’s Mod policies. Failure to comply may result in warnings, suspensions, or bans across our platforms. Rules may be updated at any time by OdysseyRP Management, so check the forum regularly for changes. 1. General Community Conduct 1.1 Respect and Inclusivity All members must treat others with respect, regardless of race, gender, sexuality, religion, disability, or any other characteristic. Harassment, bullying, discrimination, or hate speech is strictly prohibited and will result in an immediate ban. This includes, but is not limited to: Slurs, derogatory language, or offensive jokes. Targeted harassment, such as doxxing, stalking, or repeated unsolicited messages. Content that promotes violence, extremism, or illegal activities. This aligns with Discord’s Community Guidelines, which prohibit harassment and hate speech, and Steam’s Community Conduct rules, which require respectful interactions. 1.2 Age Requirement OdysseyRP requires all members to be at least 13 years old, as per Discord’s ToS and Steam’s minimum age for account creation. Members under 18 must not share personal information (e.g., real name, address) in public channels, per Discord’s safety guidelines. 1.3 No NSFW Content Explicit, pornographic, or otherwise inappropriate content (e.g., nudity, gore, sexual themes) is banned across all platforms, including the Garry’s Mod server, Discord, and forum. This includes text, images, videos, links, or roleplay scenarios. Violations will result in a permanent ban, as this breaches Discord ToS (Section 4: Prohibited Content) and Steam’s Community Content Rules. 1.4 No Spamming or Trolling Do not spam messages, emojis, sounds, or game mechanics (e.g., props, chat, voice). Trolling, such as intentionally disrupting roleplay, events, or discussions, is prohibited. Examples include: Flooding Discord channels with irrelevant messages. Mic spamming in-game or on voice channels. Posting off-topic or disruptive content on the forum. 1.5 No Advertising or Solicitation Advertising other servers, communities, or services without explicit staff approval is not allowed. This includes sharing links to external Discord servers, YouTube channels, or commercial products. Soliciting personal information, donations, or sales is also prohibited, per Discord ToS (Section 5: Prohibited Activities) and Steam’s Community Rules. 1.6 Use English in Public Channels All public communications (in-game chat, Discord channels, forum posts) must be in English for accessibility. Private messages or in-character (IC) roleplay whispers may use other languages if all parties agree and it fits the SCP lore context. 1.7 No Impersonation Do not impersonate staff, other players, or real-world figures (e.g., celebrities, SCP Foundation personnel). This includes using similar usernames, avatars, or titles to deceive others. Impersonation violates Discord ToS (Section 5) and may result in a ban. 2. Platform-Specific Rules 2.1 Garry’s Mod Server Rules 2.1.1 Roleplay Conduct\ Stay In-Character (IC): Remain in-character at all times unless using OOC channels (e.g., /ooc, /looc). Breaking character (e.g., discussing real-world topics IC) is FailRP. Realistic Names: Use realistic first and last names for Foundation personnel (e.g., Dr. Emily Carter). Class-D use their assigned ID (e.g., D-9341). SCPs use their designation (e.g., SCP-173). Serpent’s Hand (SH) and Global Occult Coalition (GOC) members use lore-appropriate aliases or codenames. Meme or offensive names are prohibited. FearRP: Simulate realistic fear in dangerous situations (e.g., complying when at gunpoint unless you’re an SCP like SCP-682 with lore-based exceptions or an SH/GOC member with approved training). No FailRP: Actions must align with your role``` role and SCP lore. Examples of FailRP include a Class-D joking during a breach or a scientist ignoring containment protocols. No Metagaming: Do not use OOC information (e.g., Discord messages, player HUD names) for IC advantage. New Life Rule (NLR): After death, forget all prior events and avoid the death area for 5 minutes unless a GameMaster approves otherwise. No Random Deathmatch (RDM): Killing or harming others requires a valid IC reason (e.g., a GOC operation, not random attacks). No Erotic Roleplay (ERP): Sexual roleplay is banned and will result in a permanent ban, per Garry’s Mod community standards. 2.1.2 Faction Rules\ Foundation Personnel: Follow chain of command. Scientists advertise tests (/advert) and use Security escorts. MTF/Security recontain SCPs and protect the facility. Site Administration (e.g., Site Director) issues binding orders unless they violate rules. Class-D: Attempt escapes or riots but follow FearRP when confronted. Do not alter uniforms via PAC3 without GameMaster approval. SCPs: Adhere to your SCP’s lore (e.g., SCP-096 only attacks when seen). No self-breaching without GameMaster authorization. Friendly SCPs (e.g., SCP-999) have limited roaming privileges. Serpent’s Hand (SH): SH members aim to liberate SCPs and oppose Foundation containment, often aligning with certain SCPs. Coordinate major actions (e.g., aiding SCP breaches) with GameMasters. Follow FearRP when outnumbered. Use only SH-appropriate equipment unless acquired through roleplay. Global Occult Coalition (GOC): GOC members seek to neutralize or destroy SCPs to protect humanity. Coordinate attacks or operations with GameMasters. Follow FearRP when facing superior forces. Use only GOC-appropriate gear unless captured via roleplay. 2.1.3 Containment and Testing\ SCPs remain contained unless a GameMaster authorizes a breach. Unauthorized breaching is FailRP. Scientists need Senior Researcher or Site Administration approval for Keter SCP tests and must document results IC. Breaches require Foundation personnel to prioritize recontainment, Class-D to follow FearRP, SH to assist SCPs (if lore-appropriate), and GOC to neutralize threats. 2.1.4 Tool and PAC3 Usage\ Tool Gun: Restricted to staff/GameMasters. Unauthorized use (e.g., spawning disruptive props) is bannable. PAC3: Cosmetic enhancements must be lore-friendly and approved via the forum’s Character Bios section. No offensive or performance-heavy PACs. Height limits: combative roles (1–1.1), non-combative (0.9–1.1). 2.2 Discord Server Rules 2.2.1 Channel Usage\ Use channels for their intended purpose (e.g., #general for casual chat, #support for tickets). Do not post in staff-only or announcement channels unless invited. Avoid excessive pings, especially of staff or roles, unless necessary (e.g., reporting an urgent issue). 2.2.2 Voice Channels\ No mic spam, background noise, or disruptive sounds (e.g., soundboards). Use push-to-talk if your environment is noisy. Voice channels for roleplay (e.g., Foundation comms) must remain IC unless marked OOC. 2.2.3 Compliance with Discord ToS Per Discord ToS (https://discord.com/terms), you must: Be at least 13 years old. Not share illegal content, including pirated software, drugs, or malicious links. Not engage in doxxing, hacking, or distributing malware. Not organize or promote real-world violence or harm. Violations reported to Discord may result in account termination and a ban from OdysseyRP. 2.3 Forum Rules (https://odysseyrp.xyz/) 2.3.1 Posting Guidelines\ Post in the correct section (e.g., staff applications, suggestions). Off-topic posts may be removed. Use clear, professional language. Avoid excessive slang, memes, or spam in serious threads (e.g., ban appeals). Do not necro-post (reply to threads inactive for over 30 days) unless relevant (e.g., updating an appeal). 2.3.2 Applications and Appeals\ Staff and GameMaster applications must follow the provided templates and be detailed. Ban appeals require your Steam ID, Discord username, incident details, and evidence. False appeals may extend bans. 2.4 Steam Community Guidelines OdysseyRP operates within Steam’s ecosystem, so you must follow Steam’s Community Conduct Rules (https://steamcommunity.com/guidelines): No cheating, hacking, or exploiting (e.g., aimbots, wallhacks) in Garry’s Mod. This includes abusing server vulnerabilities. No posting offensive content in Steam profiles linked to OdysseyRP (e.g., avatars, usernames). No trading or selling in-game items for real money, as this violates Steam’s Subscriber Agreement. Violations reported to Steam may lead to account restrictions and OdysseyRP bans. 3. Event and GameMaster Guidelines 3.1 GameMaster Authority GameMasters control major roleplay events (e.g., breaches, SH liberations, GOC operations). Their decisions during events are final, and players must comply. Disputes can be addressed post-event via Discord or the forum. 3.2 Event Participation\ Stay in-character and follow GameMaster instructions. Do not use OOC knowledge (e.g., event plans from Discord) to influence outcomes. Only GameMasters can authorize SCP breaches, SH liberations, GOC attacks, or lore-altering events. 3.3 Event Proposals Players can submit event ideas via the forum or Discord, including: Theme and objectives (e.g., SCP-173 breakout aided by SH). Player roles (e.g., MTF, GOC, SCPs). Required tools or GameMaster oversight. 4. Reporting and Enforcement 4.1 Reporting Violations To report rule breakers: In-game: Use the report system or capture evidence (screenshots, videos) showing usernames, violations, and context. Discord/Forum: Submit reports in designated channels or sections with clear details. Do not confront violators OOC in-game or publicly shame them. False reports may result in warnings. 4.2 Punishment Guidelines Punishments are at staff discretion but follow: Minor Violations (e.g., minor FailRP, spam): Verbal warning, then formal warning. Moderate Violations (e.g., RDM, metagaming): Kick or 1–3 day ban. Severe Violations (e.g., harassment, ERP, hacking): Permanent ban, appealable after 30 days. Repeated offenses escalate penalties. Bans may apply across platforms (e.g., Discord and server). 4.3 External Platform Reports Violations of Discord ToS or Steam Guidelines (e.g., doxxing, cheating) will be reported to the respective platform, potentially leading to account termination. OdysseyRP will also ban offenders. 5. Appeals and Feedback 5.1 Ban Appeals Submit appeals on the forum (https://odysseyrp.xyz/) with: Steam ID and Discord username. Incident details and why the ban is unjust. Supporting evidence (e.g., screenshots). Appeals are reviewed by Senior Staff, and decisions are final. Do not contact staff directly to expedite appeals. 5.2 Feedback and Suggestions Share ideas via: Forum’s Suggestions section. Discord’s feedback channel. Direct messages to Senior Staff or the Server Owner (avoid spamming). Constructive feedback helps improve OdysseyRP. 6. Compliance with Additional Policies 6.1 Garry’s Mod Policies OdysseyRP uses Garry’s Mod, which operates under Facepunch Studios’ guidelines. Key rules: No distribution of pirated addons or content. No server crashing or exploiting (e.g., lag-inducing props). Violations may lead to Facepunch reports and OdysseyRP bans. 6.2 XenForo Forum (if applicable) If the forum uses XenForo, follow its guidelines: No automated bots or scripts for posting. No sharing malicious links or files. Violations may result in forum account suspension. 6.3 Intellectual Property Respect SCP Foundation lore, which is community-driven and partially Creative Commons (CC BY-SA 3.0). Do not claim SCP content as your own or use it for commercial purposes without proper attribution. OdysseyRP-specific content (e.g., custom events, characters) remains the intellectual property of the community and its creators. 7. Privacy and Safety 7.1 Personal Information Do not share sensitive personal information (e.g., address, phone number) in public channels. OdysseyRP is not responsible for information shared voluntarily. This aligns with Discord ToS (Section 6: Privacy) and Steam’s Privacy Policy. 7.2 Data Handling OdysseyRP collects minimal data (e.g., Steam ID, Discord username) for moderation and roleplay purposes. We do not share this data with third parties except as required by law or platform policies (e.g., Discord ToS reports). Contact staff for data inquiries. 8. Conclusion These rules ensure OdysseyRP remains a safe, immersive, and enjoyable SCP Roleplay community. By participating, you agree to abide by these rules, Discord ToS, Steam Community Guidelines, Garry’s Mod policies, and any other applicable platform terms. Violations may result in disciplinary action across all OdysseyRP platforms. If you have questions, contact staff in-game, on Discord, or via the forum. Warning: OdysseyRP Management reserves the right to change these rules at any time with or without notice. It is your responsibility to stay updated by checking the forum at https://odysseyrp.xyz/ regularly.