Project Western · Server Standards

Rules

This handbook defines the standard of roleplay expected on Project Western. The goal is not hundreds of technical rules; it is a shared style of play where characters behave like people, scenes have consequences, and everyone contributes to believable stories.

Character FirstStay In CharacterValue ConsequencesNo Livestreaming

The Standard

The server is designed around serious, character-first roleplay. Players are expected to act in ways that make sense for their character, the situation, and the world around them. Winning a scene is never more important than making the scene believable.

Stay in character while actively participating in the server.

Treat injury, danger, arrest, loss, fear, and death as meaningful events.

Do not use game mechanics, outside information, or technical loopholes to gain an advantage.

Give other players reasonable opportunities to react, speak, investigate, negotiate, and roleplay.

Keep conflict between characters. Do not turn character conflict into player conflict.

Accept that realistic roleplay sometimes means losing money, property, freedom, status, or a confrontation.

This handbook is intentionally written around standards rather than endless edge-case rules. Staff may intervene when conduct clearly violates the spirit of immersive roleplay even if the exact situation is not described word-for-word below.

01
Section 01

Core Roleplay Standard

Every player is responsible for protecting immersion, even when nobody from staff is watching.

Character-first decisions

Your character should have motivations, limitations, habits, relationships, fears, and consequences. Avoid treating the character as a disposable avatar used only to access weapons, vehicles, or combat.

Actions should be based on what your character knows, not what you know as a player.

Roleplay should develop naturally. Do not force every encounter into a shooting, chase, robbery, arrest, or staff situation.

You may play bold, reckless, criminal, rude, corrupt, scared, inexperienced, or unstable characters, but the portrayal still needs internal logic and believable consequences.

Quality over “winning”

Being arrested, injured, robbed, outnumbered, exposed, or forced to retreat is not a failed roleplay scene.

Do not stall, disconnect, exploit mechanics, or invent last-second information simply to avoid losing a scene.

Players who consistently create good scenes for others will always be valued more than players who simply accumulate wins.

02
Section 02

In-Character / Out-Of-Character Separation

Once you are actively playing your character, the world should remain in character unless there is a genuine technical or staff necessity.

In-character communication

Use normal character dialogue for all conversations that can reasonably be handled in roleplay.

Do not discuss Discord, staff tickets, rule numbers, clips, keybinds, menus, respawns, texture loss, FPS, crashes, or other game terminology in ordinary character conversation.

Do not say things such as “I am going to report you,” “that is RDM,” “check the bodycam clip,” or “my game is lagging” while a scene is active. Finish the scene, then handle the issue through the proper channel.

If a technical problem makes roleplay impossible, keep OOC communication brief and return to character as soon as possible.

OOC conflict stays OOC

Do not use your character to retaliate against someone because of a Discord disagreement, staff report, previous argument, or personal dislike.

Do not carry IC hostility into DMs, voice channels, tickets, or public chat as player-to-player harassment.

Do not coordinate IC actions through unauthorized OOC channels.

03
Section 03

Voice, Communication & Streaming

Communication should preserve immersion and prevent outside audiences or information from shaping active scenes.

Voice standard

Use proximity voice, radio systems, telephones, dispatch tools, or other approved in-world communication methods when available.

Avoid unnecessary background noise, soundboards, music spam, voice changers that destroy intelligibility, or deliberately disruptive microphone use.

Do not remain in external voice calls with players who are participating in the same active scene unless the call is being used solely for approved server operations and no IC information is exchanged.

No livestreaming

Livestreaming server gameplay is prohibited while connected to the server, spectating server scenes, or participating in server-related voice communications.

Do not broadcast active scenes through Twitch, YouTube, TikTok Live, Discord screen share, Kick, or similar live platforms.

The purpose of this restriction is to protect player privacy, prevent stream-sniping or outside information, and allow serious roleplay to happen without an external audience influencing behavior.

Locally recorded clips may be retained for staff reports, personal review, or approved edited content, provided they are not used to harass, expose private staff information, or bypass server privacy expectations.

04
Section 04

Character Creation & Continuity

Characters should feel persistent. Their history, injuries, relationships, employment, reputation, and prior decisions matter.

Complete and verify your CAD character profile before joining the server for the first time and before playing any newly created character.

Your in-game character information must reasonably match the character represented in CAD. Keep the record updated when major character information changes.

Use a believable name and character concept appropriate to the setting.

Do not create joke characters, celebrity copies, meme identities, or intentionally immersion-breaking appearances for serious scenes.

