ESave
ESave
ESave
  • ESave Documentation
  • Pro Comparison
  • đŸ•šī¸Getting Started
    • Installation
    • Example Scenes
    • Components
      • Save File Setup
      • Save Storage
  • đŸ“Ŋī¸Videos
    • Tutorial
  • 📄Scripting
    • Saving & Loading
      • Saving
      • Loading
      • 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
  • File Structure
  • Create Menu Items
  1. Getting Started

Components

This section highlights the main ESave components you will be using.

PreviousExample ScenesNextSave File Setup

Last updated 11 months ago

File Structure

Save data is typically stored in separate files, with one for each save state and one for the player's settings. ESave is structured around this idea, which is why it's an important concept to remember.

Separating your saved data is recommended. Having all of the player's data in one file is possible and very common, but it's not a requirement. For example, you could have one save file that stores the player's inventory data, one for storing the player's progress, and another for the environmental impacts they made.

Create Menu Items

You can easily create ESave's Save File Setup and Save Storage components by right-clicking on the hierarchy and navigating to ESave.

đŸ•šī¸
ESave menu items