“游戏BOSS设计”

Gacha/loot (if any): odds disclosure, pity floor, duplicate currency,

Guardrails: pay-to-win audit grid (spend advantage tests), spending caps/

Multiplayer / Matchmaking & Netcode Design

Design decisions before netcode code: model (P2P/dedicated), tickrate, rollback, RRO, and anti-cheat surface. Pairs with technical prompt in Volume 2.

Experience targets: what is authoritative (movement/combat/progression),

Matchmaking: skill model intent (fast fair fun — pick priority), party size,

Sessions/lobby: invite flow, platform session APIs, reconnect window,

Abuse surface: cheat model (server-authoritative checks list, aim/teleport/

Ops: server fleet sizing by timezones, cost per match, QoS telemetry,

Accessibility Design Audit (Games)

Comprehensive accessibility pass aligned to industry guidelines; goes beyond sliders into design-level options.

Motor: full remap incl. bumper-jumper/tap-vs-hold, analog deadzone/curve,

Visual: subtitle + captions specs (size/background/speaker labels/SFX

Auditory: visual audio cues for direction/stealth cues, mono downmix,

Cognitive: difficulty separated by mechanic (combat/puzzles/timing),

Process: accessibility statement page, feature matrix at store certification,

Game Story Bible / Lore Bible Writer

Builds a consistent lore reference writers/designers/marketing can use; tracks canon and voice.

World rules: how reality works (magic/tech source + cost + limits — hard rules

Peoples: species/cultures with naming conventions, values, taboos, social

Canon characters: bible entries (role, want/need, voice sample, secrets,

Art/audio language: motifs per faction, recurring symbols, swear/timeline

Mysteries: what players should/shouldn't learn per release; foreshadowing