A character should not completely change personality, profession, allegiance, criminal history, or relationships from scene to scene merely because it is convenient.

Characters may grow or change over time, but major changes should have an in-character reason.

Do not create alternate characters solely to transfer information, money, property, revenge, or influence between stories.

When changing factions, careers, gangs, or departments, respect any applicable cooldowns, training requirements, and continuity expectations.

Character knowledge

Your character only knows what they have personally observed, been told in character, or can reasonably access through approved in-world systems.

Names above heads, Discord roles, player lists, map markers, staff messages, streams, clips, and OOC conversations are not character knowledge.

05
Section 05

Fear, Survival & Value Of Life

Characters should behave as though injury, imprisonment, and death are serious possibilities.

When a credible weapon is aimed at your character and you do not have a realistic advantage, show appropriate fear and caution.

Being armed does not automatically give you a believable reason to fight several people, rush a gunman at close range, or ignore a hostage situation.

Consider numbers, distance, cover, surprise, injuries, available escape routes, and the character’s personality before deciding to resist.

You are not required to play a coward. You are required to make decisions that acknowledge risk.

Suicidal actions performed only to avoid arrest, inventory loss, questioning, or roleplay consequences are not acceptable.

06
Section 06

Injuries, Medical Roleplay & Recovery

Damage is not just a health bar. Injuries should influence what your character can reasonably do.

Roleplay the severity and location of meaningful injuries. A gunshot, stabbing, severe collision, fall, or repeated taser exposure should affect movement and decision-making.

Do not sprint, fight, climb, drive aggressively, or immediately resume combat after severe injuries unless the circumstances make that believable.

Allow EMS and medical personnel reasonable opportunities to assess and treat you.

Do not dictate exact medical outcomes to other players. Describe symptoms and injuries; let qualified medical roleplay develop naturally.

After major treatment, consider a realistic recovery period rather than instantly returning to the exact conflict that caused the injury.

Medical cooperation

You may refuse treatment in character when reasonable, but refusal does not erase the injury.

Unconscious or incapacitated characters should not provide tactical callouts, detailed descriptions, or other information they could not realistically communicate.

07
Section 07

Death, Incapacitation & Scene Memory

Downed and deceased states must be treated as part of the story, not as a temporary loading screen. Every character has a maximum of two lives.

Two-Life Character System

First death: The first time your character dies, one life is consumed. The character may continue, but the death must remain part of their history. You must establish a believable survival outcome, such as being recovered by EMS, transported to a hospital, undergoing emergency treatment, and later being discharged after recovery.

If your character previously died from a shooting, stabbing, serious crash, or similar incident, you may not later act as though it never happened. If the event is discussed, your character should explain that they survived after medical intervention, hospitalization, or another believable in-character outcome.

Second death: The second time that same character dies, the death is permanent. That character may no longer be used and must be deleted. You must create a new character before returning to normal roleplay.

Before retiring or deleting a permanently deceased character, the character's MDT record must be updated to Deceased. A character may only be marked Missing when the roleplay legitimately supports an unresolved disappearance or the character's fate is not known in character.

A character's life count does not reset by changing their name, appearance, job, department, faction, or by temporarily shelving the character. The two-life limit follows that character for their entire story.

A replacement character must be treated as a genuinely new person. Do not transfer the deceased character's memories, relationships, grudges, property, criminal knowledge, or other information simply to continue the same story under a different name.

Incapacitation and Scene Conduct

When incapacitated, do not continue normal conversation, give live tactical intelligence, use outside communications, or manipulate the scene through OOC messages.

If revived, continue roleplaying injuries and confusion where appropriate.

When a character’s death is treated as permanent or a new-life event under server systems, do not immediately return with perfect memory to retaliate or recover property.

Do not repeatedly return to an active scene after being removed from it by death, hospitalization, arrest, or staff direction.

Never disconnect because your character has been killed or incapacitated in order to prevent a lawful or roleplay-appropriate search, robbery, evidence recovery, arrest, or inventory consequence.

08
Section 08

Crime, Escalation & Criminal Roleplay

Criminal roleplay should create tension and investigation, not endless random violence.

Have an in-character purpose for serious crimes. Money, revenge, intimidation, territorial conflict, desperation, organized crime, and opportunity can all be valid when developed properly.

Do not repeatedly rob, kidnap, attack, or provoke random players with little or no roleplay simply because the game allows it.

Escalate conflict naturally. Verbal hostility does not automatically justify lethal force.

Give victims a reasonable opportunity to understand demands and comply when the scene allows it.

