EMERGENCY RESPONSE
Event Mode & Raid Response
VIRCON's event mode enables temporary stricter rulesets for community events or emergency raid response. The system auto-detects coordinated attacks and provides head admins with rapid-response tools to restore order without permanent policy changes.
Event Commands
Core commands for activating and managing event mode and emergency response protocols.
- ,event start <event_name> [duration] - Activate event mode
- ,event end - Deactivate event mode and restore normal rules
- ,event status - Show current event mode state and metrics
- ,event config <setting> <value> - Adjust event mode parameters
- ,event stats - View event mode activity summary
- ,event list - Show all past events and their outcomes
Event Mode Features
Enhanced moderation capabilities and automated responses activated during event mode.
Stricter Thresholds
Reduced tolerance for rule violations during events
Example: Warning → Kick escalation threshold lowered from 3 to 2
Enhanced Monitoring
Increased staff ping frequency and alert sensitivity
Example: Callstaff auto-triggered for any moderation action
Raid Detection
Auto-flags coordinated mass joins or spam waves
Example: 5+ joins in 60 seconds triggers raid alert
Temporary Bans
All event-mode bans expire automatically after event
Example: User banned during raid auto-unbanned 24h post-event
Raid Response Protocol
Step-by-step emergency workflow for responding to coordinated server raids.
- 1. System detects anomaly: 5+ joins in 60s OR 10+ messages from new users in 2 min.
- 2. Auto-alert sent to admin channel with raid detection confidence score.
- 3. Head admin calls ,event start raid to activate emergency mode.
- 4. All new joins temporarily blocked (configurable grace period).
- 5. Mass-action commands unlocked for non-admin staff (emergency powers).
- 6. Raid participants auto-kicked after analysis (pattern-based detection).
- 7. Event ends with ,event end - normal operations restored, temporary bans reviewed.
- 8. Post-raid report generated showing actions taken and affected users.
Event Database Schema
Database structure for tracking event mode activations and raid response metrics.
| Field | Description |
|---|---|
| event_id | Unique event identifier. |
| event_name | Descriptive name (e.g., 'raid', 'community_night'). |
| started_by | Discord ID of staff who activated event mode. |
| started_at | Timestamp of event mode activation. |
| ended_at | Timestamp of event mode deactivation (NULL if active). |
| duration_minutes | Planned or actual event duration. |
| config_snapshot | JSON of modified settings during event. |
| actions_taken | Count of moderation actions during event. |
| raid_detected | Boolean: was this a raid response event. |
Event Mode Configuration
Comparison of default settings versus event mode overrides for stricter moderation.
| Setting | Default | Event Mode |
|---|---|---|
| join_rate_limit | 5 per minute | 2 per minute |
| auto_kick_new_users | false | true (if raid) |
| warning_threshold | 3 | 2 |
| bulk_action_cooldown | 5 minutes | 1 minute |
| staff_alert_frequency | per incident | every action |
Automation Features
Automated workflows and intelligent responses built into event mode operations.
- Auto-detection of coordinated raids via join pattern analysis.
- Temporary ban auto-expiration 24 hours post-event end.
- Event metrics auto-logged to analytics for trend tracking.
- Staff emergency powers auto-revoked when event mode ends.
- Post-event summary report auto-sent to admin channel.
Best Practices
Recommended guidelines for effective event mode usage and raid response management.
- Start event mode BEFORE large community events to prevent chaos.
- Use ,event stats to monitor effectiveness and adjust settings.
- Document raid events in incident reports for post-mortem analysis.
- Review temporary bans after event ends - some may need permanent action.
- Communicate event mode to community to set expectations.
- Run ,event end as soon as event concludes to restore normal operations.
Integration Note
Event mode integrates with anomaly detection (raid triggers), bulk operations (mass kick/ban), incident reports (auto-link raid events), and staff availability (emergency callstaff). All event actions are logged to audit trail for review.