LiveOps Patterns

Plan events that keep a live game fresh.

Methods for running a live mobile game after launch, for live-ops teams, producers and designers. The cards cover deciding what live service means for your game, building events worth logging in for, setting a calendar rhythm, shipping updates safely every week, talking with players, and measuring what worked so the next event is better.

48 cards · 6 suits · 5 recipes · 2 missions

What's inside

Strategy8Is it clear what live means for this game?
Events8Have you built events worth logging in for?
Calendar8Does your calendar have rhythm rather than noise?
Operations8Can you ship safely every single week?
Community8Are you talking with players, not at them?
Measure and Learn8Can you tell which events actually worked?

A few cards

Strategy

Live Promise

One sentence that tells players what keeps changing and why tomorrow is worth a visit.

Events

Event Types

A menu of event formats and what each one is good for, so you pick on purpose.

Operations

Live Config

Change events, tuning and rewards from the server, not through the app store.

One card in full

Community

Patch Notes Players Read

Tell players what changed for them, in their words, before they find out the hard way.

Most patch notes are written for the team: ticket numbers, internal names, and the bad news buried on line forty. Players skim, miss the change that matters, and discover it mid-match. Good notes are short, ordered by impact, and honest about what got worse.

How to use it

List every change, then mark each one: will a player notice it in their first session after the update?
Lead with the three changes players will feel most, including any nerf; small fixes go in a list underneath.
Rewrite each line as a player outcome: "Daily chests now open instantly" beats "Reduced chest timer config to 0".
Say why for anything that takes something away, in one sentence. For bigger removals, follow Bad News Well.
Add a "You told us" line for changes that came from players, closing the Feedback Loop.
Post the same notes through In-Game Messaging and community channels at release, not a day later.

Example

Supercell's balance-change posts for Clash Royale show each card's numbers before and after. A hypothetical puzzle game might open its notes with "Lives now refill in 20 minutes, down from 30" and leave engine changes for last.

Watch out

Hiding a nerf in the fine print. Players will find it, and the notes become proof you tried.
Shipping "bug fixes and performance improvements" every time. It teaches players to stop reading.

Recipes

Event That Works: Build an event for a named group of players, tune it so they finish, and prove it made a difference.
First Event: Run your first live event from a one-line promise to a written postmortem.
Plan A Season: Turn the gaps in your retention into a season with a rhythm, a calendar and a plan for telling players.
Ship Safely: Set up the controls that let you change, release and stop live content without an app update or a panic.
When It Breaks: Get through a live incident: stop the damage, put things right, tell players honestly and learn from it.

Missions

Build a season calendar: from a blank quarter to a calendar of events, rest weeks and real-world moments that fits the team's content budget.
Plan a live event: from "we need an event next month" to a one-page event spec with segment, format, rewards, difficulty, launch checklist and success metrics.

Related decks

Player Research Patterns

Learn what your players really want.

48 cards

UA Patterns

Acquire players who stay, at a sensible cost.

48 cards

Game Production Patterns

Take a game from concept to live service.

56 cards

← All decks