游戏设计
游戏策划、资产生成、玩法关卡设计等提示词
642 个提示词
input-to-display latency budget ms, acceptable packet loss, and tick rate; genre fit:…
Experience targets: what is authoritative (movement/combat/progression),
Design decisions before netcode code: model (P2P/dedicated), tickrate, rollback, RRO, and anti-cheat surface. Pairs with technical prompt in Volume 2.
Multiplayer / Matchmaking & Netcode Design
reminders, refund rate and chargeback monitoring, A/B ethics review, and live levers;…
Guardrails: pay-to-win audit grid (spend advantage tests), spending caps/
spending limits, minor-account blocks, regulatory checklist by country.
Gacha/loot (if any): odds disclosure, pity floor, duplicate currency,
for {{daily minutes}}, catch-up for late buyers, no-FOMO rerun policy for missed items,…
Battle pass (if any): free/premium tracks, XP pacing so completion is realistic
cosmetic category over time, starter pack/discount psychology without dark patterns, no…
Store/currencies: hard vs soft currency separation, earn paths for every
progression | content | social) marked acceptable/risky/unacceptable for our genre;…
Strategy: value-exchange inventory table (cosmetics | convenience |
Designs monetization that respects players while hitting revenue targets — with hard pay-to-win audit.
Monetization Design (Ethical F2P / Battle Pass / IAP)
test script (10 tasks, success criteria), localization text expansion space (+30%), and…
Prototyping: wireframe descriptions for the 5 most-used screens, usability
subtitle, colorblind palettes, remap, difficulty, autosave indicators), purchase…
Flows: join/invite/party, settings (complete settings tree incl. audio mixers,
memory consistency (same button does same thing), grid/list defaults, sort/…
Menus: information architecture of all screens, max depth target, muscle-
Switch/mobile; legibility at TV distance (min sizes/contrast), reticle/ interaction…
HUD layout: annotated safe-zone diagram per aspect ratio incl. 21:9 and
inventory/map), ranked by glance frequency; decide diegetic vs spatial vs screen-space…
Information hierarchy: what the player must know per state (exploration/combat/
Designs readable, diegetic-aware HUD and menu UX with console/mobile constraints.
Game UI/UX & HUD Design Brief
quit rate at door, and clear-time percentiles; plus a QA scenario checklist.…
Telemetry to verify: attempts distribution, death-cause codes per attack,
destruction, finisher moment; then post-fight reward and narrative beat.
Juice/spectacle: phase-transition presentation, music layers, arena
timing, puzzle slowdown) maintaining the same choreography so content isn't removed;…
Accessibility tiers: default / assist (damage taken, timing widows, parry
+ audio + optional weak indicators), no off-camera attacks (camera logic), recovery that…
Fairness: every attack readable via consistent multi-channel tells (animation
in a table (telegraph wind-up frames | attack | tracking | damage | safe punish window),…
Phase/state spec: phases with health %, arena changes, move list per phase
(which player verbs the dungeon taught), and the emotional signature.
Concept pillars: the single identity idea, the skill this boss EXAMINES
Designs a boss as a taught exam of player skills: phases, tells, and fair challenge — with accessibility tiers.
Enemy / Boss Design Spec
for translations, and a writer/tooling handoff format.…
Localization notes: line-length budget, string IDs, gender-neutral structure
low-intel states, romance/reputation gates, failure states (intimidation rolls) creating…
Edge cases: killing/incapacitating an NPC before scene, repeat visits,
Produces branching narrative structure that stays writable: conversation states, flags, and branching shape (not exponential bloat).