AppleyAppley Docs
Docs/Learning Paths

Saving Projects

Learn how Appley saves your work to the cloud.

14 min read Beginner Updated 2026-07-01 v2.0 ~38 min to complete

Introduction

Appley auto-saves your project to the cloud, but understanding the save system — including version history — ensures you never lose work.

Tutorial 6 of 18

This is part of the Beginner Learning Path. Estimated completion time: 38 minutes. Difficulty: Beginner.

Screenshot

Saving Projects
Saving Projects

Step-by-Step Guide

1

Manual save

Press Ctrl+S (or Cmd+S on Mac) to save your project immediately. A save icon briefly appears in the toolbar.

2

Enable auto-save

Go to Settings > Editor and ensure Auto-Save is enabled. It saves every 30 seconds by default.

3

View version history

Open the History panel to see all saved versions. Each version has a timestamp and optional description.

4

Create a checkpoint

Before major changes, click "Save Checkpoint" in the History panel and add a description. These are never auto-deleted.

5

Restore a version

Click any version in the History panel to preview it. Click "Restore" to roll back to that state.

6

Cloud sync

All saves sync to the cloud automatically. You can open your project on any device and continue where you left off.

FluxScript Example

Here is the FluxScript (Appley Scripting) code for this tutorial:

Saving Projects — FluxScript
// Save and load game state at runtime
on start {
  // Load saved player data
  highScore = save.get("highScore") || 0
  lastLevel = save.get("lastLevel") || 1
  
  print("Welcome back! Last level: " + lastLevel)
}

on event("levelComplete") {
  // Save progress
  save.set("lastLevel", currentLevel)
  if score > highScore {
    save.set("highScore", score)
  }
  save.flush()  // Force immediate save
}

Node Script Equivalent

Prefer visual programming? Here is the same logic as a Node Script graph:

Saving Projects — Node Graph
[On Start] ──► [Save.Get: "highScore"] ──► [Default: 0]
         ──► [Save.Get: "lastLevel"] ──► [Default: 1]
         ──► [Print: "Welcome back!"]

[On Event "levelComplete"] ──► [Save.Set: "lastLevel"]
   ──► [Branch: score > highScore] ──► [Save.Set: "highScore"]
   ──► [Save.Flush]

Pro Tip

Create a checkpoint before any major change (like deleting objects or rewriting scripts). If something breaks, you can instantly restore to the working state.

Watch Out

Don't rely solely on auto-save. Auto-save versions can be pruned to save storage. Always create a named checkpoint before significant changes.