LOCATION TRACKING
World Monitoring & Heatmaps
VIRCON tracks moderation activity by VRChat world and time dimension to identify problem locations, optimize staff coverage, and detect behavioral patterns. Heatmaps provide visual insights into where and when incidents occur most frequently.
World & Heatmap Commands
Commands for tracking world-based incidents and viewing heatmaps.
- ,world heatmap [days] - Show worlds with highest incident rates
- ,world stats <world_id> - Detailed stats for specific world
- ,world log <world_id> <action> - Log moderation action tied to world
- ,world users <world_id> - Show users frequently seen in problem worlds
- ,heatmap hour - Show moderation activity by hour of day
- ,heatmap day - Show moderation activity by day of week
- ,heatmap peak - Show peak moderation times
- ,heatmap record - Show all-time highest activity periods
Heatmap Types
Four visualization types for understanding incident patterns.
World Heatmap
VRChat worlds ranked by incident frequency
Use Case: Identify problem locations requiring staff attention
Time Heatmap
Moderation activity by hour and day
Use Case: Optimize staff coverage for peak times
User-World Crossover
Users frequently present in flagged worlds
Use Case: Detect patterns in repeat offender behavior
Severity Heatmap
Worlds ranked by punishment severity (bans vs warnings)
Use Case: Differentiate between rowdy and dangerous locations
World Tracking Workflow
Automated process for identifying problem locations.
- 1. Moderation logs capture VRChat world_id when ban/kick/warn occurs.
- 2. System aggregates world_id references to build historical activity map.
- 3. Worlds with >5 incidents in 7 days auto-flag as 'problem location'.
- 4. Staff can run ,world heatmap to see ranked list of flagged worlds.
- 5. Detailed world stats show incident types, severity, and user overlap.
- 6. World data cross-referenced with user trust scores for pattern detection.
World Tracking Database Schema
Database fields for tracking world-based incidents.
| Field | Description |
|---|---|
| world_id | VRChat world identifier (wrld_...). |
| world_name | Human-readable world name from VRChat API. |
| incident_count | Total moderation actions in this world. |
| ban_count | Number of bans associated with this world. |
| kick_count | Number of kicks associated with this world. |
| warn_count | Number of warnings associated with this world. |
| flagged | Boolean: exceeds incident threshold. |
| first_incident_at | Timestamp of earliest incident. |
| last_incident_at | Timestamp of most recent incident. |
Heatmap Database Schema
Database fields for time-based heatmap aggregations.
| Field | Description |
|---|---|
| heatmap_id | Unique heatmap entry identifier. |
| dimension_type | hour, day_of_week, world, user. |
| dimension_value | Specific hour (0-23), day (0-6), world_id, or user_id. |
| incident_count | Total incidents for this dimension value. |
| last_updated | Timestamp of last calculation update. |
Sample World Heatmap (7 Days)
Example output from world incident tracking.
| World Name | Incidents | Severity | Flagged |
|---|---|---|---|
| Club Vertex | 23 | High | ✅ Yes |
| The Black Cat | 18 | High | ✅ Yes |
| Midnight Rooftop | 12 | Medium | ✅ Yes |
| Cozy Cabin | 3 | Low | No |
Use Cases
Real-world applications of world tracking.
- Identify VRChat worlds where harassment occurs most frequently.
- Detect time-of-day patterns to optimize staff shift coverage.
- Flag users who repeatedly appear in problem worlds.
- Provide head admins with data for policy decisions (blacklist worlds, etc.).
- Generate weekly briefings on emerging problem locations.
Automation Features
Automated systems for world tracking and alerts.
- Daily heatmap recalculation runs at 04:00 UTC for fresh data.
- Auto-alerts to admin channel when new world exceeds flagging threshold.
- World tracking integrates with moderation logs (no manual input needed).
- Historical data retained for 90 days for trend analysis.
- Heatmap visualization exports for staff briefings (JSON/CSV).
Best Practices
Guidelines for effective world monitoring.
- Run ,world heatmap weekly to catch emerging problem locations early.
- Cross-check high-incident worlds with user trust scores for patterns.
- Use time heatmaps to schedule staff shifts during peak activity hours.
- Don't ban worlds outright - use data to inform targeted moderation.
- Document world patterns in incident reports for context.