Community Rules & Standards

1.1 Minimum Age

Every applicant must have turned seventeen (17) before submitting an application. There are no exceptions to this requirement.

1.2 Required Software

Applicants need a legitimate, working copy of Grand Theft Auto V and the ability to run FiveM at the time they apply.

1.3 Language

MVRP operates in English. Every member needs to be able to hold a conversation in English, both in voice and in text, so that scenes, radio traffic, and staff communication stay clear for everyone.

1.4 Hardware & Connectivity

Members are expected to have:

• A functioning microphone suitable for voice roleplay
• A stable internet connection
• A PC that can comfortably run FiveM, Discord, and MVRP’s supporting tools.

2.1 Treating Others with Respect

Every member deserves basic respect. Genuine discrimination of any kind, whether based on race, ethnicity, sex, gender identity, sexual orientation, religion, age, disability, nationality, or political views, has no place in MVRP. This applies in character and out of character alike: a scene, character concept, or parody built to demean a group or a real person’s identity is a violation of this rule, not creative roleplay.

2.2 Harassment

Harassment in any form will not be tolerated. This covers bullying, intimidation, sexual harassment, doxxing or sharing someone’s private information, and anything else staff reasonably identifies as harassing behavior.

2.3 General Conduct

Whenever you’re using an MVRP platform in-game, in Discord, on the radio, on the CAD, or on the member portal, you’re expected to carry yourself in a mature and appropriate manner. Characters, vehicles, names, or scenes created to troll, grief, or derail other people’s roleplay fall under this rule (see also Civilian SOP 3.7).

2.4 Slurs & Offensive Language

MVRP has a zero-tolerance stance on slurs and derogatory language targeting a protected characteristic (race, ethnicity, gender, orientation, religion, disability, and similar). This rule applies everywhere and always:

• In character and out of character alike, "it was just roleplay" is never an acceptable defense
• In voice, text chat, in-game phones, and social media scripts, Discord, and every other MVRP platform
• At staff discretion, in private messages between members when the conduct affects the community

Certain slurs may result in an immediate, permanent removal at the discretion of community leadership. Separately, a repeated pattern of excessively vulgar or grotesque language, even if it isn’t a slur, can also lead to disciplinary action.

2.5 Explicit or Illegal Content

Posting or distributing explicit, gory, disturbing, or illegal material is prohibited anywhere on MVRP platforms. That includes usernames, nicknames, avatars, bios, statuses, in-game license plates, and any clips, screenshots, or streams shared from MVRP. Members must also comply with Discord’s Terms of Service and all applicable laws. Conduct inside a live scene (sexual roleplay, in-game nudity) is governed by Civilian SOP 3.1 and department policy, with this rule as the parent.

3.1 Community Chain of Command

These are the only staff and member titles used across MVRP documents. The Civilian Operations SOP and department documents use these titles and do not create separate ones.

Community Directors

Own the overall direction of MVRP. They oversee development, staffing, and administration, and they approve community-wide policy. They may issue any disciplinary action and may overrule any decision below them.

Administrators

Hold full authority over community operations. They enforce the rules, run investigations, issue suspensions and removals, review appeals, approve restricted civilian scene types (see Civilian SOP 2.3), and maintain the Civilian Operations SOP.

Probationary Administrators

Staff in their trial period. They provide day-to-day oversight in the server (answering scene questions, monitoring roleplay quality, mentoring newer members, handling first-line rule concerns), may issue verbal and written warnings, and may approve restricted civilian scene types (see Civilian SOP 2.3). They do not issue suspensions or removals.

Members

Verified community members who have completed their 30-day probationary period. Members are expected to know and follow these rules, the Civilian Operations SOP when patrolling as a civilian, and their department’s policies.

Probationary Members

New community members during their first thirty (30) days after verification. Probationary Members hold the same conduct responsibilities as Members but a reduced civilian permission set (see Civilian SOP Section 2). Probation ends automatically after 30 days unless an Administrator extends it in writing for cause, and any formal disciplinary action during probation may result in removal without the normal escalation steps.

3.2 What We Expect from Members

1. 3.2.1 Use the proper chain of command in the community and in your department.
2. 3.2.2 Be honest with community leadership; misleading staff during any conversation or investigation is itself a violation.
3. 3.2.3 Don’t lobby for promotions, awards, or positions.
4. 3.2.4 Follow everything laid out in this document, the Civilian Operations SOP, and your department’s standards.
5. 3.2.5 Membership in a blacklisted community while a member of MVRP is prohibited. Communities are blacklisted when leadership determines they pose a risk to MVRP or its members.
6. 3.2.6 Do not attempt to poach MVRP members or guests for other FiveM communities.

3.3 What We Expect from Staff

Anyone holding a position in MVRP, direction, administration, development, or recruitment, is held to a higher standard of professionalism than the general membership.

