Game LiveOps Exploit and Bug Ticket Prioritization Matrix

Role: Lead Live Operations Customer Support Manager for AAA multiplayer live-service titles.

Context

• Live-service game title: {{game_title}}
• Active content update or season: {{live_season}}
• Virtual currency and economy impact: {{player_economy_impact}}
• Reported exploit vectors and glitch severity: {{exploit_severity}}
• Inbound player ticket volume cluster: {{ticket_cluster_data}}
• Impacted gaming platforms: {{target_platforms}}

Task

Produce a LiveOps ticket prioritization matrix that categorizes player-reported game bugs, progression blockers, and economy exploits to coordinate frontline CS macro deployments with emergency hotfix triage.

Method

1. Group {{ticket_cluster_data}} into functional domains: economy exploits, matchmaking failures, progression blockers, and cosmetic glitches.
2. Cross-reference reported bugs with {{target_platforms}} to isolate platform-specific certification risks from server-side issues.
3. Quantify financial and fair-play risks based on {{player_economy_impact}} and {{exploit_severity}}.
4. Factor in the lifecycle stage of {{live_season}} to evaluate urgency around competitive ladder integrity.
5. Determine community sentiment impact to set escalation speed for {{game_title}} player support leads.
6. Assign frontline macro responses, compensation eligibility criteria, and rollback triggers.
7. Map critical ticket groups to engineering hotfix deployment tracks and CS auto-tagging workflows.

Constraints

• MUST define compensation eligibility thresholds for affected player accounts.
• MUST NOT classify server-side economy duping exploits as standard low-priority bugs.
• Must include specific customer support containment actions alongside engineering handoffs.
• Table must maintain clear priority tiers from Critical Emergency to Cosmetic Backlog.

Output format

• Triage Framework Summary (1 paragraph, max 80 words)
• LiveOps Ticket Prioritization Matrix (Markdown table with columns: Priority Rank, Issue Classification, Economy / Gameplay Impact, CS Action & Tagging, Hotfix Escalation Path, Player Compensation Policy)
• Player Support Containment Rules (4 bulleted operational protocols)

Self-review

• Verify all 6 variables ({{game_title}}, {{live_season}}, {{player_economy_impact}}, {{exploit_severity}}, {{ticket_cluster_data}}, {{target_platforms}}) are referenced naturally in context and method.
• Ensure matrix clearly separates client-side bugs from severe live economy exploits.
• Check that output format includes compensation criteria and matrix columns match the specification.