Continue Your Game

Continue Component

The Continue Component controls what happens when the player presses Continue in your main menu.

Its job is simple:

  • Find the best playable profile

  • Select it

  • Load the correct gameplay scene

  • Restore the game state automatically

No manual scene wiring is required.


What does “Continue” mean in Hyper Save Engine?

Continue is profile-based.

The engine does not “continue a file”. It continues the last valid playthrough.

That means it will:

  • Prefer the last selected profile (if it is playable)

  • Otherwise pick the best available profile for continuing


What it does automatically

When the Continue button is pressed, the component will:

  1. Check if Continue is available

  2. Select the correct profile

  3. Resolve the last playable scene (not menus)

  4. Load that scene

  5. Restore state from the selected profile


Typical setup (UI)

Step 1 — Add the component

Add ContinueButtonHandler to your menu object.

Step 2 — Assign your button

Assign your Continue Button in the Inspector.

Step 3 — Optional visibility behavior

You can choose how the button behaves if no playable profile exists:

  • Hide the Continue button (recommended for main menus)

  • Or keep it visible but disable it

(This is controlled by visibilityRoot and hideIfUnavailable.)


Scene safety rules (important)

Continue should never load:

  • Menu scenes

  • Settings scenes

  • Transitional scenes

  • The current active scene (to avoid looping)

The component includes an Ignore Scenes list so Continue always resolves to a playable gameplay scene.

This is why your Continue flow is stable even in complex projects.


Which scene does it load?

The component looks up the last scene using multiple sources (in priority order), such as:

  • The last saved scene stored by the save system

  • Profile metadata (lastSceneName)

  • A safe fallback if needed

Then it validates the scene against Build Settings before loading.

If the scene is not valid, Continue becomes unavailable.


Optional: Cloud-aware Continue (Steam Cloud)

If cloud saving is enabled, the component can:

  • Pump the cloud sync queue on demand

  • Refresh availability shortly after Steam initializes

This helps ensure the Continue button reflects the latest cloud state.

(If you do not use cloud saving, you can disable this behavior.)


Key takeaway

Continue is not “load file”. Continue is:

Select best profile → resolve last playable scene → load → restore state.

Once your project is profile-driven, Continue becomes reliable by default.

Last updated

Was this helpful?