OOC
SERVER WEBSITERules, applications, joining information, support, and store details are out of character. Public IC information is published through the City Network.
Enter the City Network →
OOC SERVER RULES // Starter Rules Edition 1.0

PROTECT THE STORY.
RESPECT THE PEOPLE.

61 editable starter rules covering community conduct, serious roleplay, characters, crime, vehicles, businesses, departments, staff, Discord, and content.

Development edition: These are complete example rules, not automatically the final NightShift policy. Review wording, cooldowns, script-specific rules, enforcement standards, and appeal procedures before launch. IC laws are published separately through DOJ.

Community 7 rules

1.1

Respect the Community

Treat players, staff, creators, and guests with basic respect. Harassment, hate speech, threats, targeted humiliation, and discriminatory conduct are not accepted.

Examples and clarification

Disagreement about a scene is allowed. Attacking the person behind the character is not.

1.2

No Hate or Extremist Content

Slurs, hateful stereotypes, extremist propaganda, or content designed to target a protected group are prohibited in game, Discord, streams, names, clothing, businesses, and profiles.

Examples and clarification

An IC villain does not excuse OOC hate speech.

1.3

No Sexual Harassment or Forced Sexual RP

Sexual roleplay requires clear consent from everyone involved. Sexual harassment, coercive sexual content, or sexual content involving minors is prohibited.

Examples and clarification

Stop immediately when another participant withdraws consent.

1.4

Protect Personal Information

Do not expose, threaten to expose, or misuse another person's private information.

Examples and clarification

Doxxing, sharing private photos, or attempting to identify a player outside the community is prohibited.

1.5

No Cheating or Exploiting

Cheats, injectors, macros that create unfair automation, duplication, exploiting, and knowingly benefiting from a bug are prohibited.

Examples and clarification

Report an exploit privately. Do not demonstrate it publicly or distribute instructions.

1.6

No Ban Evasion

Do not use alternate accounts, identifiers, VPNs, or other methods to avoid a suspension or ban.

Examples and clarification

Appeal through the official process.

1.7

Follow Platform and Asset Rules

Players must follow Cfx.re, Rockstar, Discord, and NightShift content requirements.

Examples and clarification

Unauthorized copyrighted assets, malicious files, or prohibited content may be removed.

Roleplay 12 rules

2.1

Remain In Character

Stay in character during active scenes unless staff pauses the scene or an emergency requires OOC communication.

Examples and clarification

Use brief neutral wording for technical issues rather than arguing OOC in voice.

2.2

No Metagaming

Do not use information your character did not learn through roleplay.

Examples and clarification

Discord messages, streams, name tags, map markers, and another character's perspective are not automatically IC knowledge.

2.3

No Powergaming

Do not force actions or outcomes that remove another player's reasonable ability to respond.

Examples and clarification

Use attempts and describe actions instead of declaring that another character is restrained, searched, or injured without interaction.

2.4

No Fail RP

Respond believably to the world, injuries, threats, authority, and established circumstances.

Examples and clarification

Ignoring a serious crash, immediately returning to danger after treatment, or acting unaffected by severe injury may be fail RP.

2.5

Value Life and Consequences

Characters should respond believably when facing a credible threat to life or serious loss.

Examples and clarification

Being outnumbered at gunpoint normally requires compliance unless the scene creates a reasonable opportunity.

2.6

No Random Deathmatch

Violence requires roleplay context, escalation, and a reasonable opportunity for participants to understand the conflict.

Examples and clarification

A prior disagreement does not create permanent permission to shoot on sight.

2.7

No Vehicle Deathmatch

Do not use a vehicle as a weapon without strong scene-based justification.

Examples and clarification

Accidental collisions should be roleplayed. Repeatedly striking people with a car to win a fight is prohibited.

2.8

Fear and Injury RP

Roleplay injuries according to their cause and severity. Allow EMS and other players to create a meaningful scene.

Examples and clarification

A gunshot, major collision, or fall should affect movement, decisions, and recovery.

2.9

New Life and Memory

After a character is declared dead or respawns under the server's new-life rules, do not immediately return to the scene or use information your character should no longer remember.

Examples and clarification

Final memory rules and cooldowns must be matched to the selected medical script.

2.10

No Scene Griefing

Do not intentionally interrupt, troll, bait, or derail scenes for attention.

Examples and clarification

Driving through an organized event, repeatedly provoking a scene with no character motive, or spamming audio can be griefing.

2.11

Roleplay Before Reports

Complete the scene when reasonably possible, then use evidence and the report process.

