返回提示词目录第 1308 页

将游戏策划转为开发技术规格

把游戏设计整理为明确规则、数据结构和运行状态,补充存档、测试入口及待澄清问题。

完整提示词

<context>
Game design documents describe how a system should feel; programmers need exact rules, data and state. The gap causes the classic problems: numbers hard-coded so designers cannot tune without a programmer, ambiguous rules ("crits stack") implemented one way and designed another, edge cases discovered in playtests (what if the player levels up twice in one frame, sells an equipped item, or loads an old save), and no way to test the system without playing for an hour. The engine context is {{engine}}.
</context>

<task>
<design_section>
{{design_section}}
</design_section>

1. Summarise the system in three to five sentences, and list the other systems it touches (inventory, UI, save, audio, networking, analytics).
2. Restate every rule as precise logic: triggers, conditions, order of evaluation, formulas with variable names and units, rounding, caps and floors, random rolls with their distribution and seeding. Where the design is ambiguous, write the interpretations side by side and raise a question instead of choosing silently.
3. Data definitions: the static content types designers author (items, levels, curves, tables) with each field, type, range and default, and where they live in the engine's data pipeline. Prefer data-driven definitions over code constants.
4. Runtime state: what changes during play, who owns it, when it changes, and whether it is replicated in multiplayer.
5. Tunables: every number designers will want to change, with a sensible initial value from the design, a safe range, and whether it can change at runtime (hot reload or debug menu).
6. Edge cases: simultaneous events in one frame, interruptions (pause, death, scene change, disconnect), overflow and extreme values, stacking and order dependence, exploits (duplication, infinite loops of rewards), and localisation of any generated text.
7. Save and versioning: what is persisted, the format, how saves from earlier versions are migrated when fields or balance change, and what must never be persisted (derived values).
8. Test hooks: debug commands or cheats to reach each state quickly, deterministic seeds, automated tests for formulas and edge cases, and telemetry events designers need to balance the system.
9. Questions for design: every ambiguity and missing number, phrased so the designer can answer quickly.
</task>

<constraints>
- Use only rules and numbers from the design. Write [X] for a missing value and add a question; do not balance the game yourself.
- Keep engine-specific advice correct for the stated engine; if the engine is not stated, stay engine-neutral.
- Write formulas in plain notation with named variables, and show one worked example with numbers from the design.
- Flag any monetisation or randomised reward mechanic that may face store rules or regional regulation (for example paid loot boxes) as something to check, without stating the law.
</constraints>

<output_format>
## Summary
Paragraph and a list of touched systems.
## Rules as logic
Numbered rules, formulas in code blocks, one worked example.
## Data definitions
Table per content type: field, type, range, default, notes.
## Runtime state
Table: state, owner, changes when, persisted, replicated.
## Tunables
Table: name, initial value, safe range, runtime-editable.
## Edge cases
Table: case, expected behaviour, source (design or proposed).
## Save and versioning
Bullets.
## Test hooks
Bullets: debug commands, tests, telemetry events.
## Questions for design
Numbered.
</output_format>

可替换内容

  • {{engine}}
  • {{design_section}}
  • [X]

分类与标签

编程开发、游戏开发、技术规格、数据结构、存档设计、测试设计

前往 AI 图片创作