Contact Administration

Choose the channel that matches the issue. Using the correct route protects privacy and helps the right team respond without interrupting active roleplay.

In-character emergency

Use the in-game emergency call system or contact dispatch for an active fictional police, fire, or medical emergency. Provide the location, what is happening, immediate danger, suspect or patient description, and a safe callback method available through the game.

Do not use in-character emergency services for a real-world emergency, server-rule complaint, technical support request, or disagreement with another player.

Real-world emergency or safety concern

For an actual emergency, contact the appropriate real-world emergency service. If a player appears to be in real danger, notify platform or server administration through the fastest available out-of-character route after contacting appropriate real-world help.

Staff are not substitutes for emergency responders, clinicians, attorneys, or crisis professionals.

Server support ticket

Use the general support-ticket system for:

• harassment, consent, or prohibited-roleplay concerns;
• cheating, exploitation, or suspected rule violations;
• exposure of personal information;
• account, access, or character problems;
• technical issues affecting play;
• staff-conduct concerns; and
• questions that do not belong to a department.

Include a concise timeline, relevant server identifiers, available clips or screenshots, and the outcome requested. Do not post sensitive evidence publicly.

Department chain of command

Use the department’s official channel for scheduling, training, equipment, promotion, ordinary policy questions, or review of an in-character supervisor decision. Begin with the lowest appropriate supervisor unless the complaint involves that person or creates a retaliation concern.

For urgent operational matters, contact the on-duty supervisor through dispatch or the approved department channel.

Department of Justice and courts

Use the court or DOJ filing process for:

• warrant review;
• criminal-case filings;
• counsel requests;
• motions, hearing requests, and appeals;
• protection-order requests;
• subpoena or discovery issues; and
• formal legal interpretation of Stratos law.

Do not use private messages to seek one-sided contact with a judge about the merits of a pending case. File the request where the other parties can receive appropriate notice.

Documentation corrections

For a typo, broken link, contradiction, outdated section, or proposed rewrite, submit:

• page title and heading;
• exact language at issue;
• issue category;
• effect on players or workflow;
• proposed replacement language, if any; and
• whether the issue also affects the CAD, forms, training, or another document.

Emergency ambiguities affecting an active scene should be resolved by the scene supervisor or administrator. The temporary ruling should later be reviewed for publication.

Ban, discipline, and staff-action appeals

Use the designated appeal process rather than opening repeated tickets or contacting individual staff members. State the action appealed, date, decision-maker if known, grounds for review, and new or overlooked evidence.

An appeal is not a venue for harassment, threats, public pressure, or relitigating an unchanged claim through multiple channels.

Privacy and response expectations

Share only information needed to resolve the issue. Never send passwords, authentication codes, government identification, real addresses, or unrelated private conversations.

Response time depends on urgency, staffing, and complexity. Duplicate submissions may slow review. If immediate player safety is involved, clearly mark the safety concern without exaggerating routine issues as emergencies.

Escalation guide