• Staff decisions must be free of personal bias.
• Staff authority exists only within its assigned scope. Using a title to intimidate, coerce, or throw weight around outside that scope is prohibited.
• Staff are accountable to the community. Members are encouraged to report staff misconduct through the reporting process. Reporting staff misconduct is separate from appealing a disciplinary decision (see 6.4); a report does not reopen a closed appeal.
• Leadership positions carry monthly activity expectations; failing to meet them over consecutive months may result in removal from the position.

3.4 Leaves of Absence (LOA)

If you expect to be away for more than thirty (30) days, submit an LOA request through the official form linked in the MVRP Discord. An approved LOA covers the whole community, including all departments.

While on LOA, you are considered inactive and may not:

• Patrol or take part in in-game operations
• Log patrol, training, or event hours
• Act in any department or supervisory role
• Participate in activity-based events

Coming back early? Message a Probationary Administrator or above so your status can be updated before you resume duties.

Going silent after your LOA ends? Members who don’t return or check in after their LOA expires may be reviewed for removal under activity requirements.

Misusing an LOA to dodge activity checks or discipline may result in denial of the request or further action.

You’re always welcome to hang out and socialize in non-activity areas of the community during your LOA; it just won’t count toward any hour requirements.

4.1 MVRP Assets

MVRP assets include the MVRP Discord server, approved department Discords, the FiveM server, the MVRP website and member portal, the MVRP dispatch console, SonoranCAD, Tommy’s Radio infrastructure, and any documentation bearing MVRP branding.

4.2 Personal Information

Sharing your own personal information on any MVRP platform is your choice alone. Never share another member’s personal details; only the person the information belongs to may choose to share it.

4.3 Liability

MVRP is not responsible for information members choose to post on its platforms. Content that breaks these rules will be handled through discipline or, where appropriate, reported to the proper authorities.

4.4 Security Incidents

Development team members are trusted custodians of MVRP’s infrastructure. If leadership is unavailable during a security threat, developers have full authority to take whatever action is needed to protect community assets.

4.5 Ownership of Work

Documents, resources, and other assets created for or purchased on behalf of MVRP become MVRP property and must be turned over to the Community Directors. Withdrawing, deleting, or withholding those assets is prohibited unless leadership approves it.

4.6 Impersonation (Out of Character)

Posing as a real MVRP member, staff member, department, or official MVRP account, in Discord, on the portal, on the CAD, or anywhere else, is prohibited. This rule covers out-of-character identity. Playing a fictional police officer, firefighter, or medic as a civilian character in-game is a separate matter governed by Civilian SOP 3.1.5 and 3.6.

5.1 The Basics

The server is always live.

The MVRP FiveM server is treated as active roleplay at all times, no matter how many players are online, unless leadership says otherwise.

No unauthorized mods.

External trainers, menus, or modifications that aren’t part of the MVRP server are banned. Graphics packs are fine as long as they don’t dramatically alter the game.

5.2 Core Roleplay Violations

These definitions are the parent offenses for roleplay discipline anywhere in MVRP. SOP and department rules that describe a specific way of committing one of these cite it by name.

Metagaming

Bringing information into a scene that your character couldn’t realistically know (from streams, Discord, videos, or anything else outside the roleplay) to gain an edge. Civilians listening to, scanning, or sitting in any LEO or SAFEMS radio channel, or converging on a scene they learned about only by monitoring chat channels, is metagaming (Civilian SOP 3.1.7 and 3.12).

Forced Roleplay

Imposing actions or outcomes on another player without giving them a fair chance to react or respond.

Random Deathmatch (RDM)

Killing another player without legitimate in-character justification. Violence should grow out of the story, not appear out of nowhere. Lethal force against responders with no built-up storyline is RDM even when the priority system was used (Civilian SOP 2.4).

Powergaming

Exploiting mechanics, scripts, or the map to influence roleplay in unrealistic ways. Supernatural or superhuman characters (Civilian SOP 3.7), AI vehicles that cannot be stopped or that evade through automated pathing (Civilian SOP 3.14), and vehicle multipliers (5.3.1) are forms of powergaming.

Scene Rushing

Trying to fast-forward a scenario instead of letting it develop naturally.

No Value of Life (NVL)

Acting as if your character has nothing to lose in situations where any reasonable person would fear for their safety. Ignoring injury or death cooldowns (Civilian SOP 3.9) is treated as NVL.

Fail Roleplay (FRP)

Behaving in ways that break realism or ignore the situation your character is in. This includes driving away from a crash your vehicle or character could not realistically survive (Civilian SOP 3.8), and ignoring in-game text communication during an active scene: if you’re part of a scene, investigation, or coordinated event, you’re expected to keep an eye on the relevant chat channels and respond in a reasonable timeframe. Going dark mid-scene can be treated as scene disruption.

Civilian Stalking

Following, camping on, or repeatedly re-engaging a civilian without an articulable in-character reason (a violation, a BOLO match, an active investigation, suspicious behavior, or a call for service). This is a "play to win" behavior that kills organic roleplay.

Cop Baiting

