San Andreas Roleplay Code

The San Andreas Roleplay Code governs fictional scenes, fictional legal status, fictional property, fictional charges, and fictional court outcomes inside ZO Syndicate RP.

The code does not create real legal rights, real legal duties, real emergency guidance, or real law-enforcement authority. It exists only as a roleplay operating document.

Real safety issues, platform rules, privacy requests, payment issues, moderation actions, and staff safety decisions override roleplay law every time.

A character facing arrest, charge, forfeiture, court order, agency discipline, or serious fictional penalty should be told the in-character reason when safety and scene conditions allow.

A serious consequence should create a record that names facts, code or policy basis, decision, responsible office, and review path if one exists.

When a decision meaningfully limits a character's freedom, property, rank, license, or membership, the system should identify whether DOJ, command, staff, or another review lane owns correction.

A character may seek a DOJ member or approved representative when the filing type, court, agency, or policy allows representation.

Representatives are roleplay advocates, not real lawyers. They must not present ZSR law as real legal advice or use out-of-character pressure as a courtroom weapon.

A hearing does not stop forever because a representative is absent unless the court or policy grants a continuance.

No statute, warrant, court order, or faction rule can be used to justify harassment, doxxing, hate, real threats, sexual content involving minors, or abuse disguised as roleplay.

Staff or authorized command may pause or redirect a scene if the roleplay legal process is being used to harm the community or exploit a system.

A court or staff correction should explain what is corrected and what remains valid so players know how to continue the story.

Assault covers an attempted or threatened unlawful attack that creates immediate fear or risk in roleplay.

Battery covers unlawful harmful physical contact or completed attack in roleplay.

Robbery covers taking property from a person through force, threat, or immediate fear.

Kidnapping or unlawful confinement covers moving or holding a character against their will under facts recognized by server policy.

Theft covers unlawful taking or control of property, currency, item records, inventory, or vehicle access belonging to another character, business, organization, or system.

Burglary covers unlawful entry or remaining in a protected structure, business, vehicle, residence, or property area with intent to commit an offense.

Vandalism or property damage covers destruction, damage, tampering, or disabling of property where the record supports it.

Vehicle theft, boosting, chop-shop conduct, impound evasion, and plate tampering may be charged under property sections or a more specific vehicle code when one exists.

Obstruction covers knowingly interfering with a lawful scene, investigation, medical rescue, fire rescue, court order, or authorized roleplay process.

Resisting covers refusal, force, or interference that prevents lawful detention, arrest, citation, or scene order under roleplay cause.

False report covers knowingly giving materially false information to create, redirect, or sabotage a public safety response.

Disorder charges should be used carefully so expressive roleplay, criticism, or civilian tension does not become automatic punishment.

Contraband status depends on the current ZSR item, economy, faction, drug, weapon, evidence, or event policy.

Officers should identify the item, context, discovery method, legal basis, and case link instead of writing vague contraband claims.

Hidden crafting mechanics, stash locations, safehouses, faction ledgers, and active supply chains should not be exposed in public charges beyond what the character record requires.

Speeding, unsafe lane change, failure to yield, red-light violation, reckless turn, wrong-way travel, illegal parking, and unsafe equipment may support warning, citation, tow, or arrest depending on facts.

A warning is a valid outcome when education fits the scene and no greater risk remains.

A citation should name the observed behavior, location, vehicle, driver or responsible party, and any escalation facts.

Reckless driving covers operating a vehicle with disregard for player, pedestrian, traffic, property, weather, or roadway safety.

Evasion covers flight from a lawful stop or order when the driver knows, or reasonably should know in the scene, that law enforcement is attempting contact.

Pursuit-related records should include route, duration, risk, crash, injury, unit count, tactics used, and termination facts.

A vehicle may be towed or impounded for arrest processing, hazard removal, evidence hold, abandonment, parking rule, court order, event safety, or staff/server correction when policy supports it.

The record should include vehicle, plate if known, reason, location, officer, tow unit if used, release path, and evidence hold status.

Restricted fleet, faction, business, and evidence vehicles require tighter access and audit handling.

A stop should be based on observed conduct, call facts, warrant, BOLO, safety need, consent, or another policy-recognized cause.

Detention is temporary control tied to scene safety or investigation. It should not become an indefinite punishment without charge or review.

Arrest should be tied to a chargeable offense, warrant, court order, or policy-recognized custody basis.

Evidence should include what it is, where it came from, who handled it, when it was collected, what case it belongs to, and why it matters.

Screenshots, photos, bodycam-style notes, inventory items, witness statements, and dispatch logs should be used only in the lane where policy allows them.

Private staff notes, stream knowledge, unrelated character knowledge, and out-of-character platform data should not be introduced as RP evidence unless staff policy explicitly routes it into a case.

A warrant or order should state target, scope, facts, requested action, approving authority, time or condition limits, and execution notes.

A valid fact does not automatically open every property, stash, device, vehicle, account, or faction record. Scope must match the order or policy basis.

Emergency exceptions should be rare, documented, and reviewable.

Select the filing type: criminal review, civil claim, injunction/requested order, warrant request, appeal, record correction, license matter, or administrative review.

Name parties, character identifiers where allowed, event date, location, facts in order, code or policy section, evidence list, witnesses, urgency, and requested outcome.

Use the approved website, Discord, DOJ, or Syntra lane so the filing becomes a trackable record instead of a lost DM.

Meet the client, identify their goal, read the record, list disputed facts, check deadlines, explain risk, and decide whether the client wants to contest, plead, settle, appeal, or withdraw.

A representative may challenge cause, evidence, identification, procedure, charge fit, witness reliability, remedy, penalty, or record accuracy.

Do not guarantee a result, invent law, use OOC information, threaten staff action as leverage, or confuse fictional ZSR law with real legal advice.

A standard hearing opens with case name, appearances, issue, evidence status, order of presentation, and expected outcome path.

The court may hear opening statements, witnesses, evidence, objections or challenges if used, argument, and requested remedy.

The hearing lead may pause irrelevant testimony, stop harassment, manage OOC confusion, continue the matter, or route a safety issue to staff.

A ruling should state issue, facts relied on, code or policy applied, decision, remedy or penalty, deadlines, and appeal path if available.

If a ruling is temporary, emergency-only, narrow, or case-specific, the ruling should say so.

An appeal should identify the ruling, alleged error, requested correction, and record evidence supporting review.