Examples and clarification

Staff may intervene immediately for cheating, severe harassment, or a scene that cannot safely continue.

2.12

Character Separation

Your characters may not share knowledge, money, property, criminal contacts, or coordinated plans without legitimate RP.

Examples and clarification

Using one character to discover information for another is prohibited.

Characters 5 rules

3.1

Believable Character Names

Use a believable first and last name appropriate for the setting.

Examples and clarification

Meme names, celebrity copies, slurs, and names designed only as jokes may be rejected.

3.2

One Character, One Story

Keep each character's relationships, knowledge, assets, and affiliations separate.

Examples and clarification

Characters on the same account cannot act as convenient messengers or asset holders for one another.

3.3

No Unrealistic Backstories

Backstories cannot grant automatic authority, wealth, criminal power, military expertise, or relationships with established characters.

Examples and clarification

A background may inspire RP, but skills and influence must be demonstrated in the city.

3.4

Character Death Requires Care

Permanent character death must follow the server's approved process and should not be used to avoid debts, charges, or consequences.

Examples and clarification

Staff may require resolution of active matters before approving a permanent death.

3.5

Name and Identity Changes

Identity changes must use the approved process and cannot erase active legal or RP consequences.

Examples and clarification

A cosmetic name change does not automatically remove warrants, debts, or known relationships.

Crime and Conflict 10 rules

4.1

Conflict Requires Development

Major violence, wars, kidnappings, and repeated targeting require a clear RP foundation.

Examples and clarification

Use demands, negotiations, meetings, warnings, evidence, and consequences to build conflict.

4.2

No Immediate Escalation to Gunplay

Use proportionate escalation. Not every insult, traffic collision, or business dispute justifies lethal force.

Examples and clarification

Verbal conflict can lead to threats, fights, legal action, or future scenes before firearms.

4.3

Robbery RP Must Be Interactive

Robberies must provide interaction and cannot be used only to strip every item from another player.

Examples and clarification

Give clear demands, reasonable time to respond, and a story-driven reason for the robbery.

4.4

No Chain Robbing

Do not repeatedly rob random players or target the same person without meaningful story development.

Examples and clarification

Cooldowns and value limits may be added after economy testing.

4.5

Hostage Standards

Hostages must be real participants and treated as part of the scene, not disposable mechanics.

Examples and clarification

No fake hostages, alternate-account hostages, or prearranged hostages used only to trigger a robbery.

4.6

Kidnapping Must Create RP

Kidnapping requires a reason, meaningful interaction, and a plan that allows the scene to progress.

Examples and clarification

Do not hold a player for an excessive period without engagement or a clear objective.

4.7

No Forced Asset Transfers

Do not force players to transfer houses, businesses, entire bank accounts, or protected assets through threats unless a specific approved system allows it.

Examples and clarification

Normal robbery limits and staff-approved storyline terms apply.

4.8

Faction Conflict Is Not Arena Combat

Faction disputes should involve claims, business, reputation, supply, diplomacy, or other RP interests.

Examples and clarification

Scheduled deathmatching with no city consequence does not meet the NightShift standard.

4.9

Police and EMS Are Part of the Scene

Do not treat public departments as NPC obstacles. Give them information, negotiation, evidence, and decisions to work with.

Examples and clarification

Repeatedly baiting police only to start a chase is low-quality RP.

4.10

No Combat Logging

Do not disconnect, respawn, or use technical systems to escape an active scene or consequence.

Examples and clarification

Reconnect and contact staff if a genuine crash occurs.

Vehicles and Racing 5 rules

5.1

Drive for the Situation

Normal traffic, public areas, and crowded events require believable driving.

Examples and clarification

Extreme speeds and dangerous manoeuvres should fit a chase, race, emergency, or character reason.

5.2

Respect Vehicle Limitations

Do not drive ordinary vehicles as if they are indestructible off-road machines.

Examples and clarification

Vehicle class, damage, terrain, and collision severity should affect behaviour.

5.3

Racing Requires Structure

Organized racing should use approved routes, registration, safety rules, and event procedures where available.

Examples and clarification

Public races may create police, EMS, news, betting, sponsorship, and business RP.

5.4

No Vehicle Storage Exploits

Do not use trunks, garages, transfers, or vehicle systems to duplicate, hide, or bypass restrictions.

Examples and clarification

Report script issues privately.

5.5

No Unrealistic Repairs

Major damage should require appropriate repair RP and cannot be ignored by rapidly storing or respawning a vehicle.

Examples and clarification

