Quick Start
Start with a tiny working version
Autosave feels trustworthy only when the player understands two things: when progress was safely recorded and where they will return after failure. If save timing is invisible, restart positions feel arbitrary, or players lose track of what they had just achieved, the system creates anxiety instead of relief.
Build it in small code pieces
1. 値を用意する
Inspectorで変更できる値と表示先を置きます。
csharp
[SerializeField] private TextMeshProUGUI statusText;
[SerializeField] private float saveSlotIndex = 1f;
[SerializeField] private float checkpointDistance = 2f;
[SerializeField] private float retryCount = 3f;2. 状態を変える
ボタンを押した時に、1つだけ状態を進めます。
csharp
public void NextStep()
{
step = (step + 1) % 3;
var label = step == 0 ? "保存地点を記録" : step == 1 ? "リトライを選ぶ" : "復旧警告を出す";
if (statusText != null)
{
statusText.text = $"{label}\nsaveSlotIndex={saveSlotIndex:0.##}\ncheckpointDistance={checkpointDistance:0.##}\nretryCount={retryCount:0.##}";
}3. 画面に表示する
変わった結果を画面に出して確認します。
csharp
if (statusText != null)
{
statusText.text = $"{label}\nsaveSlotIndex={saveSlotIndex:0.##}\ncheckpointDistance={checkpointDistance:0.##}\nretryCount={retryCount:0.##}";
}
Debug.Log($"セーブと復帰導線: {label}");Complete script
csharp
using UnityEngine;
using TMPro;
public class SaveRecoveryTutorial : MonoBehaviour
{
[SerializeField] private TextMeshProUGUI statusText;
[SerializeField] private float saveSlotIndex = 1f;
[SerializeField] private float checkpointDistance = 2f;
[SerializeField] private float retryCount = 3f;
private int step;
public void NextStep()
{
step = (step + 1) % 3;
var label = step == 0 ? "保存地点を記録" : step == 1 ? "リトライを選ぶ" : "復旧警告を出す";
if (statusText != null)
{
statusText.text = $"{label}\nsaveSlotIndex={saveSlotIndex:0.##}\ncheckpointDistance={checkpointDistance:0.##}\nretryCount={retryCount: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 beginner guide to save notifications, checkpoint placement, and making restarts easier to understand.
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.
Read next
ARTBrowse English articlesReturn to the English article index and choose the next topic by engine, tag, or workflow.CMPCompare game enginesCheck Unity, Unreal Engine, Godot, and Roblox from a beginner-friendly English comparison view.HOMEEnglish learning homeGo back to the English top page for tutorials, glossary entries, news, and learning routes.
Related guides
SYSSave slot and recovery warning UI design guideLearn how to reduce overwrite mistakes, clarify the newest save, and design safer recovery flows in your game's save screen.MAPCheckpoint and retry flow basics for beginner game projectsA practical guide to placing checkpoints, shortening retry time, and making failure easier to understand in a first game.