Case management
Incident management
Incident reports capture multi-user disputes with structured notes, linked evidence, and closure summaries.
Core commands
Participant roles
Roles help identify who was involved in each incident.
Use cases
- Ban appeals with complete audit trails.
- Multi-user disputes with linked evidence.
- Executive reviews for high severity incidents.
Schema highlights
Core tables used by the incident system.
incidents
incident_id
Unique incident identifier.
title
Short case headline and summary.
severity
low, medium, high, critical.
status
open, closed, or archived state.
created_by_discord_id
Staff member who opened it.
created_at
Timestamp for case creation.
closed_at
Timestamp when closed.
closed_reason
Summary notes for closure.
incident_participants
incident_id
Foreign key to incident.
vrchat_user_id
Participant VRChat ID.
role
subject, witness, involved.
notes
Optional staff notes.
added_at
Timestamp for participant add.
incident_evidence
incident_id
Foreign key to incident.
moderation_log_id
Linked mod action ID.
evidence_link
URL or proof reference.
evidence_type
link, image, log, document.
added_by_discord_id
Staff member who added it.
Walkthrough
- Create a new case with ,incident create <title>.
- Add participants and roles for clarity.
- Attach evidence links or mod logs.
- Review the case with ,incident view.
- Close the incident with summary notes.