本文へスキップ
Boss Encounter Design

Boss phase transition and danger warning design guide

A practical guide to making boss phase changes readable so players understand what changed, where danger moved, and how to respond.

公開日: 2026-07-06#Boss Design#Phase Transition#Combat Feedback#Beginner

Quick Start

Start with a tiny working version

Boss fights often feel unfair not because the numbers are too high, but because the rule change is unclear. A new summon pattern begins, the arena becomes unsafe, the boss speeds up, or a second form appears, yet the player cannot tell what actually changed.

Build it in small code pieces

1. 値を用意する

Inspectorで変更できる値と表示先を置きます。

BossPhaseTutorial.cs
csharp
    [SerializeField] private TextMeshProUGUI statusText;
    [SerializeField] private float bossHpPercent = 1f;
    [SerializeField] private float phaseIndex = 2f;
    [SerializeField] private float warningSeconds = 3f;

2. 状態を変える

ボタンを押した時に、1つだけ状態を進めます。

BossPhaseTutorial.cs
csharp
    public void NextStep()
    {
        step = (step + 1) % 3;
        var label = step == 0 ? "通常攻撃" : step == 1 ? "移行予告" : "大技開始";
        if (statusText != null)
        {
            statusText.text = $"{label}\nbossHpPercent={bossHpPercent:0.##}\nphaseIndex={phaseIndex:0.##}\nwarningSeconds={warningSeconds:0.##}";
        }

3. 画面に表示する

変わった結果を画面に出して確認します。

BossPhaseTutorial.cs
csharp
        if (statusText != null)
        {
            statusText.text = $"{label}\nbossHpPercent={bossHpPercent:0.##}\nphaseIndex={phaseIndex:0.##}\nwarningSeconds={warningSeconds:0.##}";
        }
        Debug.Log($"ボスのフェーズ移行: {label}");

Complete script

BossPhaseTutorial.cs
csharp
using UnityEngine;
using TMPro;

public class BossPhaseTutorial : MonoBehaviour
{
    [SerializeField] private TextMeshProUGUI statusText;
    [SerializeField] private float bossHpPercent = 1f;
    [SerializeField] private float phaseIndex = 2f;
    [SerializeField] private float warningSeconds = 3f;

    private int step;

    public void NextStep()
    {
        step = (step + 1) % 3;
        var label = step == 0 ? "通常攻撃" : step == 1 ? "移行予告" : "大技開始";
        if (statusText != null)
        {
            statusText.text = $"{label}\nbossHpPercent={bossHpPercent:0.##}\nphaseIndex={phaseIndex:0.##}\nwarningSeconds={warningSeconds:0.##}";
        }
        Debug.Log($"ボスのフェーズ移行: {label}");
    }
}

Inspector

Connect the UI reference in the Inspector, then use the button to confirm each value changes.

Summary

What to take away

A practical guide to making boss phase changes readable so players understand what changed, where danger moved, and how to respond.

The page is designed to help you move from reading to a small practical decision. Use the checklist above before jumping into the next related article.

Related guides

SYSBoss Phase Transition Feedback Design GuideLearn how to communicate boss phase changes, danger spikes, and new combat rules clearly without making transitions feel unfair or confusing.MAPDamage Number Readability UI Design GuideA practical guide to showing normal hits, crits, damage-over-time ticks, and healing values without turning combat into visual noise.