Unreal Checkpoint, PlayerStart, Spawn, and Restart Guide

Direct answer

Represent a checkpoint with a stable identifier and validated spawn transform, not a raw actor pointer saved across sessions. GameMode owns restart rules, PlayerStart or checkpoint actors provide candidate transforms, PlayerState or SaveGame carries the selected identifier, and the newly spawned pawn receives restored gameplay data only after possession. Separate same-session restart from persistent load and define a fallback when the checkpoint no longer exists.

This page focuses spawn selection and restart recovery rather than general SaveGame schema design, combat death, level streaming, or project reset. The practical goal is a game-building slice that another developer can reproduce from a clean checkout. Keep engine behavior, project policy, and measured evidence separate: Epic documentation establishes supported concepts, the project defines ownership and budgets, and only a named test run proves the local result.

What this guide delivers

• A concrete ownership model for unreal checkpoint playerstart spawn restart.
• A six-stage Blueprint/C++ implementation workflow with a real API or command example.
• Three production scenarios, including normal, edge, and handoff behavior.
• Failure recovery and validation criteria for editor and packaged builds.
• A bounded SEELE handoff that leads to the Unreal creator without changing this page's technical intent.

System architecture and ownership

Checkpoint identity

Give each checkpoint a stable name, GUID, or Primary Asset-backed identifier that survives actor recreation. Save the identifier, map, version, and minimal progress data; never serialize the live world pointer.

Checkpoint identity review: capture stable ID uniqueness and map ownership and show how activation record receives or observes the accepted result without becoming a second owner.

Activation record

The authoritative rules layer validates that the pawn reached the checkpoint, then updates transient player state and optionally queues a SaveGame write. Presentation can show an effect only after acceptance.

Activation record review: capture activation authority and repeated-overlap suppression and show how spawn selection receives or observes the accepted result without becoming a second owner.

Spawn selection

Choose tagged PlayerStarts or checkpoint transforms with collision, team, game phase, and map validity checks. Return an explicit fallback rather than allowing a null start to become a random origin spawn.

Spawn selection review: capture candidate transform clearance and show how restore sequence receives or observes the accepted result without becoming a second owner.

Restore sequence

Load progress, resolve the checkpoint, spawn the pawn, possess it, initialize inventory or health, then release input. The order prevents BeginPlay consumers from reading half-restored state.

Restore sequence review: capture spawn, possession, and restore order and show how checkpoint identity receives or observes the accepted result without becoming a second owner.

Implementation workflow

1. Stage 1: Create a checkpoint actor or component with stable ID, optional PlayerStart tag, spawn transform, activation rules, and editor-time duplicate-ID validation.
2. Stage 2: When activated, ask the authoritative checkpoint manager to compare progression order and commit the selected ID once. Ignore repeated overlap noise.
3. Stage 3: Store transient selected ID in PlayerState or GameInstance according to travel needs, and persist the versioned ID plus map in SaveGame when cross-session progress is required.
4. Stage 4: Override or extend GameMode spawn selection and RestartPlayer behavior so the chosen checkpoint is resolved before pawn creation.
5. Stage 5: Validate the transform with capsule clearance and navigation or game-specific constraints. Try an ordered fallback list: checkpoint, tagged PlayerStart, default PlayerStart, then a controlled failure screen.
6. Stage 6: Test restart before activation, duplicated IDs, deleted checkpoints, renamed maps, occupied starts, streaming delay, corrupt save, multiplayer teams, and repeated death during a pending restart.

Concrete API or command example

AActor* ARunGameMode::ChoosePlayerStart_Implementation(AController* Player)
{
    const FName CheckpointId = ResolveCheckpointId(Player);
    if (AActor* Start = FindValidatedCheckpointStart(CheckpointId, Player)) return Start;
    UE_LOG(LogGameMode, Warning, TEXT("Checkpoint %s unavailable; using default start"), *CheckpointId.ToString());
    return Super::ChoosePlayerStart_Implementation(Player);
}

Three production scenarios

Example 1: Same-level death restart

PlayerState remembers CP_Foundry_02, GameMode validates its spawn capsule, destroys the dead pawn, spawns a replacement, possesses it, and restores rule-approved health or inventory.

Evidence for same-level death restart should include stable ID uniqueness and map ownership, the owning build identity, and the condition that returns this scenario to its last known-good state.

Example 2: Cross-session continue

SaveGame stores schema version, map asset path, checkpoint ID, and progression facts. On load, a migration resolves retired identifiers before opening the map and spawning.

Evidence for cross-session continue should include activation authority and repeated-overlap suppression, the owning build identity, and the condition that returns this scenario to its last known-good state.

Example 3: Co-op team start

Each checkpoint exposes team tags and multiple slots. Spawn selection avoids occupied capsules and chooses the nearest valid slot without changing the shared progression record.

Evidence for co-op team start should include candidate transform clearance, the owning build identity, and the condition that returns this scenario to its last known-good state.

Failure modes and recovery

Checkpoint actor pointer is invalid after load

Persist a stable identifier and resolve it in the loaded world. Actor memory addresses and transient object paths are not durable save identities.

Before closing checkpoint actor pointer is invalid after load, rerun same-level death restart and prove candidate transform clearance returns to the expected boundary without an undocumented repair step.

