All Activity

OdysseyRP SCP Roleplay Server Rules Introduction Welcome to OdysseyRP’s SCP Roleplay server, a serious roleplay environment set in the SCP Foundation universe. Our goal is to provide an immersive experience where players assume roles such as Foundation personnel, Class-D, SCPs, Serpent’s Hand (SH), or Global Occult Coalition (GOC) to create dynamic, lore-compliant stories. These rules are mandatory and designed to ensure realistic, respectful, and enjoyable roleplay with minimal room for misinterpretation or exploitation. Violations will result in immediate consequences, including warnings, kicks, or bans, based on severity. Appeals for punishments must be submitted via the forum at https://odysseyrp.xyz/. Ignorance of these rules is not an excuse for non-compliance. Regularly check the forum for updates. 1. General Conduct 1.1 Respect All Players Respect is non-negotiable, both in-character (IC) and out-of-character (OOC). Any form of harassment, toxicity, or discrimination (e.g., based on race, gender, sexuality, religion) is strictly prohibited. This includes slurs, targeted insults, or offensive behavior. Violations result in an immediate ban, with no warnings issued. Appeals for such bans require substantial evidence of reform. 1.2 Use English for Communication All public IC and OOC communications (e.g., in-game chat, voice, /advert) must be in English. Private IC communications (e.g., whispers) may use other languages only if all involved players consent and it aligns with SCP lore. Non-English public communication is considered disruptive and will result in a warning, escalating to a kick for repeated offenses. 1.3 No Spamming or Trolling Spamming or trolling in any form is prohibited. This includes: Repeated messages, sounds, or emotes in chat or voice. Abusing game mechanics (e.g., excessive prop spawning, tool gun misuse). Intentional disruption of roleplay (e.g., screaming OOC during a test). First offense results in a verbal warning, second in a formal warning, and third in a 24-hour ban. Severe cases (e.g., server lag caused by spam) warrant an immediate ban. 1.4 Follow Staff Instructions Staff decisions during gameplay are final. Disputing or arguing with staff in-game is disruptive and will result in a warning, followed by a kick for non-compliance. Post-situation discussions must occur via Discord or the forum, with evidence provided. Deliberately misleading staff (e.g., falsifying logs) results in a 7-day ban. 1.5 No Advertising Advertising external servers, communities, or services (e.g., Discord links, YouTube channels) without explicit Senior Staff approval is prohibited. This includes subtle promotions (e.g., “check out my friend’s server”). Violations result in a 3-day ban, escalating to permanent for repeat offenses. 2. Roleplay Rules 2.1 Stay In-Character (IC) You must remain in-character at all times unless using designated OOC channels (/ooc, /looc). Breaking character, such as discussing OOC topics (e.g., real-world events, server mechanics) in IC chat or voice, is FailRP. First offense is a verbal warning, second is a formal warning, and third is a 24-hour ban. OOC channels must not be used to influence IC actions. 2.2 Use Realistic Roleplay Names Characters must have lore-appropriate names: Foundation personnel: Realistic first and last names (e.g., Dr. Sarah Bennett). Class-D: Assigned D-Class ID (e.g., D-9341). SCPs: Designated SCP number (e.g., SCP-049). SH: Mystical or alias-based names (e.g., “Shade”). GOC: Military-style codenames or surnames (e.g., Agent Kessler). Names based on celebrities, memes, or offensive terms are prohibited. Non-compliant names must be changed immediately upon staff request. Failure to comply within 5 minutes results in a kick, followed by a 24-hour ban if unchanged upon rejoin. 2.3 Follow FearRP You must simulate realistic fear in life-threatening situations, defined as: Being held at gunpoint by two or more armed personnel. Being restrained (e.g., handcuffed, ziptied). Facing a hostile SCP without adequate protection (e.g., weapons, containment gear). Compliance is mandatory unless you have a GameMaster-approved backstory justifying resistance (e.g., GOC training). Exceptions apply to specific SCPs (e.g., SCP-682’s lore-based fearlessness). Violating FearRP is FailRP, resulting in a warning, with repeat offenses leading to a 24-hour ban. 2.4 No FailRP Actions must strictly align with your character’s role, motives, and SCP lore. FailRP includes, but is not limited to: Class-D engaging in frivolous behavior (e.g., dancing) during a breach. Scientists ignoring containment protocols (e.g., entering an SCP chamber without clearance). SCPs acting outside their lore (e.g., SCP-173 speaking). Unrealistic item use (e.g., dropping a weapon mid-combat to avoid death). First offense is a verbal warning, second is a formal warning, and third is a 24-hour ban. Severe or intentional FailRP (e.g., disrupting an event) results in a 3-day ban. 2.5 No Metagaming Using OOC information for IC advantage is prohibited. Examples include: Identifying disguised players via HUD names. Acting on Discord or stream information your character wouldn’t know. Sharing breach details in /ooc to influence IC actions. Metagaming results in a 24-hour ban, with repeat offenses escalating to a 7-day ban. Evidence (e.g., screenshots) must be provided for reports. 2.6 Respect New Life Rule (NLR) Upon death, your character forgets all events of their previous life and cannot return to the death area (within 50 meters) for 5 minutes. Acting on prior knowledge or returning early is prohibited unless a GameMaster explicitly authorizes an exception for an event. Violations result in a warning, with repeat offenses leading to a 24-hour ban. 2.7 No Random Deathmatch (RDM) Killing or harming another player requires a clear, documented IC reason (e.g., GOC neutralizing an SCP, SH liberating a Class-D). Invalid RDM includes: Killing without prior roleplay interaction. Attacking teammates without GameMaster-approved defection. Spawn camping or targeting players upon spawn. RDM results in a 24-hour ban, with repeat offenses escalating to 7 days. Victims must provide evidence (e.g., logs, video) for reports. 2.8 No Erotic Roleplay (ERP) Any sexual or erotic roleplay, including suggestive text, actions, or PAC3 creations, is strictly prohibited. Violations result in an immediate permanent ban, with appeals only considered after 90 days and requiring proof of understanding the rule. 2.9 Follow Team Loyalty You must act in your faction’s best interest unless a GameMaster-approved IC scenario (e.g., SH infiltration, GOC negotiation) permits otherwise. Examples of disloyalty include: Foundation personnel aiding SH without approval. GOC members sparing SCPs against their lore. Violations result in a 3-day ban, with repeat offenses leading to a permanent ban from the faction role. 3. Faction and Role-Specific Rules 3.1 SCP Foundation Personnel Foundation roles (e.g., Security, MTF, Scientists, Site Administration) must adhere to strict protocols: Scientists: Must use /advert for all SCP tests (e.g., “/advert SCP-049 Test, Security to LCZ”), follow containment procedures, and escort Class-D with at least one Security member. Unauthorized tests result in a warning, escalating to a 24-hour ban. Security/MTF: Protect the facility, escort Class-D, and recontain SCPs. Lockdowns (e.g., “/advert D-Block Lockdown in 30s: Riot”) require Lieutenant+ rank and a valid reason, logged IC. Unauthorized lockdowns result in a warning, then a 24-hour ban. Site Administration (e.g., Site Director): Issue facility-wide orders, which are binding unless they violate server rules. Abusing authority (e.g., ordering frivolous actions) results in a 3-day ban and possible demotion. 3.2 Class-D Personnel Class-D are prisoners used for SCP testing. Rules: Escape attempts or riots must follow FearRP when confronted by armed personnel (e.g., two or more Security with weapons drawn). Uniforms must remain standard (orange jumpsuit). PAC3 alterations require GameMaster approval via the forum. Unauthorized changes result in a warning, then a 24-hour ban. Cooperation with Foundation staff is mandatory during tests unless a GameMaster-approved backstory (e.g., SH affiliation) justifies resistance. Non-compliance without approval is FailRP, with penalties as per 2.4. 3.3 SCPs SCPs must strictly follow their lore and containment procedures: Actions are limited to your SCP’s documented abilities (e.g., SCP-173 moves only when unseen, SCP-049 creates zombies via touch). Breaching containment without GameMaster authorization or a scripted event is FailRP and results in a 3-day ban. Breaches must be logged via /advert (e.g., “/advert SCP-096 Breached”). Friendly SCPs (e.g., SCP-999) may roam within designated areas (e.g., Light Containment Zone) but must return to containment during lockdowns or night cycles. Hostile SCPs (e.g., SCP-096) remain contained unless breached. Abusing SCP mechanics (e.g., excessive killing without roleplay context) results in a 24-hour ban, escalating to a 7-day SCP role ban for repeat offenses. 3.4 Serpent’s Hand (SH) SH members aim to liberate SCPs and oppose Foundation containment, often aligning with SCPs. Rules: Major actions (e.g., aiding SCP breaches, infiltrating the facility) require GameMaster approval via Discord or forum request at least 24 hours in advance. Unauthorized actions result in a 3-day ban. Follow FearRP when outnumbered (e.g., facing three or more armed MTF). Violations are FailRP, with penalties as per 2.4. Use only SH-appropriate equipment (e.g., improvised weapons, mystical artifacts) unless capturing Foundation gear through documented roleplay (e.g., /advert “SH steals MTF keycard”). Unauthorized gear use results in a warning, then a 24-hour ban. 3.5 Global Occult Coalition (GOC) GOC members seek to neutralize or destroy SCPs to protect humanity. Rules: Operations (e.g., facility raids, SCP neutralization) must be coordinated with a GameMaster via Discord or forum request at least 24 hours in advance. Unauthorized actions result in a 3-day ban. Follow FearRP when facing superior forces (e.g., multiple MTF units). Violations are FailRP, with penalties as per 2.4. Use only GOC-appropriate gear (e.g., military weapons, anti-anomaly tech) unless capturing Foundation equipment through documented roleplay (e.g., /advert “GOC captures MTF rifle”). Unauthorized gear use results in a warning, then a 24-hour ban. 4. Containment and Breach Rules 4.1 SCP Containment SCPs must remain in their designated containment chambers unless a GameMaster authorizes a breach via a scripted event or SH/GOC action. Unauthorized breaching, including exploiting game mechanics (e.g., glitching through doors), is FailRP and results in a 7-day ban. Only Class-D, SH, GOC, or GameMaster-approved events can initiate breaches. 4.2 Breach Procedures During a breach: Foundation Personnel: Prioritize recontainment, follow MTF or Site Administration orders, and use /advert for major actions (e.g., “/advert MTF Nu-7 deployed to HCZ”). Failure to comply results in a warning, then a 24-hour ban. Class-D: May attempt escape but must follow FearRP when confronted (e.g., by Security or GOC). Violations are FailRP, with penalties as per 2.4. SCPs: Act strictly per lore (e.g., SCP-049 creates zombies, SCP-173 moves when unseen). Deviations result in a 24-hour ban. SH: May assist SCPs if lore-appropriate but must follow GameMaster instructions. Unauthorized interference results in a 3-day ban. GOC: Prioritize neutralizing SCPs but must coordinate with GameMasters. Unauthorized actions result in a 3-day ban.\ Breaches must be reported in-game via the report system or on Discord with evidence (e.g., video showing player names and violation). 4.3 Testing Protocols Scientists must: Obtain written approval from a Senior Researcher or Site Administration for Keter-class SCP tests, submitted via Discord or forum 24 hours in advance. Use at least one Security escort for Class-D transport, with no exceptions. Document test results IC via /advert or logs, avoiding unnecessary risks (e.g., direct SCP interaction without containment).\ Violations (e.g., unauthorized tests, missing escorts) result in a warning, then a 24-hour ban, with repeat offenses leading to a 7-day scientist role ban. 5. Tool and PAC3 Usage 5.1 Tool Gun Restrictions Tool gun access is restricted to staff, GameMasters, or players with explicit Senior Staff permission, granted via forum application. Unauthorized use (e.g., spawning props, vehicles, or entities) results in a 7-day ban. Using the tool gun to disrupt roleplay (e.g., crashing the server) results in a permanent ban. 5.2 PAC3 Editor Rules PAC3 is permitted for lore-compliant cosmetic enhancements, subject to: Approval via the forum’s Character Bios section, including a detailed PAC3 request with screenshots. No offensive, oversized (exceeding 1.5x player model size), or performance-heavy PACs (e.g., causing FPS drops). Height limits: combative roles (1–1.1 scale), non-combative (0.9–1.1 scale).\ Unauthorized or abusive PAC3 use (e.g., mimicking SCP models, creating lag) results in a warning, then a 7-day PAC3 ban. Repeat offenses lead to permanent PAC3 revocation. 6. Event and GameMaster Rules 6.1 GameMaster Authority GameMasters oversee events and major roleplay scenarios (e.g., breaches, SH liberations, GOC raids). Their decisions are final, and non-compliance results in a warning, followed by a kick. Disputes must be addressed post-event via Discord or the forum with evidence. 6.2 Event Participation\ Participate in-character, following GameMaster instructions without deviation. Using OOC knowledge (e.g., event plans from Discord) to influence outcomes is Metagaming, with penalties as per 2.5. Only GameMasters can authorize SCP breaches, SH/GOC actions, or major lore changes. Unauthorized interference results in a 3-day ban. 6.3 Custom Events Players may propose events via the forum or Discord, including: Event theme and objectives (e.g., SH-led SCP-999 liberation). Expected player involvement (e.g., MTF, GOC, SCPs). Required GameMaster oversight or tools (e.g., tool gun, PAC3).\ Proposals must be submitted 48 hours in advance and approved by a GameMaster. Unauthorized events result in a warning, then a 24-hour ban. 7. Reporting and Punishment 7.1 Reporting Violations To report a violation: Use the in-game report system or capture evidence (e.g., screenshots, video) showing the player’s Steam ID, username, violation, and context. Submit reports via Discord or the forum within 24 hours, with clear details. False or malicious reports result in a warning, escalating to a 3-day ban. Do not confront rule-breakers OOC in-game or via public channels. Doing so results in a warning. 7.2 Punishment Guidelines Punishments are enforced consistently, with no exceptions: Minor Violations (e.g., minor FailRP, OOC spam): Verbal warning, then formal warning logged in staff records. Moderate Violations (e.g., RDM, metagaming): 24-hour ban, escalating to 3 days for repeat offenses. Severe Violations (e.g., harassment, ERP, intentional crashing): Permanent ban, appealable after 90 days via the forum with evidence of reform.\ All punishments are logged, and repeated violations within 30 days escalate penalties (e.g., second moderate violation is a 7-day ban). Staff discretion applies only to situational context, not rule enforcement. 8. Appeals and Feedback 8.1 Ban Appeals Submit appeals via the forum at https://odysseyrp.xyz/ within 7 days of the ban, including: Steam ID and Discord username. Detailed explanation of the incident and why the ban is unjust. Evidence (e.g., screenshots, video) supporting your case.\ Appeals are reviewed by Senior Staff within 72 hours, and decisions are final. Contacting staff directly to expedite appeals results in a 7-day appeal delay. 8.2 Feedback Submit suggestions to improve the server via: Forum’s Suggestions section, using the provided template. Discord’s dedicated feedback channel, with concise details. Direct messages to Senior Staff or the Server Owner, limited to one message per week to avoid spam.\ Frivolous or spam feedback results in a warning. Conclusion These rules foster a respectful, immersive, and fair SCP roleplay experience. Compliance is mandatory, and attempts to exploit loopholes (e.g., vague interpretations, unreported violations) will be met with strict enforcement. By playing on OdysseyRP, you agree to uphold these standards and contribute to a positive community. For questions, contact staff in-game, on Discord, or via the forum. Secure. Contain. Protect. Warning These rules may be changed at any time with or without notice by OdysseyRP Management. It is your responsibility to stay updated by regularly checking the forum at https://odysseyrp.xyz/.

ODYSSEYRP GAMEMASTER APPLICATION FORMAT 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!

ODYSSEYRP STAFF APPLICATION FORMAT 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: 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? (Explain your motivation and how you can contribute to the community.) What skills or qualities make you a good fit for our staff team? (e.g., communication, conflict resolution, roleplay knowledge, etc.) 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? Scenario 2: Two players are in a heated OOC argument in chat about a rule violation. What steps would you take? Scenario 3: A player reports another for suspected cheating (e.g., aimbot). How would you investigate and proceed? 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.