Survival game server Discord ops: wipes, VIPs, raid reports, appeals, and staff control

Rust, ARK, DayZ, 7 Days to Die, Unturned, and similar servers do not only sell slots. They sell a belief that wipes are fair, VIP access works, staff decisions are consistent, and reports do not disappear into chat.

• Publish wipe dates and restart windows in one place.
• Separate VIP perks from staff authority.
• Give raid, exploit, admin-abuse, and ban-appeal reports different routes.
• Close every decision with evidence, owner, verdict, and next step.

The first wipe weekend exposes every weak Discord decision. If staff shifts, escalation routes, status updates, donor roles, and report templates are still improvised, players experience that as unfairness even when the owner meant well.

A survival report should capture who, when, where, what evidence exists, what staff already checked, and what resolution is possible. A raid report without map/grid or timestamp is not actionable. An admin abuse report without a private senior-review path becomes public drama.

• Start-here, rules, wipe schedule, server status, VIP info, announcements.
• General, teams/clans, trade, media, suggestions.
• Access help, raid report, admin abuse report, exploit report, bug report, appeals.
• Staff log, mod queue, wipe room, evidence archive.

KeepGrid turns the survival-server Discord into an installable operations layer: role matrix, VIP boundaries, ticket routes, report templates, appeal flow, staff shift notes, launch checklist, dry-run preview, audit log, and rollback.