Restart returns to map origin

Log selected ID, candidate lookup, collision result, and Super fallback. Missing or invalid PlayerStarts must be visible, not silently accepted.

Before closing restart returns to map origin, rerun cross-session continue and prove spawn, possession, and restore order returns to the expected boundary without an undocumented repair step.

Inventory restores before pawn is ready

Define a restore phase after possession and component initialization, then notify UI when the transaction completes. Avoid arbitrary delays.

Before closing inventory restores before pawn is ready, rerun co-op team start and prove save migration and fallback selection returns to the expected boundary without an undocumented repair step.

Old saves reference removed content

Version the save, maintain redirect or migration data, and select a safe fallback checkpoint with a user-visible recovery path.

Before closing old saves reference removed content, rerun same-level death restart and prove stable ID uniqueness and map ownership returns to the expected boundary without an undocumented repair step.

Validation matrix

• stable ID uniqueness and map ownership: inspect it beside checkpoint identity; pass only when checkpoint actor pointer is invalid after load does not recur during same-level death restart and the evidence names the exact build.
• activation authority and repeated-overlap suppression: inspect it beside activation record; pass only when restart returns to map origin does not recur during cross-session continue and the evidence names the exact build.
• candidate transform clearance: inspect it beside spawn selection; pass only when inventory restores before pawn is ready does not recur during co-op team start and the evidence names the exact build.
• spawn, possession, and restore order: inspect it beside restore sequence; pass only when old saves reference removed content does not recur during same-level death restart and the evidence names the exact build.
• save migration and fallback selection: inspect it beside checkpoint identity; pass only when checkpoint actor pointer is invalid after load does not recur during cross-session continue and the evidence names the exact build.

Version and source boundaries

These steps target the current Unreal Engine 5 documentation surface as of 2026-07-26. Engine defaults, experimental status, plugin packaging, API signatures, and platform support can change. Select the documentation version that matches the project, test the exact patch and target, and retain a rollback revision. Public documentation does not replace NDA platform requirements, store review, console certification, or project-specific performance evidence.

Official sources

• Player Start Actor — source evidence for checkpoint identity in this unreal checkpoint playerstart spawn restart workflow; verify the documentation version against the shipping branch.
• Saving and Loading Your Game — source evidence for activation record in this unreal checkpoint playerstart spawn restart workflow; verify the documentation version against the shipping branch.
• Game Mode and Game State — source evidence for spawn selection in this unreal checkpoint playerstart spawn restart workflow; verify the documentation version against the shipping branch.

Unreal Engine is a trademark of Epic Games. SEELE AI is independent and this article does not imply Epic Games or Valve endorsement.

From the technical plan to a SEELE Unreal game

Use this page to define the system, acceptance tests, and failure boundaries; then carry that precise brief into [SEELE's Unreal game creator](/features/create/unreal-game). SEELE can generate a native Unreal 5 project, provide an in-browser preview, support optimization and packaging in SEELE, and let you download the project or packaged output for external publishing or publish it as a free or paid SEELE game.

That handoff does not change the native production responsibility described above. Store approval, sales, revenue, certification, third-party plugin compatibility, and platform compliance are not guaranteed. Keep the source Unreal project, build logs, test evidence, and external publishing decisions under your team's control.

FAQ

What is the correct architecture for unreal checkpoint playerstart spawn restart?

Represent a checkpoint with a stable identifier and validated spawn transform, not a raw actor pointer saved across sessions. GameMode owns restart rules, PlayerStart or checkpoint actors provide candidate transforms, PlayerState or SaveGame carries the selected identifier, and the newly spawned pawn receives restored gameplay data only after possession. Separate same-session restart from persistent load and define a fallback when the checkpoint no longer exists. Start with checkpoint identity and activation record, then keep presentation as an observer of committed gameplay state.

Should unreal checkpoint playerstart spawn restart be built in Blueprint or C++?

Either can work. Blueprint is effective for rapid game logic and designer iteration; C++ is useful for reusable contracts, complex lifetime, performance-sensitive loops, and automated tests. Preserve the same owner, validation, failure, and recovery boundaries in both.

How should unreal checkpoint playerstart spawn restart be tested?

Test one normal case, one invalid input, interruption or teardown, clean restart, and packaged-build parity. Capture stable ID uniqueness and map ownership, activation authority and repeated-overlap suppression, candidate transform clearance with a build identifier and explicit pass criteria.

What is the most dangerous failure in unreal checkpoint playerstart spawn restart?

Checkpoint actor pointer is invalid after load is an early warning: Persist a stable identifier and resolve it in the loaded world. Actor memory addresses and transient object paths are not durable save identities. Also verify cleanup and retry so the apparent fix does not leave stale state.

Which Unreal version does this unreal checkpoint playerstart spawn restart guide target?

It uses the Unreal Engine 5 documentation surface available on 2026-07-26. Confirm the version selector, API signature, plugin status, platform toolchain, and packaged behavior in the exact engine patch that will ship.

What can SEELE do after this unreal checkpoint playerstart spawn restart plan is ready?

SEELE can generate a native Unreal 5 project, provide browser preview, support optimization and packaging, and provide project or packaged downloads for external publishing or a free or paid SEELE release. It does not guarantee third-party store approval, compatibility, sales, or revenue.