---
name: multiplayer-live-service
description: "Design and critique multiplayer dynamics, cooperation, competition, social systems, fairness, toxicity prevention, guilds, matchmaking, content cadence, seasons, events, battle passes, late-game loops, and live-service health. Do not use for networking implementation, backend architecture, graphics, assets, or code."
---

# Multiplayer And Live Service

Use when players interact with each other or a game must stay healthy after launch.

## Multiplayer Dynamics

Map:

- cooperation, competition, coexistence, spectatorship, trading, teaching, rivalry, and griefing;
- what players can do to each other;
- what players need from each other;
- how status is gained;
- how newcomers meet veterans;
- how groups form, persist, and dissolve;
- how the game rewards prosocial behavior;
- how it contains hostile behavior before moderation is needed.

## Fairness And Social Health

Review:

- matchmaking promise versus actual experience;
- team dependency and blame surfaces;
- communication tools and abuse risk;
- social reputation and repair paths;
- smurfing, boosting, collusion, griefing, kingmaking, and snowball risk;
- solo player dignity in group-oriented systems;
- reward structures for leadership, helping, teaching, and cooperation.

Competition should support competence and relatedness. Reduce harmful incentives upstream; do not solve toxicity only with punishment.

## Live-Service Health

Ask:

- Is the late-game loop interesting enough for repeated play?
- What can expand without exhausting the team?
- What content is original enough to matter?
- What quality-of-life changes reduce friction without erasing mastery?
- What catch-up path protects latecomers and lapsed players?
- What cadence is sustainable for the production team?

## Seasons, Events, And Battle Passes

Use only when they reinforce the core game. Healthy patterns:

- clear season fantasy;
- free and paid value that feels fair;
- visible completion effort;
- catch-up for latecomers;
- optional tasks across playstyles;
- no forced narrow modes or classes;
- strong first and final rewards;
- no unhealthy time commitment;
- rewards that do not short-circuit the core loop.

## Content Portfolio

Plan sustainable content by role:

- evergreen mastery content;
- novelty events;
- social rituals;
- progression milestones;
- narrative or world updates;
- economy refreshes;
- accessibility and quality-of-life updates;
- experimental high-risk/high-learning beats.

## Output

Return:

- multiplayer interaction map;
- social-health risks;
- fairness and competition review;
- live-service loop and cadence diagnosis;
- season/event/battle-pass recommendations or rejection rationale;
- content portfolio plan;
- validation signals.