Do not manufacture hostage scenes with friends or alternate characters solely to force police into a payout or mechanical advantage.

Criminals should account for witnesses, cameras, plates, fingerprints, injuries, police response, surveillance, and later investigation.

Hostages and kidnapping

Kidnapping should have a narrative purpose and should not be used to trap someone in an excessively long scene without meaningful interaction.

Hostages must be treated as actual leverage and actual human beings. Unnecessary execution with no escalation or story value may be treated as poor roleplay.

Hostage takers should communicate demands clearly and allow reasonable negotiation when police are involved.

09
Section 09

Robbery, Searching & Property Loss

Property loss is an intentional part of consequence-driven roleplay, but it must be handled reasonably.

Robberies require believable interaction. Do not silently empty inventories without roleplay when the target is conscious and available to interact.

Only take items that make sense for the scene and server economy. Do not use robbery mechanics primarily to grief or wipe another player’s progress.

Law enforcement searches should be tied to a lawful or roleplay-supported basis within the server’s legal framework.

Players must not disconnect, transfer items, hide property through alternate characters, exploit storage, or intentionally die to prevent an otherwise valid search or seizure.

If an inventory search is occurring, the searched player should not use inventory mechanics to move, drop, consume, stash, or destroy items to defeat the search.

10
Section 10

Firearms, Combat & Use Of Force

Weapons are serious tools in the world. Pulling one should materially change the scene.

Do not shoot without a believable reason and sufficient escalation.

Do not fire at people merely because they insulted you, bumped your vehicle, ran near you, or annoyed you.

Warning shots, blind firing, indiscriminate spraying, shooting through crowds, and intentionally unrealistic gunplay may be treated as fail roleplay.

Use cover, distance, communication, surrender, retreat, and negotiation when those options make sense.

Do not exploit third-person camera angles, desync, animation states, interiors, or other mechanics to shoot or observe in ways your character could not reasonably accomplish.

After a major shooting, allow the aftermath to exist: injuries, witnesses, medical response, evidence, police investigation, fear, and consequences.

Random and vehicle-based violence

Random Deathmatch (RDM) and Vehicle Deathmatch (VDM) are not acceptable substitutes for roleplay.

A vehicle may be used as a weapon only where the character has a believable reason and the circumstances support that level of force. Accidental collisions should be roleplayed as accidents, not instantly converted into gunfights.

11
Section 11

Vehicles, Pursuits & Road Behavior

Driving should reflect the character, vehicle, road, traffic, weather, and stakes of the scene.

Routine driving should be reasonably believable. Constantly driving at maximum speed, jumping curbs, launching over terrain, or ignoring collisions without a scene-based reason breaks immersion.

High-performance driving is appropriate during emergencies, pursuits, races, escapes, or other developed scenes, but vehicle limitations still matter.

Do not take vehicles through terrain, gaps, jumps, stairs, barriers, or water merely because the game physics allow it when the real vehicle could not reasonably do so.

Crashes should matter. A major impact may require slowing down, stopping, roleplaying injuries, disabling the vehicle, or waiting for assistance.

Police and suspects should avoid “win at any cost” pursuit behavior. The goal is a believable chase, not abusing physics until one side loses.

12
Section 12

Law Enforcement Roleplay

Law enforcement characters carry authority and therefore have a higher responsibility to create fair, believable scenes.

Use communication, de-escalation, commands, positioning, backup, and investigation before force when practical.

An arrest should be supported by the facts your character has. Do not use OOC knowledge, player reputation, Discord history, or assumptions as probable cause.

Searches, seizures, detentions, warrants, and charges should follow the server’s legal framework and department policy where applicable.

Officers should articulate what they are doing. Give detained players enough information to understand the scene without turning every stop into a courtroom debate.

Use force proportionally. A disrespectful or fleeing suspect does not automatically justify lethal force.

Do not intentionally prolong detention, stack absurd charges, seize irrelevant property, or use police mechanics to punish a player OOC.

Police corruption, misconduct, or rogue behavior requires server/department approval when it could substantially affect other players or undermine the department structure.

Investigations

Treat evidence as meaningful. Witness statements, video, fingerprints, DNA, casings, plates, vehicle damage, clothing, timelines, and phone records should be handled as information, not magical certainty.

Allow suspects and attorneys reasonable opportunities to speak. Good police roleplay is not measured only by arrests; it is measured by the quality of the investigation and scene.

13
Section 13

Civilian Roleplay

