MASS ACTIONS
Bulk Operations & Automation
VIRCON provides bulk moderation commands for handling mass rule violations and coordinated raids, plus automation workflows that reduce manual workload. All bulk actions include safety measures to prevent abuse and ensure accountability.
Bulk Commands
Core commands for executing mass moderation actions on multiple users simultaneously.
- ,bulkban <vrc_id_1> <vrc_id_2> ... <reason>
- ,bulkkick <vrc_id_1> <vrc_id_2> ... <reason>
- ,bulkwarn <vrc_id_1> <vrc_id_2> ... <reason>
Automation Commands
Commands for pattern detection, reason templates, and automated log backfilling.
- ,patterns [days] [min_actions] - Detect repeat offenders
- ,reasons - Select from common moderation reason templates
- ,backfill - Auto-backfill missing moderation logs from channels
Bulk Action Safety Features
Built-in protections and safety mechanisms to prevent abuse of bulk operations.
Rate Limiting
Max 10 users per bulk action to prevent API abuse
Protection: Auto-throttling with 2-second delay between actions
Transaction Safety
All-or-nothing execution - failures trigger rollback
Protection: Database transaction wrapping with automatic recovery
Audit Logging
Every bulk action logged individually to mod-log
Protection: Full accountability trail for each affected user
Reason Enforcement
Bulk actions require documented reason
Protection: Command rejected if reason missing or too vague
Automation Workflows
Scheduled and triggered automation processes that reduce manual moderation workload.
| Workflow | Trigger | Output |
|---|---|---|
| Pattern Detection | Daily scan at 02:00 UTC | Alert to admin channel with user list and suggested actions |
| Reason Templates | Staff calls ,reasons command | Auto-fills reason field with standardized text |
| Log Backfilling | Manual ,backfill or scheduled daily run | Reconstructs historical data from Discord message logs |
| Auto-sync Integration | Every 3 hours (VRChat member sync) | Updates member database and flags suspicious accounts |
Bulk Action Workflow
Step-by-step process for safely executing bulk moderation actions with transaction safety.
- 1. Staff initiates bulk command with list of VRChat user IDs and reason.
- 2. System validates input: max 10 users, reason not empty, IDs valid format.
- 3. Database transaction begins to wrap all actions.
- 4. Each user processed individually with 2-second delay between API calls.
- 5. Success/failure tracked for each user - partial failures logged separately.
- 6. If critical failure occurs, transaction rolls back (all-or-nothing).
- 7. Each action logged to mod-log channel with individual embed.
- 8. Final summary sent to command invoker with success/failure breakdown.
Safety & Abuse Prevention
Permission gates, cooldowns, and rollback capabilities to prevent misuse of bulk commands.
- Owner/Head Admin only for bulk bans (permission-gated).
- Dry-run mode available: ,bulkban --dry-run shows preview without executing.
- Cooldown timer: 5-minute delay between bulk actions per staff member.
- Automatic backup triggered before any bulk ban execution.
- Undo command: ,rollback can reverse last bulk action within 10 minutes.
Best Practices
Recommended guidelines for responsible and effective use of bulk operations.
- Use bulk commands for coordinated raids or mass rule violations only.
- Always provide detailed reason - 'rule violation' is too vague.
- Run ,patterns before bulk kicks to validate targets.
- Test with single action first if unsure about user IDs.
- Review ,reasons templates weekly to keep them current.
- Check backfill logs monthly to ensure no data gaps.
Integration with Other Systems
Bulk operations integrate seamlessly with incident reports (auto-linking), evidence vault (batch evidence upload), trust scoring (mass recalculation), and audit trails (full accountability logging). Pattern detection feeds into alt detection and risk forecasting systems.