返回提示词目录第 1416 页

游戏首领战机制与关卡设计

围绕玩家已有技能规划战斗场地、阶段和攻击预警,输出重试机制、调参表与试玩观察项。

完整提示词

<context>
You design boss fights. A boss is an exam on skills the game has already taught, so it should test one or two of them hard rather than introduce new ones without warning. Every dangerous attack needs a readable tell (animation wind-up, sound, a ground marker) that works without colour alone, and a matching opening the player can punish. Phases raise the stakes by remixing known attacks, not by doubling health. Players accept losing when they can see why; they quit when the retry is slow or the death felt random.

Game: {{game}}
Boss: {{boss_idea}}
</context>

<task>
1. Name the skills the fight tests, drawn from the player's moveset at this point, and the feeling it should leave (triumph, dread, spectacle).
2. Design the arena: size, cover, hazards, and how it changes between phases. Explain how it supports the tested skills.
3. Design two or three phases: trigger (health threshold or event), what changes, and the beat that tells the player a new phase started.
4. Write the attack list: name, tell (visual and audio, with timing in frames or seconds), what the player should do, damage, and the opening it leaves. Include at least one attack that punishes the player's most likely bad habit.
5. Design retry and fairness: checkpoint, time from death to retry, skippable intro, what stays learned, and any optional help (summons, assist settings).
6. Give a tuning sheet: boss health per phase, attack cooldowns, tell durations, damage, the target fight length and the expected number of attempts for the intended audience; mark all values as starting points to tune in playtests.
7. List what to watch in playtests: deaths per attack, attacks players never learn to read, cheese strategies.
</task>

<constraints>
- Use only skills the player has at this point; flag any new skill the fight would need and how to teach it earlier.
- Every damaging attack has a tell that does not rely on colour or sound alone.
- No unavoidable damage unless it is clearly a scripted moment with no penalty.
- Mark numbers as starting values, not tested values.
</constraints>

<output_format>
## What the fight tests
## Arena
## Phases
Table: Phase | Trigger | What changes | Signal.
## Attack list
Table: Attack | Tell | Player answer | Damage | Opening.
## Retry and fairness
## Tuning sheet
Table: Value | Starting number | Why. Then playtest watch list.
</output_format>

可替换内容

  • {{game}}
  • {{boss_idea}}

分类与标签

设计创意、游戏策划、首领战设计、战斗机制、难度调优、试玩测试

前往 AI 图片创作