Mechanics should be used when available.

Businesses and Economy 6 rules

6.1

Businesses Must Create Public RP

Owners are expected to operate, hire, train staff, advertise, and create reasons for residents to visit.

Examples and clarification

Inactive ownership may be reviewed or reclaimed under the business policy.

6.2

Use IC Systems for Upgrades

Branding, upgrades, inventory, advertising, staffing, and expansion are handled through the city economy and approved RP processes.

Examples and clarification

Do not bypass business RP with unauthorized OOC arrangements.

6.3

No Economic Exploiting

Price fixing through OOC coordination, duplication, laundering exploits, and manipulation of broken scripts are prohibited.

Examples and clarification

IC negotiations and competition are allowed.

6.4

Employment Must Be Roleplayed

Applications may begin on the website, but interviews, training, hiring, discipline, and termination should occur in character.

Examples and clarification

The website records interest; it does not replace management RP.

6.5

No Ownership Hoarding

Do not control multiple major businesses solely to restrict opportunities or funnel money.

Examples and clarification

Ownership limits may be established as the city economy develops.

6.6

Advertisements Must Be Truthful IC

Businesses may exaggerate creatively, but scams or misleading promotions must create fair RP and comply with IC law.

Examples and clarification

OOC false claims about store purchases or server systems are prohibited.

Departments and Government 6 rules

7.1

Authority Is a Roleplay Responsibility

Department positions exist to serve and create RP, not to dominate scenes.

Examples and clarification

Abuse of job permissions or authority may result in IC discipline and OOC review.

7.2

Follow Department SOPs

LSPD, EMS, DOJ, Weazel, and other public roles must follow their approved policies and chain of command.

Examples and clarification

SOP breaches may be handled IC unless they also violate server rules.

7.3

Protect Restricted Information

Private MDT, medical, staff, and internal department information may not be published or transferred without authorization.

Examples and clarification

Public notices must be intentionally approved for release.

7.4

Department Neutrality

EMS and other neutral services should not use protected job access to assist factions or personal conflicts.

Examples and clarification

Characters may have relationships, but restricted tools and information cannot be abused.

7.5

DOJ Laws Are IC

Penal-code disagreements, court rulings, warrants, licences, and legal procedure are IC matters unless a server rule is also involved.

Examples and clarification

Do not use OOC staff reports to relitigate ordinary IC legal outcomes.

7.6

Weazel Must Separate Fact, Opinion, and Rumour

Published stories should identify verified reporting, opinion, correction, and unconfirmed information.

Examples and clarification

News RP may be biased IC, but fabricated OOC accusations or private information are prohibited.

Staff and Reports 5 rules

8.1

Use the Correct Support Process

Reports, appeals, compensation requests, and staff complaints must use the designated form or ticket system.

Examples and clarification

Do not pressure individual staff through private messages for a preferred outcome.

8.2

Evidence Must Be Honest

Do not edit evidence deceptively, omit material context intentionally, or submit false claims.

Examples and clarification

Provide the relevant lead-up and timestamps where possible.

8.3

Staff Decisions Are Not IC Knowledge

Do not reference warnings, tickets, admin actions, or staff conversations in character.

Examples and clarification

OOC outcomes must not become IC leverage.

8.4

No Staff Impersonation

Do not claim staff authority, use confusing names, or imply access you do not have.

Examples and clarification

Report suspected impersonation privately.

8.5

Appeals Require New Information or Accountability

An appeal should explain the decision being challenged, relevant evidence, responsibility accepted, and why reconsideration is appropriate.

Examples and clarification

Repeated identical appeals may be closed.

Discord and Content 5 rules

9.1

Discord Is OOC Unless Labelled IC

Information in general Discord channels is not automatically known by your character.

Examples and clarification

Only approved IC channels and posts may be treated as city information.

9.2

No Stream Sniping

Do not use streams, clips, chats, or creator activity to locate or gain advantage over a character.

Examples and clarification

Publicly available content is still OOC unless learned in RP.

9.3

Content Creators Must Protect Others

Do not use content creation to harass players, reveal private information, or intentionally disrupt scenes.

Examples and clarification

Follow platform rules and respect reasonable privacy requests.

9.4

No Advertising Without Approval

Do not advertise unrelated servers, services, products, or communities without permission.

Examples and clarification

NightShift business promotion should use approved IC and website channels.

9.5

Use Appropriate Channels

Keep applications, reports, support, development feedback, and IC content in their designated systems.

Examples and clarification

This allows the correct staff team to respond and preserves records.