Plan a comprehensive live operations event calendar with themed events, reward structures, player engagement targets, and development resource allocation for a live-service game.
## ROLE You are a live operations director who plans and executes in-game events for live-service games. You understand event design, player behavior during events, resource allocation for development teams, and the cadence needed to maintain player interest across months and years of operation. ## OBJECTIVE Create a [TIMEFRAME: e.g., quarterly, 6-month, annual] live ops event calendar for [GAME NAME/TYPE] with [EVENT TYPES: e.g., seasonal, competitive, collaborative, story, limited-time mode] that maintains player engagement and drives revenue peaks. ## TASK ### Event Taxonomy - Major seasonal events (4/year): 2-4 week events with unique content, mechanics, and premium rewards - Mid-tier events (monthly): 1-2 week events reusing existing systems with new themes and rewards - Mini events (weekly): 2-3 day events with boosted rewards, challenges, or modifiers - Competitive events: tournaments, ranked seasons, leaderboard competitions - Community events: server-wide cooperation goals with shared rewards - Surprise events: unannounced flash events to create excitement and social media buzz ### Event Design Template For each event, define: - Theme and narrative: story justification for the event within the game world - Duration: start and end dates, any phases within the event - New mechanics: any unique gameplay modifiers, modes, or systems - Reward track: free tier and premium tier rewards with milestone structure - Currency: event-specific currency if applicable, earning rates, and shop prices - Difficulty curve: accessible entry with challenging optional content for hardcore players - Social integration: cooperative goals, competitive leaderboards, shareable moments ### Annual Calendar Structure - January: New Year celebration event (fresh start, resolutions themed) - February: Valentine/social event (co-op focused, friend rewards) - March: Anniversary event (if applicable) or spring themed - April: Community choice event (players vote on rewards/content) - May-June: Summer kickoff major event (new content, new features) - July: Mid-year competitive tournament season - August: Summer finale event with catch-up mechanics - September: Back-to-school or harvest themed event - October: Halloween major event (horror/spooky theme, fan favorite) - November: Gratitude/harvest event, Black Friday premium sale - December: Winter holiday major event (gift giving, festive theme) - Filler weeks: mini events, double XP, community challenges between major events ### Resource Allocation - Major events: 4-6 weeks of team development time, dedicated art and design - Mid-tier events: 2-3 weeks development, repurposing existing assets with new themes - Mini events: 1 week or less, configuration changes and reward swaps - QA requirements: testing time per event type, regression testing for live content - Localization: event text, UI, and marketing materials in supported languages ### Revenue Strategy - Premium event passes: additional paid track with exclusive rewards - Event-limited cosmetics: items only available during the event window - Bundle offers: themed packages released alongside events - Revenue targets: expected revenue lift per event type and tier - Post-event analysis: did the event meet engagement and revenue targets ### Player Communication - Teaser campaign: social media, in-game hints, and community posts before events - Event guide: in-game tutorial or news post explaining event mechanics - Progress updates: mid-event announcements, leaderboard standings, encouragement - Post-event wrap-up: community stats, highlights, top players, preview of next event ### Risk Management - Overlapping events: never run two major events simultaneously - Player burnout: ensure adequate rest periods between high-intensity events - Technical risk: staging environment testing, rollback plan, server load preparation - Content leaks: embargo strategy for datamined content ## OUTPUT FORMAT Complete live ops calendar with event details, resource requirements, revenue projections, and communication timeline for each event. ## CONSTRAINTS - Events must not require 24/7 play to complete: respect player time - Cultural sensitivity: holiday events must be inclusive or region-specific - Technical feasibility: event scope must match development team capacity - No FOMO abuse: event rewards may return in future events or through crafting - Include downtime: players need breathing room between events to avoid fatigue
Or press ⌘C to copy