Deliberately provoking law enforcement with unrealistic or unnecessary antics, with no scene behind it, just to trigger a pursuit, a detention, or a fight. This is likewise a "play to win" behavior and is prohibited. Cop Baiting is about manufacturing responder attention from nothing; inserting yourself into someone else’s existing scene is Scene Leeching, defined in Civilian SOP 3.12. Staff cite whichever one fits; the same act is not charged under both.

5.3 Script & Mechanic Rules

1. 5.3.1 Vehicle multipliers: Don’t use external scripts or settings to boost speed, engine power, or torque unless your department’s policy explicitly permits it. Civilians have no department policy, so multipliers are never permitted on a civilian character.
2. 5.3.2 God mode: Never make your character or vehicle invulnerable.
3. 5.3.3 Invisibility: Never activate invisibility.
4. 5.3.4 Teleporting: Only teleport when spawning in, getting back to a scene after a crash, or switching characters / starting a fresh scenario.
5. 5.3.5 Priority system: Civilians must follow the priority system exactly as defined in Civilian SOP Section 4 (activation parameters, /prio commands, and limits). The SOP is the only place those mechanics are defined.
6. 5.3.6 No-clip: Only use no-clip to reach a legitimate roleplay spot you can’t otherwise get to, or to free yourself from a glitch.

5.4 Chat Commands

/gooc

Global out-of-character. Server-wide OOC messages only when genuinely necessary. Not for conversations, complaints, or general questions.

/ooc

Local out-of-character chat visible to nearby players.

/gme

Global action descriptions for events that affect the entire server.

/me

Describes your character’s actions.

/do

Describes the environment, context, or the result of an action.

/county

Requests county-style services (basic tows, minor injuries) that locals can reasonably cover when the relevant department is not in server (see Civilian SOP 3.2).

/civchat

Civilian coordination channel, used to announce priorities (see Civilian SOP 4.2). Not a source of scene locations for uninvolved players, see Metagaming, 5.2.

Chat etiquette: Stay in character unless you’re explicitly using an OOC channel, keep it respectful even when characters clash, and don’t spam or flood chat with repetitive or irrelevant messages.

6.1 Who Can Issue Discipline

• Probationary Administrators may issue verbal warnings and written warnings for any violation, and may remove a member from the server for the remainder of the current session to stop an active problem.
• Administrators may issue any action, including suspensions and removals, and are the only staff below Director level who may impose a permanent removal.
• Community Directors may issue any action and may overrule any decision below them.
• Department supervisors do not issue community-level discipline. They handle department-internal discipline under their own policy; anything that rises to a violation of this document is referred to a Probationary Administrator or above.
• Probationary Members: any formal action (written warning or above) issued during the 30-day probationary period may be converted to removal by an Administrator without the escalation steps in 6.2.

6.2 How Discipline Is Decided

Discipline is decided case by case because no two incidents are identical. Staff review what happened, weigh the circumstances, and land on a proportional outcome. The table below shows the normal range for each category so members know what to expect; staff may go outside the range where the facts justify it, and must say why in the notice.

Repeat violations. A second violation of the same rule number within sixty (60) days of the previous notice is escalated at least one step beyond the previous outcome. A second violation of a different rule in the same window is considered in the outcome but does not automatically escalate.

6.3 Disciplinary Notices

Every formal action (written warning, suspension, or removal) is delivered in writing through the MVRP Discord ticket or DM system and states: the rule number(s) from this document, the SOP or department section involved if any, a short description of what happened, the action taken, the issuing staff member, and the date. Verbal warnings are logged by staff but do not require a written notice.

6.4 Appeals

Any member who receives a formal action, a written warning, suspension, or removal, is entitled to one (1) appeal per action. An appeal is not a retrial of the incident; it is a review of three things: whether the rule was applied correctly, whether the investigation was fair and supported by sufficient evidence, and whether the outcome was proportional to the offense.

Appeals must:

• Be submitted within 72 hours of receiving the disciplinary notice.
• Be submitted in writing through a ticket in the MVRP Discord.
• Include your username and community ID, the date the discipline was issued, the rule(s) cited, and any supporting evidence or documentation.

Appeals are reviewed by an Administrator (or a Community Director) who was not involved in the original decision. The reviewer’s decision is final and cannot itself be appealed. Permanent removals issued under 2.4 may be appealed only to a Community Director.

6.5 Removal

Members may be removed from MVRP for violations under this section or for failing to meet activity requirements.

6.6 Cooperating with Staff

Members must cooperate with investigations and outreach from Probationary Administrators and above. That means answering messages, acknowledging contact, and participating in any related discussions. Ignoring staff outreach for more than 48 hours, or actively dodging contact, counts as non-cooperation and can result in a server suspension until you respond.

6.7 Resigning

You may resign at any time. Notify your department’s chain of command and they’ll process your departure properly. Members with no department may resign through a Discord ticket.

Mountain Valley Roleplay exists to give its members immersive, realistic, and genuinely fun emergency services and civilian roleplay. These rules aren’t here to restrict creativity; they’re here to protect it. Follow them, look out for each other, and don’t hesitate to bring feedback to community leadership; MVRP only gets better when its members help shape it.