GLOBAL STANDARD
OPERATING PROCEDURES.

1.1 Purpose

These Global Standard Operating Procedures establish the community-wide rules for Project 713. They apply to every member while using Project 713 services, participating in the FiveM server, using Project 713 Discord spaces, or representing the community.

Project 713 is built around structured, realistic roleplay with open civilian access and whitelisted law enforcement departments. Civilian players do not need to join a department to participate. Law enforcement access is restricted to approved department members.

1.2 Agreement to the Rules

By participating in Project 713, members agree to follow community rules, reasonable staff instructions, department policies that apply to them, and the intended spirit of the rules. Attempting to exploit technicalities or loopholes is not acceptable.

Ignorance of a published rule does not automatically excuse a violation.

1.3 Community Structure

Project 713 separates community-wide rules from department-specific SOPs. These Global SOPs apply to everyone. Individual law enforcement departments may maintain additional policies, training standards, pursuit policies, radio procedures, uniforms, equipment rules, and command structures, provided those policies do not override Project 713 community rules.

2.1 Respect & Behavior

Treat other members with reasonable respect. Harassment, targeted bullying, hate speech, discriminatory conduct, threats, doxxing, excessive personal attacks, and intentionally disruptive toxicity are prohibited.

Disagreements should remain focused on the issue. Do not turn roleplay disagreements into personal conflicts.

2.2 Staff Interactions

During an active staff situation, follow staff instructions and allow the situation to be handled. Do not interfere with a staff investigation, intentionally evade moderation, or create a public argument over an active punishment.

Members may challenge a staff decision through the proper ticket or appeal process.

2.3 Advertising & Solicitation

Unauthorized advertising of other FiveM communities, Discord servers, paid services, or competing communities is prohibited. Members may not stream or screen share other FiveM or roleplay Discord servers in Project 713 voice channels, tickets, or community spaces. Casual discussion is not automatically advertising; actively recruiting Project 713 members, repeatedly promoting another community, or displaying another server through Discord screen sharing is prohibited.

2.5 Exploits, Cheats & Abuse

Cheats, mod menus, unauthorized injectors, duplication exploits, script abuse, animation abuse, or knowingly using a bug for an unfair advantage are prohibited.

If a serious exploit is discovered, report it to staff rather than demonstrating or distributing it.

3.1 Random Deathmatch (RDM)

Attacking, injuring, or killing another player without a legitimate roleplay reason or meaningful roleplay interaction is prohibited. A scene should have enough context for the other player to reasonably understand why force is occurring.

3.2 Vehicle Deathmatch (VDM)

Using a vehicle as a weapon without legitimate and realistic roleplay justification is prohibited. Intentionally running people over, repeatedly ramming vehicles, or using a vehicle to kill for no valid scene reason may be treated as VDM.

3.3 FailRP

FailRP includes actions that are clearly unrealistic, immersion-breaking, or inconsistent with the circumstances of a scene. Examples include ignoring serious injuries, impossible vehicle use, instantly recovering from major trauma, or intentionally refusing to engage with obvious roleplay consequences.

3.4 Powergaming

Do not force an outcome on another player without allowing a reasonable opportunity to react. Roleplay actions should leave room for response unless the game mechanics or circumstances clearly determine the outcome.

3.5 Metagaming

Do not use out-of-character information to gain an in-character advantage. This includes stream sniping, using information from unrelated Discord conversations, or receiving live scene information from someone who is not legitimately communicating with your character.

3.6 Combat Logging

Leaving the server to avoid arrest, a roleplay consequence, death, staff action, or an active scene is prohibited. If you disconnect unexpectedly, make a reasonable effort to return or notify involved members/staff.

3.7 New Life Rule (NLR)

After your character dies and respawns, do not immediately return to the same active scene, seek revenge, or act on detailed knowledge of the events that directly caused the character's death. Staff may set or modify an NLR period when needed for a scene.

3.8 Restricted Roleplay

Sexual roleplay, explicit sexual content, torture-focused roleplay, suicide/self-harm roleplay, and terrorism/extremism roleplay are prohibited unless Project 713 Ownership has explicitly published a narrower approved policy for a specific type of scenario. Do not use restricted themes as a surprise element in ordinary scenes.

4.1 Vehicle Realism

Drive vehicles within reasonable real-world limits for the vehicle and scene. Excessive stunt driving, unrealistic jumps, driving normal vehicles up extreme terrain, or repeatedly treating major crashes as meaningless is FailRP.

4.2 Firearm & Equipment Realism

