1. Moderation Principles
- Actions should be based on available evidence, current rules, context, severity, safety risk and relevant history.
- Comparable cases should be treated consistently, while recognising that facts and impact can differ.
- Staff should avoid acting where a serious personal conflict exists when another authorised reviewer is reasonably available.
- Urgent safety, security, legal or platform risks may be contained immediately before the case is fully reviewed.
2. Cases And Audit Records
Dashboard-issued moderation actions may create numbered cases recording the target, action type, reason, issuing Admin, timestamps, duration, expiry, related cases and outcome. Protected case records may now include evidence references, evidence revisions, staff reviews, manually recorded appeals and linked decisions. Protected audit records may also record rejected or failed actions for security and accountability.
Legacy or externally issued Discord and Nitrado bans may appear without a dashboard case. Missing historical metadata will not be fabricated.
3. Evidence
Evidence may include Discord message links, screenshots, videos, player reports, DayZ or ADM logs, Nitrado records, bot records and staff observations. The dashboard stores short references and summaries rather than uploading large media files to Railway. Evidence should be authentic, relevant and kept no broader than necessary.
- Edited media should be identified as edited and accompanied by context where available.
- Evidence changes and removals retain an internal audit record instead of silently erasing the previous entry.
- Private evidence is restricted to authorised staff and should not be reposted publicly without a legitimate reason.
- Evidence involving credible threats, child safety, crime or platform security may be referred to the relevant platform or authority.
4. Available Actions
Depending on the incident and available tools, staff may use guidance, warnings, content removal, virtual-economy correction, Discord kick, Discord ban, DayZ ban, account unlinking, restrictions or other proportionate community controls.
Temporary Discord and DayZ bans may use preset or custom expiries. Permanent bans have no scheduled expiry. Automatic expiry depends on the bot, Discord or Nitrado being available; failed expiries remain active and are retried rather than falsely recorded as complete.
5. Duration And Repeat Conduct
Duration may reflect severity, intent, harm, cooperation, relevant history, ban evasion and risk of recurrence. Repeated conduct may justify escalation. A first incident may still justify a permanent ban where the conduct is sufficiently serious.
Expiry of one ban does not override an independent active restriction, platform enforcement decision or new rule violation.
6. Review And Appeals
A linked member may use My appeals in the protected dashboard or the direct /appeal Discord command to request review of an eligible case. Railway derives the identity from the signed-in account and does not allow the player to select another person's case. Where configured, a private Discord ticket is created and linked to the authoritative numbered case.
Only one active appeal may exist for a case. Deadlines, cooldowns and submission limits apply. A player may edit before staff assignment only where the Owner has enabled that option, and may withdraw an undecided appeal. Submission does not automatically pause, shorten or reverse an active punishment. Do not evade a ban, create alternate accounts or harass staff to obtain a different result.
Include Where Possible
- The relevant case selected from the protected list.
- A clear explanation of what you believe was incorrect or disproportionate.
- Any new, complete and authentic evidence.
- The outcome you are requesting.
Appeals may be declined where they are abusive, repetitive, fraudulent, unrelated, submitted through ban evasion, outside the configured deadline, or provide no reviewable information.
7. Review Outcomes
Where practical, a different authorised Admin should decide a contested action. A regular Admin cannot decide a review of an action they originally issued. The Owner may override that separation where no practical alternative exists, and the override is recorded. An outcome may be upheld, reduced or overturned, with the decision and reason added to the protected case history.
For supported active warnings and community-issued Discord or DayZ bans, a reduction changes the scheduled expiry and an overturn performs the corresponding warning removal or unban before the case is closed. Reversal of a community action cannot force Discord, PlayStation, Nitrado or another independent provider to reverse its own separate enforcement.
8. Privacy And Retention
Moderation records may be retained longer than ordinary session data where reasonably needed for safety, ban enforcement, ban-evasion detection, dispute resolution, audit integrity, security or legal obligations. Access is limited to authorised roles and exposed through the dashboard only as allowlisted fields.
See the Privacy Policy for information requests and handling practices.
9. Errors And Technical Failures
If an action appears to have been applied to the wrong player, expired incorrectly or failed technically, report it promptly with the case number and evidence. Audit and recovery records may be used to investigate or restore an account link. Staff must not promise a technical reversal until the actual Discord, Nitrado and database state is confirmed.
10. Contact
Use the established World War Z Discord support-ticket process where accessible. Do not post private evidence or security information in public channels.