Основы мультиплеера

Почему в одних онлайн-играх лаги frustrating, а в других незаметны? Почему matchmaking иногда создаёт stomps? Multiplayer design - не только 'подключи игроков', а система решений о latency, fairness, и trust.

• **Clash of Clans** - async attacks. Атакуешь когда хочешь, defender даже не онлайн. Perfect для mobile casual
• **Fighting games rollback** - Killer Instinct's netcode революция. Same latency feels way better с prediction
• **Valorant's anti-cheat** - Vanguard runs at kernel level. Controversial но effective. Design + tech approach

Synchronous vs Asynchronous

**Synchronous multiplayer** - все игроки онлайн одновременно, взаимодействуют в реальном времени. **Asynchronous** - игроки играют по очереди, не обязательно вместе. Разные требования к дизайну, технологии, и player commitment.

**Mobile games и async.** Clash of Clans attacks = async. Ты атакуешь базу когда хочешь, defender даже не онлайн. Perfect для mobile - no commitment to specific time.

**Choosing model:** - Target audience availability (casual = async) - Core gameplay requirements (twitch = sync) - Technical resources (servers cost) - Social goals (strong bonds = sync)

Designing for Latency

**Latency (ping)** - задержка между action и server response. 20ms = excellent, 100ms = noticeable, 200ms+ = frustrating. Game designers must design AROUND latency, не ignore его.

**Rollback netcode revolution.** Fighting games switched от delay-based (wait for opponent input) к rollback (predict, correct if wrong). Same latency feels 3x better. Killer Instinct → industry standard.

**Design for latency:** - Test на high ping (simulate 200ms) - Slower gameplay = more forgiving - Hide latency с animation (wind-up) - Communicate когда lag affects gameplay

Anti-Cheat Design

**Cheating** - breaking game rules для unfair advantage. Aimbots, wallhacks, speed hacks, item duplication. Designer's role: make game resistant to cheats BY DESIGN, не only technical solutions.

**Fog of war server-side.** В старых RTS fog of war был client-side - maphacks просто показывали hidden units. Modern games: server не sends enemy positions until visible. No data = no hack.

**Design anti-cheat:** - Minimize client authority - Hide information until needed - Validate все critical actions - Design systems robust to exploitation

Matchmaking Systems

**Matchmaking** - система подбора игроков для fair, fun matches. Skill-based (SBMM), connection-based, или hybrid. Goal: минимизировать one-sided games без long queue times.

**SBMM controversy.** Casual players love it (fair games). Streamers/pros hate it (no stomps for content). COD: hidden SBMM + lobbies disband = constant recalibration. Transparent vs hidden debate.

**Matchmaking design:** - Balance queue time и match quality - Protect new players (separate pools) - Consider parties (premade vs randoms) - Transparency builds trust

Итоги

• **Sync vs async** - real-time требует latency compensation. Async = flexible schedule, lower tech requirements
• **Latency design** - client prediction, server reconciliation, lag compensation. Design around latency, не ignore
• **Anti-cheat** = authoritative server + validation + hide info from client. 'Never trust the client'

Связанные темы

Multiplayer fundamentals connect to specific modes:

• Competitive Design — Ranked systems, esports readiness
• Cooperative Design — Co-op specific challenges

Вопросы для размышления

• В какой online game ты чувствовал lag most? Как game handled (или не handled) это?
• Ты когда-нибудь был matched против much stronger opponent? Как это felt?
• Если бы ты designed mobile multiplayer game, sync или async? Почему?

Связанные уроки

• gt-01