Civilian characters are the foundation of the world. You do not need to be a criminal or police officer to create meaningful roleplay.

Create jobs, businesses, social groups, relationships, disputes, hobbies, local events, accidents, emergencies, and everyday interactions.

Do not treat civilian gameplay as downtime between shootouts. The strongest worlds feel alive even when no crime is happening.

Use realistic reactions to police activity, shootings, crashes, fires, severe injuries, and dangerous scenes.

Do not swarm emergency scenes simply because you saw activity on the map or heard about it OOC.

When portraying a professional occupation, make a reasonable effort to understand the basics of that role without turning it into a rigid simulation requirement.

14
Section 14

Factions, Gangs & Organized Groups

Organized groups should generate long-term stories, not function as permanent combat teams.

Faction loyalty, transfers, alliances, rivalries, promotions, and leadership decisions should be treated as meaningful character events.

Do not faction-hop to chase whichever group is currently winning, active, or better equipped.

Group conflicts should develop through identifiable causes and escalation. Avoid declaring endless wars over trivial incidents.

Do not use faction Discord channels to live-feed information your characters could not reasonably communicate in game.

Leadership is responsible for the culture of the group. Encouraging repeated rule-adjacent behavior may result in group-level administrative action.

When a faction transfer policy exists, its BCT, time-in-unit, leadership approval, and cooldown requirements apply in addition to this handbook.

15
Section 15

Sensitive, Offensive & Mature In-Character Content

Serious roleplay may include characters who are rude, prejudiced, hostile, criminal, offensive, or morally objectionable. The distinction between character portrayal and player harassment must remain clear.

In-character offensive language

Derogatory, discriminatory, or offensive language, including slurs, may only be used in a clearly in-character context where it serves the scene or character portrayal rather than the player’s OOC hostility.

Such language may never be used to target, intimidate, harass, or demean another player outside of roleplay, in tickets, DMs, staff discussions, public OOC channels, or after a player has made clear the scene is crossing into real-world harassment.

Do not spam offensive language, use it as shock content, or make it the entire identity of a character. Context, restraint, and narrative relevance matter.

Never use roleplay as a shield for targeted OOC harassment or coordinated abuse.

All content remains subject to the rules and terms of the platforms and services the server uses. A server rule cannot override platform-level restrictions.

Sexual and excessively graphic content

Do not force sexual, sexually humiliating, or graphically intimate roleplay onto another player.

Any mature relationship roleplay must be consensual between the involved players and remain within applicable platform and community requirements.

Graphic torture, hate content, or other extreme material should never be sprung on an unwilling player merely for shock value.

16
Section 16

Metagaming, Powergaming & Information Abuse

Immersion depends on characters acting only on information and abilities they actually possess.

Metagaming

Do not use Discord messages, streams, clips, player lists, staff tools, map knowledge, alternate characters, or another player’s screen to locate or identify people in character.

Do not recognize masked or disguised characters solely by voice, username, clothing habits, or OOC familiarity unless the recognition is genuinely reasonable in context.

Do not return to a scene because someone told you what happened through an unauthorized OOC channel.

Powergaming

Do not force actions or outcomes on another player without giving them a reasonable opportunity to respond.

Do not claim impossible abilities, invisible equipment, nonexistent evidence, or guaranteed outcomes simply to win a scene.

Use /me, /do, emotes, animations, and server mechanics to describe or support roleplay, not to unilaterally dictate another character’s injuries, emotions, knowledge, or actions.

17
Section 17

Exploits, Mechanics & Unrealistic Advantages

If a mechanic creates an obviously unrealistic advantage, using it intentionally may still violate the roleplay standard even if the game technically permits it.

Do not exploit animation cancels, hitboxes, camera angles, collision, invulnerability, interior loading, desync, inventory timing, reconnect behavior, or other technical quirks for an advantage.

Do not abuse character switching, relogging, respawning, storage, garages, impounds, or inventories to escape an active consequence.

Do not intentionally duplicate, hide, transfer, or destroy items through bugs or unintended mechanics.

If you discover an exploitable issue, stop using it and report it privately to staff. Repeated use after discovering the issue may be treated more severely.

18
Section 18

Scene Etiquette & Continuity

Strong roleplay requires giving scenes room to develop.

Do not interrupt an active scene solely to troll, provoke a shootout, steal attention, or create chaos with no connection to the story.

Give players enough time to respond to commands, questions, medical treatment, negotiations, searches, and major actions.

Do not talk over everyone simply to control the scene. Use radio discipline and allow relevant parties to speak.