Large weapons and equipment must be retrieved or carried realistically. Rifles, shotguns, shields, breaching equipment, and similar items should not appear from nowhere. Use weapons in a manner consistent with the scene. A minor disagreement should not instantly become a shootout without believable escalation.

4.3 Injury Roleplay

Serious crashes, shootings, falls, assaults, and other major injuries must have reasonable roleplay consequences. Injury roleplay should reflect the severity and location of the injury without requiring medical-level simulation.

4.4 FearRP / Value of Life

Characters must reasonably value their lives. Being heavily outnumbered or held at gunpoint should affect decision-making. FearRP does not require automatic surrender in every situation, but intentionally acting as though serious danger does not exist may be FailRP.

4.5 Scene Conduct

Do not crowd, hijack, or insert yourself into active scenes without a legitimate roleplay reason. Do not hunt active scenes solely for clips, gunfights, pursuits, or attention.

5.1 Voice Conduct

Keep voice communication understandable and reasonably controlled. Mic spam, ear rape, repeated soundboard abuse, intentional voice disruption, and excessive screaming intended to annoy others are prohibited.

5.2 In-Game / Discord Separation

Do not use Discord voice communication to bypass in-game radio or proximity systems during active roleplay. If you are in a Discord voice channel while actively playing, avoid transmitting in-game conversations into Discord in a way that creates metagaming.

5.3 Discord Channels

Use channels for their intended purpose. Do not spam mentions, abuse ticket systems, flood channels, impersonate staff, or intentionally create community drama.

5.4 Department Communications

Whitelisted department radios and official department channels should remain professional enough to support active operations. Department leadership may set additional radio and communication standards.

6.1 Priority Scenes

Priority scenes are major incidents that require focused emergency-service attention, such as shootings, hostage situations, major robberies, or significant manhunts. Members must follow the active priority system and any cooldown shown by the server.

6.2 Priority Abuse

Do not intentionally chain major violent scenes, interrupt another active priority, ignore cooldowns, or escalate minor situations solely to create a priority.

6.3 Area of Patrol (AOP)

When an AOP is active, members should keep primary roleplay within the announced area unless a scene naturally moves outside it or staff authorizes otherwise. Only authorized staff may make an official AOP change.

7.1 Open Civilian Access

Civilian roleplay is open. Members may join and roleplay as civilians without joining a law enforcement department, subject to Project 713 age/access requirements and community rules.

Open civilian access does not mean unrestricted roleplay. Civilians are held to the same realism, conduct, priority, and scene-quality standards as every other member.

7.2 Criminal Roleplay

Criminal roleplay should be story-driven and believable. Avoid nonstop violent crime, repetitive cop-baiting, robbery spam, intentionally forcing pursuits, or treating every police interaction as a reason to flee or shoot.

7.3 Civilian Vehicles & Characters

Civilian vehicles and characters should fit the intended realism of Project 713. Staff may stop or remove meme vehicles, immersion-breaking liveries, intentionally troll characters, or unrealistic vehicle setups that materially disrupt roleplay.

7.4 Emergency-Service Impersonation

Open civilians may not represent themselves as an active Project 713 law enforcement officer, firefighter, EMS member, or other whitelisted public-safety member unless they are authorized for that role. Civilian characters may portray lawful private-sector or fictional roles when they do not falsely claim whitelisted department authority.

8.1 Whitelist Requirement

All Project 713 law enforcement departments are whitelisted. A player must be accepted, trained, and authorized by the applicable department before going on duty as that department.

Possessing a uniform, vehicle, callsign, or EUP item does not grant department membership or authority.

8.2 Department Applications

New applicants must use the department's official application and onboarding process unless they qualify for an approved department transfer under Section 9.

8.3 Professional Conduct

Law enforcement members must maintain reasonable professionalism while on duty, follow lawful roleplay procedure, and avoid abusing department tools, weapons, vehicles, permissions, or authority.

8.4 Use of Force

Force must be reasonably connected to the threat and circumstances presented in roleplay. Excessive, punitive, or clearly unrealistic force is prohibited. Department-specific use-of-force policies may be more restrictive.

8.5 Pursuits

Pursuits must balance realism, public safety, and the seriousness of the offense. Supervisors may terminate unsafe or unrealistic pursuits. Unit limits, intervention techniques, and pursuit tactics may be established by each department's SOP.

8.6 Corruption & Abuse

Unauthorized corruption, evidence planting, intentionally false arrests, personal targeting, or misuse of police powers is prohibited. Any approved corruption storyline must have explicit authorization from the appropriate Project 713 authority before it begins.

