ESave
ESave
ESave
  • ESave Documentation
  • Pro Comparison
  • 🕹️Getting Started
    • Installation
    • Example Scenes
    • Components
      • Save File Setup
      • Save Storage
  • 📽️Videos
    • Tutorial
  • 📄Scripting
    • Saving & Loading
      • Data Management
        • Saving
        • Loading
        • Deleting
        • Writing Changes
      • Custom Serializable Objects
      • Example Script
    • Runtime Save Creation
      • Creating a Save File
      • Infinite Saves
        • Infinite Save Scripting
    • Runtime Save Deletion
    • Understanding Background Save & Load
    • Using the Save Storage
  • 🛠️Support
    • Getting Help
  • 📚Changelogs
    • Latest Releases
  • ⭐Rate Me?
Powered by GitBook
On this page
  1. Scripting
  2. Saving & Loading
  3. Data Management

Writing Changes

Officially saving the data.

Saving, Loading, and Deleting, only edit the save data in memory. The changes aren't officially saved until the Save method is called.

saveFile.Save();

Why Is It Like This?

There are 2 reasons as to why the data management methods don't automatically call Save:

  1. The Save method writes data directly to a file on the user's system—a process that can be time-consuming, especially with large amounts of data. If Save was called automatically every time AddOrUpdateData or DeleteData was used, it would affect performance.

  2. You can give players control over when their data is officially saved—for example, by letting them manually save through a dedicated save menu. This approach allows AddOrUpdateData and DeleteData to be used frequently during gameplay to modify player data while reserving Save for moments when the data needs to be officially written into the save file.

PreviousDeletingNextCustom Serializable Objects

Last updated 5 days ago

📄