When entering an existing scene, take a moment to understand what is happening before acting.

After a scene, carry forward reasonable consequences. Injuries, damaged property, warrants, relationships, debts, arrests, and reputation should not vanish because the immediate excitement ended.

Leaving the server

Do not disconnect during an active interaction, pursuit, arrest, medical scene, robbery, search, or confrontation to avoid the outcome.

If you crash, make a reasonable effort to return and continue the scene when possible. If returning is impossible, notify the appropriate party or staff channel when practical.

Logging out after a scene has clearly concluded is normal. Logging out because the scene is going badly is not.

19
Section 19

Staff Interaction, Reports & Evidence

Staff exist to resolve problems without replacing normal roleplay.

Do not summon staff in the middle of every disagreement. Finish the scene when reasonably possible and report afterward.

Use reports for genuine rule or technical concerns, not as leverage to win an IC dispute.

Provide clear evidence when available: timestamps, player IDs, names, clips, screenshots, and a concise description of what occurred.

Do not edit clips in a misleading way, omit critical context, fabricate evidence, or coordinate false reports.

Follow staff direction during an active review. Arguing endlessly in scene or continuing the disputed behavior can create additional problems.

Staff decisions may consider the totality of the scene, prior behavior, intent, severity, and whether the player made a good-faith effort to roleplay.

20
Section 20

Enforcement & Administrative Outcomes

Enforcement is intended to protect the quality of the server, not to turn every mistake into a permanent punishment.

Possible outcomes

Verbal coaching or documented warning for minor or first-time issues.

Strikes for clear or repeated violations of the server standard.

Inventory, money, vehicle, item, or scene rollback when an exploit or disconnect was used to preserve an advantage.

Character consequences, character wipe, faction removal, department discipline, or role restrictions when the violation is tied to a specific character or position.

Temporary suspension for serious or repeated behavior.

Permanent removal for severe abuse, cheating, targeted harassment, repeated bad-faith conduct, or conduct that makes continued participation incompatible with the community.

Staff discretion

Not every situation can be reduced to a checklist. Staff may consider context, intent, severity, prior history, cooperation, and the effect on other players. Technical loopholes are not exemptions from the underlying standard.

21
Section 21

Quick Reference: What Good Rp Looks Like

The best way to understand the server standard is to see how it changes everyday decisions.

SituationImmersive responsePoor response
Before you connectMake sure your active character is fully created and correctly set up in CAD.Join with no CAD record, placeholder information, or an incomplete profile.
Your character dies for the first timeCount the first life, establish believable hospital treatment or recovery, and keep the incident as part of the character's history.Return and pretend the death, shooting, or other fatal incident never happened.
Your character dies for the second timeMake the death permanent, update the MDT to Deceased or legitimately Missing, delete the character, and create a new one.Continue playing the same character, reset their life count, or recreate them under a slightly different identity.
You lose a gunfightRoleplay injuries, allow the scene to continue, accept search/medical consequences.Disconnect, respawn to save items, or immediately return for revenge.
Police stop your vehicleRoleplay the stop, respond as your character, challenge the officer through IC methods.Argue rule terminology, threaten reports, or use Discord information.
Someone insults your characterRespond verbally, walk away, escalate proportionally if the story supports it.Instantly shoot or run them over.
Your car crashes at high speedAcknowledge the impact, injuries, damage, and loss of control.Continue at full speed as though nothing happened.
You hear scene information in DiscordIgnore it unless your character independently learns it in game.Drive directly to the location or act on the information.
Your character is searchedAllow the search and accept legitimate discovery of carried items.Move, stash, delete, transfer, or disconnect to protect inventory.
You want to portray an offensive characterUse restraint, context, and keep all hostility strictly IC.Spam slurs, target a player personally, or continue into OOC harassment.
A scene goes against youLet the loss create the next chapter of your character’s story.Treat the server like a competitive match that must be won.

Acknowledgment

By playing on the server, a player acknowledges that they are expected to understand and follow the standards in this handbook, applicable department/faction policies, and the terms of the platforms used by the community. Claiming not to have read the handbook does not automatically excuse conduct that clearly violates the server standard.

Acknowledgment

Playing means accepting the standard.

By playing on Project Western, you acknowledge that you are expected to understand and follow these standards, applicable department or faction policies, and the terms of the platforms used by the community. Not reading the handbook does not automatically excuse conduct that clearly violates the server standard.

Continue to Start Here
Ready to join?Read the standards, build a believable character, and start your Project Western story.