# Components

## 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

<figure><img src="/files/l3PcDmn4KTeKkpqvD6fG" alt=""><figcaption><p>ESave menu items</p></figcaption></figure>

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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://espergames.gitbook.io/esave/getting-started/components.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.