CR-300 — Sensitive Roleplay & Emergency Services

STATUS: CURRENT / ENFORCEABLE

Effective: August 24, 2026

Last revised: August 24, 2026

CR-301 — Consent for sensitive content

The following content requires clear out-of-character consent from every directly affected participant before it begins:

• Torture, dismemberment, or deliberately graphic injury.
• Invasive or graphic medical procedures.
• Permanent injury, disfigurement, or a lasting disability imposed by the scene.
• Captivity intended to exceed 45 continuous minutes.
• Sexual or intimate content.
• Self-harm or suicide themes.
• Storylines centered on real-world hate crimes or highly personal trauma.

Consent must be specific to the content, can be limited, and may be withdrawn at any time. Previous participation, a character relationship, or remaining in the server does not imply consent. If consent is not obtained, use a less sensitive alternative or fade past the content.

CR-310 — Prohibited content

The following may not be actively depicted, requested, or used as leverage in roleplay:

• Sexual violence or forced sexual contact.
• Sexual content involving a minor or a character presented as a minor.
• Non-consensual intimate scenarios.
• Graphic torture after any participant declines or withdraws consent.
• Demands that a player disclose or reenact real-world trauma, diagnosis, identity, or medical information.
• Threats to expose real-world personal information or private communications.

A story may acknowledge that difficult subjects exist without reenacting prohibited conduct. Staff may restrict additional content when required by platform rules or an immediate community-safety concern.

CR-320 — Pause, simplify, fade, and stop

Any directly affected participant may request one of these safety actions without explaining personal details:

• Pause: temporarily stop the scene to resolve a safety or clarity issue.
• Simplify: continue with less detail or intensity.
• Fade: skip the sensitive action and continue with an agreed outcome.
• Stop: end the sensitive content or the scene.

The request must be honored promptly and without character or out-of-character retaliation. A request does not automatically decide a rules dispute or reverse unrelated consequences; it controls how the sensitive content continues. Staff may pause or end a scene and may separate participants while reviewing the issue.

CR-330 — Major-event pre-approval

Written administrative approval is required before launching:

• Terrorism, mass-casualty incidents, or attacks designed to affect the whole community.
• A sustained serial-offender storyline aimed broadly at uninvolved players.
• A major government shutdown, coup, citywide emergency, or destruction of critical public infrastructure.
• A storyline that predetermines permanent death, permanent injury, or long-term captivity for another character.
• An event that requires custom systems, unavailable assets, or staff-controlled outcomes.

The request must identify the organizer, scope, expected participants, sensitive themes, approximate duration, safety controls, and intended consequences. Approval may set additional limits and may be withdrawn if the event departs materially from the approved plan.

Spontaneous crimes and emergencies that stay within ordinary server systems, current rules, and reasonable scale do not require pre-approval.

CR-340 — Emergency-services interaction

Emergency-services scenes must create roleplay, not merely delay or erase consequences.

• Do not attack responders, steal an emergency vehicle, call false emergencies, or create hazards solely to manufacture a pursuit or response.
• Respect reasonable scene boundaries, triage priorities, and instructions needed to keep an active scene orderly.
• A conscious character with decision-making capacity may refuse nonessential treatment. The refusal must be roleplayed and may carry believable in-character consequences.
• A person in custody remains a patient. Custody does not authorize humiliation, unnecessary force, forced graphic detail, or denial of necessary care.
• Responders may describe assessment and treatment attempts, but they may not force invasive or graphic procedures or permanent injury without consent.
• A player may not disconnect, respawn, or switch characters to escape treatment, custody, questioning, or a scene that is still active.
• Do not force responders to perform systems, equipment, or specialist procedures that the server or current SOP does not support.

CR-350 — Custody and protected access

Custody must be handled through supported roleplay and current department procedures.

• Searching, restraining, transporting, or questioning another character must leave reasonable room for response and must not rely on animation or inventory abuse.
• Do not use a restrained person's phone, inventory, account, or interface as though the player personally surrendered credentials.
• Officers and custodial staff may secure supported evidence and property consistent with law and SOP, but may not use custody to settle an out-of-character dispute.
• Hostage and long-term custody scenes require continuing participation. After 45 minutes, the directly affected player may request release, a fade, or staff review unless the player freely agrees to continue.
• A safety pause or support request cannot be treated as an in-character admission, confession, or act of resistance.

Return to Community Rules