Odyssey Roleplay ✔ Odyssey RP Posted March 22 Odyssey Roleplay ✔ Posted March 22 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.
Recommended Posts