STAFF ACCOUNTABILITY
Staff Strike System
VIRCON's strike system provides transparent staff accountability tracking. Strikes are issued for policy violations, abuse of power, or repeated performance issues. The system maintains full history for fairness while supporting resolution and improvement pathways.
Strike Commands
Core commands for managing staff strikes and accountability.
- ,strike @staff <reason> - Issue strike to staff member
- ,strikes [@staff] - View strike history (self or other)
- ,strikelist - Show all staff with active strikes
- ,resolvestrike <strike_id> <reason> - Mark strike as resolved
- ,clearstrikes @staff1 @staff2 - Clear all strikes (Owner only)
Common Strike Reasons
Typical violations that warrant strike issuance.
Strike Thresholds & Actions
Graduated consequences based on strike accumulation.
| Strike Count | Consequence |
|---|---|
| 1 strike | Verbal warning, performance review scheduled |
| 2 strikes | Written warning, temporary demotion consideration |
| 3 strikes | Demotion to Trial Moderator or removal |
| 4 strikes | Staff removal and access revocation |
Strike Workflow
Step-by-step process for strike issuance and resolution.
- 1. Head admin or higher issues strike with ,strike @staff <reason>.
- 2. Strike recorded to staff_strikes table with timestamp and issuer.
- 3. Staff member receives automated DM notification with strike details.
- 4. Strike appears in staff's ,strikes history for transparency.
- 5. Admin can use ,resolvestrike to mark strike as addressed/expired.
- 6. Cleared strikes remain in history but marked as inactive.
- 7. Owner can use ,clearstrikes to wipe strike history (rare, emergency only).
Strike Database Schema
Fields stored for each staff strike record.
| Field | Description |
|---|---|
| strike_id | Auto-incremented unique identifier. |
| staff_discord_id | Discord ID of strike recipient. |
| staff_vrc_id | VRChat ID of strike recipient. |
| issued_by_discord_id | Admin who issued the strike. |
| reason | Detailed explanation for the strike. |
| severity | low, medium, high, critical. |
| status | active or resolved. |
| issued_at | Timestamp of strike issuance. |
| resolved_at | Timestamp of resolution (if resolved). |
| resolved_by | Admin who resolved the strike. |
| resolution_notes | Explanation for resolution. |
Automation Features
Automated strike-related workflows and alerts.
- Strike count auto-displayed in staff profiles and leaderboards.
- Auto-alerts to admin channel when staff reaches 3+ strikes.
- Strike history integrated into staff performance analytics.
- Expired strikes (90+ days old, resolved) auto-archived monthly.
- Strike data cross-referenced with incident reports.
Real-World Use Cases
Examples of strike system implementation in action.
Case 1
Moderator bans user without documenting reason
Action: Strike issued for policy violation
Outcome: Moderator required to attend documentation training
Case 2
Trial mod kicks user for personal dispute
Action: Strike issued for abuse of power
Outcome: Trial mod demoted, requires re-training
Case 3
Staff leaks confidential incident report to community
Action: Critical strike + immediate access review
Outcome: Staff removed, all credentials revoked
Best Practices
Guidelines for fair and effective strike management.
- Document strike reasons clearly - vague strikes undermine trust.
- Use strikes for serious/repeated issues, not one-off mistakes.
- Schedule performance review meeting after strike issuance.
- Resolve strikes once corrective action is completed.
- Never issue retaliatory strikes - use audit trail to verify.