9.1 Department Transfers

A member in good standing may submit a department transfer request to move from one Project 713 whitelisted law enforcement department to another. An approved transfer request replaces the need to submit a brand-new department application unless the receiving department or Project 713 Management requires one for a specific reason.

Transfers are not automatic. The receiving department may review disciplinary history, activity, training status, qualifications, and available staffing before accepting the request.

9.2 Rank Reset on Transfer

ALL DEPARTMENT TRANSFERS START FROM THE BOTTOM OF THE RECEIVING DEPARTMENT'S RANK STRUCTURE. Previous Project 713 rank, command status, certifications, staff rank, friendship, donation status, or rank held in another community does not entitle a member to an equivalent or elevated rank in the receiving department.

Example: a Lieutenant transferring from one department does not transfer into another department as a Lieutenant. The member begins at the receiving department's entry rank and earns advancement through that department.

9.3 Training & Certifications After Transfer

A receiving department may recognize prior knowledge to streamline training, but it is not required to recognize certifications, supervisor status, specialty assignments, or command qualifications. Department leadership determines what must be retrained or re-certified.

9.4 Promotions & Free Ranking

Ranks must be earned through the receiving department's established process. Free ranking, favoritism, or granting command positions solely because of a member's previous department rank, staff position, friendship, relationship, donation, or outside-community status is prohibited.

Project 713 Ownership may make organizational appointments when necessary to establish or rebuild a department; such appointments are administrative exceptions, not member transfer privileges.

9.5 Department SOP Authority

Department leadership controls internal training, promotions, certifications, subdivisions, scheduling, and operational policies within the limits of Project 713 rules. No department policy may override these Global SOPs.

10.1 Access

If Project 713 operates a whitelisted Fire/EMS department, only authorized members may represent that department on duty. If Fire/EMS is not staffed, civilians and law enforcement should roleplay medical outcomes reasonably within available server mechanics.

10.2 Scene Conduct

Fire/EMS personnel must coordinate with law enforcement when scenes are unsafe, maintain reasonable scene safety, and provide professional medical/fire roleplay.

11.1 Safe Zones

Staff may designate spawn areas, training locations, official event areas, or other locations as temporary or permanent safe zones. Unless an event specifically allows otherwise, hostile actions, theft, trolling, and violence are prohibited inside an active safe zone.

11.2 Official Events

Members must follow event-specific instructions. Deliberately disrupting memorials, ceremonies, trainings, community events, or staff-managed scenes may receive elevated punishment depending on severity and intent.

12.1 Staff Authority

Staff may intervene when conduct harms roleplay, community safety, server stability, or fair play even if the exact behavior is not listed word-for-word in this document. Staff should apply the closest applicable rule and consider context.

12.2 Administrative Actions

Possible actions include verbal direction, warnings, kicks, temporary bans, permanent bans, department discipline referrals, whitelist removal, or other reasonable restrictions.

Punishment is based on severity, intent, prior history, impact, cooperation, and whether the conduct was repeated. Project 713 does not guarantee a fixed punishment ladder for every violation.

12.3 Serious Violations

Cheating, malicious exploitation, doxxing, credible threats, severe harassment, ban evasion, or deliberate attacks on Project 713 infrastructure may result in immediate permanent removal.

12.4 Staff Discretion & Consistency

Staff decisions during an active situation must be followed. A decision may later be reviewed through the appeal process. Staff members are also subject to Project 713 rules and may be reviewed for misuse of authority.

13.1 Appeal Process

Members may appeal eligible punishments through the official Project 713 support or appeal system. Appeals should explain what occurred, identify the action being appealed, and include relevant evidence when available.

13.2 Appeal Conduct

Appeals must remain truthful and respectful. Fabricated evidence, harassment, spam appeals, or attempts to pressure staff may result in denial or additional administrative action.

14.1 Rule Interpretation

Project 713 rules are intended to protect realistic, fair, and enjoyable roleplay rather than provide loopholes. Staff may interpret unclear situations according to the purpose of these standards.

14.2 Updates

Project 713 may revise these Global SOPs as the community grows. The current published version supersedes prior Project 713 global rule documents.

This document is written specifically for Project 713. Policies from Coastal State Roleplay (CSRP) or any other community are not Project 713 policy unless they are separately adopted and published by Project 713.

14.3 Fictional Use

Project 713 is a fictional roleplay community operating within Grand Theft Auto V / FiveM. These procedures are for game and community use and are not intended as real-world legal, law-enforcement, medical, or emergency-services guidance.